UE reporting time domain channel characteristics
By configuring Doppler configuration and TRS in the 5G NR system, the UE measures and reports Doppler information, and the network node predicts the downlink channel and pre-decoder based on this information, solving the problem of channel prediction and pre-decoding and improving the accuracy and efficiency of channel prediction and pre-decoding.
Patent Information
- Application Number
- CN202380032684.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-15
- Filing Date
- 2023-03-24
- Publication Date
- 2024-11-22
AI Technical Summary
Existing 5G NR technologies have room for improvement in channel prediction and pre-decoding, especially when dealing with different channel paths having different Doppler spectra, making it difficult to achieve effective channel prediction and pre-decoding.
By configuring a Doppler configuration and tracking reference signal (TRS) between the user equipment (UE) and the network node, the UE measures and reports Doppler information, and the network node uses this information to predict the downlink channel and pre-decoder, thereby achieving prediction and pre-decoding of channel characteristics.
It improves the accuracy of downlink channel prediction and the efficiency of pre-decoding, thereby enhancing the performance of communication systems, especially in channel environments with non-uniform Doppler spectra.
Smart Images

Figure CN119013937A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of Greek patent application serial number 20220100333, filed on April 15, 2022, entitled “UE REPORTING OF TIME DOMAIN CHANNEL CHARACTERISTICS,” 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 configurations for UE reporting time domain channel characteristics. 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 city, country, region, and even global levels. 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. 5G NR 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 a comprehensive overview of all contemplated aspects. This summary is neither intended to identify key or important elements of all aspects, nor to describe 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 a device at a UE. The apparatus may be a processor and / or a modem at the UE or the UE itself. The apparatus receives a Doppler configuration to measure Doppler information for at least one of a plurality of channel paths. The apparatus receives a tracking reference signal (TRS) based on the Doppler configuration to obtain Doppler information for at least one of a plurality of channel paths. The apparatus sends a Doppler report based on the received TRS, the Doppler report including Doppler information for at least one of a plurality of channel paths. The apparatus receives a downlink transmission on a predicted channel and a pre-decoder, the predicted channel and the pre-decoder being based at least on the Doppler report.
[0008] In one aspect of the present disclosure, a method, a computer readable medium, and an apparatus are provided. The apparatus may be a device at a network node. The apparatus may be a processor and / or a modem at a network node or the network node itself. The apparatus sends a Doppler configuration to measure Doppler information for at least one of a plurality of channel paths. The apparatus sends a tracking reference signal (TRS) to allow measurement of Doppler information for at least one of a plurality of channel paths. The apparatus receives a Doppler report based on the sent tracking reference signal, the Doppler report including Doppler information for at least one of a plurality of channel paths. The apparatus predicts a downlink channel and a pre-decoder based at least on the Doppler report. The apparatus sends a downlink transmission on the predicted downlink channel and pre-decoder.
[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 are only indicative of 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 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 2Dis a diagram illustrating an example of 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] FIG. 4A to FIG. 4C is a diagram illustrating an example of delay-Doppler analysis of a channel.
[0017] Figure 5A and Figure 5B is a diagram illustrating an example of channel and pre-decoder prediction.
[0018] Figure 6 is a diagram illustrating an example of reciprocity-based downlink precoding.
[0019] Figure 7 is a diagram illustrating an example of codebook-based downlink precoding.
[0020] Fig. 8A is a diagram illustrating an example of reciprocity-based downlink precoding.
[0021] Figure 8B is a diagram illustrating an example of codebook-based downlink precoding.
[0022] Fig. 9 is a diagram illustrating an example in which a UE reports a Doppler for each tap.
[0023] Fig.10 is a diagram illustrating an example of a CSI report configuration.
[0024] Fig.11 is a diagram illustrating an example of measurement averaging for Doppler shift reporting.
[0025] Fig.12 It is a call flow diagram of the signaling between the UE and the network entity.
[0026] Fig.13 is a flow chart of a method of wireless communication.
[0027] Fig.14 is a flow chart of a method of wireless communication.
[0028] Fig.15 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.
[0029] Fig.16 is a flow chart of a method of wireless communication.
[0030] Fig.17 is a flow chart of a method of wireless communication.
[0031] Fig.18 is a diagram illustrating an example of a hardware implementation of an example network entity. DETAILED DESCRIPTION
[0032] In wireless communications, Rayleigh fading channels, such as but not limited to tapped delay line (TDL), extended pedestrian A (EPA) model, extended vehicular A (EVA) model, etc., may have the same or similar Doppler spectrum for all paths. In some spatial channel models (e.g., clustered delay line (CDL)), each delay path may be associated with a different Doppler spectrum. However, if the path has a spectrum with more or less 1 main peak from the cluster, the spatial characteristics of the channel may resemble a Doppler shift rather than path spreading. Good channel prediction can be achieved, which can help improve downlink pre-decoding. In some instances, each path of a channel or delay may have a different Doppler spectrum. Ideally, each channel tap estimate (0)can be Weighted to obtain the where T is the lag between channel observation and PDSCH transmission. The delay-time channel impulse response taps for the transmit-receive antenna element pair (i, j) can be given by Represented as, where i is the base station transmit antenna index, j is the UE receive antenna index, l is the delay index, and n is the time index. To achieve this, the empirical time domain correlation of each channel tap for each transmit-receive antenna pair should be tracked. In some instances, only the phase component of the time domain correlation for each path may be tracked and averaged over the transmit-receive pair, which may be viewed as estimating the centroid of the Doppler spectrum for each path, which may require phase coherence of the SRS transmission. The aspects presented herein provide a configuration for a UE to provide a report on time domain channel characteristics measured via a TRS. A UE that reports time domain channel characteristics may allow a network entity to predict or extrapolate a downlink channel and a pre-decoder based on the time domain channel characteristics measured by the UE.
[0033] The detailed description set forth below in conjunction with the accompanying drawings is a description of various configurations and does not represent the only configurations in which the concepts described herein may be practiced. In order to provide a thorough understanding of the various concepts, the detailed description includes specific details. However, these concepts may be practiced without these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring these concepts.
[0034] Several aspects of the telecommunication system are also 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 such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0035] For example, an element or any part of an element or any combination of elements may 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 the various functions described in this disclosure. One or more processors in a processing system may execute software. Whether referred to as software, firmware, middleware, microcode, hardware description language, or other terms, software should be broadly interpreted as 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, processes, functions, or any combination thereof.
[0036] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions 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. By way of 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.
[0037] 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 can 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 practical environments, 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.
[0038] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a 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.
[0039] The aggregated base station can be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. The decomposed base station can 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 (CU), one or more distributed units (DU), or one or more radio units (RU). In some aspects, the CU can be implemented within a RAN node, and one or more DUs can be co-located with the CU, or alternatively, can be geographically or virtually distributed in one or more other RAN nodes. The DU can be implemented to communicate with one or more RUs. Each of the CU, DU, and RU can be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).
[0040] 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 configurations such as those 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 functionality across two or more units at various physical locations, as well as virtually distributing functionality of at least one unit, which may enable flexibility in network design. Individual units of a disaggregated base station or disaggregated RAN architecture may be configured for wired or wireless communication with at least one other unit.
[0041] 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, which 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.
[0042] 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 referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface 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 from one or more of the other units on a wired transmission medium or to send signals to one or more of the other units. In addition, these units may include a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) configured to receive signals from one or more of the other units on a wireless transmission medium or to send signals to one or more of the other units, or both.
[0043] 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 as having an interface configured to communicate signals with other control functions hosted by CU 110. CU110 may be configured to handle user plane functions (i.e., central unit-user plane (CU-UP)), control plane functions (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.
[0044] 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, demodulation, etc.) at least in part according to a functional split (such as a functional split defined by 3GPP). In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented with 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.
[0045] The lower layer functions 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, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the DU 130 and CU 110 to be implemented in a cloud-based RAN architecture (such as a vRAN architecture).
[0046] 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 instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 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. Additionally, 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 .
[0047] 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 communicate 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.
[0048] 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 creation of RAN management policies (such as A1 policies).
[0049] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Thus, 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 or may not be included in the base station 102). 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. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric for DL and UL (e.g., more or fewer carriers may be allocated for DL than for UL). The component carrier 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).
[0050] 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.
[0051] 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 or the like. 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.
[0052] 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 (interchangeably) referred to as the "sub-6 GHz" band in various documents and articles. A similar naming issue sometimes occurs with respect to FR2, which is often (interchangeably) referred to as the "millimeter wave" band in documents and articles, although different from the extremely high frequency (EHF) band (30 GHz–300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).
[0053] 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, and therefore 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.
[0054] In view of the above, unless otherwise specified, if the term "sub-6 GHz" or the like is used in this document, 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" or the like is used in this document, 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.
[0055] 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 different. The transmit direction and receive direction of the UE 104 may be the same or different.
[0056] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a transceiver base 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 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).
[0057] 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 shown 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, the LMF 166, the position determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurement and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the location of the UE 104. The NG-RAN may determine the location of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, position estimation, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the 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.
[0058] 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 constellation arrangement. One or more of these devices may access the network collectively and / or individually.
[0059] Reference again Figure 1 In certain aspects, the UE 104 may include a reporting component 198 configured to: receive a Doppler configuration to measure Doppler information for at least one of a plurality of channel paths; receive a TRS based on the Doppler configuration to obtain Doppler information for at least one of the plurality of channel paths; send a Doppler report based on the received TRS, the Doppler report including Doppler information for at least one of the plurality of channel paths; and receive a downlink transmission on a predicted channel and a pre-decoder, the predicted channel and the pre-decoder being based at least on the Doppler report.
[0060] Reference again Figure 1 In some aspects, the base station 102 may include a prediction component 199 configured to: send a Doppler configuration to measure Doppler information for at least one of a plurality of channel paths; send a TRS to allow measurement of Doppler information for at least one of a plurality of channel paths; receive a Doppler report based on the sent TRS, the Doppler report including Doppler information for at least one of a plurality of channel paths; predict a downlink channel and a pre-decoder based at least on the Doppler report; and send a downlink transmission on the predicted downlink channel and pre-decoder.
[0061] Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar areas such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.
[0062] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B is a diagram 230 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 2D FIG280 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 the 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 the 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 DL and UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The slot format is configured for the UE by a received slot format indicator (SFI) (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling). Note that the following description also applies to the 5G NR frame structure as TDD.
[0063] FIG. 2A to FIG. 2DThe 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 subframes of the same size (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 conventional or extended. For a conventional CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbols on the DL may be CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of slots within a subframe is based on the CP and the parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.
[0064]
[0065]
[0066] 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. Accordingly, 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. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, and parameter set μ=4 has a subcarrier spacing of 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a conventional CP is provided, where there are 14 symbols per slot and the parameter set μ=2, where there are 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 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).
[0067] A resource grid may be used to represent the frame structure. Each slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
[0068] 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 a 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).
[0069] Figure 2B Examples 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 specific 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 specific 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 called SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information not sent via the PBCH (such as the system information block (SIB)), and paging messages.
[0070] like Figure 2CAs 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 can 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 combs in the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.
[0071] Figure 2D Examples 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 be used to carry, among other things, buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.
[0072] Figure 33 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 functions. 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 functions 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 functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions 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 functions 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.
[0073] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transmission channel, forward error correction (FEC) decoding / decoding of the transmission channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 processes the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The decoded and modulated symbols can then be divided into parallel streams. Subsequently, each stream can be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to generate 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 based on reference signals and / or channel condition 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 with a corresponding spatial stream for transmission.
[0074] 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 functions 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 symbol on each subcarrier and the reference signal are recovered and demodulated by determining the signal constellation point most likely to be sent by the base station 310. These soft decisions can be based on the channel estimate 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 functions.
[0075] 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.
[0076] Similar to the functions described in conjunction with DL transmission performed by the base station 310, the controller / processor 359 provides RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transfer 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 functions 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.
[0077] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 to select 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 corresponding transmitters 354Tx. Each transmitter 354Tx may modulate an RF carrier with a corresponding spatial stream for transmission.
[0078] 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 corresponding antenna 320. Each receiver 318Rx recovers information modulated onto an RF carrier and provides the information to the RX processor 370.
[0079] 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.
[0080] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 Various aspects related to the reporting component 198.
[0081] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 The prediction component 199 combines various aspects.
[0082] In wireless communications, Rayleigh fading channels, such as but not limited to tapped delay line (TDL), extended pedestrian A (EPA) model, extended vehicular A (EVA) model, etc., may have the same or similar Doppler spectra for all paths. In some spatial channel models (e.g., clustered delay line (CDL)), each delay path may be associated with a different Doppler spectrum. However, if the paths have spectra with more or less 1 main peak from the cluster, the spatial characteristics of the channel may resemble a Doppler shift rather than spreading for the paths. Good channel prediction can be achieved, which can help improve downlink precoding. For example, refer to Figure 4A , diagram 400 provides an example of TDL-C at 300 ns, where the x-axis represents Doppler and the y-axis represents path index (eg, tap), and all taps in the time domain have the same Doppler distribution. However, at Figure 4B In a massive MIMO channel, the taps do not have the same Doppler distribution. Different taps have different Doppler distributions. In addition, Figure 4C The diagram 420 shows a Figure 4B Graph 410 of different implemented CDL models further illustrates that the taps do not have the same Doppler distribution.
[0083] In some instances, each path of a channel or delay may have a different Doppler spectrum. Ideally, each channel tap estimate (0)can be Weighted to obtain the where T is the lag between channel observation and PDSCH transmission. The delay-time channel impulse response taps for the transmit-receive antenna element pair (i, j) can be given by Denoted as , where i is the base station transmit antenna index, j is the UE receive antenna index, l is the delay index, and n is the time index. To achieve this, the empirical time domain correlation of each channel tap for each transmit-receive antenna pair should be tracked. In some instances, only the phase component of the time domain correlation for each path may be tracked and averaged over the transmit-receive pair, which can be viewed as estimating the centroid of the Doppler spectrum for each path, which may require phase coherence of the SRS transmission. The time average can be expressed as The phase is calculated in such a way that a sufficient time averaging is performed.
[0084] Aspects presented herein provide a configuration for a UE to provide a report of time domain channel characteristics measured via a TRS. A UE reporting time domain channel characteristics may allow a network entity to predict or extrapolate a downlink channel and a pre-decoder based on the time domain channel characteristics measured by the UE. At least one advantage of the present disclosure is that a downlink channel and a pre-decoder may be predicted based on the Doppler distribution.
[0085] Figure 5A A diagram 500 is provided that illustrates an example of channel and pre-decoder prediction. Diagram 500 includes time slot n 502, where a TRS 504 (e.g., a CSI-RS for tracking) is received in time slot n 502. An SRS 506 (e.g., H(n)) may be sent in time slot n 502. Prediction or extrapolation may occur so that the base station may send a PDSCH 508 in time slot n+k 510. The prediction or extrapolation may be based on the time domain correlation (e.g., Doppler shift) of the channel observed at time n (e.g., from the SRS 506) and the channel reported by the UE based on the TRS 506. The prediction or extrapolation may be based on the Doppler reciprocity between the downlink TRS 504 received by the UE and the uplink SRS 506 sent by the UE. Mapping may occur between downlink and uplink channel taps of the TRS and SRS.
[0086] Figure 5B A diagram 520 illustrating an example of channel and pre-decoder prediction is provided. Diagram 520 includes time slot n 502, where a TRS 504 (e.g., CSI-RS for tracking) is received in time slot n 502. CSI-RS 522 (e.g., H(n)) may be sent by a UE in time slot n 502. Prediction or extrapolation may occur based on at least the reported CSI 522. Predecoder prediction or extrapolation may be based on the reported CSI at time n and on the time domain correlation of the channel based on the received TRS 504. Figure 5B The prediction or extrapolation of is based on the codebook, where W(n) is the predicted precoder based at least on the reported CSI 522 (e.g., H(n)). The base station may send PDSCH 508 in time slot n+k 510 using the predicted precoder W(n+k).
[0087] Figure 6A diagram 600 is provided that illustrates an example of reciprocity-based downlink precoding. Extrapolation or prediction of the downlink channel and downlink precoder may be based on the main tap 602 or taps within a specified time window. The UE may report the average Doppler for each tap, which may help the base station extrapolate the phase and amplitude of the channel taps at future time slots (e.g., time slot n+k 604) for downlink PDSCH precoding (e.g., H(n+k)). The extrapolation may be done based on the Jakes Doppler of each tap or the Doppler shift of each tap (or each path). For example, the Jakes Doppler of each tap may be given by h l (n+T)=h l (n)×J0(2πf d (l), T) represents the Doppler spectrum of each tap of J0. In another example, the Doppler frequency shift of each path can be given by express.
[0088] For frequency domain channel extrapolation, the extrapolated channel H f The time domain correlation matrix (e.g., Rtt) of (n+T) can be based on the reported Doppler spectrum / frequency shift and Doppler power. For example, the time domain correlation matrix Rtt can be expressed as or
[0089] Figure 7 A diagram 700 is provided illustrating an example of codebook-based downlink precoding. In some instances, in addition to reporting path / tap Doppler within an UL channel (e.g., PUSCH 704), the UE can also help the base station extrapolate or predict the downlink precoder by providing a codebook (e.g., CSF report) based on CSI-RS 702. The precoder can be extrapolated in the frequency domain and can be obtained by The CSF report may include Doppler spectra at different frequencies (eg, F0, F1, F2).
[0090] Fig. 8AA diagram 800 illustrating an example of reciprocity downlink precoding is provided. Diagram 800 includes time slot n 802, wherein TRS 804 is received in time slot n 802. The UE may provide a Doppler report 806 via a PUCCH or a PUSCH. The Doppler report 806 may be based on the TRS measured by the UE in time slot n. In some aspects, the UE may send an SRS 808 in time slot m 810, wherein the SRS 808 identifies an uplink channel of the UE. The base station may extrapolate or predict a downlink channel and precoder for a future time slot (e.g., time slot n+k 814) based on at least the Doppler report 806 and / or the SRS 808. The base station may then send a downlink transmission (e.g., PDSCH 812) using the predicted channel and precoder (e.g., H(n+k)).
[0091] Figure 8B A diagram 820 illustrating an example of codebook-based downlink precoding is provided. Diagram 820 includes time slot n 802, where TRS 804 is received within time slot n 802. The UE may provide a Doppler report 806 via a PUCCH or a PUSCH. The Doppler report 806 may be based on the TRS measured by the UE within time slot n. In some aspects, the UE may receive a CSI-RS 822 from a base station, such that the UE measures the CSI-RS and sends a CSF report (e.g., a CSI report) 824 to the base station based on the measured CSI-RS 822. The base station may extrapolate or predict a downlink channel and precoder for a future time slot (e.g., time slot n+k814) based on at least the Doppler report 806 and / or the CSF report 824. The base station may then send a downlink transmission (e.g., a PDSCH 812) using the predicted channel and precoder (e.g., H(n+k)).
[0092] Fig. 9A diagram 900 is provided illustrating an example of a UE reporting the Doppler of each tap. In some instances, a time window 902 may be used to identify a channel path / tap. The time window 902 may be based on a downlink reference time, such as based on the first arrival path (e.g., t0). The length of the window may be configured via RRC signaling. In some instances, the length of the window may be based on a TRS (e.g., a CSI-RS for tracking configuration). The number of taps used for Doppler reporting may be configured via RRC signaling. For example, a tap may be identified based on a tap power (e.g., the strongest power) or based on a tap with a maximum Doppler value. The UE may report correlation in the time domain. For example, the UE may report the Doppler shift of the centroid of the Doppler spectrum for each path. In some aspects, the UE may report the maximum Doppler frequency. In some aspects, the UE may report multiple Doppler frequency values for each path or tap. In some aspects, the UE may report empirical correlations (e.g., E[h l (T)h l (0)]), where T is the time interval between observations (e.g., for TRS, T=4). The UE may report the tap position or index in the time domain and one or more Doppler frequencies for each tap (e.g., {ti, list{Fi, j}}). In some aspects, the UE may report the tap position, average Doppler, and relative power (e.g., {ti, list{Fi, j, Pij}}).
[0093] Fig.10A diagram 1000 illustrating an example of a CSI report configuration is provided. The CSI report configuration may include a new type of CSI for path Doppler reporting. The CSI report configuration may be linked to a CSI-RS resource setting (e.g., resourcesForChannelMeasurement 1002), which is a TRS (e.g., a non-zero power (NZP) CSI-RS set for tracking) or a positioning reference signal. In some aspects, the CSI report configuration may include a quantity separated from an existing precoding matrix indicator (PMI), channel quality information (CQI), CSI-RS resource indicator (CRI), or layer indicator (LI) in the report configuration. For example, the CSI report configuration may include the quantity PerPath-Doppler 1004. The quantity PerPath-Doppler 1004 may include a report of Doppler shifts for N paths and a time index for each path. For example, if N is not configured, N=1 may be the default case. The UE may indicate the path index of the strongest Doppler to the base station based on a power spectrum perspective. The UE may report the differential Doppler for the average Doppler or the maximum Doppler. In some aspects, the CSI reporting configuration may include the quantity PerPath-Doppler and Power 1006. The quantity PerPath-Doppler and Power 1006 may include reporting of the Doppler shift for the N paths, the time index for each path, and the relative power for each Doppler value.
[0094] Fig.11 A diagram 1100 is provided illustrating an example of measurement averaging for Doppler shift reporting. In some instances, Doppler measurements may be filtered. For example, Doppler averaging and measurement filtering may be based on a single shot or multiple shots. In some aspects, a time domain window 1102 may be defined in which the UE may coherently average the measurements. For example, the time domain window 1102 may include 2 time slots for FR1. In some aspects, coherent averaging may be enabled or disabled via RRC signaling. A time limit may be configured to a single shot so that the Doppler estimate is not averaged. In some aspects, a time limit may not be configured so that multiple shots are utilized and the UE may be allowed to use a previous reference signal from a previous measurement to enhance the estimated Doppler frequency value.
[0095] Fig.12 1200 is a call flow diagram of signaling between a UE 1202 and a network entity (eg, a base station) 1204. The UE 1202 may be configured to communicate with the base station 1204. For example, in Figure 1 In the context of , base station 1204 may correspond to base station 102. Further, UE 1202 may correspond to at least UE 104. In another example, in Figure 3In the context of , base station 1204 may correspond to base station 310 and UE 1202 may correspond to UE 350.
[0096] At 1206, the base station 1204 may send a Doppler configuration to the UE 1202. The UE 1202 may receive the Doppler configuration from the base station 1204. The UE 1202 may receive the Doppler configuration to measure Doppler information for at least one channel path of the plurality of channel paths. In some aspects, the Doppler configuration may be sent via RRC signaling.
[0097] At 1208, the base station 1204 may send a TRS to the UE 1202. The UE 1202 may receive the TRS from the base station 1204. The base station may send the TRS to allow the UE to measure the TRS for Doppler information for at least one of the multiple channel paths. The UE may receive the TRS to obtain Doppler information for at least one of the multiple channel paths. The UE may receive the TRS based on the Doppler configuration to obtain Doppler information for at least one of the multiple channel paths. In some aspects, the TRS may be measured within a configured time window or an indicated time window to identify at least one of the multiple channel paths. The configured time window or the indicated time window may include a start time based on a downlink reference time. The length of the configured time window or the indicated time window may be configured by the Doppler configuration. In some aspects, the Doppler information may be obtained based on an average of multiple measurements of the Doppler frequency within a time domain window spanning one or more time slots. In some aspects, the Doppler information may be obtained based on whether the time limit is enabled or disabled. In some aspects, the Doppler information may be enabled in response to the time limit being not averaged. In some aspects, Doppler information may be averaged in response to the time limit being disabled.
[0098] At 1210, UE 1202 may send a Doppler report to base station 1204 based on the TRS measurement. Base station 1204 may receive the Doppler report from UE 1202. The Doppler report may include Doppler information for at least one of the multiple channel paths. The Doppler report may include Doppler information for at least one of the multiple channel paths based on the received TRS. In some aspects, the Doppler report may include at least one of the following: an average Doppler shift or Doppler spectrum centroid for at least one channel path, a maximum Doppler frequency for at least one channel path, at least one Doppler frequency value for at least one channel path, or a correlation between multiple observations of at least one channel path, wherein each observation is separated by a time interval. In some aspects, the Doppler report may be sent on a PUCCH or a PUSCH.
[0099] At 1212, UE 1202 may send an SRS identifying an uplink channel of the UE. The UE may send the SRS to base station 1204. Base station 1204 may receive the SRS from UE 1202. In some aspects, the predicted channel and pre-decoder may be based at least on Doppler reciprocity between the TRS and the SRS. The predicted pre-decoder may include a phase and amplitude of a channel tap at a future time slot.
[0100] At 1214, the base station 1204 may send a channel state information reference signal (CSI-RS) to the UE 1202 for the UE to measure the downlink channel and report a CSI report. The UE 1202 may receive the CSI-RS signal from the base station 1204. The UE 1202 may measure the CSI-RS signal received from the base station 1204.
[0101] At 1216, UE 1202 may send a channel state feedback (CSF) report (e.g., a CSI report) to base station 1204. Base station 1204 may receive the CSF report from UE 1202. The UE may send a channel state feedback report based on the measured CSI-RS. In some aspects, the CSF report may include a CSI report configuration, wherein the resources used for channel measurement are configured as NZP CSI-RS for tracking. The CSI report configuration may include a report amount set to the Doppler of each path or set to the Doppler and power of each path. In some aspects, the report amount set to the Doppler of each path may include the Doppler frequency for one or more channel paths and the time index for one or more channel paths. In some aspects, the report amount set to the Doppler of each path may include the path index with the strongest Doppler power spectrum, which identifies the channel alignment between the UE and the base station. In some aspects, the report amount set to the Doppler and power of each path may include one or more Doppler frequencies for each channel path in one or more channel paths, the time index for the one or more channel paths, and the relative power of each Doppler frequency value. In some aspects, codebook based downlink precoding may be predicted based on at least a CSF report and a Doppler report.
[0102] At 1218, the base station 1204 may predict the downlink channel and precoder. The base station may predict the downlink channel and precoder based at least on the Doppler report.
[0103] At 1220, the base station 1204 may send a downlink transmission on the predicted downlink channel and precoder. The base station may send the downlink transmission on the predicted channel and precoder to the UE 1202. The UE 1202 may receive the downlink transmission on the predicted channel and precoder from the base station 1204. The predicted channel and precoder may be based on at least the Doppler report.
[0104] Fig.13 1300 is a flow chart of a wireless communication method. The method may be performed by a UE (eg, UE 104; device 1504). One or more of the operations shown may be omitted, reversed in order, or performed simultaneously. The method may allow the UE to report time domain channel characteristics measured from the TRS.
[0105] At 1302, a UE may receive a Doppler configuration. For example, 1302 may be performed by a reporting component 198 of an apparatus 1504. The UE may receive the Doppler configuration from a base station. The UE may receive the Doppler configuration to measure Doppler information for at least one channel path of a plurality of channel paths. In some aspects, the Doppler configuration may be received via RRC signaling.
[0106] At 1304, the UE may receive a TRS to obtain Doppler information. For example, 1304 may be performed by the reporting component 198 of the device 1504. The UE may receive a TRS from a base station. The UE may receive a TRS to obtain Doppler information for at least one of the multiple channel paths. The UE may receive a TRS based on a Doppler configuration to obtain Doppler information for at least one of the multiple channel paths. In some aspects, the TRS may be measured within a configured time window or an indicated time window to identify at least one of the multiple channel paths. The configured time window or the indicated time window may include a start time based on a downlink reference time. The length of the configured time window or the indicated time window may be configured by the Doppler configuration. In some aspects, the Doppler information may be obtained based on an average of multiple measurements of Doppler frequencies within a time domain window spanning one or more time slots. In some aspects, the Doppler information may be obtained based on whether a time limit is enabled or disabled. In some aspects, the Doppler information may not be averaged in response to the time limit being enabled. In some aspects, the Doppler information may be averaged in response to the time limit being disabled.
[0107] At 1306, the UE may send a Doppler report. For example, 1306 may be performed by the reporting component 198 of the device 1504. The UE may send a Doppler report to the base station based on the TRS measurement. The Doppler report may include Doppler information for at least one of the multiple channel paths. The Doppler report may include Doppler information for at least one of the multiple channel paths based on the received TRS. In some aspects, the Doppler report may include at least one of the following: an average Doppler shift or Doppler spectrum centroid for at least one channel path, a maximum Doppler frequency for at least one channel path, at least one Doppler frequency value for at least one channel path, or a correlation between multiple observations of at least one channel path, wherein each observation is separated by a time interval. In some aspects, the Doppler report may be sent on a PUCCH or a PUSCH.
[0108] At 1308, the UE may receive a downlink transmission on the predicted channel and precoder. For example, 1308 may be performed by reporting component 198 of apparatus 1504. The UE may receive a downlink transmission from a base station on the predicted channel and precoder. The predicted channel and precoder may be based at least on the Doppler report.
[0109] Fig.14 1400 is a flow chart of a method of wireless communication. The method may be performed by a UE (eg, UE 104; device 1504). One or more of the operations shown may be omitted, reversed in order, or performed simultaneously. The method may allow the UE to report time domain channel characteristics measured from the TRS.
[0110] At 1402, a UE may receive a Doppler configuration. For example, 1402 may be performed by a reporting component 198 of an apparatus 1504. The UE may receive the Doppler configuration from a base station. The UE may receive the Doppler configuration to measure Doppler information for at least one channel path of a plurality of channel paths. In some aspects, the Doppler configuration may be received via RRC signaling.
[0111] At 1404, the UE may receive a TRS to obtain Doppler information. For example, 1404 may be performed by the reporting component 198 of the device 1504. The UE may receive a TRS from a base station. The UE may receive a TRS to obtain Doppler information for at least one of the multiple channel paths. The UE may receive a TRS based on a Doppler configuration to obtain Doppler information for at least one of the multiple channel paths. In some aspects, the TRS may be measured within a configured time window or an indicated time window to identify at least one of the multiple channel paths. The configured time window or the indicated time window may include a start time based on a downlink reference time. The length of the configured time window or the indicated time window may be configured by the Doppler configuration. In some aspects, the Doppler information may be obtained based on an average of multiple measurements of Doppler frequencies within a time domain window spanning one or more time slots. In some aspects, the Doppler information may be obtained based on whether a time limit is enabled or disabled. In some aspects, the Doppler information may not be averaged in response to the time limit being enabled. In some aspects, the Doppler information may be averaged in response to the time limit being disabled.
[0112] At 1406, the UE may send a Doppler report. For example, 1406 may be performed by the reporting component 198 of the device 1504. The UE may send a Doppler report to the base station based on the TRS measurement. The Doppler report may include Doppler information for at least one of the multiple channel paths. The Doppler report may include Doppler information for at least one of the multiple channel paths based on the received TRS. In some aspects, the Doppler report may include at least one of the following: an average Doppler shift or Doppler spectrum centroid for at least one channel path, a maximum Doppler frequency for at least one channel path, at least one Doppler frequency value for at least one channel path, or a correlation between multiple observations of at least one channel path, wherein each observation is separated by a time interval. In some aspects, the Doppler report may be sent on a PUCCH or a PUSCH.
[0113] At 1408, the UE may send an SRS identifying an uplink channel of the UE. For example, 1408 may be performed by reporting component 198 of apparatus 1504. The UE may send the SRS to a base station. In some aspects, the predicted channel and precoder may be based at least on Doppler reciprocity between the TRS and the SRS.
[0114] At 1410, the UE can measure the CSI-RS. For example, 1410 can be performed by the reporting component 198 of the device 1504. The UE can measure the CSI-RS from the base station to measure the downlink channel and report the CSI report.
[0115] At 1412, the UE may send a channel state feedback (CSF) report (e.g., a CSI report). For example, 1412 may be performed by the reporting component 198 of the device 1504. The UE may send a channel state feedback report to a base station. The UE may send a channel state feedback report based on the measured CSI-RS. In some aspects, the CSF report may include a CSI report configuration, in which the resources used for channel measurement are configured as NZP CSI-RS for tracking. The CSI report configuration may include a report amount set to the Doppler of each path or set to the Doppler and power of each path. In some aspects, the report amount set to the Doppler of each path may include a Doppler frequency for one or more channel paths and a time index for one or more channel paths. In some aspects, the report amount set to the Doppler of each path may include a path index with the strongest Doppler power spectrum, which identifies the channel alignment between the UE and the network node. In some aspects, the report amount set to the Doppler and power of each path may include one or more Doppler frequencies for each channel path in one or more channel paths, a time index for one or more channel paths, and a relative power of each Doppler frequency value.
[0116] At 1414, the UE may receive a downlink transmission on the predicted channel and precoder. For example, 1414 may be performed by reporting component 198 of device 1504. The UE may receive a downlink transmission from a base station on the predicted channel and precoder. The predicted channel and precoder may be based on at least a Doppler report.
[0117] Fig.151500 is an example of a hardware implementation of an example device 1504. The device 1504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 1504 may include a cellular baseband processor 1524 (also referred to as a modem) coupled to one or more transceivers 1522 (e.g., a cellular RF transceiver). The cellular baseband processor 1524 may include on-chip memory 1524'. In some aspects, the device 1504 may also include one or more subscriber identity module (SIM) cards 1520 and an application processor 1506 coupled to a secure digital (SD) card 1508 and a screen 1510. The application processor 1506 may include on-chip memory 1506'. In some aspects, the device 1504 may also include a Bluetooth module 1512, a WLAN module 1514, an SPS module 1516 (e.g., a GNSS module), one or more sensor modules 1518 (e.g., an atmospheric pressure sensor / altimeter; a motion sensor such as an inertial management unit (IMU), a gyroscope, and / or an accelerometer; light detection and ranging (LIDAR), radio-aided detection and ranging (RADAR), sound navigation and ranging (SONAR), a magnetometer, audio, and / or other technologies for positioning), an additional memory module 1526, a power source 1530, and / or a camera 1532. The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include an on-chip transceiver (TRX) (or, in some cases, only a receiver (RX)). The Bluetooth module 1512, the WLAN module 1514, and the SPS module 1516 may include their own dedicated antennas and / or communicate using an antenna 1580. The cellular baseband processor 1524 communicates with the UE 104 and / or with the RU associated with the network entity 1502 through the transceiver 1522 via one or more antennas 1580. The cellular baseband processor 1524 and the application processor 1506 may each include a computer-readable medium / memory 1524', 1506', respectively. The additional memory module 1526 may also be considered a computer-readable medium / memory. Each computer-readable medium / memory 1524', 1506', 1526 may be non-transitory. The cellular baseband processor 1524 and the application processor 1506 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software, when executed by the cellular baseband processor 1524 / application processor 1506, enables the cellular baseband processor 1524 / application processor 1506 to perform the various functions described above. The computer-readable medium / memory may also be used to store data manipulated by the cellular baseband processor 1524 / application processor 1506 when executing the software.The cellular baseband processor 1524 / application processor 1506 may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. In one configuration, the device 1504 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1524 and / or the application processor 1506, while in another configuration, the device 1504 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1504.
[0118] As discussed above, component 198 is configured to: receive a Doppler configuration to measure Doppler information for at least one of a plurality of channel paths; receive a TRS based on the Doppler configuration to obtain Doppler information for at least one of a plurality of channel paths; send a Doppler report based on the received TRS, the Doppler report including Doppler information for at least one of a plurality of channel paths; and receive a downlink transmission on a predicted channel and a pre-decoder, the predicted channel and the pre-decoder being based at least on the Doppler report. Component 198 may be within cellular baseband processor 1524, application processor 1506, or both cellular baseband processor 1524 and application processor 1506. Component 198 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 thereof. As shown, apparatus 1504 may include a variety of components configured for various functions. In one configuration, the device 1504 (particularly the cellular baseband processor 1524 and / or the application processor 1506) includes a component for receiving a Doppler configuration to measure Doppler information for at least one of a plurality of channel paths. The device includes a component for receiving a TRS based on the Doppler configuration to obtain Doppler information for at least one of a plurality of channel paths. The device includes a component for sending a Doppler report based on the received TRS, the Doppler report including Doppler information for at least one of a plurality of channel paths. The device includes a component for receiving a downlink transmission on a predicted channel and a pre-decoder, the predicted channel and the pre-decoder being based at least on the Doppler report. The device also includes a component for sending an SRS identifying an uplink channel of the UE. The predicted channel and the pre-decoder are based on Doppler reciprocity between the TRS and the SRS. The device also includes a component for measuring a CSI-RS. The device also includes a component for sending a CSF report based on the measured CSI-RS. The means may be a component 198 of the apparatus 1504 configured to perform the functions recited by the means. As described above, the apparatus 1504 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, the means may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the means.
[0119] Fig.161600 is a flow chart of a method of wireless communication. The method may be performed by a base station (e.g., base station 102; network entity 1802. One or more of the operations shown may be omitted, reversed, or performed simultaneously. The method may allow the network entity to predict or extrapolate a downlink channel and a pre-decoder based on time domain channel characteristics measured by a UE.
[0120] At 1602, the network entity may send a Doppler configuration. For example, 1602 may be performed by a prediction component 199 of the network entity 1802. The network entity may send the Doppler configuration to the UE. The network entity may send the Doppler configuration to measure Doppler information for at least one channel path of a plurality of channel paths. In some aspects, the Doppler configuration may be sent via RRC signaling.
[0121] At 1604, the network entity may send a TRS. For example, 1604 may be performed by the prediction component 199 of the network entity 1802. The network entity may send the TRS to the UE. The network entity may send the TRS to allow measurement of Doppler information for at least one channel path of a plurality of channel paths.
[0122] At 1606, the network entity may receive a Doppler report. For example, 1606 may be performed by the prediction component 199 of the network entity 1802. The network entity may receive the Doppler report from the UE. The Doppler report may include Doppler information for at least one of the multiple channel paths based on the transmitted TRS. In some aspects, the Doppler report may include at least one of the following: an average Doppler shift or a Doppler spectrum centroid for the at least one channel path, a maximum Doppler frequency for the at least one channel path, at least one Doppler frequency value for the at least one channel path, or a correlation between multiple observations of the at least one channel path, wherein each observation is separated by a time interval. In some aspects, the Doppler report may be received on a PUCCH or a PUSCH.
[0123] At 1608, the network entity may predict a downlink channel and a precoder. For example, 1608 may be performed by a prediction component 199 of the network entity 1802. The network entity may predict a downlink channel and a precoder based at least on the Doppler report.
[0124] At 1610, the network entity may send a downlink transmission on the predicted downlink channel and precoder. For example, 1610 may be performed by prediction component 199 of network entity 1802. The network entity may send a downlink transmission to the UE on the predicted channel and precoder.
[0125] Fig.171700 is a flow chart of a method of wireless communication. The method may be performed by a base station (e.g., base station 102; network entity 1802. One or more of the operations shown may be omitted, reversed, or performed simultaneously. The method may allow the network entity to predict or extrapolate a downlink channel and a pre-decoder based on time domain channel characteristics measured by a UE.
[0126] At 1702, the network entity may send a Doppler configuration. For example, 1702 may be performed by a prediction component 199 of the network entity 1802. The network entity may send the Doppler configuration to the UE. The network entity may send the Doppler configuration to measure Doppler information for at least one channel path in a plurality of channel paths. In some aspects, the Doppler configuration may be sent via RRC signaling.
[0127] At 1704, the network entity may send a TRS. For example, 1704 may be performed by the prediction component 199 of the network entity 1802. The network entity may send the TRS to the UE. The network entity may send the TRS to allow measurement of Doppler information for at least one channel path of a plurality of channel paths.
[0128] At 1706, the network entity may receive a Doppler report. For example, 1706 may be performed by a prediction component 199 of the network entity 1802. The network entity may receive a Doppler report from a UE. The Doppler report may include Doppler information for at least one of the multiple channel paths based on the transmitted TRS. In some aspects, the Doppler report may include at least one of the following: an average Doppler shift or a Doppler spectrum centroid for the at least one channel path, a maximum Doppler frequency for the at least one channel path, at least one Doppler frequency value for the at least one channel path, or a correlation between multiple observations of the at least one channel path, wherein each observation is separated by a time interval. In some aspects, the Doppler report may be received on a PUCCH or a PUSCH.
[0129] At 1708, the network entity may receive an SRS identifying an uplink channel of the UE. For example, 1708 may be performed by a prediction component 199 of the network entity 1802. The network entity may receive the SRS from the UE. In some aspects, the predicted downlink channel and pre-decoder may be based at least on Doppler reciprocity between the TRS and the SRS. In some aspects, the pre-decoder may be predicted based at least on the SRS. The predicted pre-decoder may include a phase and amplitude of a channel tap at a future time slot.
[0130] At 1710, the network entity may send a CSI-RS. For example, 1710 may be performed by the prediction component 199 of the network entity 1802. The network entity may send the CSI-RS to the UE for the UE to measure the downlink channel and report the CSI report.
[0131] At 1712, the network entity may receive a CSF report (e.g., a CSI report) based on the transmitted CSI-RS. For example, 1712 may be performed by the prediction component 199 of the network entity 1802. The network entity may receive a CSF report from the UE. In some aspects, the CSF report may include a CSI report configuration, wherein the resources for channel measurement are configured as NZP CSI-RS for tracking. The CSI report configuration may include a report amount set to the Doppler of each path or set to the Doppler and power of each path. In some aspects, the report amount set to the Doppler of each path may include a Doppler frequency for one or more channel paths and a time index for one or more channel paths. In some aspects, the report amount set to the Doppler of each path may include a path index with the strongest Doppler power spectrum, which identifies the channel alignment between the UE and the network node. In some aspects, the report amount set to the Doppler and power of each path may include one or more Doppler frequencies for each channel path in one or more channel paths, a time index for one or more channel paths, and a relative power of each Doppler frequency value. In some aspects, codebook based downlink precoding may be predicted based on at least a CSF report and a Doppler report.
[0132] At 1714, the network entity may predict a downlink channel and a precoder. For example, 1714 may be performed by a prediction component 199 of the network entity 1802. The network entity may predict a downlink channel and a precoder based at least on the Doppler report.
[0133] The network entity may send a downlink transmission on the predicted downlink channel and precoder at 1716. For example, 1716 may be performed by prediction component 199 of network entity 1802. The network entity may send a downlink transmission to the UE on the predicted channel and precoder.
[0134] Fig.181800 is a diagram illustrating an example of a hardware implementation for a network entity 1802. The network entity 1802 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1802 may include at least one of a CU 1810, a DU 1830, or a RU 1840. For example, depending on the layer functionality handled by the component 199, the network entity 1802 may include a CU 1810; both the CU 1810 and the DU 1830; each of the CU 1810, the DU 1830, and the RU 1840; the DU 1830; both the DU 1830 and the RU 1840; or the RU 1840. The CU 1810 may include a CU processor 1812. The CU processor 1812 may include an on-chip memory 1812'. In some aspects, the CU 1810 may also include an additional memory module 1814 and a communication interface 1818. CU 1810 communicates with DU 1830 via a midhaul link such as an F1 interface. DU 1830 may include a DU processor 1832. DU processor 1832 may include on-chip memory 1832'. In some aspects, DU 1830 may also include additional memory modules 1834 and communication interfaces 1838. DU 1830 communicates with RU 1840 via a fronthaul link. RU 1840 may include a RU processor 1842. RU processor 1842 may include on-chip memory 1842'. In some aspects, RU 1840 may also include additional memory modules 1844, one or more transceivers 1846, antennas 1880, and communication interfaces 1848. RU 1840 communicates with UE 104. On-chip memories 1812', 1832', 1842' and additional memory modules 1814, 1834, 1844 may each be considered a computer-readable medium / memory. Each computer readable medium / memory may be non-transitory. Each of processors 1812, 1832, 1842 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.
[0135] As discussed above, component 199 is configured to: send a Doppler configuration to measure Doppler information for at least one of a plurality of channel paths; send a TRS to allow measurement of Doppler information for at least one of a plurality of channel paths; receive a Doppler report based on the sent TRS, the Doppler report including Doppler information for at least one of a plurality of channel paths; predict a downlink channel and a pre-decoder based at least on the Doppler report; and send a downlink transmission on the predicted downlink channel and pre-decoder. Component 199 may be within one or more processors of one or more of CU 1810, DU 1830, and RU 1840. 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 thereof. Network entity 1802 may include a variety of components configured for various functions. In one configuration, the network entity 1802 includes a component for sending a Doppler configuration to measure Doppler information for at least one of a plurality of channel paths. The network entity includes a component for sending a TRS to allow measurement of Doppler information for at least one of a plurality of channel paths. The network entity includes a component for receiving a Doppler report based on the sent TRS, the Doppler report including Doppler information for at least one of a plurality of channel paths. The network entity includes a component for predicting a downlink channel and a pre-decoder based at least on the Doppler report. The network entity includes a component for sending a downlink transmission on the predicted downlink channel and the pre-decoder. The network entity also includes a component for receiving an SRS identifying an uplink channel of a UE. The predicted downlink channel and the pre-decoder may be based at least on Doppler reciprocity between the TRS and the SRS. The network entity also includes a component for sending a CSI-RS. The network entity also includes a component for receiving a CSF report based on the sent CSI-RS. The component may be a component 199 of the network entity 1802 configured to perform the functions recorded by the component. As described above, the network entity 1802 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, the means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.
[0136] 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 can be rearranged based on design preferences. Further, some blocks can be combined or omitted. The attached method claims provide the elements of each block in a sample order, but are not limited to the specific order or hierarchy provided.
[0137] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the 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 an action will occur if a condition is met, but no specific or immediate time limit is required for the occurrence of an action. The wording "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 an advantage 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 include 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, data can be directly received / sent between the first device and the second device, or data can be indirectly received / sent between the first device and the second device by a collection of devices. All structural and functional equivalents known to those of ordinary skill in the art or later that are known to the elements of the various aspects described in this disclosure are expressly incorporated herein by reference, and are covered by the claims. In addition, anything disclosed herein is not intended to be dedicated to the public, regardless of whether such disclosures are explicitly stated in the claims. "Module", "mechanism", "element", "equipment" and other words cannot replace the word "component". Therefore, no claim element will be understood as a functional component unless the element is explicitly recorded using the phrase "component for...".
[0138] 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.
[0139] The following aspects are merely illustrative and may be combined with other aspects or teachings described herein, but are not limiting.
[0140] Aspect 1 is a method for performing wireless communications at a UE, the method comprising: receiving a Doppler configuration to measure Doppler information for at least one channel path among a plurality of channel paths; receiving a TRS based on the Doppler configuration to obtain the Doppler information for the at least one channel path among the plurality of channel paths; sending a Doppler report based on the received TRS, the Doppler report including the Doppler information for the at least one channel path among the plurality of channel paths; and receiving a downlink transmission on a predicted channel and a pre-decoder, the predicted channel and the pre-decoder being based at least on the Doppler report.
[0141] Aspect 2 is a method according to aspect 1, the method further comprising: receiving the Doppler configuration via RRC signaling.
[0142] Aspect 3 is a method according to any one of aspects 1 and 2, the method further comprising: measuring the TRS within a configured or indicated time window to identify the at least one channel path among the multiple channel paths.
[0143] Aspect 4 is a method according to any one of Aspects 1 to 3, the method further comprising: the configured or indicated time window comprises a start time based on a downlink reference time, wherein the length of the configured or indicated time window is configured by the Doppler configuration.
[0144] Aspect 5 is a method according to any one of Aspects 1 to 4, the method further comprising: the Doppler report comprises at least one of the following: an average Doppler frequency shift or a Doppler spectrum centroid for the at least one channel path, a maximum Doppler frequency for the at least one channel path, at least one Doppler frequency value for the at least one channel path, or a correlation between multiple observations of the at least one channel path, wherein each observation is separated by a time interval.
[0145] Aspect 6 is a method according to any one of aspects 1 to 5, wherein the method further comprises: sending the Doppler report on a PUCCH or a PUSCH.
[0146] Aspect 7 is a method according to any one of aspects 1 to 6, the method further comprising: sending an SRS identifying an uplink channel of the UE, wherein the predicted channel and the pre-decoder are based at least on Doppler reciprocity between the TRS and the SRS.
[0147] Aspect 8 is a method according to any one of aspects 1 to 7, the method further comprising: measuring a CSI-RS; and sending a CSF report based on the measured CSI-RS.
[0148] Aspect 9 is a method according to any one of Aspects 1 to 8, the method further comprising: the CSF report includes a CSI report configuration, wherein the resources used for channel measurement are configured as NZP CSI-RS for tracking, and the CSI report configuration includes a reporting amount set to the Doppler of each path or set to the Doppler and power of each path.
[0149] Aspect 10 is a method according to any one of aspects 1 to 9, the method further comprising: the reporting amount set as the Doppler of each path includes a Doppler frequency for one or more channel paths and a time index for the one or more channel paths.
[0150] Aspect 11 is a method according to any one of Aspects 1 to 10, the method further comprising: the reported amount of Doppler set to each path includes a path index having the strongest Doppler power spectrum, the path index identifying the channel alignment between the UE and the network node.
[0151] Aspect 12 is a method according to any one of Aspects 1 to 11, the method further comprising: the reported quantity set to be the Doppler and power of each path includes one or more Doppler frequencies for each channel path in one or more channel paths, a time index for the one or more channel paths, and the relative power of each Doppler frequency value.
[0152] Aspect 13 is a method according to any one of aspects 1 to 12, the method further comprising: obtaining the Doppler information based on an average of multiple measurements of Doppler frequency within a time domain window spanning one or more time slots.
[0153] Aspect 14 is a method according to any one of Aspects 1 to 13, the method further comprising: obtaining the Doppler information based on whether the time limit is enabled or disabled, wherein the Doppler information is not averaged in response to the time limit being enabled, and wherein the Doppler information is averaged in response to the time limit being disabled.
[0154] Aspect 15 is an apparatus for wireless communication at a UE, the apparatus comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor being configured to implement any one of aspects 1 to 14.
[0155] Aspect 16 is an apparatus for wireless communication at a UE, the apparatus comprising means for implementing any one of aspects 1 to 14.
[0156] Aspect 17 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 1 to 14.
[0157] Aspect 18 is a method for performing wireless communications at a network node, the method comprising: sending a Doppler configuration to measure Doppler information for at least one channel path among a plurality of channel paths; sending a TRS to allow measurement of the Doppler information for the at least one channel path among the plurality of channel paths; receiving a Doppler report based on the sent TRS, the Doppler report including the Doppler information for the at least one channel path among the plurality of channel paths; predicting a downlink channel and a pre-decoder based at least on the Doppler report; and sending a downlink transmission on the predicted downlink channel and the pre-decoder.
[0158] Aspect 19 is a method according to aspect 18, the method further comprising: sending the Doppler configuration via RRC signaling.
[0159] Aspect 20 is a method according to any one of Aspects 18 and 19, the method further comprising: the Doppler report includes at least one of the following: an average Doppler frequency shift or a Doppler spectrum centroid for the at least one channel path, a maximum Doppler frequency for the at least one channel path, at least one Doppler frequency value for the at least one channel path, or a correlation between multiple observations of the at least one channel path, wherein each observation is separated by a time interval.
[0160] Aspect 21 is a method according to any one of aspects 18 to 20, the method further comprising: receiving the Doppler report on a PUCCH or a PUSCH.
[0161] Aspect 22 is a method according to any one of aspects 18 to 21, the method further comprising: receiving an SRS identifying an uplink channel of a UE, wherein the predicted downlink channel and the predecoder are based at least on Doppler reciprocity between the TRS and the SRS.
[0162] Aspect 23 is a method according to any one of aspects 18 to 22, the method further comprising: predicting the predecoder based at least on the SRS, wherein the predicted predecoder includes a phase and an amplitude of a channel tap at a future time slot.
[0163] Aspect 24 is a method according to any one of aspects 18 to 23, the method further comprising: transmitting a CSI-RS; and receiving a CSF report based on the transmitted CSI-RS.
[0164] Aspect 25 is a method according to any one of Aspects 18 to 24, the method further comprising: the CSF report includes a CSI report configuration, wherein the resources used for channel measurement are configured as NZP CSI-RS for tracking, and the CSI report configuration includes a reporting amount set to the Doppler of each path or set to the Doppler and power of each path.
[0165] Aspect 26 is a method according to any one of Aspects 18 to 25, the method further comprising: the reported amount set as the Doppler of each path includes a Doppler frequency for one or more channel paths and a time index for the one or more channel paths.
[0166] Aspect 27 is a method according to any one of Aspects 18 to 26, the method further comprising: the reported amount of Doppler set to each path includes a path index having the strongest Doppler power spectrum, the path index identifying the channel alignment between the UE and the network node.
[0167] Aspect 28 is a method according to any one of Aspects 18 to 27, the method further comprising: the reported quantity set to be the Doppler and power of each path includes one or more Doppler frequencies for each channel path in one or more channel paths, a time index for the one or more channel paths, and the relative power of each Doppler frequency value.
[0168] Aspect 29 is a method according to any one of aspects 18 to 28, the method further comprising: predicting codebook-based downlink pre-decoding based at least on the CSF report and the Doppler report.
[0169] Aspect 30 is an apparatus for wireless communication at a network node, the apparatus comprising at least one processor coupled to a memory and at least one transceiver, the at least one processor configured to implement any one of aspects 18 to 29.
[0170] Aspect 31 is an apparatus for wireless communication at a network node, the apparatus comprising means for implementing any one of aspects 18 to 29.
[0171] Aspect 32 is a computer-readable medium storing computer-executable code, wherein the code, when executed by a processor, causes the processor to implement any one of aspects 18 to 29.
Claims
1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: receiving a Doppler configuration to measure Doppler information for at least one channel path of a plurality of channel paths; receiving a tracking reference signal (TRS) based on the Doppler configuration to obtain the Doppler information for the at least one channel path of the plurality of channel paths; sending a Doppler report based on the received TRS, the Doppler report including the Doppler information for the at least one channel path of the plurality of channel paths; as well as A downlink transmission is received on a predicted channel and pre-decoder, the predicted channel and the pre-decoder being based at least on the Doppler report. 2 . The apparatus of claim 1 , further comprising a transceiver coupled to the at least one processor.
3. The apparatus of claim 1, wherein the Doppler configuration is received via radio resource control (RRC) signaling. 4 . The apparatus of claim 1 , wherein the TRS is measured within a configured or indicated time window to identify the at least one channel path among the plurality of channel paths.
5. The apparatus of claim 4, wherein the configured or indicated time window comprises a start time based on a downlink reference time, wherein a length of the configured or indicated time window is configured by the Doppler configuration.
6. The apparatus of claim 1, wherein the Doppler report comprises at least one of: an average Doppler frequency shift or a Doppler spectrum centroid for the at least one channel path, a maximum Doppler frequency of the at least one channel path, at least one Doppler frequency value for the at least one channel path, or A correlation is provided between a plurality of observations of the at least one channel path, wherein each observation is separated by a time interval.
7. The apparatus of claim 1, wherein the Doppler report is sent on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).
8. The apparatus of claim 1, wherein the at least one processor is further configured to: A sounding reference signal (SRS) is transmitted that identifies an uplink channel of the UE, wherein the predicted channel and the precoder are based at least on Doppler reciprocity between the TRS and the SRS.
9. The apparatus of claim 1 , wherein the at least one processor is further configured to: Measuring a channel state information reference signal (CSI-RS); and A channel state feedback (CSF) report is sent based on the measured CSI-RS.
10. The apparatus of claim 9, wherein the CSF report comprises a channel state information (CSI) reporting configuration, wherein resources for channel measurement are configured as non-zero power (NZP) channel state information reference signals (CSI-RS) for tracking, and the CSI reporting configuration comprises a reporting amount set to the Doppler of each path or set to the Doppler and power of each path.
11. The apparatus of claim 10, wherein the reported quantity set as the Doppler of each path comprises a Doppler frequency for one or more channel paths and a time index for the one or more channel paths.
12. The apparatus of claim 10, wherein the reported amount set as the Doppler for each path comprises a path index having a strongest Doppler power spectrum, the path index identifying a channel alignment between the UE and a network node.
13. An apparatus according to claim 10, wherein the reporting quantity set to the Doppler and power of each path includes one or more Doppler frequencies for each channel path in one or more channel paths, a time index for the one or more channel paths, and a relative power of each Doppler frequency value.
14. The apparatus of claim 1, wherein the Doppler information is obtained based on an average of multiple measurements of Doppler frequency within a time domain window spanning one or more time slots.
15. The apparatus of claim 1, wherein the Doppler information is obtained based on a time limit being enabled or disabled, wherein the Doppler information is not averaged in response to the time limit being enabled, and wherein the Doppler information is averaged in response to the time limit being disabled.
16. A method of wireless communication at a user equipment (UE), the method comprising: receiving a Doppler configuration to measure Doppler information for at least one channel path of a plurality of channel paths; receiving a tracking reference signal (TRS) based on the Doppler configuration to obtain the Doppler information for the at least one channel path of the plurality of channel paths; sending a Doppler report based on the received TRS, the Doppler report including the Doppler information for the at least one channel path of the plurality of channel paths; as well as A downlink transmission is received on a predicted channel and pre-decoder, the predicted channel and the pre-decoder being based at least on the Doppler report.
17. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and at least one processor coupled to the memory and based at least in part on the information stored in the memory, the at least one processor configured to: sending a Doppler configuration to measure Doppler information for at least one channel path of a plurality of channel paths; transmitting a tracking reference signal (TRS) to enable measurement of the Doppler information for the at least one channel path of the plurality of channel paths; receiving a Doppler report based on the transmitted TRS, the Doppler report comprising the Doppler information for the at least one channel path of the plurality of channel paths; predicting a downlink channel and a pre-decoder based at least on the Doppler report; as well as A downlink transmission is sent on the predicted downlink channel and the pre-decoder.
18. The apparatus of claim 17, further comprising a transceiver coupled to the at least one processor.
19. The apparatus of claim 17, wherein the Doppler configuration is sent via radio resource control (RRC) signaling.
20. The apparatus of claim 17, wherein the Doppler report comprises at least one of: an average Doppler frequency shift or a Doppler spectrum centroid for the at least one channel path, a maximum Doppler frequency of the at least one channel path, at least one Doppler frequency value for the at least one channel path, or A correlation is provided between a plurality of observations of the at least one channel path, wherein each observation is separated by a time interval.
21. The apparatus of claim 17, wherein the Doppler report is received on a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH).
22. The apparatus of claim 17, wherein the at least one processor is further configured to: A sounding reference signal (SRS) identifying an uplink channel of a user equipment (UE) is received, wherein the predicted downlink channel and the pre-decoder are based at least on Doppler reciprocity between the TRS and the SRS.
23. The apparatus of claim 22, wherein the pre-decoder is predicted based at least on the SRS, wherein the predicted pre-decoder comprises a phase and an amplitude of a channel tap at a future time slot.
24. The apparatus of claim 17, wherein the at least one processor is further configured to: transmitting a channel state information reference signal (CSI-RS); and A channel state feedback (CSF) report is received based on the transmitted CSI-RS.
25. An apparatus according to claim 24, wherein the CSF report includes a channel state information (CSI) reporting configuration, wherein the resources used for channel measurement are configured as non-zero power (NZP) channel state information reference signals (CSI-RS) for tracking, and the CSI reporting configuration includes a reporting amount set to the Doppler of each path or set to the Doppler and power of each path.
26. The apparatus of claim 25, wherein the reported quantity set as the Doppler of each path comprises a Doppler frequency for one or more channel paths and a time index for the one or more channel paths.
27. The apparatus of claim 25, wherein the reported quantity set to the Doppler of each path comprises a path index having a strongest Doppler power spectrum, the path index identifying a channel alignment between a user equipment (UE) and the network node.
28. An apparatus according to claim 25, wherein the reporting quantity set to the Doppler and power of each path includes one or more Doppler frequencies for each channel path in one or more channel paths, a time index for the one or more channel paths, and a relative power of each Doppler frequency value.
29. The apparatus of claim 24, wherein codebook-based downlink precoding is predicted based on at least the CSF report and the Doppler report.
30. A method for wireless communication at a network node, the method comprising: sending a Doppler configuration to measure Doppler information for at least one channel path of a plurality of channel paths; transmitting a tracking reference signal (TRS) to enable measurement of the Doppler information for the at least one channel path of the plurality of channel paths; receiving a Doppler report based on the transmitted TRS, the Doppler report comprising the Doppler information for the at least one channel path of the plurality of channel paths; predicting a downlink channel and a pre-decoder based at least on the Doppler report; as well as A downlink transmission is sent on the predicted downlink channel and the pre-decoder.
