TCI for customized non-codebook-based beams

Abstract

In some embodiments, an apparatus may be a UE or a base station configured to transmit a TCI indicating a non-codebook-based beam direction based on angle information, and transmit a data transmission via the non-codebook-based beam direction indicated in the TCI. In some aspects, the apparatus may be configured to receive a TCI indicating a non-codebook-based beam direction, and receive a data transmission transmitted via the non-codebook-based beam direction indicated in the TCI.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to beam management and beam reporting operations. Background Art

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

[0003] 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). 5GNR 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 communications (mMTC), and ultra-reliable low latency communications (URLLC). Certain aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. Further improvements to 5G NR technology are needed. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] A simplified summary of one or more aspects is presented below to provide a basic understanding of these aspects. This summary is not an extensive review of all contemplated aspects. This summary 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.

[0005] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be configured to send a transmit configuration indicator (TCI) indicating a non-codebook based beam direction to a wireless device based on at least one of quasi co-location (QCL) information or angle information. The apparatus may be further configured to send data to the wireless device via the non-codebook based beam direction indicated in the TCI.

[0006] In one aspect of the present disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus may be configured to receive a TCI indicating a non-codebook-based beam direction from a network node, and receive data transmission from the network node via the non-codebook-based beam direction indicated in the TCI.

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

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

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

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

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

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

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

[0014] Figure 4 Compressed sensing techniques applied to generate a sparse matrix of gain values ​​associated with a set of angles of departure (AoD) and angles of arrival (AoA) for communications between a UE and a base station are illustrated.

[0015] Figure 5A A set of quantized azimuth angle AoD (A-AoD) / elevation angle AoD (Z-AoD) for DL ​​communication at a base station according to some aspects of the present disclosure is illustrated.

[0016] Figure 5B A set of quantized azimuth angle AoA (A-AoA) / elevation angle AoA (Z-AoA) for DL ​​communication at a UE is illustrated.

[0017] Figure 6 is a call flow diagram illustrating a method of wireless communication according to some aspects of the present disclosure.

[0018] Figure 7 is a flow chart of a wireless communication method.

[0019] Figure 8 is a flow chart of a wireless communication method.

[0020] Fig. 9 is a flow chart of a wireless communication method.

[0021] Fig.10 is a flow chart of a wireless communication method.

[0022] Fig.11 is a diagram illustrating an example of a hardware implementation of an exemplary device.

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

[0024] In some aspects of wireless communication, a pair of network devices (e.g., base stations, UEs, or other wireless devices associated with a wireless network) may communicate via a set of directional beams. The pair of network devices may include a first network device configured with a first (preconfigured and / or known) beam codebook and a second network device with a second (preconfigured and / or known) beam codebook. In some aspects, the beam codebook may be associated with a fixed set of beam directions, such that the first beam codebook may be associated with a first number of preconfigured beam directions and the second beam codebook may be associated with a second number of preconfigured beam directions.

[0025] In some aspects, the pair of network devices including the first network device and the second network device may select a most appropriate pair of beams (e.g., beam directions) from the first beam codebook and the second beam codebook for communication between the first network device and the second network device. In some aspects, the selected most appropriate pair of beams may not represent an optimal set of beam directions that maximizes channel gain (e.g., using an optimal beam direction to maximize signal strength of communication). In some aspects, the inability to select the optimal set of beam directions may be based on a quantization of the first codebook beam directions and the second codebook beam directions. For example, a UE may include a first beam codebook based on a set of beams having azimuth intervals of ~90 degrees and elevation intervals of ~90 degrees, which may be associated with four different beam directions (e.g., (φ r ,θ r ) = {[-45,45],[-45,135],[45,45],[45,135]}). In some aspects, a base station (or other UE) may be associated with a finer quantization (e.g., azimuth spacing of 45 degrees, elevation spacing of 22.5 degrees, possibly with 32 different beam directions (e.g., (φr ,θ r )={[-78.75,22.5],[-78.75,67.5],…,[-56.25,112.5],…,[78.75,157.5]}).

[0026] In some aspects, the granularity of quantization may reduce the spectral efficiency of the communication below the theoretical maximum spectral efficiency.By introducing the use of non-codebook based beams, the apparatus and methods disclosed herein may provide higher spectral efficiency.

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

[0028] 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 these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

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

[0030] Therefore, in one or more example aspects, specific implementations and / or use cases, the described functions may be implemented with hardware, software, or any combination thereof. If implemented with 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. The storage medium may be any available medium that can be accessed by a computer. For 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.

[0031] 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, devices that enable artificial intelligence (AI), etc.). Although some examples may be specifically for use cases or applications, or may not be specifically for use cases or applications, the described examples may have a wide range of applicability. Various aspects, specific implementations and / or use cases may be in the range from chip-level or modular components to non-modular, non-chip-level specific implementations, and further to the range of aggregated, distributed or original equipment manufacturer (OEM) devices or systems in conjunction with one or more technologies herein. In some practical environments, the equipment in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the various aspects claimed and described. 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 / accumulators, 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.

[0032] The deployment of a communication system (such as a 5G NR system) can be arranged in a variety of ways using various components or constituent parts. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element, or a network equipment (such as a base station (BS), or one or more units (or one or more components) that perform base station functionality) can be implemented in an aggregated architecture or a 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.

[0033] A converged base station may be configured to utilize a radio protocol stack physically or logically integrated within a single RAN node. A decomposed base station may be configured to utilize a protocol stack physically or logically distributed between two or more units, such as one or more central or centralized units (CUs), one or more distributed units (DUs), or one or more radio units (RUs). In some aspects, a CU may be implemented within a RAN node, and one or more DUs may be co-located with the CU, or alternatively, may be geographically or virtually distributed in one or more other RAN nodes. A DU may be implemented to communicate with one or more RUs. Each of a CU, a DU, and a RU may be implemented as a virtual unit, i.e., a virtual central unit (VCU), a virtual distributed unit (VDU), or a virtual radio unit (VRU).

[0034] Base station operation or network design may take into account the aggregated nature of base station functionality. For example, a disaggregated base station may be used in an integrated access backhaul (IAB) network, an open radio access network (O-RAN (network configuration such as that initiated by the O-RAN Alliance)), or a virtualized radio access network (vRAN, also known as a cloud radio access network (C-RAN)). Decomposition may include distributing 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.

[0035] Figure 11 is a diagram 100 illustrating an example of a wireless communication system and an access network. The illustrated wireless communication system includes a disaggregated base station architecture. The disaggregated base station architecture may include one or more CUs 110 that may communicate directly with a core network 120 via a backhaul link, or indirectly with the core network 120 through one or more disaggregated base station units, such as a near real-time (near RT) RAN intelligent controller (RIC) 125 via an E2 link, or a non-real-time (non-RT) RIC 115 associated with a service management and orchestration (SMO) framework 105, or both. The CU 110 may communicate with one or more DUs 130 via corresponding midhaul links, such as an F1 interface. The DU 130 may communicate with one or more RUs 140 via corresponding fronthaul links. The RU 140 may communicate with corresponding UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 140.

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

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

[0038] DU 130 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 140. In some aspects, DU 130 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) depending at least in part on a functional split such as that defined by 3GPP. In some aspects, DU 130 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 130 or with control functions hosted by CU 110.

[0039] The lower layer functionality may be implemented by one or more RUs 140. In some deployments, the RUs 140 controlled by the DUs 130 may correspond to logical nodes that host 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 RUs 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RUs 140 may be controlled by the corresponding DUs 130. In some scenarios, this configuration may enable the implementation of the DUs 130 and CUs 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0040] The SMO framework 105 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 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 .

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

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

[0043] At least one of the CU 110, the DU 130, and the RU 140 may be referred to as a base station 102. Therefore, the base station 102 may include one or more of the CU 110, the DU 130, and the RU 140 (each component is indicated by a dotted line to indicate that each component may be included in the base station 102, or may not be included in the base station). The base station 102 provides an access point to the core network 120 for the UE 104. The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). Small cells include femto cells, pico cells, and micro cells. A network including both small cells and macro cells may be referred to as a heterogeneous network. A heterogeneous network may also include a home evolved Node B (eNB) (HeNB), which may provide services to a restricted group referred to as a closed subscriber group (CSG). The communication link between RU 140 and UE 104 may include uplink (UL) (also known as reverse link) transmission from UE 104 to RU 140 and / or downlink (DL) (also known as forward link) transmission from RU 140 to UE 104. The communication link may use multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming and / or transmission diversity. The communication link may pass through one or more carriers. For each carrier allocated in a carrier aggregation of up to YxMHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to YMHz (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 with respect to DL and UL (e.g., more or fewer carriers may be allocated to DL compared to 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).

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

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

[0046] 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 to 7.125 GHz) and FR2 (24.25 GHz to 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 to 300 GHz) identified as the "millimeter wave" band by the International Telecommunication Union (ITU).

[0047] 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.125 GHz to 24.25 GHz). 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.6 GHz. For example, three higher operating bands have been identified as frequency range designations FR2-2 (52.6 GHz to 71 GHz), FR4 (71 GHz to 114.25 GHz), and FR5 (114.25 GHz to 300 GHz). Each of these higher frequency bands falls within the EHF band.

[0048] In view of the above, unless otherwise specified, if the term "6 GHz or less" is used in this document, it can broadly refer to frequencies that may be less than 6 GHz, may be within FR1, or may include mid-band frequencies. In addition, unless otherwise specified, if the term "millimeter wave" is used in this document, it can 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.

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

[0050] The base station 102 may include and / or be referred to as a gNB, a Node B, an eNB, an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS), an extended service set (ESS), a transmit receive point (TRP), a network node, a network entity, a network equipment, or some other suitable term. The base station 102 may be implemented as an integrated access 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 disaggregated base station including one or more of a CU, a DU, and / or a RU. A set of base stations that may include disaggregated base stations and / or aggregated base stations may be referred to as a next generation (NG) RAN (NG-RAN).

[0051] 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 core network 120. AMF 161 supports registration management, connection management, mobility management, and other functions. SMF 162 supports session management and other functions. UPF 163 supports packet routing, packet forwarding, and other functions. UDM 164 supports the generation of authentication and key agreement (AKA) credentials, user identity handling, access authorization, and subscription management. One or more location servers 168 are illustrated as including a gateway mobile location center (GMLC) 165 and a location management function (LMF) 166. However, in general, the one or more location servers 168 may include one or more location / positioning servers, which may include one or more of the GMLC 165, LMF 166, positioning determination entity (PDE), serving mobile location center (SMLC), mobile positioning center (MPC), etc. GMLC 165 and LMF 166 support UE location services. GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. LMF 166 receives measurement results and auxiliary information from NG-RAN and UE 104 via AMF 161 to calculate the positioning of UE 104. NG-RAN may determine the positioning of UE 104 using one or more positioning methods. Positioning UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by UE 104 and / or serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / location 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.

[0052] Examples of UE 104 include cellular phones, smart phones, session initiation protocol (SIP) phones, laptops, personal digital assistants (PDAs), satellite radios, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, tablet computers, smart devices, wearable devices, vehicles, electric meters, gas pumps, large or small kitchen appliances, healthcare equipment, implants, sensors / actuators, displays, or any other similarly functional devices. Some of the UEs 104 may be referred to as IoT devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). UE 104 may also be referred to as stations, mobile stations, subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless terminals, remote terminals, mobile phones, user agents, mobile clients, clients, or some other suitable terminology. In some scenarios, the term "UE" may also be applied to one or more supporting devices, such as in a device cluster arrangement. One or more of these devices may access the network collectively and / or individually.

[0053] Reference again Figure 1 In some aspects, the UE 104 may include a non-codebook based (NCBB) TCI component 198, which is configured to send a TCI indicating a non-codebook based beam direction to a wireless device based on at least one of QCL information or angle information; and send a data transmission to the wireless device via the non-codebook based beam direction indicated in the TCI. In some aspects, the NCBB TCI component 198 may be configured to receive a TCI indicating a non-codebook based beam direction from a network node, and receive a data transmission sent via the non-codebook based beam direction indicated in the TCI from the network node. In some aspects, the base station 102 may include a NCBB TCI component 199, which is configured to receive a TCI indicating a non-codebook based beam direction from a network node, and receive a data transmission sent via the non-codebook based beam direction indicated in the TCI from the network node. In some aspects, the NCBB TCI component 199 may also be configured to send a TCI indicating a non-codebook based beam direction to the wireless device based on at least one of the QCL information or the angle information, and send data to the wireless device via the non-codebook based beam direction indicated in the TCI. Although the following description may focus on 5G NR, the concepts described herein may be applicable to other similar fields, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies.

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

[0055] 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 normal or extended. For a normal CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The symbol on the DL may be a CP orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbol. The symbol on the UL may be a CP-OFDM symbol (for high throughput scenarios) or a discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbol (also known as a single carrier frequency division multiple access (SC-FDMA) symbol) (for power-limited scenarios; limited to single-stream transmission). The number of time slots within a subframe is based on the CP and parameter set. The parameter set defines the subcarrier spacing (SCS) and effectively defines the symbol length / duration, which is equal to 1 / SCS.

[0056]

[0057]

[0058] 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. Therefore, the subcarrier spacing for parameter set μ=0 is 15kHz, and the subcarrier spacing for parameter set μ=4 is 240kHz. The symbol length / duration is inversely related to the subcarrier spacing. FIG. 2A to FIG. 2D An example of a parameter set μ=2 with a normal CP of 14 symbols per slot and 4 slots per subframe is provided. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is about 16.67 μs. Within a frame set, there may be one or more different bandwidth parts (BWPs) that are frequency-division multiplexed (see Figure 2B ). Each BWP may have a specific parameter set and CP (normal or extended).

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

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

[0061] 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 particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identification. A secondary synchronization signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and the radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also referred to as an SS block (SSB)). The MIB provides the system frame number (SFN) and the number of RBs in the system bandwidth. The physical downlink shared channel (PDSCH) carries user data, broadcast system information such as system information blocks (SIBs) that are not sent via the PBCH, and paging messages.

[0062] 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 may be sent in different configurations. The UE may send a sounding reference signal (SRS). The SRS may be sent in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0063] 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 additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0064] Figure 33 is a block diagram of a base station 310 communicating with a UE 350 in an access network. In the DL, Internet Protocol (IP) packets may be provided to a controller / processor 375. The controller / processor 375 implements layer 3 and layer 2 functionality. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functionality associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functionality associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

[0065] The transmit (TX) processor 316 and the receive (RX) processor 370 implement layer 1 functionality associated with various signal processing functions. Layer 1 (which includes the physical (PHY) layer) may include error detection on the transport channel, forward error correction (FEC) coding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles the mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-order phase shift keying (M-PSK), M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols 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 and / or frequency domain, and then combined using an inverse fast Fourier transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially pre-coded to generate multiple spatial streams. Channel estimates from a channel estimator 374 may be used to determine the coding and modulation schemes, as well as for spatial processing. Channel estimates may be derived from reference signals and / or channel state feedback sent by the UE 350. Each spatial stream may then be provided to a different antenna 320 via a separate transmitter 318Tx. Each transmitter 318Tx may modulate a radio frequency (RF) carrier with a corresponding spatial stream for transmission.

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

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

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

[0069] The TX processor 368 may use channel estimates derived by the channel estimator 358 from a reference signal or feedback sent 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.

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

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

[0072] 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 The NCBB TCI component 198 combines various aspects.

[0073] 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 NCBB TCI component 199 combines various aspects.

[0074] In some aspects of wireless communication, a pair of network devices (e.g., base stations, UEs, or other wireless devices associated with a wireless network) may communicate via a set of directional beams. The pair of network devices may include a first network device configured with a first (preconfigured and / or known) beam codebook and a second network device with a second (preconfigured and / or known) beam codebook. In some aspects, the beam codebook may be associated with a fixed set of beam directions, such that the first beam codebook may be associated with a first number of preconfigured beam directions and the second beam codebook may be associated with a second number of preconfigured beam directions.

[0075] In some aspects, the pair of network devices including the first network device and the second network device may select a most appropriate pair of beams (e.g., beam directions) from the first beam codebook and the second beam codebook for communication between the first network device and the second network device. In some aspects, the selected most appropriate pair of beams may not represent an optimal set of beam directions that maximizes channel gain (e.g., using an optimal beam direction to maximize signal strength of communication). In some aspects, the inability to select the optimal set of beam directions may be based on a quantization of the first codebook beam directions and the second codebook beam directions. For example, a UE may include a first beam codebook based on a set of beams having azimuth intervals of ~90 degrees and elevation intervals of ~90 degrees, which may be associated with four different beam directions (e.g., (φ r ,θ r ) = {[-45,45],[-45,135],[45,45],[45,135]}). In some aspects, a base station (or other UE) may be associated with a finer quantization (e.g., azimuth spacing of 45 degrees, elevation spacing of 22.5 degrees, possibly with 32 different beam directions (e.g., (φ r ,θ r )={[-78.75,22.5],[-78.75,67.5],…,[-56.25,112.5],…,[78.75,157.5]}).

[0076] In some aspects, the granularity of quantization may reduce the spectral efficiency of the communication below the theoretical maximum spectral efficiency.By introducing the use of non-codebook based beams, the apparatus and methods disclosed herein may provide higher spectral efficiency.

[0077] Figure 4 4 is a diagram illustrating a compressed sensing technique applied to generate a sparse matrix of gain values ​​associated with a set of angles of departure (AoD) and a set of angles of arrival (AoA) for communication between a UE 404 and a base station 402. Each AoD and AoA may be defined based on a pair of angles defined for a polar coordinate system (e.g., each AoA or AoD may be defined based on an elevation angle φ r and azimuth angle θ r UE 404 and base station 402 may include beams or beam directions A1 to A1 associated with UE 404. k and beams B1 to B associated with base station 402 m The beam pairs perform beam scanning operations.

[0078] The compressed sensing technique may be based on the following equation that models the hybrid beamforming input-output relationship for each tone for the downlink (in some aspects, a similar formula may be used for the uplink): y = AHBPx + n, where y is the observed baseband sample and H is the original channel matrix N Rx ×N Tx , which is a function of core parameters such as the number of beam clusters, azimuth AoA (A-AoA), A-AoD, elevation AoA (Z-AoA) and Z-AoD per cluster, delay and power. Additionally, A is the Rx (analog) beamforming matrix, N RP ×N Rx ; B = Tx (analog) beamforming matrix, N Tx ×N TP ; and P is the Tx (digital) pre-coding matrix, N TP ×N SS .

[0079] Compared to a more complete set of scanning Tx and Rx beamforming measurements (using a larger set of Tx or Rx beams), using a reduced set of Tx and Rx beamforming measurements (A i HB j) to collect some information about the original channel H can predict the best beam pair (defined by A-AoA, A-AoD, Z-AoA and Z-AoD) with less overhead. The best beam pair can then be used to select beam pairs from a larger set of Rx and Tx beams, or to define non-codebook based beams based on the best beam pair to improve spectral efficiency, compared to codebook-based beam pairs using a reduced set of Tx and Rx beams. In some aspects, the information about the original channel H can be recovered based on an orthogonal matching pursuit (OMP) algorithm, where the information about the original channel may include information about actual A-AoA / Z-AoA 410, actual A-AoD / Z-AoD 420, and gains associated with beam directions. A-AoA / Z-AoA 410 and A-AoD / Z-AoD 420 may be more accurate than estimated AoA / Z-AoA 412 and A-AoD / Z-AoD 422 that may have been identified without the OMP algorithm.

[0080] Figure 5A is a graph 500 illustrating a quantized A-AoD / Z-AoD set for DL ​​communications at a base station according to some aspects of the present disclosure. Figure 5B is a diagram 510 illustrating a quantized A-AoA / Z-AoA set for DL ​​communication at a UE. Figure 5A and 5B It is illustrated that there may be an optimal beam (real channel 506 or real channel 516) defined by the A-AoD / Z-AoD pair for the base station or the A-AoA / Z-AoA pair for the UE. The UE may also derive a set of A-AoA / Z-AoA pairs 518 based on local beam management / beam measurement operations at the UE. The codebook-based beam direction at the base station (e.g., codebook pointing angle 502) or the codebook-based beam direction at the UE (e.g., codebook pointing angle 512) may (and in some aspects is likely to) be inconsistent with the real channel 506 or 516. Based on the above, the codebook-based beam direction at the base station (e.g., codebook pointing angle 502) or the codebook-based beam direction at the UE (e.g., codebook pointing angle 512) may not be consistent with the real channel 506 or 516. Figure 4 For the described beam management and / or beam measurement operations, the base station and the UE may select a customized (e.g., non-codebook based beam) beam direction 504 and / or a customized (e.g., non-codebook based beam) beam direction 514, as described below with respect to Figures 6 to 10 described.

[0081] Figure 6600 is a call flow diagram illustrating a wireless communication method according to some aspects of the present disclosure. At 606, the first network node 602 may obtain angle information about an AoD and / or an AoA set associated with an original channel between the first network node 602 and the second network node 604. In some aspects, the first network node 602 may be a base station and the second network node 604 may be a wireless device (e.g., a UE). In some aspects, the first network node 602 may be a wireless device (e.g., a UE) and the second network node 604 may be one of a base station or a second wireless device.

[0082] In some aspects, obtaining the angle information at 606 may include one or more components indicated in the set of beam training operations 605. In some aspects, the first network node 602 may obtain the angle information at 606 by receiving angle information 605D from the second network node 604 based on a set of beam scanning signals (e.g., reference transmissions 605A and / or reference transmissions 605B) exchanged with the second network node 604. In some aspects, the second network node 604 may identify angle information associated with at least one beam direction associated with the set of reference transmissions 605B at 605C. In some aspects, the network node 602 may obtain the angle information from the network node 604 at 606, and the network node 604 may perform one or more compressed sensing operations (employing compressed sensing techniques). For example, the second network node 604 may receive and measure the reference transmissions 605B to estimate and / or identify angle information (e.g., AoA and / or AoD). In some aspects, the angle information estimation and / or identification may include performing a machine learning operation (e.g., an OMP algorithm) based on a beam scanning signal set and / or compressed sensing to provide the angle information 605D. In some aspects, obtaining the angle information at 606 may include identifying the AoD associated with the highest gain from the angle information 605D. In some aspects, one or more of the above operations may be performed jointly by the first network node 602 and the second network node 604, such that a first portion of the angle information is received from the second network node 604, and a second portion of the angle information is obtained by the first network node 602 performing one or more additional operations.

[0083] At 608, the first network node 602 may identify a first AoD (e.g., a beam direction associated with the first AoD) and / or a first AoA (e.g., a beam direction associated with the first AoA) in the set of AoDs and / or AoAs based on the angle information obtained at 606. In some aspects, the identified first AoD and / or first AoA may be an AoD and / or AoA associated with a peak gain. The first AoD and / or first AoA may be identified based on a set of reference transmissions 605A, wherein the set of reference transmissions 605A is associated with a beam scanning operation for a transmit (Tx) beam, and the first network node 602 performs a concurrent beam scanning operation on a receive (Rx) beam to identify a gain associated with each beam pair (e.g., an AoD and AoA pair associated with each beam pair). In some aspects, the network node 602 may identify a set of a first number of AoDs and / or AoAs associated with a set of a first number of highest gains. In some aspects, the first number of sets of AoDs and AoAs may include codebook-based beam directions. In some aspects, the first number of sets of AoDs and AoAs may be used to determine one or more non-codebook-based beams associated with AoDs and / or AoAs for communication between the first network node 602 and the network node 604.

[0084] The network node 602 may send TCI 610 indicating a non-codebook based beam direction (or a set of beam directions) based on the angle information obtained at 606. In some aspects, TCI 610 may refer to a set of one or more TCI states in a set of configured TCI states. The configured TCI states may indicate QCL information associated with multiple different beam directions. In some aspects, contrary to known reference signal QCL information, TCI 610 may be bound to and / or identified by a channel AoD to allow non-codebook based beam direction indication. In some aspects, the indicated non-codebook based beam direction may be based on the identification at 608. Contrary to the codebook based beam direction selected from the set of configured (predefined) beam directions, the non-codebook based beam direction may be selected and / or constructed based on the underlying channel. In some aspects, the selected and / or constructed non-codebook based beam direction may provide improved performance based on an optimal beam direction capable of more closely matching the beam direction to the channel compared to codebook based beam direction selection.

[0085] In some aspects, the non-codebook based beam direction is the appropriate beam direction that is closest to the first AoD (e.g., the first AoD identified at 608). In some aspects, the TCI 610 may indicate the non-codebook based beam direction via an indication of a first azimuth angle associated with the non-codebook based beam direction and a second elevation angle associated with the non-codebook based beam direction. In some aspects, the indication of the first azimuth angle and the second elevation angle may be indicated as a set of azimuth and elevation angle pairs via a bitmap. In some aspects, the bitmap may be represented as a vector, wherein each value maps to a set of angles including an azimuth angle and an elevation angle. In some aspects, the bitmap may be represented as a matrix, wherein each column and each row is associated with a specific angle of one of the azimuth angle or the elevation angle, such that each value in the bitmap may be mapped to a set of angles including an azimuth angle and an elevation angle. For example, the angle space may be quantized into a 2-D grid, and each point in the grid may be identified with a set of bits. For example, if the size of the 2-D grid is 256, any point may be identified by a set of 8 bits. The bitmap may be received via RRC signaling, or may be known (e.g., preconfigured). The bitmap may include a set of angles, the angular differences between which are less than the angles between codebook-based beams. In some aspects, the indication of the first azimuth angle and the second elevation angle may be indicated via a plurality of non-zero values ​​in a bitmap, wherein each non-zero value in the plurality of non-zero values ​​(or a set of values ​​in a multi-bit indication) is associated with a corresponding weight (e.g., a weight indicating the magnitude of a component used to determine a non-codebook-based beam direction). The corresponding weight may be indicated by a multi-bit (e.g., 2 to 8-bit) weight. For example, if the size of the 2-D grid is 256, each point having a non-zero weight may be identified by a set of 8 bits, and the weight associated with the point may be identified by an additional set of 2 bits to indicate, for example, a weight of 1 / 4, 1 / 2, 3 / 4, or 1. In some aspects where multiple non-zero values ​​are used to indicate a first azimuth and a second elevation, multiple non-zero values ​​and corresponding weights in a bitmap may be used (eg, using a weighted sum) to indicate beam directions that are inconsistent with an azimuth and elevation pair in the set of azimuth and elevation pairs.

[0086] In some aspects, the TCI 610 indicates a non-codebook based beam direction based on a QCL with a set of reference beam directions. In some aspects, each reference beam direction may be one of: (1) a reference signal from a plurality of reference signals; or (2) a configured beam direction from a plurality of configured beam directions. In some aspects, the set of reference beam directions includes a plurality of reference beam directions, and each reference beam direction in the set of reference beam directions may be associated with a corresponding weight in a corresponding weight set. In some aspects, a plurality of reference beam directions and a corresponding weight set are used to indicate a beam direction that is inconsistent with a particular reference beam direction.

[0087] At 612, based on TCI 610, second network node 604 may adjust the receive beam used by second network node 604. Finally, first network node 602 and second network node 604 may exchange data transmissions 614 via the beams indicated in TCI 610 (eg, non-codebook based beams).

[0088] Figure 7 700 is a flow chart of a wireless communication method. The method may be performed by a network node (e.g., network node 602 or 604), a UE (e.g., UE 104; device 1104), or a base station (e.g., base station 102; network entity 1202). The network node may obtain angle information about an AoD (and / or AoA) set associated with an original channel. For example, referring to Figure 6 , the network node 602 may obtain angle information about an AoD and / or an AoA set associated with an original channel between the first network node 602 and the second network node 604 at 606 .

[0089] In some aspects, to obtain the angle information, the network node may receive the angle information from other network nodes based on a set of beam scanning signals exchanged with other network nodes. The beam scanning signals and / or transmissions may be as described above with respect to Figure 6 A portion of the set of beam training and / or beam management operations described. For example, reference Figure 6 , based on the reference transmission 605B, the second network node 604 may transmit and the first network node may receive angle information 605D.

[0090] In some aspects, the network node may perform one or more compressed sensing operations to obtain the angle information. In some aspects, the compressed sensing operation and / or processing is preceded by a beam scanning operation on a sparse set of AoA and AoD beam pairs, as described above with respect to Figure 4 , Figure 5A and Figure 5B As described, the beam scanning operation is used to determine one or more of the underlying (original) channels and the associated optimal beam directions (e.g., AoA and / or AoD). Figure 6 , the first network node 602 or the second network node 604 may perform a compressed sensing operation based on a set of reference transmissions 605A sent by the second network node 604 or a set of reference transmissions 605B sent by the first network node 602, respectively.

[0091] In some aspects, based on angle information received from other network nodes and / or angle information obtained by performing compressed sensing operations, the network node may perform a machine learning operation to obtain the angle information. In some aspects, the machine learning operation may be an OMP algorithm. For example, the OMP algorithm may be applied to angle information received from other network nodes and / or angle information obtained by performing compressed sensing operations. Figure 6 For example, network node 602 may receive angle information 605D based on reference transmission 605B from network node 604 and / or perform a compressed sensing operation based on a set of reference transmissions 605A sent by a second network node 604 and apply a machine learning operation to obtain angle information (e.g., as described with respect to FIG. Figure 4 to identify channel information as described in FIG. 5 ).

[0092] The network node may identify a first AoD from a set of AoDs that is associated with a peak gain. In some aspects, the network node may also identify a first AoA from a set of AoAs that is associated with a peak gain. The first AoD and the first AoA may constitute a beam pair associated with a peak gain. In some aspects, the network node may identify a set of a first number of AoDs and / or AoAs associated with a set of a first number of highest gains. In some aspects, the set of a first number of AoDs and AoAs may include codebook-based beam directions. In some aspects, the set of a first number of AoDs and AoAs may be used to identify one or more non-codebook-based beams associated with the first AoD and / or the first AoA. For example, referring to Figure 6 The network node 602 may identify, at 608, a first AoD (e.g., a beam direction associated with the first AoD) and / or a first AoA (e.g., a beam direction associated with the first AoA) in the set of AoDs and / or AoAs that is associated with a peak gain.

[0093] At 706, the network node may send a TCI indicating a non-codebook based beam direction based on the angle information. For example, 706 may be performed by the antenna 1180 or 1280, the transceiver 1122 or 1246, the cellular baseband processor 1124, the application processor 1106, the RU processor 1242, and / or the NCBB TCI component 198 or 199. In some aspects, the indicated non-codebook based beam direction may be based on an identified first AoD associated with a peak gain in the set of AoDs. In some aspects, the non-codebook based beam direction is a suitable beam direction that is closest to the first AoD (e.g., the first AoD identified at 704). In some aspects, the TCI may indicate the non-codebook based beam direction via an indication of a first azimuth angle associated with the non-codebook based beam direction and a second elevation angle associated with the non-codebook based beam direction. In some aspects, the indication of the first azimuth and the second elevation angle may be indicated as a set of azimuth and elevation pairs via a bitmap. In some aspects, the indication of the first azimuth and the second elevation angle may be indicated via a plurality of non-zero values ​​in the bitmap, wherein each non-zero value in the plurality of non-zero values ​​is associated with a corresponding weight. In some aspects where a plurality of non-zero values ​​are used to indicate the first azimuth and the second elevation angle, a plurality of non-zero values ​​and corresponding weights in the bitmap may be used to indicate a beam direction that is inconsistent with an azimuth and elevation pair in the set of azimuth and elevation pairs.

[0094] In some aspects, the TCI indicates a non-codebook based beam direction based on quasi-co-location with a set of reference beam directions. In some aspects, each reference beam direction can be one of: (1) a reference signal from a plurality of reference signals; or (2) a configured beam direction from a plurality of configured beam directions. In some aspects, the set of reference beam directions includes a plurality of reference beam directions, and each reference beam direction in the set of reference beam directions can be associated with a corresponding weight in a corresponding weight set. In some aspects, a plurality of reference beam directions and corresponding weight sets are used to indicate a beam direction that is inconsistent with a particular reference beam direction. For example, a reference beam direction may be a reference beam direction that is inconsistent with a particular reference beam direction. Figure 5A , Figure 5B and Figure 6 , the network node 602 may send and the network node 604 may receive TCI 610, which may refer to one or more beams in the set of codebook-based beams (eg, codebook pointing angles 502 or 512).

[0095] Finally, at 708, the network node may send a data transmission via the non-codebook based beam direction indicated in the TCI sent at 706. In some aspects, the data transmission may be sent to other network nodes (e.g., UE or base station). For example, 706 may be performed by the antenna 1180 or 1280, the transceiver 1122 or 1246, the cellular baseband processor 1124, the application processor 1106, the RU processor 1242 and / or the NCBB TCI component 198 or 199. Figure 6 , for example, based on the information included in TCI 610 , network node 602 may send and network node 604 may receive data transmission 614 .

[0096] Figure 8 800 is a flowchart of a wireless communication method. The method may be performed by a network node (e.g., network node 602 or 604), a UE (e.g., UE 104; device 1104), or a base station (e.g., base station 102; network entity 1202). At 802, the network node may obtain angle information about a set of AoDs (and / or AoAs) associated with an original channel. For example, 802 may be performed by antenna 1180 or 1280, transceiver 1122 or 1246, cellular baseband processor 1124, application processor 1106, RU processor 1242, and / or NCBB TCI component 198 or 199. For example, referring to Figure 6 , the network node 602 may obtain angle information about an AoD and / or an AoA set associated with an original channel between the first network node 602 and the second network node 604 at 606 .

[0097] In some aspects, to obtain the angle information at 802, the network node may receive the angle information from the other network nodes based on the set of beam scanning signals exchanged with the other network nodes. The beam scanning signals and / or transmissions may be as described above with respect to Figure 6 A portion of the set of beam training and / or beam management operations described. For example, reference Figure 6 , based on the reference transmission 605B, the second network node 604 may transmit and the first network node 602 may receive angle information 605D.

[0098] At 804, the network node may identify a first AoD from a set of AoDs that is associated with a peak gain. In some aspects, the network node may also identify a first AoA from a set of AoAs that is associated with a peak gain. The first AoD and the first AoA may constitute a beam pair associated with a peak gain. For example, 804 may be performed by the cellular baseband processor 1124, the application processor 1106, the RU processor 1242, and / or the NCBB TCI component 198 or 199. In some aspects, the network node may identify a first number of sets of AoDs and / or AoAs associated with a first number of sets of highest gains. In some aspects, the first number of sets of AoDs and AoAs may include codebook-based beam directions. In some aspects, at 804, the first number of sets of AoDs and AoAs may be used to identify one or more non-codebook-based beams associated with the first AoD and / or the first AoA. For example, referring to Figures 4 to 6 The network node 602 may identify, at 608, a first AoD (e.g., a beam direction associated with the first AoD) and / or a first AoA (e.g., a beam direction associated with the first AoA) in the set of AoDs and / or AoAs that is associated with a peak gain.

[0099] At 806, the network node may send a TCI indicating a non-codebook based beam direction based on the angle information. For example, 806 may be performed by the antenna 1180 or 1280, the transceiver 1122 or 1246, the cellular baseband processor 1124, the application processor 1106, the RU processor 1242, and / or the NCBB TCI component 198 or 199. In some aspects, the indicated non-codebook based beam direction may be based on the identification at 804. In some aspects, the non-codebook based beam direction is a suitable beam direction that is closest to the first AoD (e.g., the first AoD identified at 804). In some aspects, the TCI may indicate the non-codebook based beam direction via an indication of a first azimuth angle associated with the non-codebook based beam direction and a second elevation angle associated with the non-codebook based beam direction. In some aspects, the indication of the first azimuth angle and the second elevation angle may be indicated as a set of azimuth angle and elevation angle pairs via a bitmap. In some aspects, the indication of the first azimuth angle and the second elevation angle may be indicated via a plurality of non-zero values ​​in a bitmap, wherein each non-zero value in the plurality of non-zero values ​​is associated with a corresponding weight. In some aspects where a plurality of non-zero values ​​are used to indicate the first azimuth angle and the second elevation angle, the plurality of non-zero values ​​and the corresponding weights in the bitmap may be used to indicate a beam direction that is inconsistent with an azimuth angle and elevation angle pair in the set of azimuth angle and elevation angle pairs.

[0100] In some aspects, the TCI indicates a non-codebook based beam direction based on quasi-co-location with a set of reference beam directions. In some aspects, each reference beam direction can be one of: (1) a reference signal from a plurality of reference signals; or (2) a configured beam direction from a plurality of configured beam directions. In some aspects, the set of reference beam directions includes a plurality of reference beam directions, and each reference beam direction in the set of reference beam directions can be associated with a corresponding weight in a corresponding weight set. In some aspects, a plurality of reference beam directions and corresponding weight sets are used to indicate a beam direction that is inconsistent with a particular reference beam direction. For example, a reference beam direction may be a reference beam direction that is inconsistent with a particular reference beam direction. Figures 4 to 6 , the network node 602 may send and the network node 604 may receive TCI 610, which may refer to one or more beams in the set of codebook-based beams (eg, codebook pointing angles 502 or 512).

[0101] Finally, at 808, the network node may send a data transmission via the non-codebook based beam direction indicated in the TCI sent at 806. In some aspects, the data transmission may be sent to other network nodes (e.g., UE or base station). For example, 806 may be performed by the antenna 1180 or 1280, the transceiver 1122 or 1246, the cellular baseband processor 1124, the application processor 1106, the RU processor 1242 and / or the NCBB TCI component 198 or 199. Figure 6 , for example, based on the information included in TCI 610 , network node 602 may send and network node 604 may receive data transmission 614 .

[0102] Fig. 9 900 is a flowchart of a wireless communication method. The method may be performed by a network node (e.g., network node 602 or 604), a UE (e.g., UE 104; device 1104), or a base station (e.g., base station 102; network entity 1202). The network node may receive a reference transmission set for a beam scanning operation. In some aspects, the received reference transmission set may include a reference transmission set transmitted from other network nodes via a sparse set of transmission beams. In some aspects, the reference transmission set received at 902 may be received via an Rx beam set at the network node as part of the beam scanning operation. In some aspects, the Rx beam set may be a sparse set of Rx beams. For example, the reference Figure 6 , the network node 604 may receive the reference transmission 605B sent from the network node 602 via the Tx beam set via the Rx beam set.

[0103] In some aspects, the network node may identify angle information associated with at least one beam direction (e.g., at least one AoD and / or AoA) associated with a reference transmission set. The angle information may include a gain associated with the at least one beam direction and / or a gain set associated with the reference transmission set (e.g., a gain set for each pair of Tx beams and Rx beams scanned by the reference transmission). For example, the reference Figure 6 , the network node 604 may identify, at 605C, angle information associated with at least one beam direction associated with the set of reference transmissions 605B

[0104] In some aspects, the network node may send the angle information to the network node. In some aspects, the angle information sent may include signal strength and / or channel quality measurements for each beam in the set of beam pairs scanned when receiving the reference transmission. In some aspects, the angle information may be included in a beam measurement report. For example, the reference transmission Figure 6 , network node 604 may send and network node 602 may receive angle information 605D.

[0105] At 908, the network node may receive TCI indicating a non-codebook based beam direction. In some aspects, the TCI received at 908 may be based on the angle information sent at 906. For example, 908 may be performed by the antenna 1180 or 1280, the transceiver 1122 or 1246, the cellular baseband processor 1124, the application processor 1106, the RU processor 1242, and / or the NCBB TCI component 198 or 199. In some aspects, the indicated non-codebook based beam direction may be based on the angle information associated with at least one beam direction sent at 906. In some aspects, the non-codebook based beam direction is a suitable beam direction that is closest to the at least one beam direction. For example, referring to Figure 6 , the network node 602 may send and the network node 604 may receive TCI 610 indicating a non-codebook based beam direction.

[0106] In some aspects, the TCI may indicate a non-codebook-based beam direction via an indication of a first azimuth angle associated with the non-codebook-based beam direction and a second elevation angle associated with the non-codebook-based beam direction. In some aspects, the indication of the first azimuth angle and the second elevation angle may be indicated as a set of azimuth angle and elevation angle pairs via a bitmap. In some aspects, the indication of the first azimuth angle and the second elevation angle may be indicated via a plurality of non-zero values ​​in a bitmap, wherein each non-zero value in the plurality of non-zero values ​​is associated with a corresponding weight. In some aspects where a plurality of non-zero values ​​are used to indicate the first azimuth angle and the second elevation angle, a plurality of non-zero values ​​and corresponding weights in a bitmap may be used to indicate a beam direction that is inconsistent with an azimuth angle and elevation angle pair in a set of azimuth angle and elevation angle pairs.

[0107] In some aspects, the TCI indicates a non-codebook based beam direction based on quasi-co-location with a set of reference beam directions. In some aspects, each reference beam direction can be one of: (1) a reference signal from a plurality of reference signals; or (2) a configured beam direction from a plurality of configured beam directions. In some aspects, the set of reference beam directions includes a plurality of reference beam directions, and each reference beam direction in the set of reference beam directions can be associated with a corresponding weight in a corresponding weight set. In some aspects, a plurality of reference beam directions and corresponding weight sets are used to indicate a beam direction that is inconsistent with a particular reference beam direction. For example, a reference beam direction may be a reference beam direction that is inconsistent with a particular reference beam direction. Figures 4 to 6 , the network node 602 may send and the network node 604 may receive TCI 610, which may refer to one or more beams in the set of codebook-based beams (eg, codebook pointing angles 502 or 512).

[0108] In some aspects, if the network node is already communicating with other network nodes, the network node may adjust the receive beam direction based on the TCI and angle information received at 908. For example, if the TCI indicates a beam direction (e.g., Tx or Rx beam direction) that is different from the current beam direction, the network node may adjust the beam direction. The updated beam direction may be a non-codebook based beam direction. Figure 6 , for example, the second network node 604 may receive TCI 610 from the first network node 602 and adjust a receive beam used by the second network node 604 at 612 .

[0109] Finally, at 912, the network node may receive a data transmission sent via a non-codebook based beam direction indicated in the TCI. In some aspects, the data transmission may be received from other network nodes (e.g., a UE or a base station). For example, 912 may be performed by antenna 1180 or 1280, transceiver 1122 or 1246, cellular baseband processor 1124, application processor 1106, RU processor 1242, and / or NCBB TCI component 198 or 199. Figure 6 , for example, based on the information included in TCI 610 , network node 604 may receive and network node 602 may send data transmission 614 .

[0110] Fig.101000 is a flowchart of a wireless communication method. The method may be performed by a network node (e.g., network node 602 or 604), a UE (e.g., UE 104; device 1104), or a base station (e.g., base station 102; network entity 1202). At 1002, the network node may receive a reference transmission set for a beam scanning operation. For example, 1002 may be performed by an antenna 1180 or 1280, a transceiver 1122 or 1246, a cellular baseband processor 1124, an application processor 1106, a RU processor 1242, and / or an NCBB TCI component 198 or 199. In some aspects, the reference transmission set received at 1002 may include a reference transmission set transmitted from other network nodes via a sparse set of transmission beams. In some aspects, the reference transmission set received at 1002 may be received via an Rx beam set at the network node as part of a beam scanning operation. In some aspects, the Rx beam set may be a sparse set of Rx beams. For example, refer to Figure 6 , the network node 604 may receive the reference transmission 605B sent from the network node 602 via the Tx beam set via the Rx beam set.

[0111] At 1004, the network node may identify angle information associated with at least one beam direction (e.g., at least one AoD and / or AoA), the at least one beam direction being associated with a reference transmission set. For example, 1004 may be performed by the cellular baseband processor 1124, the application processor 1106, the RU processor 1242, and / or the NCBB TCI component 198 or 199. The angle information may include a gain associated with the at least one beam direction and / or a gain set associated with the reference transmission set (e.g., a gain set for each pair of Tx beams and Rx beams scanned by the reference transmission). For example, the reference Figure 6 , the network node 604 may identify, at 605C, angle information associated with at least one beam direction associated with the set of reference transmissions 605B.

[0112] In some aspects, at 1004, the network node may perform one or more compressed sensing operations to identify the angle information. In some aspects, the compressed sensing operation is preceded by a beam scanning operation on a sparse set of AoA and AoD beam pairs, as described above with respect to Figure 4 , Figure 5A and Figure 5B As described, the beam scanning operation is used to determine one or more of the underlying (original) channels. For example, referring to Figure 6 , the second network node 604 may perform a compressed sensing operation based on the set of reference transmissions 605B sent by the first network node 602.

[0113] In some aspects, at 1004, based on the reference signal set received at 1002 and / or the compressed sensing operation, the network node may perform a machine learning operation (e.g., an OMP algorithm) to identify the angle information. For example, the machine learning operation (e.g., an OMP algorithm) may be applied to the angle information associated with the reference signal set received at 1002 and / or the angle information obtained by performing the compressed sensing operation. Figure 6 For example, the second network node 604 may perform a compressed sensing operation based on a set of reference transmissions 605B sent by the first network node 602, and apply a machine learning operation to obtain angle information (e.g., such as Figure 4 to identify channel information as described in FIG. 5 ).

[0114] At 1006, the network node may send angle information to the network node. For example, 1006 may be performed by antenna 1180 or 1280, transceiver 1122 or 1246, cellular baseband processor 1124, application processor 1106, RU processor 1242 and / or NCBBTCI component 198 or 199. In some aspects, the angle information sent at 1006 may include signal strength and / or channel quality measurements for each beam in the set of beam pairs scanned when receiving the reference transmission at 1002. In some aspects, the angle information may be included in a beam measurement report. In some aspects, the angle information sent at 1006 may include angle information identified by a compressed sensing operation and / or a machine learning operation. For example, the reference Figure 6 , network node 604 may send and network node 602 may receive angle information 605D.

[0115] At 1008, the network node may receive TCI indicating a non-codebook based beam direction. In some aspects, the TCI received at 1008 may be based on the angle information sent at 1006. For example, 1008 may be performed by the antenna 1180 or 1280, the transceiver 1122 or 1246, the cellular baseband processor 1124, the application processor 1106, the RU processor 1242, and / or the NCBB TCI component 198 or 199. In some aspects, the indicated non-codebook based beam direction may be based on the angle information associated with at least one beam direction sent at 1006. In some aspects, the non-codebook based beam direction is a suitable beam direction that is closest to the at least one beam direction. For example, referring to Figures 4 to 6 , the network node 602 may send and the network node 604 may receive TCI 610 indicating a non-codebook based beam direction.

[0116] In some aspects, the TCI may indicate a non-codebook-based beam direction via an indication of a first azimuth angle associated with the non-codebook-based beam direction and a second elevation angle associated with the non-codebook-based beam direction. In some aspects, the indication of the first azimuth angle and the second elevation angle may be indicated as a set of azimuth angle and elevation angle pairs via a bitmap. In some aspects, the indication of the first azimuth angle and the second elevation angle may be indicated via a plurality of non-zero values ​​in a bitmap, wherein each non-zero value in the plurality of non-zero values ​​is associated with a corresponding weight. In some aspects where a plurality of non-zero values ​​are used to indicate the first azimuth angle and the second elevation angle, a plurality of non-zero values ​​and corresponding weights in a bitmap may be used to indicate a beam direction that is inconsistent with an azimuth angle and elevation angle pair in a set of azimuth angle and elevation angle pairs.

[0117] In some aspects, the TCI indicates a non-codebook based beam direction based on quasi-co-location with a set of reference beam directions. In some aspects, each reference beam direction can be one of: (1) a reference signal from a plurality of reference signals; or (2) a configured beam direction from a plurality of configured beam directions. In some aspects, the set of reference beam directions includes a plurality of reference beam directions, and each reference beam direction in the set of reference beam directions can be associated with a corresponding weight in a corresponding weight set. In some aspects, a plurality of reference beam directions and corresponding weight sets are used to indicate a beam direction that is inconsistent with a particular reference beam direction. For example, a reference beam direction may be a reference beam direction that is inconsistent with a particular reference beam direction. Figures 4 to 6 , the network node 602 may send and the network node 604 may receive TCI 610, which may refer to one or more beams in the set of codebook-based beams (eg, codebook pointing angles 502 or 512).

[0118] At 1010, if the network node is already communicating with other network nodes, the network node may adjust the receive beam direction based on the TCI received at 1008 and the angle information sent at 1006. For example, 1010 may be performed by the cellular baseband processor 1124, the application processor 1106, the RU processor 1242, and / or the NCBB TCI component 198 or 199. For example, if the TCI indicates a beam direction (e.g., a Tx or Rx beam direction) that is different from the current beam direction, the network node may adjust the beam direction. The updated beam direction may be a non-codebook based beam direction. Reference Figure 6 , for example, the second network node 604 may receive TCI 610 from the first network node 602 and adjust a receive beam used by the second network node 604 at 612 .

[0119] Finally, at 1012, the network node may receive a data transmission sent via a non-codebook based beam direction indicated in the TCI. In some aspects, the data transmission may be received from other network nodes (e.g., a UE or a base station). For example, 1012 may be performed by antenna 1180 or 1280, transceiver 1122 or 1246, cellular baseband processor 1124, application processor 1106, RU processor 1242, and / or NCBB TCI component 198 or 199. Figure 6 , for example, based on the information included in TCI 610 , network node 604 may receive and network node 602 may send data transmission 614 .

[0120] Fig.111100 is an example of a hardware implementation of an example device 1104. The device 1104 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the device 1104 may include a cellular baseband processor 1124 (also referred to as a modem) coupled to one or more transceivers 1122 (e.g., a cellular RF transceiver). The cellular baseband processor 1124 may include on-chip memory 1124'. In some aspects, the device 1104 may also include one or more subscriber identity module (SIM) cards 1120 and an application processor 1106 coupled to a secure digital (SD) card 1108 and a screen 1110. The application processor 1106 may include on-chip memory 1106'. In some aspects, the device 1104 may also include a Bluetooth module 1112, a WLAN module 1114, an SPS module 1116 (e.g., a GNSS module), one or more sensor modules 1118 (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 1126, a power source 1130, and / or a camera 1132. The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 1112, the WLAN module 1114, and the SPS module 1116 may include their own dedicated antennas and / or communicate using antennas 1180. The cellular baseband processor 1124 communicates with the UE 104 and / or with the RU associated with the network entity 1102 through the transceiver 1122 via one or more antennas 1180. The cellular baseband processor 1124 and the application processor 1106 may each include a computer-readable medium / memory 1124', 1106', respectively. The additional memory module 1126 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 1124', 1106', 1126 may be non-transitory. The cellular baseband processor 1124 and the application processor 1106 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 1124 / application processor 1106, enables the cellular baseband processor 1124 / application processor 1106 to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 1124 / application processor 1106 when executing the software.The cellular baseband processor 1124 / application processor 1106 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 1104 may be a processor chip (modem and / or application) and include only the cellular baseband processor 1124 and / or the application processor 1106, while in another configuration, the device 1104 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 1104.

[0121] As discussed above, the NCBB TCI component 198 is configured to send a TCI indicating a non-codebook based beam direction to a wireless device based on at least one of the QCL information or the angle information, and send a data transmission to the wireless device via the non-codebook based beam direction indicated in the TCI. In some aspects, the NCBB TCI component 198 may also be configured to receive a TCI indicating a non-codebook based beam direction from a network node, and receive a data transmission sent via the non-codebook based beam direction indicated in the TCI from the network node. The NCBB TCI component 198 may be within the cellular baseband processor 1124, the application processor 1106, or within both the cellular baseband processor 1124 and the application processor 1106. The NCBB TCI component 198 may be one or more hardware components specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 1104 may include multiple components configured for various functions. In one configuration, the device 1104 (and specifically, the cellular baseband processor 1124 and / or the application processor 1106) includes a component for sending a TCI indicating a non-codebook-based beam direction based on angle information. The device 1104 may also include a component for sending data transmission via the non-codebook-based beam direction indicated in the TCI, and the data transmission is sent to the network node. The device 1104 may also include a component for obtaining the angle information about the AoD set associated with the original channel. The device 1104 may also include a component for identifying the first AoD associated with the peak gain in the AoD set. The device 1104 may also include a component for receiving the angle information from the network node based on a beam scanning signal set exchanged with the network node. The device 1104 may also include a component for performing one or more compressed sensing techniques to obtain the angle information. The device 1104 may also include a component for performing machine learning operations to obtain the angle information. The apparatus 1104 may also include a component for receiving a TCI indicating a non-codebook based beam direction. The apparatus 1104 may also include a component for receiving a data transmission sent via the non-codebook based beam direction indicated in the TCI, the data transmission being received from a network node. The apparatus 1104 may also include a component for receiving a reference transmission set for a beam scanning operation. The apparatus 1104 may also include a component for identifying angle information associated with at least one beam direction, the at least one beam direction being associated with the reference transmission set. The apparatus 1104 may also include a component for sending the angle information to the network node, wherein the TCI is based on the angle information.The apparatus 1104 may also include means for adjusting a receive beam direction based on the TCI and the angle information.

[0122] These components may be the NCBB TCI components 198 of the device 1104 configured to perform the functions recited by the components. As described above, the device 1104 may include the TX processor 368, the RX processor 356, and the controller / processor 359. Thus, in one configuration, these components may be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the components.

[0123] Fig.121200 is a diagram illustrating an example of a hardware implementation for a network entity 1202. The network entity 1202 may be a BS, a component of a BS, or may implement BS functionality. The network entity 1202 may include at least one of a CU 1210, a DU 1230, or a RU 1240. For example, depending on the layer functionality handled by the NCBB TCI component 199, the network entity 1202 may include a CU 1210; both a CU 1210 and a DU 1230; each of the CU 1210, the DU 1230, and the RU 1240; the DU 1230; both the DU 1230 and the RU 1240; or the RU 1240. The CU 1210 may include a CU processor 1212. The CU processor 1212 may include an on-chip memory 1212'. In some aspects, the CU 1210 may also include an additional memory module 1214 and a communication interface 1218. CU1210 communicates with DU 1230 via a midhaul link (such as an F1 interface). DU 1230 may include a DU processor 1232. DU processor 1232 may include on-chip memory 1232'. In some aspects, DU 1230 may also include an additional memory module 1234 and a communication interface 1238. DU 1230 communicates with RU 1240 via a fronthaul link. RU 1240 may include a RU processor 1242. RU processor 1242 may include on-chip memory 1242'. In some aspects, RU 1240 may also include an additional memory module 1244, one or more transceivers 1246, an antenna 1280, and a communication interface 1248. RU 1240 communicates with UE 104. On-chip memory 1212', 1232', 1242' and additional memory modules 1214, 1234, 1244 can each be considered a computer-readable medium / memory. Each computer-readable medium / memory can be non-transitory. Each of the processors 1212, 1232, 1242 is responsible for general processing, including executing software stored on the computer-readable medium / memory. The software, when executed by the corresponding processor, enables the processor to perform the various functions described above. The computer-readable medium / memory can also be used to store data manipulated by the processor when executing the software.

[0124] As discussed above, the NCBB TCI component 199 is configured to receive a TCI indicating a non-codebook based beam direction from a network node, and to receive a data transmission from the network node via the non-codebook based beam direction indicated in the TCI. In some aspects, the NCBB TCI component 199 may also be configured to send a TCI indicating a non-codebook based beam direction to a wireless device based on at least one of the QCL information or the angle information, and to send a data transmission to the wireless device via the non-codebook based beam direction indicated in the TCI. The NCBB TCI component 199 may be within one or more processors of one or more of the CU 1210, DU 1230, and RU 1240. The NCBB TCI component 199 may be one or more hardware components that are specifically configured to perform the process / algorithm, implemented by one or more processors configured to perform the process / algorithm, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 1202 may include a variety of components configured for various functions. In one configuration, the network entity 1202 includes a component for receiving a TCI indicating a non-codebook based beam direction. The network entity 1202 may also include a component for receiving a data transmission sent via the non-codebook based beam direction indicated in the TCI. The network entity 1202 may also include a component for receiving a reference transmission set for a beam scanning operation. The network entity 1202 may also include a component for identifying angle information associated with at least one beam direction, the at least one beam direction being associated with the reference transmission set. The network entity 1202 may also include a component for sending the angle information to the network node, wherein the TCI is based on the angle information. The network entity 1202 may also include a component for adjusting the receive beam direction based on the TCI and the angle information. The network entity 1202 may also include a component for sending a TCI indicating a non-codebook based beam direction based on the angle information. The network entity 1202 may also include a component for sending a data transmission via the non-codebook based beam direction indicated in the TCI, the data transmission being sent to the network node. The network entity 1202 may also include a component for obtaining angle information about a set of AoDs associated with the original channel. The network entity 1202 may also include a component for identifying a first AoD in the set of AoDs associated with a peak gain. The network entity 1202 may also include a component for receiving the angle information from the network node based on a set of beam scanning signals exchanged with the network node. The network entity 1202 may also include a component for performing one or more compressed sensing techniques to obtain the angle information. The network entity 1202 may also include a component for performing a machine learning operation to obtain the angle information.These components may be the NCBB TCI components 199 of the network entity 1202 configured to perform the functions recited by the components. As described above, the network entity 1202 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, these components may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the components.

[0125] In some aspects of wireless communication, a pair of network devices (e.g., base stations, UEs, or other wireless devices associated with a wireless network) may communicate via a set of directional beams. The pair of network devices may include a first network device configured with a first (preconfigured and / or known) beam codebook and a second network device with a second (preconfigured and / or known) beam codebook. In some aspects, the beam codebook may be associated with a fixed set of beam directions, such that the first beam codebook may be associated with a first number of preconfigured beam directions and the second beam codebook may be associated with a second number of preconfigured beam directions.

[0126] In some aspects, the pair of network devices including the first network device and the second network device may select a most appropriate pair of beams (e.g., beam directions) from the first beam codebook and the second beam codebook for communication between the first network device and the second network device. In some aspects, the selected most appropriate pair of beams may not represent an optimal set of beam directions that maximizes channel gain (e.g., using an optimal beam direction to maximize signal strength of communication). In some aspects, the inability to select the optimal set of beam directions may be based on a quantization of the first codebook beam directions and the second codebook beam directions. For example, a UE may include a first beam codebook based on a set of beams having azimuth intervals of ~90 degrees and elevation intervals of ~90 degrees, which may be associated with four different beam directions (e.g., (φ r ,θ r ) = {[-45,45],[-45,135],[45,45],[45,135]}). In some aspects, a base station (or other UE) may be associated with a finer quantization (e.g., azimuth spacing of 45 degrees, elevation spacing of 22.5 degrees, possibly with 32 different beam directions (e.g., (φ r ,θ r )={[-78.75,22.5],[-78.75,67.5],…,[-56.25,112.5],…,[78.75,157.5]}).

[0127] In some aspects, the granularity of quantization may reduce the spectral efficiency of the communication below the theoretical maximum spectral efficiency.By introducing the use of non-codebook based beams, the apparatus and methods disclosed herein may provide higher spectral efficiency.

[0128] It should be understood that the specific order or hierarchy of the blocks in the disclosed process / flowchart is only 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. In addition, 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.

[0129] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not limited to the various aspects described herein, but should be given the full scope consistent with the language claims. Unless otherwise specified, reference to an element in the singular form does not mean "one and only one", but "one or more". Terms such as "if", "when ..." and "at ..." do not mean a direct temporal relationship or reaction. That is, these phrases, such as "when ...", do not mean an instant action in response to the occurrence of an action or during the occurrence of an action, but only mean that if the condition is met, the action will occur without a specific or instantaneous time constraint to make the action occur. The word "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described as "exemplary" herein is not necessarily interpreted as being preferred or having 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, and may include multiple A, multiple B, or multiple C. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, where any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, where the number of elements is one or more. Thus, for a set of X, X will include one or more elements. If the first device receives data from the second device or sends data to the second device, data may be directly received / sent between the first device and the second device, or indirectly received / sent between the first device and the second device through a collection of devices. All structural and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or will later be known to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device", etc. cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

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

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

[0132] Aspect 1 is a method for performing wireless communications at a network node, the method comprising: sending a TCI indicating a non-codebook based beam direction to a wireless device based on at least one of QCL information or angle information; and sending data to the wireless device via the non-codebook based beam direction indicated in the TCI.

[0133] Aspect 2 is a method according to aspect 1, the method further comprising: obtaining the angle information about an AoD set associated with an original channel; and identifying a first AoD in the AoD set associated with a peak gain, wherein the TCI is based on the first AoD.

[0134] Aspect 3 is a method according to aspect 2, wherein the non-codebook based beam direction is a suitable beam direction closest to the first AoD.

[0135] Aspect 4 is a method according to any one of Aspects 2 to 3, wherein obtaining the angle information about the AoD set includes one or more of the following: receiving the angle information from the network node based on a beam scanning signal set exchanged with the network node; performing one or more compressed sensing techniques to obtain the angle information; or performing a machine learning operation to obtain the angle information.

[0136] Aspect 5 is a method according to any one of Aspects 1 to 4, wherein the TCI indicates the non-codebook based beam direction via an indication of a first azimuth angle associated with the non-codebook based beam direction and a second elevation angle associated with the non-codebook based beam direction.

[0137] Aspect 6 is a method according to aspect 5, wherein the indication of the first azimuth angle and the second elevation angle is indicated as a set of azimuth and elevation angle pairs via a bitmap.

[0138] Aspect 7 is a method according to Aspect 6, wherein the indication of the first azimuth angle and the second elevation angle is indicated via a plurality of non-zero values ​​in the bitmap, wherein each non-zero value of the plurality of non-zero values ​​is associated with a corresponding weight, wherein the plurality of non-zero values ​​in the bitmap and the corresponding weights are used to indicate a beam direction that is inconsistent with an azimuth and elevation angle pair in the set of the azimuth and elevation angle pairs.

[0139] Aspect 8 is a method according to any one of Aspects 1 to 5, wherein the TCI indicates the non-codebook based beam direction based on quasi-co-location with a set of reference beam directions, wherein each reference beam direction includes one of the following: (1) a reference signal among multiple reference signals; or (2) a configured beam direction among multiple configured beam directions.

[0140] Aspect 9 is a method according to Aspect 8, wherein the reference beam direction set includes multiple reference beam directions, and each reference beam direction in the reference beam direction set is associated with a corresponding weight in a corresponding weight set, wherein the multiple reference beam directions and the corresponding weight set are used to indicate beam directions that are inconsistent with a specific reference beam direction.

[0141] Aspect 10 is a method according to any one of aspects 1 to 9, wherein the wireless device is a base station, a component of the base station, a first network node, a component of the first network node, a first network entity, or a component of the first network entity.

[0142] Aspect 11 is a method for wireless communication at a wireless device, the method comprising: receiving a TCI indicating a non-codebook based beam direction from a network node; and receiving a data transmission from the network node via the non-codebook based beam direction indicated in the TCI.

[0143] Aspect 12 is a method according to Aspect 11, the method further comprising: receiving a reference transmission set for a beam scanning operation; identifying angle information associated with at least one beam direction, wherein the at least one beam direction is associated with the reference transmission set; and sending the angle information to the network node, wherein the TCI is based on the angle information.

[0144] Aspect 13 is a method according to aspect 12, wherein the wireless device identifies a first AoD associated with a peak gain based on the angle information, the TCI is based on the first AoD, and the non-codebook based beam direction is a suitable beam direction closest to the first AoD.

[0145] Aspect 14 is a method according to any one of Aspects 12 to 13, the method further comprising: adjusting a receive beam direction based on the TCI and the angle information.

[0146] Aspect 15 is a method according to any one of Aspects 11 to 14, wherein the TCI indicates the non-codebook based beam direction via an indication of a first azimuth angle associated with the non-codebook based beam direction and a second elevation angle associated with the non-codebook based beam direction.

[0147] Aspect 16 is a method according to aspect 15, wherein the indication of the first azimuth angle and the second elevation angle is indicated as a set of azimuth and elevation angle pairs via a bitmap.

[0148] Aspect 17 is a method according to Aspect 16, wherein the indication of the first azimuth angle and the second elevation angle is indicated via a plurality of non-zero values ​​in the bitmap, wherein each non-zero value of the plurality of non-zero values ​​is associated with a corresponding weight, wherein the plurality of non-zero values ​​in the bitmap and the corresponding weights are used to indicate a beam direction that is inconsistent with an azimuth and elevation angle pair in the set of the azimuth and elevation angle pairs.

[0149] Aspect 18 is a method according to any one of Aspects 11 to 15, wherein the TCI indicates the non-codebook based beam direction based on quasi-co-location with a set of reference beam directions, wherein each reference beam direction includes one of the following: (1) a reference signal among multiple reference signals; or (2) a configured beam direction among multiple configured beam directions.

[0150] Aspect 19 is a method according to Aspect 18, wherein the reference beam direction set includes multiple reference beam directions, and each reference beam direction in the reference beam direction set is associated with a corresponding weight in a corresponding weight set, wherein the multiple reference beam directions and the corresponding weight set are used to indicate beam directions that are inconsistent with a specific reference beam direction.

[0151] Aspect 20 is a method according to any one of aspects 11 to 19, wherein the wireless device is a UE or a component of the UE.

[0152] Aspect 21 is an apparatus for wireless communication at a device, the apparatus comprising a memory and at least one processor, the at least one processor being coupled to the memory and being configured to implement any one of Aspects 1 to 20 based at least in part on information stored in the memory.

[0153] Aspect 22 is the method according to aspect 21, the method further comprising a transceiver or an antenna coupled to the at least one processor.

[0154] Aspect 23 is an apparatus for wireless communication at a device, the apparatus comprising means for implementing any one of aspects 1 to 20.

[0155] Aspect 24 is a computer-readable medium (eg, non-transitory 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 20.

Claims

1. An apparatus for wireless communication at a wireless device, 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 transmit configuration indicator (TCI) indicating a non-codebook based beam direction from a network node; and Receiving, from the network node, data transmission via the non-codebook based beam direction indicated in the TCI.

2. The apparatus of claim 1 , wherein the at least one processor is further configured to: receiving a reference signal transmission set for a beam scanning operation; identifying angle information associated with at least one beam direction, the at least one beam direction being associated with the reference signal transmission set; and The angle information is sent to the network node, wherein the TCI is based on the angle information.

3. The device according to claim 2, wherein: The wireless device identifies a first angle of departure (AoD) associated with a peak gain based on the angle information, The TCI is based on the first AoD, and The non-codebook based beam direction is a suitable beam direction closest to the first AoD.

4. The apparatus of claim 2, wherein the at least one processor is further configured to: The receive beam direction is adjusted based on the TCI and the angle information.

5. The apparatus of claim 2, wherein to identify the angle information associated with the at least one beam direction, the at least one processor is configured to: Perform one or more of the following: (1) one or more compressed sensing operations to obtain channel angle information associated with the at least one beam direction; or (2) machine learning operations to obtain the channel angle information associated with the at least one beam direction.

6. The apparatus of claim 1, wherein the TCI indicates the non-codebook based beam direction via an indication of a first azimuth angle associated with the non-codebook based beam direction and a second elevation angle associated with the non-codebook based beam direction. 7 . The apparatus of claim 6 , wherein the indication of the first azimuth angle and the second elevation angle is indicated as a set of azimuth and elevation angle pairs via a bitmap.

8. The apparatus of claim 7, wherein the indication of the first azimuth angle and the second elevation angle is indicated via a plurality of non-zero values ​​in the bitmap, wherein each non-zero value of the plurality of non-zero values ​​is associated with a corresponding weight, wherein the plurality of non-zero values ​​in the bitmap and the corresponding weights are used to indicate a beam direction that is inconsistent with an azimuth and elevation angle pair in the set of azimuth and elevation angle pairs.

9. An apparatus according to claim 1, wherein the TCI indicates the non-codebook based beam direction based on quasi co-location with a set of reference beam directions, wherein each reference beam direction comprises one of the following: (1) a reference signal among multiple reference signals; or (2) a configured beam direction among multiple configured beam directions.

10. The apparatus of claim 9, wherein the reference beam direction set comprises a plurality of reference beam directions, and each reference beam direction in the reference beam direction set is associated with a corresponding weight in a corresponding weight set, wherein the plurality of reference beam directions and the corresponding weight set are used to indicate beam directions that are inconsistent with a specific reference beam direction.

11. The apparatus of claim 1, wherein the wireless device is a user equipment (UE) or a component of the UE.

12. 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: Based on at least one of quasi co-location (QCL) information or angle information, sending a transmit configuration indicator (TCI) indicating a non-codebook based beam direction to the wireless device; and Data is transmitted to the wireless device via the non-codebook based beam direction indicated in the TCI.

13. The apparatus of claim 12, wherein the at least one processor is further configured to: obtaining said angle information about a set of angles of departure (AoD) associated with an original channel; and A first AoD in the set of AoDs that is associated with a peak gain is identified, wherein the TCI is based on the first AoD.

14. The apparatus of claim 13, wherein the non-codebook based beam direction is a suitable beam direction closest to the first AoD.

15. The apparatus of claim 12, wherein the TCI indicates the non-codebook based beam direction via an indication of a first azimuth angle associated with the non-codebook based beam direction and a second elevation angle associated with the non-codebook based beam direction.

16. The apparatus of claim 15, wherein the indication of the first azimuth angle and the second elevation angle is indicated as a set of azimuth and elevation angle pairs via a bitmap.

17. The apparatus of claim 16, wherein the indication of the first azimuth angle and the second elevation angle is indicated via a plurality of non-zero values ​​in the bitmap, wherein each non-zero value of the plurality of non-zero values ​​is associated with a corresponding weight, wherein the plurality of non-zero values ​​in the bitmap and the corresponding weights are used to indicate a beam direction that is inconsistent with an azimuth and elevation angle pair in the set of azimuth and elevation angle pairs.

18. An apparatus according to claim 12, wherein the TCI indicates the non-codebook based beam direction based on a QCL with a set of reference beam directions, wherein each reference beam direction comprises one of the following: (1) a reference signal among multiple reference signals; or (2) a configured beam direction among multiple configured beam directions.

19. An apparatus according to claim 18, wherein the reference beam direction set includes multiple reference beam directions, and each reference beam direction in the reference beam direction set is associated with a corresponding weight in a corresponding weight set, wherein the multiple reference beam directions and the corresponding weight set are used to indicate beam directions that are inconsistent with a specific reference beam direction.

20. The apparatus of claim 12, wherein the network node is a base station, a component of the base station, a first network entity, or a component of the first network entity.

21. A method for wireless communication at a network node, the method comprising: Based on at least one of quasi co-location (QCL) information or angle information, sending a transmit configuration indicator (TCI) indicating a non-codebook based beam direction to the wireless device; and Data is transmitted to the wireless device via the non-codebook based beam direction indicated in the TCI.

22. The method according to claim 21, further comprising: obtaining said angle information about a set of angles of departure (AoD) associated with an original channel; as well as A first AoD in the set of AoDs that is associated with a peak gain is identified, wherein the TCI is based on the first AoD.

23. The method of claim 21, wherein the TCI indicates the non-codebook based beam direction via an indication of a first azimuth angle associated with the non-codebook based beam direction and a second elevation angle associated with the non-codebook based beam direction.

24. The method of claim 23, wherein the indication of the first azimuth angle and the second elevation angle is indicated as a set of azimuth angle and elevation angle pairs via a bitmap, and the indication of the first azimuth angle and the second elevation angle is indicated via a plurality of non-zero values ​​in the bitmap, wherein each non-zero value of the plurality of non-zero values ​​is associated with a corresponding weight, wherein the plurality of non-zero values ​​in the bitmap and the corresponding weights are used to indicate a beam direction that is inconsistent with an azimuth angle and elevation angle pair in the set of azimuth angle and elevation angle pairs.

25. A method according to claim 21, wherein the TCI indicates the non-codebook based beam direction based on quasi co-location with a set of reference beam directions, wherein each reference beam direction comprises one of the following: (1) a reference signal from a plurality of reference signals; or (2) a configured beam direction from a plurality of configured beam directions, wherein the set of reference beam directions comprises a plurality of reference beam directions, and each reference beam direction in the set of reference beam directions is associated with a corresponding weight in a corresponding weight set, wherein the plurality of reference beam directions and the corresponding weight set are used to indicate a beam direction that is inconsistent with a particular reference beam direction.

26. A method of wireless communication at a wireless device, the method comprising: receiving a transmit configuration indicator (TCI) indicating a non-codebook based beam direction from a network node; as well as Receiving, from the network node, data transmission via the non-codebook based beam direction indicated in the TCI.

27. The method according to claim 26, further comprising: receiving a reference transmit set for a beam scanning operation; identifying angle information associated with at least one beam direction associated with the reference transmission set based on performing one or more of: (1) one or more compressed sensing operations to obtain channel angle information associated with the at least one beam direction; or (2) a machine learning operation to obtain the channel angle information associated with the at least one beam direction, wherein the wireless device identifies a first angle of departure (AoD) associated with a peak gain based on the angle information; sending the angle information to the network node, wherein the TCI is based on the first AoD, and the non-codebook based beam direction is a suitable beam direction closest to the first AoD; and The receive beam direction is adjusted based on the TCI and the angle information.

28. The method of claim 26, wherein the TCI indicates the non-codebook based beam direction via an indication of a first azimuth angle associated with the non-codebook based beam direction and a second elevation angle associated with the non-codebook based beam direction.

29. The method of claim 28, wherein the indication of the first azimuth angle and the second elevation angle is indicated as a set of azimuth angle and elevation angle pairs via a bitmap, and the indication of the first azimuth angle and the second elevation angle is indicated via a plurality of non-zero values ​​in the bitmap, wherein each non-zero value of the plurality of non-zero values ​​is associated with a corresponding weight, wherein the plurality of non-zero values ​​in the bitmap and the corresponding weights are used to indicate a beam direction that is inconsistent with an azimuth angle and elevation angle pair in the set of azimuth angle and elevation angle pairs.

30. A method according to claim 26, wherein the TCI indicates the non-codebook based beam direction based on quasi co-location with a set of reference beam directions, wherein each reference beam direction comprises one of the following: (1) a reference signal from a plurality of reference signals; or (2) a configured beam direction from a plurality of configured beam directions, wherein the set of reference beam directions comprises a plurality of reference beam directions, and each reference beam direction in the set of reference beam directions is associated with a corresponding weight in a corresponding weight set, wherein the plurality of reference beam directions and the corresponding weight set are used to indicate beam directions that are inconsistent with a particular reference beam direction.

Images