Positioning in o-ran environment

Abstract

Aspects presented herein relate to methods and apparatus, including apparatuses, such as network entities, for wireless communication. The apparatus may obtain a configuration of a control plane including a set of time offsets. The apparatus may also compute a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets. The apparatus may also receive at least one reference signal (RS) during the corresponding FFT window of each time offset of the set of time offsets.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Greek patent application serial number 20220100917, filed on November 9, 2022, entitled “POSITIONING IN O-RAN ENVIRONMENTS”, which is expressly incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates generally to communication systems, and more particularly, to positioning measurements in wireless communication systems. Background Art

[0004] Wireless communication systems are widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcast. 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 telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. An example telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third 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. 5GNR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0006] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary neither identifies the key or important 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 a more detailed description presented later.

[0007] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus for wireless communication at a network entity, such as a radio unit (RU) or a distributed unit (DU) in a radio access network (RAN). The apparatus may obtain a configuration of a control plane including a set of time offsets. The apparatus may also select a set of subpanels or a set of transmit-receive (Tx-Rx) streams for at least one reference signal (RS) based on the configuration of the control plane. The apparatus may also apply each time offset in the set of time offsets to a corresponding fast Fourier transform (FFT) window. In addition, the apparatus may determine a starting point of the corresponding FFT window based on each applied time offset. The apparatus may also calculate a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets. The apparatus may also receive at least one reference signal (RS) during a corresponding FFT window for each time offset in the set of time offsets. Moreover, the apparatus may process at least one RS after a corresponding FFT window for each time offset in the set of time offsets. The apparatus may also send at least one RS based on processing of at least one RS after a corresponding FFT window.

[0008] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be an apparatus for wireless communication at a network entity, such as a radio unit (RU) or a distributed unit (DU) in a radio access network (RAN). The apparatus may configure a control plane including a set of time offsets. The apparatus may also send a configuration of a control plane including the set of time offsets, wherein each time offset in the set of time offsets is associated with a corresponding fast Fourier transform (FFT) window. The apparatus may also receive at least one reference signal (RS) after the corresponding FFT window of each time offset in the set of time offsets. In addition, the apparatus may process at least one RS based on the reception of at least one RS after the corresponding FFT window of each time offset in the set of time offsets.

[0009] To achieve the aforementioned and related purposes, one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail some exemplary features of one or more aspects. However, these features indicate only some of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0011] Figure 2A is a diagram illustrating an example of a first frame according to various aspects of the present disclosure.

[0012] Figure 2B is a diagram illustrating an example of downlink (DL) channels within a subframe according to various aspects of the present disclosure.

[0013] Figure 2C is a diagram illustrating an example of a second frame according to various aspects of the present disclosure.

[0014] Figure 2D is a diagram illustrating an example of uplink (UL) channels within a subframe according to various aspects of the present disclosure.

[0015] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.

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

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

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

[0019] Figure 7 is a diagram illustrating an example open radio access network (O-RAN) structure.

[0020] Figure 8 is a diagram illustrating an example timing structure.

[0021] Fig. 9 is a diagram illustrating an example timing scheme.

[0022] Fig.10 is a diagram illustrating an example timing extension of a message.

[0023] Fig.11 is a communication flow diagram illustrating example communications between network entities and network entities.

[0024] Fig.12 is a flow chart of a wireless communication method.

[0025] Fig.13 is a flow chart of a wireless communication method.

[0026] Fig.14 is a flow chart of a wireless communication method.

[0027] Fig.15 is a flow chart of a wireless communication method.

[0028] Fig.16 is a diagram illustrating an example of a hardware implementation of an example network entity.

[0029] Fig.17 is a diagram illustrating an example of a hardware implementation of an example network entity. DETAILED DESCRIPTION

[0030] Some aspects of wireless communication may utilize a radio access network (RAN) as part of a mobile telecommunication system. The RAN may implement a radio access technology for a telecommunication system. In addition, the RAN may provide resource access rights to various radio sites in the telecommunication system and coordinate the management of these resources. Some aspects of wireless communication may utilize the functionality of locating a location. There may be multiple different positioning features enabled on the UE side and the network side. For example, the positioning features enabled on the network side may include at least one of the following features: uplink (UL) time difference of arrival (UL-TDOA), UL angle of arrival (UL-AoA), or round trip time (RTT). These features may be based on UL reference signal reception (e.g., sounding reference signal (SRS)). These positioning features may also be enabled for layer 1 (L1) / layer 2 (L2) mobility. In addition, there may be multiple sensing features supported by the network side. Uplink frequency domain (FD) samples of a sounding reference signal (SRS) may be transmitted based on the following configurations: fast Fourier transform (FFT) size, cyclic prefix (CP) length, subcarrier spacing (SCS), and / or time offset (e.g., if a segment type 3 message is used, the earliest in-phase and quadrature (IQ) time division (TD) sample may be indicated by a symbol identifier (ID)). In some aspects, certain features (e.g., UL TDoA, UL AoA, and / or RTT) may be based on SRS FD IQ samples. For example, in UL TDoA, for each SRS pilot, a network entity may calculate a time offset based on an SRS channel estimate (e.g., by calculating a channel impulse response and detecting the strongest time offset associated with the strongest path or the first path). Moreover, UL TDoA may utilize a certain number of observations (e.g., M observations) of SRS FD IQ samples to be provided for each SRS symbol and each reception point. Each observation may be associated with a different time offset (timeOffset). In some cases, the control user synchronization (CUS) specification may not support a control plane (C-plane) message with a certain number of time offset (timeOffset) parameters (e.g., M timeOffset parameters). In order to support UL TDoA at a network entity with some CUS specifications, M C-plane messages that incur fronthaul (FH) overhead may be utilized. Therefore, it may be beneficial to include a solution that does not incur C-plane overhead. In some aspects, similar to UL TDoA, some types of positioning features (e.g., UL AoA, RTT) may be based on SRS FD IQ samples. Moreover, these types of positioning features (e.g., UL AoA, RTT) may utilize a certain amount of observations (e.g., M observations) of SRS for neighboring cells and non-serving transmit reception points (TRPs).For example, an SRS observation may involve SRS IQ samples to be delivered from a radio unit (RU) to a distributed unit (DU) at a given FFT size, timeOffset, SCS, and / or CP length. Moreover, in some aspects, when a UE moves from a source cell (e.g., adjusting the timing at the UE relative to the source cell) to a target cell within a set of cells configured for L1 / L2 mobility, the timing at the target cell may need to be adjusted, and when the UE begins to communicate data with the target cell, different time offsets may be used to enhance the timing adjustment. Therefore, a certain amount of observations (e.g., M observations) may be used for UL reference signals and / or SRS. Moreover, the sensing feature may need to have different observations to achieve accurate sensing. However, the CUS specification may not support C-plane messages with M time offset parameters. In order to support UL positioning features for DU, L1 / L2 mobility and sensing, a certain number of C-plane messages (e.g., M C-plane messages) may be used. However, these C-plane messages may cause forward transmission (FH) overhead. Various aspects of the present disclosure may implement UL positioning features without incurring certain overheads (e.g., FH overhead). For example, various aspects presented herein may utilize a certain number of C-plane messages (e.g., M C-plane messages). In some cases, this number of C-plane messages may support UL positioning features without adding certain overhead (e.g., FH overhead). That is, various aspects presented herein may support UL positioning features in a network environment without adding overhead, such as L1 / L2 mobility features and / or sensing features. In addition, various aspects presented herein may allow C-plane messages to be sent and / or received between certain network entities (e.g., RUs and / or DUs). Moreover, various aspects presented herein may support control plane messages including adjustments or extensions to message structures (e.g., segment extensions associated with time offset structures).

[0031] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations in which the concepts described herein can be practiced. In order to provide a thorough understanding of the various concepts, the specific embodiments include specific details. However, these concepts can be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid blurring such concepts.

[0032] Several aspects of telecommunication systems are presented with reference to various apparatus and methods. These apparatus and methods are described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0033] As an example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system", which includes 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, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gating logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0034] Thus, 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 codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available media that can be accessed by a computer. As an example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, 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 that can be accessed by a computer.

[0035] Although various aspects, specific implementations and / or use cases are described in this application by the illustration of some examples, additional or different aspects, specific implementations and use cases may be generated in many different arrangements and scenarios. The various aspects, specific implementations and / or use cases described herein can be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, various aspects, specific implementations and / or use cases can be generated via integrated chip specific implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication equipment, computing equipment, industrial equipment, retail / purchase equipment, medical equipment, artificial intelligence (AI) enabled devices, etc.). Although some examples may or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some actual settings, the equipment combined with the various aspects and features described 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 include 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 of various sizes, shapes, and configurations, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc.

[0036] The deployment of a communication system such as a 5G NR system can be arranged in a variety of ways with various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or network equipment (such as a base station (BS)) or one or more units (or one or more components) performing base station functions can be implemented in an aggregated or decomposed architecture. For example, a BS (such as a Node B (NB), an evolved NB (eNB), an NR BS, a 5G NB, an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also referred to as an independent BS or a monolithic BS) or a decomposed base station.

[0037] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between 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 aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0038] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing functions across two or more units at various physical locations, as well as virtually distributing the functions of at least one unit, which may enable flexibility in network design. Various units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.

[0039] Figure 1 1 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated 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. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

[0040] Each of the units (i.e., CU 110, DU 130, RU 140, and near-RT RIC 125, non-RT RIC 115, and SMO framework 105) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively, signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interfaces of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive signals or send signals to one or more of the other units via a wired transmission medium. Additionally, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive and / or send signals to one or more of the other units via a wireless transmission medium.

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

[0042] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium 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.) at least in part according to a functional split 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 that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0043] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RU 140 controlled by the 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, etc.), or both, based at least in part on functional splitting (such as lower layer functional splitting). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some specific implementations, the real-time and non-real-time aspects of communicating with the control plane and user plane of the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0044] The SMO framework 105 may be configured to support RAN deployment and configuration of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 105 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 105 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 190) to perform network element lifecycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 111) via the O1 interface. In addition, in some specific implementations, the SMO framework 105 may communicate directly with one or more RUs 140 via the O1 interface. The SMO framework 105 may also include a non-RT RIC 115 configured to support the functionality of the SMO framework 105 .

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

[0046] In some implementations, in order to generate an AI / ML model 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. Such information may be utilized by the near-RT RIC 125 and may be received from a non-network data source or from a network function 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 of performance and employ AI / ML models to perform corrective actions through the SMO framework 105 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0047] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102 or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services 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) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmit diversity. The communication link may be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. These carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​compared to UL). Component carriers may include a primary component carrier and one or more secondary component carriers. The primary component carrier may be referred to as a primary cell (PCell) and the secondary component carrier may be referred to as a secondary cell (SCell).

[0048] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use DL / UL wireless wide area network (WWAN) spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). The D2D communication may be through a variety of wireless D2D communication systems, such as, for example, Bluetooth, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.

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

[0050] The electromagnetic spectrum is typically subdivided into various categories, bands, channels, etc. based on frequency / wavelength. In 5G NR, two initial operating bands have been identified as frequency range designations FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with reference to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz-300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

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

[0052] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used herein, it may broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used herein, it may broadly refer to frequencies that may include mid-band frequencies, may be within FR2, FR4, FR2-2, and / or FR5, or may be within the EHF band.

[0053] The base station 102 and the UE 104 may each include multiple antennas (such as antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. The base station 102 may send a beamformed signal 182 to the UE 104 in one or more transmit directions. The UE 104 may receive the beamformed signal from the base station 102 in one or more receive directions. The UE 104 may also send a beamformed signal 184 to the base station 102 in one or more transmit directions. The base station 102 may receive the beamformed signal from the UE 104 in one or more receive directions. The base station 102 / UE 104 may perform beam training to determine the best receive direction and transmit direction for each of the base station 102 / UE 104. The transmit direction and receive direction of the base station 102 may be the same or may not be the same. The transmit direction and receive direction of the UE 104 may be the same or may not be the same.

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

[0055] The core network 120 may include an access and mobility management function (AMF) 161, a session management function (SMF) 162, a user plane function (UPF) 163, a unified data management (UDM) 164, one or more location servers 168, and other functional entities. AMF 161 is a 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 the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, position determination entity (PDE), serving mobile location center (SMLC), mobile positioning 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 positioning information. LMF 166 receives measurement and assistance information from NG-RAN and UE 104 via AMF 161 to calculate the location of UE 104. NG-RAN may determine the location of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, positioning estimates, and speed calculations based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / positioning systems), LTE signals, wireless local area network (WLAN) signals, Bluetooth signals, a terrestrial beacon system (TBS), sensor-based information (e.g., an atmospheric pressure sensor, a motion sensor), an NR enhanced cell ID (NR E-CID) method, NR signals (e.g., multi-round trip time (multi-RTT), DL angle of departure (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 one or more of other systems / signals / sensors.

[0056] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network together and / or individually. In some scenarios, the term UE may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network together and / or individually. The network node can be implemented as a base station (i.e., an aggregated base station), a decomposed base station, an integrated access and backhaul (IAB) node, a relay node, a side link node, etc. The network entity can be implemented as a base station (i.e., an aggregated base station), or alternatively, as a central unit (CU), a distributed unit (DU), a radio unit (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC in a decomposed base station architecture.

[0057] See again Figure 1In certain aspects, the base station 102, the core network 120, the DU 130, or the RU 140 may include an offset component 198, which may be configured to obtain a configuration of a control plane including a set of time offsets. The offset component 198 may also be configured to select a set of subpanels or a set of transmit-receive (Tx-Rx) streams for at least one reference signal (RS) based on the configuration of the control plane. The offset component 198 may also be configured to apply each time offset in the set of time offsets to a corresponding fast Fourier transform (FFT) window. The offset component 198 may also be configured to determine a starting point of a corresponding FFT window based on each applied time offset. The offset component 198 may also be configured to calculate a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets. The offset component 198 may also be configured to receive at least one reference signal (RS) during a corresponding FFT window for each time offset in the set of time offsets. The offset component 198 may also be configured to process at least one RS after a corresponding FFT window for each time offset in the set of time offsets. The offset component 198 may also be configured to transmit the at least one RS based on processing the at least one RS after a corresponding FFT window.

[0058] In certain aspects, the base station 102, the core network 120, the DU 130, or the RU 140 may include an offset component 199 that may be configured to configure a control plane including a set of time offsets. The offset component 199 may also be configured to send a configuration of a control plane including the set of time offsets, wherein each time offset in the set of time offsets is associated with a corresponding fast Fourier transform (FFT) window. The offset component 199 may also be configured to receive at least one reference signal (RS) after the corresponding FFT window of each time offset in the set of time offsets. The offset component 199 may also be configured to process at least one RS based on the reception of at least one RS after the corresponding FFT window of each time offset in the set of time offsets. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

[0059] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, 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 may be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and full UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The UE is configured with the slot format through the received slot format indicator (SFI) (dynamically configured through DL control information (DCI) or semi-statically / statically configured through radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.

[0060] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 equally sized subframes (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, 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 a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0061]

[0062] For normal CP (14 symbols / slot), different parameter sets μ0 to 4 allow 1, 2, 4, 8, and 16 slots per subframe, respectively. For extended CP, parameter set 2 allows 4 slots per subframe. Thus, for normal CP and parameter set μ, there are 14 symbols / slot and 2 μ timeslots / subframe. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is parameter set 0 to 4. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

[0063] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a number of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

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

[0065] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein 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. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity 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 referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent over the PBCH (such as the system information block (SIB)), and paging messages.

[0066] like Figure 2C As illustrated, some of the REs carry DM-RS (indicated as R for a particular configuration, but other DM-RS configurations are possible) for channel estimation at the base station. The UE may send a DM-RS for a physical uplink control channel (PUCCH) and a DM-RS for a physical uplink shared channel (PUSCH). The PUSCH DM-RS may be sent in the first or first two symbols of the PUSCH. Depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the comb structures in the comb structure. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

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

[0068] Figure 3 375. The Controller / Processor 375 is a block diagram of a base station 310 in an access network communicating with a UE 350. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of 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 delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation 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 through HARQ, priority handling, and logical channel prioritization.

[0069] The 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) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles 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 coded and modulated symbols may then be separated into parallel streams. Each stream may then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and / or frequency domain, and then combined together using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier for transmission using a corresponding spatial stream.

[0070] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the 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 the UE 350. If multiple spatial streams are destined for the UE 350, they can be combined into a single OFDM symbol stream by the RX processor 356. The RX processor 356 then converts the OFDM symbol stream from the time domain to the frequency domain using a fast Fourier transform (FFT). The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier and the reference signal are recovered and demodulated by determining the most likely signal constellation point sent by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. The soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.

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

[0072] Similar to the functionality described in conjunction with DL transmissions performed by the base station 310, the controller / processor 359 provides RRC layer functionality associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functionality associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functionality associated with delivery of upper layer PDUs, error correction through 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 through HARQ, priority handling, and logical channel prioritization.

[0073] Channel estimates derived by the channel estimator 358 based on a reference signal or feedback sent by the base station 310 may be used by the TX processor 368 to select the appropriate coding and modulation schemes and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via separate transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.

[0074] UL transmissions are processed at the base station 310 in a manner similar to that described in conjunction with the receiver functionality at the UE 350. Each receiver 318Rx receives a signal through its respective antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.

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

[0076] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The offset component 198 performs various aspects. At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The offset component 199 performs various aspects.

[0077] Figure 4 4 is a diagram illustrating an example of UE positioning based on reference signal measurement. UE 404 may be at time T SRS_TX UL-SRS 412 is sent and at time T PRS_RX A DL positioning reference signal (PRS) (DL-PRS) 410 is received. TRP 406 may be at time T SRS_RX Receive UL-SRS 412 and at time T PRS_TX 410. UE 404 may receive DL-PRS 410 before transmitting UL-SRS 412, or may transmit UL-SRS 412 before receiving DL-PRS 410. In both cases, a positioning server (e.g., location server 168) or UE 404 may determine the UL-SRS 412 based on ||T SRS_RX -T PRS_TX |-|T SRS_TX -T PRS_RX || to determine RTT 414. Thus, multi-RTT positioning may utilize UE ERx-Tx time difference measurements (i.e., |T 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 (ie, |T SRS_RX -T PRS_TX |) and UL-SRS-RSRP. UE 404 measures UE Rx-Tx time difference measurement (and DL-PRS-RSRP of received signals) using assistance data received from the positioning server, and TRP 402, 406 measures gNB Rx-Tx time difference measurement (and UL-SRS-RSRP of received signals) using assistance data received from the positioning server. These measurements may be used at the positioning server or UE 404 to determine RTT, which is used to estimate the position of UE 404. Other methods for determining RTT are possible, such as, for example, using DL-TDOA and / or UL-TDOA measurements.

[0078] DL-AoD positioning may utilize measured DL-PRS-RSRP of downlink signals received at a UE 404 from multiple TRPs 402, 406. The UE 404 uses assistance data received from a positioning server to measure the DL-PRS-RSRP of the received signals, and the resulting measurements are used along with the departure azimuth angle (A-AoD), departure zenith angle (Z-AoD), and other configuration information to position the UE 404 relative to neighboring TRPs 402, 406. DL-TDOA positioning may utilize DL reference signal time difference (RSTD) (and DL-PRS-RSRP) of downlink signals received at a UE 404 from multiple TRPs 402, 406. The UE 404 uses assistance data received from a positioning server to measure the DL RSTD (and DL-PRS-RSRP) of the received signals, and the resulting measurements are used along with other configuration information to position the UE 404 relative to neighboring TRPs 402, 406.

[0079] UL-TDOA positioning may utilize the UL relative time of arrival (RTOA) (and UL-SRS-RSRP) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the UL-RTOA (and UL-SRS-RSRP) of the received signals using assistance data received from the positioning server, and the resulting measurements are used together with other configuration information to estimate the position of the UE 404. UL-AoA positioning may utilize the measured azimuth angle of arrival (A-AoA) and zenith angle of arrival (Z-AoA) of uplink signals sent from the UE 404 at multiple TRPs 402, 406. The TRPs 402, 406 measure the A-AoA and Z-AoA of the received signals using assistance data received from the positioning server, and the resulting measurements are used together with other configuration information to estimate the position of the UE 404.

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

[0081] Figure 5500 is a diagram illustrating an example of estimating the positioning of a UE based on multi-RTT measurements from multiple TRPs according to various aspects of the present disclosure. The UE 502 may be configured by a serving base station to decode DL-PRS resources 512 corresponding to and transmitted from a first TRP 504 (TRP-1), a second TRP 506 (TRP-2), a third TRP 508 (TRP-3), and a fourth TRP 510 (TRP-4). The UE 502 may also be configured to transmit a 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, so that a 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 may be able to measure the UL-SRS resource set transmitted from the UE 502. For multi-RTT measurements based on DL-PRS and UL-SRS, since there may be a correlation between the UE's measurement of the DL-PRS and the TRP's measurement of the UL-SRS, 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 positioning and / or the UE's distance for each TRP may be.

[0082] In some aspects of wireless communications, the terms "positioning reference signal" and "PRS" may generally refer to specific reference signals used for positioning in NR and LTE systems. However, as used herein, the terms "positioning reference signal" and "PRS" may 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. In addition, the terms "positioning reference signal" and "PRS" may 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". In addition, for signals that can be sent in both uplink and downlink (e.g., DMRS, PTRS), these signals may be prepended with "UL" or "DL" to distinguish the direction. For example, "UL-DMRS" may be distinguished from "DL-DMRS".

[0083] Figure 66 is a communication flow 600 illustrating an example multi-RTT positioning process according to various aspects of the present disclosure. The numbers associated with the communication flow 600 do not specify a particular time order and are merely used as a reference for the communication flow 600. In addition, DL-only and / or UL-only positioning may use one or more subsets of the multi-RTT positioning process.

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

[0085] At 614, the serving base station 604 may determine resources available for UL SRS, and at 616, the serving base station 604 may configure one or more UL SRS resource sets for the UE 602 based on the available resources. At 618, the serving base station 604 may provide UL SRS configuration information to the LMF 606, such as via an NRPPa Positioning Information Response message. At 620, the LMF 606 may select one or more candidate neighboring BS / TRPs 608, and the LMF 606 may provide the UL SRS configuration to the one or more candidate neighboring BS / TRPs 608 and / or the serving base station 604, such as via an NRPPa Measurement Request message. The message may include information for enabling the one or more candidate neighboring BS / TRPs 608 and / or the serving base station to perform UL measurements.

[0086] At 622, the LMF 606 may transmit an LPP Provide Assistance Data message to the UE 602. The message may include specified assistance data for the UE 602 to perform DL measurements. At 624, the LMF 606 may transmit an LPP Request Location Information message to the UE 602 to request multi-RTT measurements. At 626, for semi-persistent or aperiodic UL SRS, the LMF 606 may request the serving base station 604 to activate / trigger the UL SRS in the UE 602. For example, the LMF 606 may request activation of UE SRS transmission by transmitting an NRPPa Positioning Activation Request message to the serving base station 604.

[0087] At 628, the serving base station 604 may activate UE SRS transmission and transmit an NRPPa positioning activation response message. In response, the UE 602 may start UL-SRS transmission according to the time domain behavior of the UL SRS resource configuration. At 630, the UE 602 may perform DL measurements from one or more candidate neighboring BS / TRPs 608 and / or serving base stations 604 provided in the auxiliary data. At 632, each of the configured one or more candidate neighboring BS / TRPs 608 and / or serving base stations 604 may perform UL measurements. At 634, the UE 602 may report DL measurements to the LMF 606, such as via an LPP provide location information message. At 636, each of the one or more candidate neighboring BS / TRPs 608 and / or serving base stations 604 may report UL measurements to the LMF 606, such as via an NRPPa measurement response message. At 638, the LMF 606 may determine the RTT from the UE 602 and the BS / TRP Rx-Tx time difference measurements for each of the one or more candidate neighboring BS / TRPs 608 and / or serving base stations 604 for which corresponding UL and DL measurements were provided at 634 and 636, and the LMF 606 may calculate the positioning of the UE 602.

[0088] Some aspects of wireless communication may utilize a radio access network (RAN) as part of a mobile telecommunication system. The RAN may implement a radio access technology for a telecommunication system. In addition, the RAN may provide resource access rights to various radio sites in the telecommunication system and coordinate the management of these resources. The RAN may reside between devices (e.g., user equipment (UE) or mobile phones, computers, or any remotely controlled machines) and provide a connection to its core network (CN). The CN may provide coordination between different parts of the access network and also provide connectivity to the Internet. The RAN may also include a transport network that provides connectivity between the RAN and the CN. In some aspects of the RAN, a radio unit (RU) may process digital radio signals, as well as send, receive, and convert signals for RAN base stations. Types of RAN may include an open radio access network (O-RAN), such as a network configuration initiated by the O-RAN Alliance. In some types of operator deployments for wireless communication, the RAN infrastructure may include an open distributed unit (O-DU) and an open radio unit (O-RU), such as a RAN infrastructure with an O-DU / O-RU split that complies with the O-RAN Control User Synchronization (CUS) specification.

[0089] Some aspects of wireless communication may utilize the functionality of locating a location. There may be multiple different positioning features enabled on the UE side and the network side. For example, the positioning features enabled on the network side may include at least one of the following features: uplink (UL) time difference of arrival (UL-TDOA), UL angle of arrival (UL-AOA), or round trip time (RTT). These features may be based on UL reference signal reception (e.g., sounding reference signal (SRS)). In addition, there may be multiple sensing features supported by the network side.

[0090] Figure 7 700 is a diagram illustrating an example open radio access network (O-RAN) architecture. More specifically, Figure 7 Depicts the open distributed unit (O-DU) and open radio unit (O-RU) in the O-RAN architecture. Figure 7 As shown, diagram 700 shows an O-DU 710, including a physical uplink channel (PUxCH) component 712, an SRS component 714, a PRACH component 716, a descrambling component 720, a demodulation component 722, an equalization component 730, a channel estimation component 732, a detection component 734, a resource element (RE) demapping component 740, an RE demapping component 741, an RE demapping component 742, an in-phase and quadrature (IQ) decompression component 743, an IQ decompression component 744 and an IQ decompression component 745. Diagram 700 also depicts an O-RAN fronthaul (FH) 750 and an O-RU 760, including an IQ compression component 761, an IQ compression component 762, an IQ compression component 763, a digital beamforming component 770, a digital beamforming component 771, a digital beamforming component 772, a fast Fourier transform (FFT) and cyclic prefix (CP) removal component 780, a filtering component 782, an analog-to-digital component 784, an analog beamforming component 790, an analog beamforming component 791, and an analog beamforming component 792.

[0091] like Figure 7As shown, the O-RAN UL split may define a split between a layer 1 (L1) L1 upper layer on the DU side (e.g., O-DU 710) and an L1 lower layer on the RU side (e.g., O-RU 760). In addition, information may be exchanged between the DU side (e.g., O-DU 710) and the RU side (e.g., O-RU 760) based on a control plane (C-plane) message, a user plane (U-plane) message, and / or a synchronization plane (S-plane) message. In addition, the O-RU (e.g., O-RU 760) may transmit UL frequency domain (FD) samples of certain RSs (e.g., SRS) to the O-DU (e.g., O-DU 710) based on a plurality of different configurations. For example, the UL FD samples of the SRS may be transmitted based on the following configurations: FFT size, cyclic prefix (CP) length, subcarrier spacing (SCS), and / or time offset (e.g., if a segment type 3 message is used, the earliest IQ time division (TD) sample may be indicated by a symbol identifier (ID)).

[0092] Figure 8 8 is a diagram illustrating an example timing structure. More specifically, Figure 8 The timing structure for UL FD timing samples is depicted. Figure 8 As shown, diagram 800 includes a cyclic prefix (CP) 810, an FFT window 820 (e.g., an FFT timing window), and an offset 830 (e.g., a timing offset derived from a time offset (timeOffset) parameter). For example, diagram 800 shows that UL FD samples for SRS can be transmitted based on an FFT size (e.g., FFT window 820), a CP length (e.g., CP 810), and a time offset (e.g., offset 830).

[0093] In some aspects, certain features (e.g., UL TDoA, UL AoA, and / or RTT) may be based on SRS FD IQ samples. For example, in UL TDoA, for each SRS pilot, the O-DU may calculate a time offset based on an SRS channel estimate (e.g., by calculating a channel impulse response and detecting a time offset associated with the strongest path or the first path). Moreover, the UL TDoA may utilize a certain number of observations (e.g., N observations) of SRS FD IQ samples to be provided for each SRS symbol and each receiving point. Each observation may be associated with a different time offset (timeOffset). This may be important for non-serving TRPs or neighboring cells, such as when timing is not adjusted for neighboring cells. In fact, timing may be adjusted only for serving TRPs. In some aspects, a transmission timing adjustment process may be used to adjust the timing of a UE relative to a serving TRP. In some cases, the control user synchronization (CUS) specification may not support C-plane messages with a certain number of time offset (timeOffset) parameters (e.g., N timeOffset parameters). To support UL TDoA at O-DU with some CUS specifications, N C-Plane messages may be utilized which incur FH overhead. Therefore, it may be beneficial to include a solution that does not incur C-Plane overhead.

[0094] Fig. 9 is a diagram 900 illustrating an example timing scheme. More specifically, Fig. 9 A timing scheme including a timing structure for UL FD samples is depicted. Fig. 9As shown, diagram 900 depicts an O-RU 902, including a cyclic prefix (CP) 910, an FFT window 920 (e.g., an FFT timing window), and a timeOffset 921 (e.g., a timing offset derived from a time offset (timeOffset) parameter). The O-RU 902 also includes a CP N, an FFT window N, and a timeOffset N (e.g., CPs, FFT windows, and timeOffsets up to a certain number N). In some aspects, the CP window and the FFT window may be the same for different observations. That is, the CP of observation N and the FFT of observation N may be equal to the CP window and FFT window of the first observation. For example, diagram 900 shows that UL FD samples of an SRS may be transmitted based on an FFT size (e.g., FFT window 920), a CP length (e.g., CP 910), and a time offset (e.g., timeOffset 921). Diagram 900 also depicts fronthaul (FH) 904 and O-DU 906, including SRS channel estimation (CE) 930, SRS CE N (e.g., SRS CE up to a certain value N), time offset (TO) 940, time offset (TO) N, and UL TDOA 950. Fig. 9 As shown, TO 940 and TO N are equal to a function of the channel impulse response (CIR) used for channel estimation (CE).

[0095] In some aspects, similar to UL TDoA, some types of positioning features (e.g., UL AoA, RTT) may be based on SRSFD IQ samples. Moreover, these types of positioning features (e.g., UL AoA, RTT) may utilize a certain amount of observations (e.g., N observations) of SRS for neighboring cells and non-serving TRPs. For example, one SRS observation may involve SRS IQ samples to be delivered from the O-RU to the O-DU under a given FFT size, timeOffset, SCS, and / or CP length. Moreover, in some aspects, when the UE moves from a source cell (e.g., adjusting the timing at the UE relative to the source cell) to a target cell within a set of cells configured for L1 / L2 mobility, the timing at the target cell may need to be adjusted, and when the UE begins to communicate data with the target cell, different time offsets may be used to enhance the timing adjustment. Therefore, a certain amount of observations (e.g., N observations) may be used for UL reference signals and / or SRS. Moreover, the sensing feature may need to have different observations to achieve accurate sensing. However, the CUS specification may not support C-plane messages with N time offset parameters. In order to support UL positioning features for O-DU, L1 / L2 mobility and sensing, a certain number of C-plane messages (e.g., N C-plane messages) may be utilized. However, these C-plane messages may incur fronthaul (FH) overhead. Based on the above, it may be beneficial to support UL positioning features without incurring certain overhead (e.g., FH overhead). For example, it may be beneficial to provide C-plane messages without incurring FH overhead.

[0096] Various aspects of the present disclosure may implement UL positioning features without incurring certain overhead (e.g., FH overhead). For example, various aspects presented herein may utilize a certain number of C-plane messages (e.g., N C-plane messages). In some cases, this number of C-plane messages may support the UL positioning feature without adding certain overhead (e.g., FH overhead). That is, various aspects presented herein may support UL positioning features in an O-RAN environment without adding overhead, such as L1 / L2 mobility features and / or sensing features. In addition, various aspects presented herein may allow C-plane messages to be sent and / or received between certain network entities (e.g., O-RU and / or O-DU). Moreover, various aspects presented herein may support control plane messages including adjustments or extensions to message structures (e.g., segment extensions associated with time offset structures).

[0097] The various aspects presented herein may adjust or extend the structure of certain types of messages used to support UL positioning features. For example, the various aspects of the present disclosure may adjust or extend control plane (C-plane) messages to support UL positioning features. For example, the various aspects presented herein may add a segment extension in a C-plane message to allow a time offset (timeoffset or timeOffset) structure with a certain number of values ​​(e.g., N values). The various aspects of the present disclosure may also add a structure of a certain number of time offset fields (e.g., N-1 time offset fields) to a message (e.g., a C-plane message). These added time offset fields may be fields in addition to the time offset fields already supported in the control user synchronization (CUS) specification. For example, if 1 time offset field is added to a C-plane message that already includes 1 time offset field, N=2 (i.e., in the CUS specification, the previous C-plane message may correspond to N=1). In addition, a user plane (U-plane) service may be applied to receive SRS frequency domain (FD) in-phase and quadrature (IQ) samples. That is, non-delay managed U-plane services may be applied to receive SRS FD samples at the O-DU or O-RU (eg, in the case of utilizing N SRS observations).

[0098] Fig.10 is a diagram 1000 illustrating an example timing extension of a message. More specifically, Fig.10 Depicted are example timing extensions for the structure of a control plane (C-plane) message. Fig.10 As shown, diagram 1000 includes a plurality of octets (e.g., octet 1010, octet 1011, octet 1012), an extension field 1020, and an extension type (extensionType) 1030. Furthermore, diagram 1000 includes an extension length (extensionLength) 1040 and a time offset (timeOffset_2_1050). For example, extensionType 1030 and extensionLength 1040 may be equal to the same value (e.g., "xxx"). Fig.10 As shown, in addition to the time offset field already supported in the CUS specification, the various aspects presented herein may also add a time offset field in the C-plane message. Fig.10 As shown, if the various aspects presented herein add 1 time offset field to a C-Plane message that already includes 1 time offset field, then N=2 (i.e., in the CUS specification, the previous C-Plane message may correspond to N=1). That is, various aspects of the present disclosure may add one or more additional time offset fields to the current C-Plane message format. Fig.10As depicted, a message for a control plane (e.g., a C-plane message) may include a section extension associated with a time offset structure. The section extension of the control plane message may correspond to at least one of: multiple time offset fields, multiple values ​​in a time offset structure, or multiple time offset parameters.

[0099] In addition, the various aspects presented herein can reduce the amount of FH overhead utilized when transmitting UL RS (e.g., SRS). For example, on the basis of non-delayed managed U-plane services, in order to reduce the FH overhead of transmitting UL SRS at adjacent cells or non-service transmit receive points (TRPs), the various aspects presented herein can receive energy-based or power-based solutions to be used by certain network entities (e.g., O-RU or O-DU). That is, the various aspects presented herein can receive energy-based or power-based solutions to be used at O-RU or O-DU, so as to select a sub-panel or transmit-receive (Tx-Rx) stream with sufficient energy or power to reduce overhead. For example, one criterion can be that the received power is higher than a threshold configured at the O-DU or O-RU. Another criterion can be that the received power is higher than the load on the fronthaul (FH) interface. In some cases, the O-RU can select a group of sub-panels or a group of transmit-receive (Tx-Rx) streams for RS based on the configuration of the control plane. The configuration of the control plane may be received by the O-RU from the O-DU, wherein the configuration of the control plane includes at least one of the following: a maximum number of time offset fields, a maximum number of values ​​in a time offset structure, or a maximum number of time offset parameters. In addition, the selection of the group of sub-panels or the group of Tx-Rx streams for the RS may include the selection of the group of sub-panels or the group of Tx-Rx streams based on at least one power condition. As noted above, the at least one power condition may correspond to a power threshold or a load threshold of a fronthaul (FH) interface.

[0100] In some cases, the power measurement may be performed in the time domain before the corresponding FFT window. Streams that do not meet the aforementioned power criteria may be discarded. For example, if the stream does not meet the received power above a configured threshold or load on the FH interface, the stream may be discarded. In some cases, if all streams do not meet the power criteria, the entire SRS symbol may be discarded (i.e., the symbol may not be sent from one network entity (e.g., O-RU) to another network entity (e.g., O-DU)). In addition, if a particular SRS does not cross a threshold, there may be some indication to the O-DU (i.e., from O-RU to O-DU).

[0101] In some aspects, a network entity (e.g., O-DU) may define a maximum value (e.g., an N value) that the network entity (e.g., O-DU) may indicate to another network entity (e.g., O-RU). Subsequently, the O-RU may determine or use its own judgment regarding the amount of different FFT offsets (e.g., offsets in the case of L < N) for which it provides data. The amount of different FFT offsets may be determined as long as the amount is within the configured maximum number (e.g., the maximum value N). Also, this determination or judgment may be based on the energy level as described above. In some cases, a network entity (e.g., O-RU) may need to signal to another network entity (e.g., O-DU) the number of FFT offsets (e.g., "L" FFT offsets) that have been used from the total amount of configured FFT offsets (e.g., "N" configured FFT offsets).

[0102] Additionally, aspects of the present disclosure may include CUS specification-friendly solutions to support certain UL positioning features. For example, the aspects presented herein may provide CUS specification-friendly solutions to support L1 / L2 mobility and / or sensing features in an O-RAN environment. Additionally, the aspects presented herein may support RAN-compliant solutions for certain types of networks or network entities, as well as support certain positioning features (e.g., UL positioning features), such as L1 / L2 mobility and / or sensing features at the network. The aspects presented herein may achieve these RAN-compliant solutions by adjusting or extending the structure of certain messages (e.g., C-plane messages).

[0103] As noted herein, certain types of control plane, user plane, and synchronization plane (CUS plane) specifications may not support C-plane messages with certain types of time offset parameters (e.g., N time offset parameters). To support UL TDoA at certain network entities (e.g., O-DU and O-RU) with CUS specifications, the aspects presented herein may support a certain amount of C-plane messages (e.g., N C-plane messages) that may reduce and / or eliminate FH overhead. Additionally, the aspects presented herein may provide solutions that do not cause C-plane overhead. For example, aspects of the present disclosure may add a section extension to a C-plane message that indicates a time offset structure with a certain amount of values (e.g., N values). Additionally, aspects of the present disclosure may add the structure of a certain number of time offset fields (e.g., N - 1 time offset fields) in addition to the time offset fields already supported in the CUS specification.

[0104] Various aspects of the present disclosure may include multiple benefits or advantages. For example, the various aspects presented herein may provide UL positioning features without incurring certain overhead (e.g., FH overhead). For example, the various aspects presented herein may utilize a certain number of C-plane messages (e.g., N C-plane messages). In some aspects, a certain amount of C-plane messages may be added without increasing certain overhead (e.g., FH overhead). For example, the various aspects presented herein may support UL positioning features in an O-RAN environment without increasing overhead (e.g., L1 / L2 mobility features and / or sensing features). In addition, the various aspects presented herein may allow C-plane messages to be sent and / or received between certain network entities (e.g., O-RU and / or O-DU). In addition, the various aspects presented herein may provide control plane messages including adjustments or extensions to the structure of control plane messages (e.g., segment extensions associated with a time offset structure). The methods described herein may be applied to multiple different uplink (UL) signals or channels, such as UL signals or channels in which multiple observations are utilized. For example, the methods described herein may be applied to UL DMRS signals.

[00136] In some aspects, the methods of locating position described herein may utilize UL DMRS with UL SRS and / or without UL SRS.

[0105] Fig.11 FIG. 1 is a communication flow diagram 1100 for wireless communication according to one or more techniques of this disclosure. Fig.11 As shown, diagram 1100 includes example communications between a network entity 1102 (e.g., RU or DU) and a network entity 1104 (e.g., RU or DU) according to one or more techniques of this disclosure. In some aspects, network entity 1102 may be a first wireless device (e.g., UE, base station, TRP, or network entity), and network entity 1104 may be a second wireless device (e.g., UE, base station, TRP, or network entity).

[0106] At 1110, the network entity 1104 may configure a control plane including a set of time offsets.

[0107] At 1120, the network entity 1104 may send a configuration of a control plane including the set of time offsets (e.g., configuration 1124), wherein each time offset in the set of time offsets is associated with a corresponding fast Fourier transform (FFT) window. In some aspects, each time offset in the set of time offsets may be applied to a corresponding FFT window. Moreover, a starting point of the corresponding FFT window may be based on each applied time offset in the set of time offsets. In some cases, the corresponding FFT window of each time offset may be associated with at least one message of the control plane. The at least one message of the control plane may include a segment extension associated with the time offset structure. Moreover, the segment extension of the at least one message of the control plane may correspond to at least one of: a plurality of time offset fields, a plurality of values ​​in the time offset structure, or a plurality of time offset parameters. The configuration of the control plane may include at least one of: a maximum number of time offset fields, a maximum number of values ​​in the time offset structure, or a maximum number of time offset parameters. The configuration of the control plane may be associated with adjusting the set of time offsets. In addition, the configuration of the control plane may include at least one of the following: a frame structure, a cyclic prefix (CP) length, a starting PRB in a set of physical resource blocks (PRBs), or a number of PRBs in the set of PRBs. In addition, a corresponding FFT window for each time offset in the set of time offsets may be associated with an observation window. In some cases, the network entity may be a distributed unit (DU) in a radio access network (RAN). In addition, sending the configuration of the control plane may include sending the configuration to a radio unit (RU) in the RAN.

[0108] At 1122, the network entity 1102 may obtain a configuration of a control plane including a set of time offsets (e.g., configuration 1124). The configuration of the control plane may include at least one of the following: a maximum number of time offset fields, a maximum number of values ​​in a time offset structure, or a maximum number of time offset parameters. Moreover, the configuration of the control plane may be associated with an adjustment of the set of time offsets. The configuration of the control plane may also include at least one of the following: a frame structure, a cyclic prefix (CP) length, a starting PRB in a set of physical resource blocks (PRBs), or a number of PRBs in the set of PRBs. In some aspects, the network entity may be a radio unit (RU) in a radio access network (RAN). In addition, obtaining the configuration of the control plane may include receiving the configuration of the control plane from a distributed unit (DU) in the RAN.

[0109] At 1130, the network entity 1102 may select a set of subpanels or a set of transmit-receive (Tx-Rx) flows for at least one reference signal (RS) based on the configuration of the control plane. In some aspects, selecting the set of subpanels or the set of Tx-Rx flows for at least one RS may include selecting the set of subpanels or the set of Tx-Rx flows based on at least one power condition. Moreover, the at least one power condition may correspond to a power threshold or a load threshold of a fronthaul (FH) interface.

[0110] At 1140, the network entity 1102 may apply each time offset in the set of time offsets to a corresponding Fast Fourier Transform (FFT) window. In some aspects, calculating a corresponding FFT window for each time offset may include calculating a corresponding FFT window for each applied time offset.

[0111] At 1142, the network entity 1102 may determine a starting point of a corresponding FFT window based on each applied time offset. In some aspects, calculating the corresponding FFT window for each time offset may include further calculating the corresponding FFT window for each time offset based on the starting point of the corresponding FFT window.

[0112] At 1150, the network entity 1102 may calculate a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets. The corresponding FFT window for each time offset may be associated with at least one message of the control plane. The at least one message of the control plane may include a segment extension associated with the time offset structure. The segment extension of the at least one message of the control plane may correspond to at least one of the following: a plurality of time offset fields, a plurality of values ​​in the time offset structure, or a plurality of time offset parameters. In addition, the corresponding FFT window for each time offset in the set of time offsets may be associated with an observation window.

[0113] At 1160, the network entity 1102 may receive at least one reference signal (RS) during a corresponding FFT window for each time offset in the set of time offsets. In some aspects, receiving at least one RS during a corresponding FFT window for each time offset in the set of time offsets may include receiving at least one RS from a user equipment (UE) or a transmit reception point (TRP) during the corresponding FFT window.

[0114] At 1170, the network entity 1102 may process at least one RS after a corresponding FFT window for each time offset in the set of time offsets.

[0115] At 1180, the network entity 1102 may send at least one RS (e.g., RS 1184) based on processing the at least one RS after the corresponding FFT window. In some aspects, sending the at least one RS may include sending the at least one RS to a distributed unit (DU) in a radio access network (RAN).

[0116] At 1182, the network entity 1104 may receive at least one reference signal (RS) (e.g., RS 1184) after a corresponding FFT window for each time offset in the set of time offsets. In some aspects, a set of subpanels or a set of transmit-receive (Tx-Rx) flows for at least one RS may be based on a configuration of a control plane. In addition, the set of subpanels or the set of Tx-Rx flows for at least one RS may be further based on at least one power condition, wherein the at least one power condition corresponds to a power threshold or a load threshold of a fronthaul (FH) interface. In addition, receiving at least one RS may include receiving at least one RS from a RU in the RAN.

[0117] At 1190, the network entity 1104 may process at least one RS based on reception of the at least one RS after a corresponding FFT window for each time offset in the set of time offsets.

[0118] Fig.12 1200 is a flow chart of a wireless communication method. The method may be performed by a network entity, RU, DU, or base station (e.g., base station 102, network entity 1102, network entity 1602, network entity 1760). The methods described herein may provide several benefits, such as improved resource utilization and / or power savings.

[0119] At 1202, a network entity may obtain a control plane configuration including a set of time offsets, such as reference Figures 4 to 11 As discussed. For example, Fig.11 As described in 1122 of , the network entity 1102 may obtain a configuration of a control plane including a set of time offsets. In addition, step 1202 may be performed by the offset component 198. The configuration of the control plane may include at least one of the following: a maximum number of time offset fields, a maximum number of values ​​in a time offset structure, or a maximum number of time offset parameters. Moreover, the configuration of the control plane may be associated with an adjustment of the set of time offsets. The configuration of the control plane may also include at least one of the following: a frame structure, a cyclic prefix (CP) length, a starting PRB in a set of physical resource blocks (PRBs), or the number of PRBs in the set of PRBs. In some aspects, the network entity may be a radio unit (RU) in a radio access network (RAN). In addition, obtaining the configuration of the control plane may include receiving the configuration of the control plane from a distributed unit (DU) in the RAN.

[0120] At 1210, the network entity may calculate a corresponding Fast Fourier Transform (FFT) window for each time offset in the set of time offsets, as shown in FIG. Figures 4 to 11 As discussed. For example, Fig.11 As described in 1150 of , the network entity 1102 may calculate a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets. In addition, step 1210 may be performed by the offset component 198. The corresponding FFT window for each time offset may be associated with at least one message of the control plane. The at least one message of the control plane may include a segment extension associated with the time offset structure. The segment extension of the at least one message of the control plane may correspond to at least one of the following: multiple time offset fields, multiple values ​​in the time offset structure, or multiple time offset parameters. In addition, the corresponding FFT window for each time offset in the set of time offsets may be associated with an observation window.

[0121] At 1212, the network entity may receive at least one reference signal (RS) during a corresponding FFT window of each time offset in the set of time offsets, such as a reference signal. Figures 4 to 11 As discussed. For example, Fig.11 As described in 1160 of , the network entity 1102 may receive at least one reference signal (RS) during a corresponding FFT window of each time offset in the set of time offsets. In addition, step 1212 may be performed by the offset component 198. In some aspects, receiving at least one RS during a corresponding FFT window of each time offset in the set of time offsets may include receiving at least one RS from a user equipment (UE) or a transmit reception point (TRP) during the corresponding FFT window.

[0122] Fig.13 1300 is a flow chart of a wireless communication method. The method may be performed by a network entity, RU, DU, or base station (e.g., base station 102, network entity 1102, network entity 1602, network entity 1760). The methods described herein may provide several benefits, such as improved resource utilization and / or power savings.

[0123] At 1302, a network entity may obtain a control plane configuration including a set of time offsets, such as reference Figures 4 to 11 As discussed. For example, Fig.11As described in 1122 of , the network entity 1102 may obtain a configuration of a control plane including a set of time offsets. In addition, step 1302 may be performed by the offset component 198. The configuration of the control plane may include at least one of the following: a maximum number of time offset fields, a maximum number of values ​​in a time offset structure, or a maximum number of time offset parameters. Moreover, the configuration of the control plane may be associated with an adjustment of the set of time offsets. The configuration of the control plane may also include at least one of the following: a frame structure, a cyclic prefix (CP) length, a starting PRB in a set of physical resource blocks (PRBs), or the number of PRBs in the set of PRBs. In some aspects, the network entity may be a radio unit (RU) in a radio access network (RAN). In addition, obtaining the configuration of the control plane may include receiving the configuration of the control plane from a distributed unit (DU) in the RAN.

[0124] At 1304, the network entity may select a set of subpanels or a set of transmit-receive (Tx-Rx) flows for at least one reference signal (RS) based on the configuration of the control plane, such as the reference signal. Figures 4 to 11 As discussed. For example, Fig.11 As described in 1130 of , the network entity 1102 may select a group of sub-panels or a group of transmit-receive (Tx-Rx) streams for at least one reference signal (RS) based on the configuration of the control plane. In addition, step 1304 may be performed by the offset component 198. In some aspects, selecting the group of sub-panels or the group of Tx-Rx streams for at least one RS may include selecting the group of sub-panels or the group of Tx-Rx streams based on at least one power condition. Moreover, the at least one power condition may correspond to a power threshold or a load threshold of a fronthaul (FH) interface.

[0125] At 1306, the network entity may apply each time offset in the set of time offsets to a corresponding fast Fourier transform (FFT) window, as shown in FIG. Figures 4 to 11 As discussed. For example, Fig.11 As described in 1140 of , the network entity 1102 may apply each time offset in the set of time offsets to a corresponding fast Fourier transform (FFT) window. In addition, step 1306 may be performed by the offset component 198. In some aspects, calculating the corresponding FFT window for each time offset may include calculating the corresponding FFT window for each applied time offset.

[0126] At 1308, the network entity may determine the starting point of the corresponding FFT window based on each applied time offset, as shown in FIG. Figures 4 to 11 As discussed. For example, Fig.11As described in 1142 of , the network entity 1102 may determine a starting point of a corresponding FFT window based on each applied time offset. In addition, step 1308 may be performed by the offset component 198. In some aspects, calculating the corresponding FFT window for each time offset may include further calculating the corresponding FFT window for each time offset based on the starting point of the corresponding FFT window.

[0127] At 1310, the network entity may calculate a corresponding Fast Fourier Transform (FFT) window for each time offset in the set of time offsets, as shown in FIG. Figures 4 to 11 As discussed. For example, Fig.11 As described in 1150 of , the network entity 1102 may calculate a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets. In addition, step 1310 may be performed by the offset component 198. The corresponding FFT window for each time offset may be associated with at least one message of the control plane. The at least one message of the control plane may include a segment extension associated with the time offset structure. The segment extension of the at least one message of the control plane may correspond to at least one of the following: multiple time offset fields, multiple values ​​in the time offset structure, or multiple time offset parameters. In addition, the corresponding FFT window for each time offset in the set of time offsets may be associated with an observation window.

[0128] At 1312, the network entity may receive at least one reference signal (RS) during a corresponding FFT window of each time offset in the set of time offsets, such as a reference signal. Figures 4 to 11 As discussed. For example, Fig.11 As described in 1160 of , the network entity 1102 may receive at least one reference signal (RS) during a corresponding FFT window of each time offset in the set of time offsets. In addition, step 1312 may be performed by the offset component 198. In some aspects, receiving at least one RS during a corresponding FFT window of each time offset in the set of time offsets may include receiving at least one RS from a user equipment (UE) or a transmit reception point (TRP) during the corresponding FFT window.

[0129] At 1314, the network entity may process at least one RS after a corresponding FFT window for each time offset in the set of time offsets, as described with reference to Figures 4 to 11 As discussed. For example, Fig.11 As described in 1170 of , the network entity 1102 may process at least one RS after a corresponding FFT window of each time offset in the set of time offsets. In addition, step 1314 may be performed by the offset component 198.

[0130] At 1316, the network entity may send at least one RS based on processing the at least one RS after the corresponding FFT window, as shown in reference Figures 4 to 11 As discussed. For example, Fig.11 As described in 1180 of , the network entity 1102 may send at least one RS based on processing the at least one RS after the corresponding FFT window. In addition, step 1316 may be performed by the offset component 198. In some aspects, sending at least one RS may include sending at least one RS to a distributed unit (DU) in a radio access network (RAN).

[0131] Fig.14 1400 is a flow chart of a wireless communication method. The method may be performed by a network entity, RU, DU, or base station (e.g., base station 102, network entity 1104, network entity 1602, network entity 1760). The methods described herein may provide several benefits, such as improved resource utilization and / or power savings.

[0132] At 1402, a network entity may configure a control plane including a set of time offsets, such as reference Figures 4 to 11 As discussed. For example, Fig.11 As described in 1110 of , the network entity 1104 can configure a control plane including a set of time offsets. In addition, step 1402 can be performed by the offset component 199.

[0133] At 1404, the network entity may send a configuration of a control plane including the set of time offsets, wherein each time offset in the set of time offsets is associated with a corresponding Fast Fourier Transform (FFT) window, as shown in FIG. Figures 4 to 11 As discussed. For example, Fig.11As described in 1120 of , the network entity 1104 may send a configuration of the control plane including the group of time offsets, wherein each time offset in the group of time offsets is associated with a corresponding fast Fourier transform (FFT) window. In addition, step 1404 may be performed by the offset component 199. In some aspects, each time offset in the group of time offsets may be applied to a corresponding FFT window. Moreover, the starting point of the corresponding FFT window may be based on each applied time offset in the group of time offsets. In some cases, the corresponding FFT window of each time offset may be associated with at least one message of the control plane. At least one message of the control plane may include a segment extension associated with the time offset structure. Moreover, the segment extension of at least one message of the control plane may correspond to at least one of the following: multiple time offset fields, multiple values ​​in the time offset structure, or multiple time offset parameters. The configuration of the control plane may include at least one of the following: a maximum number of time offset fields, a maximum number of values ​​in the time offset structure, or a maximum number of time offset parameters. The configuration of the control plane may be associated with the adjustment of the group of time offsets. In addition, the configuration of the control plane may include at least one of the following: a frame structure, a cyclic prefix (CP) length, a starting PRB in a set of physical resource blocks (PRBs), or a number of PRBs in the set of PRBs. In addition, a corresponding FFT window for each time offset in the set of time offsets may be associated with an observation window. In some cases, the network entity may be a distributed unit (DU) in a radio access network (RAN). In addition, sending the configuration of the control plane may include sending the configuration to a radio unit (RU) in the RAN.

[0134] At 1406, the network entity may receive at least one reference signal (RS) after a corresponding FFT window for each time offset in the set of time offsets, such as a reference signal. Figures 4 to 11 As discussed. For example, Fig.11 As described in 1182 of , the network entity 1104 may receive at least one reference signal (RS) after the corresponding FFT window of each time offset in the group of time offsets. In addition, step 1406 may be performed by the offset component 199. In some aspects, a set of sub-panels or a set of transmit-receive (Tx-Rx) flows for at least one RS may be based on the configuration of the control plane. In addition, the set of sub-panels or the set of Tx-Rx flows for at least one RS may be further based on at least one power condition, wherein the at least one power condition corresponds to a power threshold or a load threshold of a fronthaul (FH) interface. In addition, receiving at least one RS may include receiving at least one RS from a RU in the RAN.

[0135] Fig.151500 is a flow chart of a wireless communication method. The method may be performed by a network entity, RU, DU, or base station (e.g., base station 102, network entity 1104, network entity 1602, network entity 1760). The methods described herein may provide several benefits, such as improved resource utilization and / or power savings.

[0136] At 1502, a network entity may configure a control plane including a set of time offsets, such as reference Figures 4 to 11 As discussed. For example, Fig.11 As described in 1110 of , the network entity 1104 can configure a control plane including a set of time offsets. In addition, step 1502 can be performed by the offset component 199.

[0137] At 1504, the network entity may send a control plane configuration including the set of time offsets, wherein each time offset in the set of time offsets is associated with a corresponding Fast Fourier Transform (FFT) window, as shown in FIG. Figures 4 to 11 As discussed. For example, Fig.11 As described in 1120 of , the network entity 1104 may send a configuration of the control plane including the group of time offsets, wherein each time offset in the group of time offsets is associated with a corresponding fast Fourier transform (FFT) window. In addition, step 1504 may be performed by the offset component 199. In some aspects, each time offset in the group of time offsets may be applied to a corresponding FFT window. Moreover, the starting point of the corresponding FFT window may be based on each applied time offset in the group of time offsets. In some cases, the corresponding FFT window of each time offset may be associated with at least one message of the control plane. At least one message of the control plane may include a segment extension associated with the time offset structure. Moreover, the segment extension of at least one message of the control plane may correspond to at least one of the following: multiple time offset fields, multiple values ​​in the time offset structure, or multiple time offset parameters. The configuration of the control plane may include at least one of the following: a maximum number of time offset fields, a maximum number of values ​​in the time offset structure, or a maximum number of time offset parameters. The configuration of the control plane may be associated with the adjustment of the group of time offsets. In addition, the configuration of the control plane may include at least one of the following: a frame structure, a cyclic prefix (CP) length, a starting PRB in a set of physical resource blocks (PRBs), or a number of PRBs in the set of PRBs. In addition, a corresponding FFT window for each time offset in the set of time offsets may be associated with an observation window. In some cases, the network entity may be a distributed unit (DU) in a radio access network (RAN). In addition, sending the configuration of the control plane may include sending the configuration to a radio unit (RU) in the RAN.

[0138] At 1506, the network entity may receive at least one reference signal (RS) after a corresponding FFT window for each time offset in the set of time offsets, such as a reference signal. Figures 4 to 11 As discussed. For example, Fig.11 As described in 1182 of , the network entity 1104 may receive at least one reference signal (RS) after the corresponding FFT window of each time offset in the group of time offsets. In addition, step 1506 may be performed by the offset component 199. In some aspects, a set of sub-panels or a set of transmit-receive (Tx-Rx) flows for at least one RS may be based on the configuration of the control plane. In addition, the set of sub-panels or the set of Tx-Rx flows for at least one RS may be further based on at least one power condition, wherein the at least one power condition corresponds to a power threshold or a load threshold of a fronthaul (FH) interface. In addition, receiving at least one RS may include receiving at least one RS from a RU in the RAN.

[0139] At 1508, the network entity may process at least one RS based on reception of at least one RS after a corresponding FFT window for each time offset in the set of time offsets, as described with reference to Figures 4 to 11 As discussed. For example, Fig.11 As described in 1190 of , the network entity 1104 may process at least one RS based on reception of at least one RS after a corresponding FFT window of each time offset in the set of time offsets. In addition, step 1508 may be performed by the offset component 199.

[0140] Fig.161600 is a diagram illustrating an example of a hardware implementation of a network entity 1602. The network entity 1602 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1602 may include at least one of a CU 1610, a DU 1630, or a RU 1640. For example, depending on the layer functionality handled by the offset component 198 and the offset component 199, the network entity 1602 may include a CU 1610; both a CU 1610 and a DU 1630; each of the CU 1610, the DU 1630, and the RU 1640; the DU 1630; both a DU 1630 and a RU 1640; or a RU 1640. The CU 1610 may include a CU processor 1612. The CU processor 1612 may include an on-chip memory 1612'. In some aspects, the CU 1610 may also include an additional memory module 1614 and a communication interface 1618. CU1610 communicates with DU 1630 via a midhaul link (such as an F1 interface). DU 1630 may include a DU processor 1632. DU processor 1632 may include on-chip memory 1632'. In some aspects, DU 1630 may also include additional memory modules 1634 and communication interfaces 1638. DU 1630 communicates with RU 1640 via a fronthaul link. RU 1640 may include a RU processor 1642. RU processor 1642 may include on-chip memory 1642'. In some aspects, RU 1640 may also include additional memory modules 1644, one or more transceivers 1646, antenna 1680, and communication interface 1648. RU 1640 communicates with UE 104. On-chip memory 1612', 1632', 1642' and additional memory modules 1614, 1634, 1644 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1612, 1632, 1642 is responsible for general processing, including executing software stored on the computer readable medium / memory. The software, when executed by the corresponding processor, causes the processor to perform the various functions described above. The computer readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0141] As discussed above, the offset component 198 may be configured to obtain a configuration of a control plane including a set of time offsets. The offset component 198 may also be configured to calculate a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets. The offset component 198 may also be configured to receive at least one reference signal (RS) during the corresponding FFT window for each time offset in the set of time offsets. The offset component 198 may also be configured to apply each time offset in the set of time offsets to a corresponding FFT window. The offset component 198 may also be configured to determine a starting point of a corresponding FFT window based on each applied time offset. The offset component 198 may also be configured to select a set of sub-panels or a set of transmit-receive (Tx-Rx) streams for at least one RS based on the configuration of the control plane. The offset component 198 may also be configured to process at least one RS after the corresponding FFT window for each time offset in the set of time offsets. The offset component 198 may also be configured to send at least one RS based on the processing of at least one RS after the corresponding FFT window. The offset component 199 may also be configured to configure a control plane including a set of time offsets. The offset component 199 may also be configured to send a configuration of a control plane including the set of time offsets, wherein each time offset in the set of time offsets is associated with a corresponding fast Fourier transform (FFT) window. The offset component 199 may also be configured to receive at least one reference signal (RS) after a corresponding FFT window for each time offset in the set of time offsets. The offset component 199 may also be configured to process at least one RS based on reception of at least one RS after a corresponding FFT window for each time offset in the set of time offsets.

[0142] The offset component 198 and the offset component 199 may be within one or more processors of one or more of the CU 1610, the DU 1630, and the RU 1640. The offset component 198 and the offset component 199 may be one or more hardware components that are 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 some combination of the above. The network entity 1602 may include a variety of components configured for various functions. In one configuration, the network entity 1602 may include a component for obtaining a configuration of a control plane including a set of time offsets. The network entity 1602 may also include a component for calculating a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets. The network entity 1602 may also include a component for receiving at least one reference signal (RS) during a corresponding FFT window for each time offset in the set of time offsets. The network entity 1602 may also include a component for applying each time offset in the set of time offsets to a corresponding FFT window. The network entity 1602 may also include a component for determining a starting point of a corresponding FFT window based on each applied time offset. The network entity 1602 may also include a component for selecting a group of sub-panels or a group of transmit-receive (Tx-Rx) streams for at least one RS based on the configuration of the control plane. The network entity 1602 may also include a component for processing at least one RS after the corresponding FFT window of each time offset in the group of time offsets. The network entity 1602 may also include a component for sending at least one RS based on the processing of at least one RS after the corresponding FFT window. The network entity 1602 may also include a component for configuring a control plane including a group of time offsets. The network entity 1602 may also include a component for sending a configuration of a control plane including the group of time offsets, wherein each time offset in the group of time offsets is associated with a corresponding fast Fourier transform (FFT) window. The network entity 1602 may also include a component for receiving at least one reference signal (RS) after the corresponding FFT window of each time offset in the group of time offsets. The network entity 1602 may also include means for processing at least one RS based on reception of at least one RS after a corresponding FFT window of each time offset in the set of time offsets. The means may be an offset component 198 and an offset component 199 of the network entity 1602 configured to perform the functions recited by the means. As described above, the network entity 1602 may include a TX processor 316, an RX processor 370, and a controller / processor 375. Thus, in one configuration, the means may be a TX processor 316, an RX processor 370, and / or a controller / processor 375 configured to perform the functions recited by the means.

[0143] Fig.17 1700 is an example of a hardware implementation of an example network entity 1760. In one example, the network entity 1760 may be within the core network 120. The network entity 1760 may include a network processor 1712. The network processor 1712 may include an on-chip memory 1712'. In some aspects, the network entity 1760 may also include an additional memory module 1714. The network entity 1760 communicates with the CU 1702 directly (e.g., backhaul link) or indirectly (e.g., through the RIC) via a network interface 1780. The on-chip memory 1712' and the additional memory module 1714 may each be considered as a computer-readable medium / memory. Each computer-readable medium / memory may be non-transitory. The processor 1712 is responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the processor when executing the software.

[0144] As discussed above, the offset component 198 may be configured to obtain a configuration of a control plane including a set of time offsets. The offset component 198 may also be configured to calculate a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets. The offset component 198 may also be configured to receive at least one reference signal (RS) during the corresponding FFT window for each time offset in the set of time offsets. The offset component 198 may also be configured to apply each time offset in the set of time offsets to a corresponding FFT window. The offset component 198 may also be configured to determine a starting point of a corresponding FFT window based on each applied time offset. The offset component 198 may also be configured to select a set of sub-panels or a set of transmit-receive (Tx-Rx) streams for at least one RS based on the configuration of the control plane. The offset component 198 may also be configured to process at least one RS after the corresponding FFT window for each time offset in the set of time offsets. The offset component 198 may also be configured to send at least one RS based on the processing of at least one RS after the corresponding FFT window. The offset component 199 may also be configured to configure a control plane including a set of time offsets. The offset component 199 may also be configured to send a configuration of a control plane including the set of time offsets, wherein each time offset in the set of time offsets is associated with a corresponding fast Fourier transform (FFT) window. The offset component 199 may also be configured to receive at least one reference signal (RS) after a corresponding FFT window for each time offset in the set of time offsets. The offset component 199 may also be configured to process at least one RS based on reception of at least one RS after a corresponding FFT window for each time offset in the set of time offsets.

[0145] The offset component 198 and the offset component 199 may be within the processor 1712. The offset component 198 and the offset 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 some combination of the above. The network entity 1760 may include a variety of components configured for various functions. In one configuration, the network entity 1760 may include a component for obtaining a configuration of a control plane including a set of time offsets. The network entity 1760 may also include a component for calculating a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets. The network entity 1760 may also include a component for receiving at least one reference signal (RS) during a corresponding FFT window for each time offset in the set of time offsets. The network entity 1760 may also include a component for applying each time offset in the set of time offsets to a corresponding FFT window. The network entity 1760 may also include a component for determining a starting point of a corresponding FFT window based on each applied time offset. The network entity 1760 may also include a component for selecting a set of sub-panels or a set of transmit-receive (Tx-Rx) streams for at least one RS based on the configuration of the control plane. The network entity 1760 may also include a component for processing at least one RS after a corresponding FFT window for each time offset in the set of time offsets. The network entity 1760 may also include a component for sending at least one RS based on processing of at least one RS after a corresponding FFT window. The network entity 1760 may also include a component for configuring a control plane including a set of time offsets. The network entity 1760 may also include a component for sending a configuration of a control plane including the set of time offsets, wherein each time offset in the set of time offsets is associated with a corresponding fast Fourier transform (FFT) window. The network entity 1760 may also include a component for receiving at least one reference signal (RS) after a corresponding FFT window for each time offset in the set of time offsets. The network entity 1760 may also include a component for processing at least one RS based on receiving at least one RS after a corresponding FFT window for each time offset in the set of time offsets. A means may be an offset component 199 of a network entity 1760 configured to perform the functions recited by the means.

[0146] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is merely an illustration of the exemplary method. It should be understood that the specific order or hierarchy of the blocks in the process / flowchart may be rearranged based on design preferences. Further, some blocks may be combined or omitted. The attached method claims provide the elements of the various blocks in a sample order, but are not limited to the specific order or hierarchy provided.

[0147] 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 can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when" and "while" do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that if the conditions are met, then the action will occur, but no specific or immediate time limit is required for the occurrence of the action. The word "exemplary" is used herein to mean "used as an example, instance or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having advantages over other aspects. Unless otherwise specified, 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" may 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 set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, the data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

[0148] As used herein, 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, a condition, a factor, etc.) should be interpreted as "based at least on A" unless specifically stated differently.

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

[0150] Aspect 1 is a device for performing wireless communications at a network entity, the device comprising a memory and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to: obtain a configuration of a control plane comprising a set of time offsets; calculate a corresponding fast Fourier transform (FFT) window for each time offset in the set of time offsets; and receive at least one reference signal (RS) during a corresponding FFT window for each time offset in the set of time offsets.

[0151] Aspect 2 is an apparatus according to Aspect 1, wherein the at least one processor is further configured to: apply each time offset in the group of time offsets to a corresponding FFT window, wherein in order to calculate the corresponding FFT window for each time offset, the at least one processor is configured to: calculate the corresponding FFT window for each applied time offset.

[0152] Aspect 3 is an apparatus according to any one of Aspect 1 and Aspect 2, wherein the at least one processor is further configured to: determine the starting point of the corresponding FFT window based on each applied time offset, wherein in order to calculate the corresponding FFT window of each time offset, the at least one processor is configured to: further calculate the corresponding FFT window of each time offset based on the starting point of the corresponding FFT window.

[0153] Aspect 4 is an apparatus according to any one of aspects 1 to 3, wherein the corresponding FFT window of each time offset is associated with at least one message of the control plane.

[0154] Aspect 5 is the apparatus according to aspect 4, wherein at least one message of the control plane includes a segment extension associated with the time offset structure.

[0155] Aspect 6 is an apparatus according to any one of Aspects 4 to 5, wherein the segment extension of at least one message of the control plane corresponds to at least one of the following: multiple time offset fields, multiple values ​​in the time offset structure, or multiple time offset parameters.

[0156] Aspect 7 is an apparatus according to any one of Aspects 1 to 6, wherein the at least one processor is further configured to: select a group of sub-panels or a group of transmit-receive (Tx-Rx) streams for at least one RS based on the configuration of the control plane.

[0157] Aspect 8 is an apparatus according to Aspect 7, wherein in order to select the group of sub-panels or the group of Tx-Rx streams for at least one RS, the at least one processor is configured to: select the group of sub-panels or the group of Tx-Rx streams based on at least one power condition, wherein the at least one power condition corresponds to a power threshold or a load threshold of a fronthaul (FH) interface.

[0158] Aspect 9 is an apparatus according to any one of aspects 1 to 8, wherein the configuration of the control plane includes at least one of the following: a maximum number of time offset fields, a maximum number of values ​​in a time offset structure, or a maximum number of time offset parameters.

[0159] Aspect 10 is an apparatus according to any one of aspects 1 to 9, wherein the at least one processor is further configured to: process at least one RS after a corresponding FFT window of each time offset in the set of time offsets.

[0160] Aspect 11 is the apparatus according to aspect 10, wherein the at least one processor is further configured to: send at least one RS based on the at least one processor being configured to process at least one RS after a corresponding FFT window.

[0161] Aspect 12 is an apparatus according to any one of aspects 10 to 11, wherein, in order to send at least one RS, the at least one processor is configured to: send at least one RS to a distributed unit (DU) in a radio access network (RAN).

[0162] Aspect 13 is an apparatus according to any one of aspects 1 to 12, wherein the configuration of the control plane is associated with adjusting the set of time offsets.

[0163] Aspect 14 is an apparatus according to any one of Aspects 1 to 13, wherein the configuration of the control plane also includes at least one of the following: a frame structure, a cyclic prefix (CP) length, a starting PRB in a set of physical resource blocks (PRBs), or the number of PRBs in the set of PRBs.

[0164] Aspect 15 is an apparatus according to any one of aspects 1 to 14, wherein the corresponding FFT window of each time offset in the set of time offsets is associated with an observation window.

[0165] Aspect 16 is an apparatus according to any one of Aspects 1 to 15, wherein the network entity is a radio unit (RU) in a radio access network (RAN), and wherein in order to obtain the configuration of the control plane, the at least one processor is configured to: receive the configuration of the control plane from a distributed unit (DU) in the RAN.

[0166] Aspect 17 is an apparatus according to any one of Aspects 1 to 16, the apparatus further comprising at least one of an antenna or a transceiver coupled to the at least one processor, wherein in order to receive at least one RS during a corresponding FFT window of each time offset in the group of time offsets, the at least one processor is configured to: receive at least one RS from a user equipment (UE) or a transmit receive point (TRP) during the corresponding FFT window via at least one of the antenna or the transceiver.

[0167] Aspect 18 is a device for performing wireless communications at a network entity, the device comprising a memory and at least one processor, the at least one processor being coupled to the memory and, based at least in part on information stored in the memory, the at least one processor being configured to: configure a control plane comprising a set of time offsets; send a configuration of a control plane comprising the set of time offsets, wherein each time offset in the set of time offsets is associated with a corresponding fast Fourier transform (FFT) window; and receive at least one reference signal (RS) after the corresponding FFT window of each time offset in the set of time offsets.

[0168] Aspect 19 is the apparatus according to aspect 18, wherein each time offset in the set of time offsets is configured to be applied to a corresponding FFT window.

[0169] Aspect 20 is an apparatus according to any one of aspects 18 and 19, wherein a starting point of a corresponding FFT window is based on the time offset applied by each of the set of time offsets.

[0170] Aspect 21 is an apparatus according to any one of Aspects 18 to 20, wherein the corresponding FFT window of each time offset is associated with at least one message of the control plane.

[0171] Aspect 22 is an apparatus according to Aspect 21, wherein at least one message of the control plane includes a segment extension associated with a time offset structure, and wherein the segment extension of at least one message of the control plane corresponds to at least one of: multiple time offset fields, multiple values ​​in the time offset structure, or multiple time offset parameters.

[0172] Aspect 23 is an apparatus according to Aspect 18 to Aspect 22, wherein a set of sub-panels or a set of transmit-receive (Tx-Rx) flows for at least one RS is based on a configuration of the control plane, and wherein the set of sub-panels or the set of Tx-Rx flows for at least one RS is further based on at least one power condition, wherein the at least one power condition corresponds to a power threshold or a load threshold of a fronthaul (FH) interface.

[0173] Aspect 24 is an apparatus according to any one of aspects 18 to 23, wherein the configuration of the control plane includes at least one of the following: a maximum number of time offset fields, a maximum number of values ​​in a time offset structure, or a maximum number of time offset parameters.

[0174] Aspect 25 is an apparatus according to any one of Aspects 18 to 24, wherein the at least one processor is further configured to: process at least one RS based on the at least one processor being configured to receive at least one RS after the corresponding FFT window of each time offset in the group of time offsets.

[0175] Aspect 26 is an apparatus according to Aspect 18 to Aspect 25, wherein the configuration of the control plane is associated with the adjustment of the group of time offsets, and wherein the configuration of the control plane also includes at least one of the following: a frame structure, a cyclic prefix (CP) length, a starting PRB in a group of physical resource blocks (PRBs), or the number of PRBs in the group of PRBs.

[0176] Aspect 27 is an apparatus according to aspects 18 to 26, wherein the corresponding FFT window of each time offset in the set of time offsets is associated with an observation window.

[0177] Aspect 28 is an apparatus according to Aspect 18 to Aspect 27, the apparatus further comprising at least one of an antenna or a transceiver coupled to the at least one processor, wherein the network entity is a distributed unit (DU) in a radio access network (RAN), wherein in order to send a configuration of the control plane, the at least one processor is configured to: send the configuration to a radio unit (RU) in the RAN via at least one of the antenna or the transceiver, and wherein in order to receive at least one RS, the at least one processor is configured to: receive at least one RS from the RU in the RAN.

[0178] Aspect 29 is an apparatus according to any one of aspects 1 to 28, wherein the apparatus is a wireless communication device, and the apparatus further includes at least one of an antenna or a transceiver coupled to the at least one processor.

[0179] Aspect 30 is a wireless communication method for implementing any one of Aspects 1 to 29.

[0180] Aspect 31 is an apparatus for wireless communication, the apparatus comprising means for implementing any one of Aspect 1 to Aspect 29.

[0181] Aspect 32 is a computer-readable medium (eg, non-transitory computer-readable medium) storing computer-executable code, which, when executed by at least one processor, causes the at least one processor to implement any one of Aspects 1 to 29.

Claims

1. A device for wireless communication at a network entity, the device include: Memory; and at least one processor coupled to the memory and based at least in part on first information stored in the memory, the at least one processor configured to: obtaining a configuration of a control surface including a set of time offsets; calculating a corresponding Fast Fourier Transform (FFT) window for each time offset in the set of time offsets; and At least one reference signal (RS) is received during the corresponding FFT window of each time offset in the set of time offsets.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: Each time offset of the set of time offsets is applied to the corresponding FFT window, wherein to calculate the corresponding FFT window for each time offset, the at least one processor is configured to calculate the corresponding FFT window for each applied time offset.

3. The apparatus of claim 2, wherein the at least one processor is further configured to: The starting point of the corresponding FFT window is determined based on each applied time offset, wherein in order to calculate the corresponding FFT window of each time offset, the at least one processor is configured to: further calculate the corresponding FFT window of each time offset based on the starting point of the corresponding FFT window. 4 . The apparatus of claim 1 , wherein the corresponding FFT window of each time offset is associated with at least one message of the control plane. The apparatus of claim 4 , wherein the at least one message of the control plane comprises a segment extension associated with a time offset structure.

6. The apparatus of claim 5, wherein the segment extension of the at least one message of the control plane corresponds to at least one of: a plurality of time offset fields, a plurality of values ​​in the time offset structure, or a plurality of time offset parameters.

7. The apparatus of claim 1, wherein the at least one processor is further configured to: A set of subpanels or a set of transmit-receive (Tx-Rx) flows for the at least one RS is selected based on the configuration of the control plane.

8. The apparatus according to claim 7, wherein in order to select the set of sub-panels or the set of Tx-Rx streams for the at least one RS, the at least one processor is configured to: select the set of sub-panels or the set of Tx-Rx streams based on at least one power condition, wherein the at least one power condition corresponds to a power threshold or a load threshold of a fronthaul (FH) interface.

9. The apparatus of claim 1, wherein the configuration of the control plane comprises at least one of: a maximum number of time offset fields, a maximum number of values ​​in a time offset structure, or a maximum number of time offset parameters.

10. The apparatus of claim 1, wherein the at least one processor is further configured to: The at least one RS is processed after the corresponding FFT window for each time offset in the set of time offsets.

11. The apparatus of claim 10, wherein the at least one processor is further configured to: The at least one RS is sent based on the at least one processor being configured to process the at least one RS after the corresponding FFT window.

12. The apparatus of claim 11, wherein to transmit the at least one RS, the at least one processor is configured to transmit the at least one RS to a distributed unit (DU) in a radio access network (RAN).

13. The apparatus of claim 1, wherein the configuration of the control plane is associated with adjustment of the set of time offsets.

14. The apparatus of claim 1, wherein the configuration of the control plane further comprises at least one of: a frame structure, a cyclic prefix (CP) length, a starting PRB in a set of physical resource blocks (PRBs), or a number of PRBs in the set of PRBs.

15. The apparatus of claim 1, wherein the corresponding FFT window of each time offset in the set of time offsets is associated with an observation window.

16. The apparatus of claim 1, wherein the network entity is a radio unit (RU) in a radio access network (RAN), and wherein in order to obtain the configuration of the control plane, the at least one processor is configured to: receive the configuration of the control plane from a distributed unit (DU) in the RAN.

17. The apparatus according to claim 1, further comprising at least one of an antenna or a transceiver coupled to the at least one processor, wherein in order to receive the at least one RS during a corresponding FFT window of each time offset in the set of time offsets, the at least one processor is configured to: receive the at least one RS from a user equipment (UE) or a transmit receive point (TRP) during the corresponding FFT window via the antenna or at least one of the transceiver.

18. An apparatus for wireless communication at a network entity, the apparatus include: Memory; and at least one processor coupled to the memory and based at least in part on first information stored in the memory, the at least one processor configured to: configuring a control surface including a set of time offsets; transmitting a configuration of the control plane including the set of time offsets, wherein each time offset in the set of time offsets is associated with a corresponding Fast Fourier Transform (FFT) window; as well as At least one reference signal (RS) is received after the corresponding FFT window for each time offset in the set of time offsets.

19. The apparatus of claim 18, wherein each time offset in the set of time offsets is configured to be applied to the corresponding FFT window.

20. The apparatus of claim 19, wherein a starting point of the corresponding FFT window is based on a time offset applied by each of the set of time offsets.

21. The apparatus of claim 18, wherein the corresponding FFT window for each time offset is associated with at least one message of the control plane.

22. An apparatus according to claim 21, wherein the at least one message of the control plane includes a segment extension associated with a time offset structure, and wherein the segment extension of the at least one message of the control plane corresponds to at least one of the following: multiple time offset fields, multiple values ​​in the time offset structure, or multiple time offset parameters.

23. The apparatus of claim 18, wherein a set of sub-panels or a set of transmit-receive (Tx-Rx) flows for the at least one RS is based on the configuration of the control plane, and wherein the set of sub-panels or the set of Tx-Rx flows for the at least one RS is further based on at least one power condition, wherein the at least one power condition corresponds to a power threshold or a load threshold of a fronthaul (FH) interface.

24. The apparatus of claim 18, wherein the configuration of the control plane comprises at least one of: a maximum number of time offset fields, a maximum number of values ​​in a time offset structure, or a maximum number of time offset parameters.

25. The apparatus of claim 18, wherein the at least one processor is further configured to: The at least one RS is processed based on the at least one processor being configured to receive the at least one RS after the corresponding FFT window for each time offset in the set of time offsets.

26. The apparatus of claim 18, wherein the configuration of the control plane is associated with an adjustment of the set of time offsets, and wherein the configuration of the control plane further comprises at least one of: a frame structure, a cyclic prefix (CP) length, a starting PRB in a set of physical resource blocks (PRBs), or a number of PRBs in the set of PRBs.

27. The apparatus of claim 18, wherein the corresponding FFT window of each time offset in the set of time offsets is associated with an observation window.

28. The apparatus of claim 18, further comprising at least one of an antenna or a transceiver coupled to the at least one processor, wherein the network entity is a distributed unit (DU) in a radio access network (RAN), wherein to send the configuration of the control plane, the at least one processor is configured to: send the configuration to a radio unit (RU) in the RAN via at least one of the antenna or the transceiver, and wherein to receive the at least one RS, the at least one processor is configured to: receive the at least one RS from the RU in the RAN.

29. A method for wireless communication at a network entity, the method include: obtaining a configuration of a control surface including a set of time offsets; calculating a corresponding Fast Fourier Transform (FFT) window for each time offset in the set of time offsets; as well as At least one reference signal (RS) is received during the corresponding FFT window of each time offset in the set of time offsets.

30. A method for wireless communication at a network entity, the method include: configuring a control surface including a set of time offsets; transmitting a configuration of the control plane including the set of time offsets, wherein each time offset in the set of time offsets is associated with a corresponding Fast Fourier Transform (FFT) window; as well as At least one reference signal (RS) is received after the corresponding FFT window for each time offset in the set of time offsets.

Images