Layer 1 reporting enhancements for base station assisted beam pair prediction

Abstract

An apparatus for wireless communication at a UE is disclosed. The apparatus includes a memory and at least one processor coupled to the memory. The apparatus is configured to measure a CMR for each of the one or more downlink transmit beams. The apparatus is further configured to transmit an L1 measurement report comprising one or more measurements for the CMR and a receive beam identifier (ID) of a receive beam for each of the one or more measurements. Different measurements associated with the same CMR are associated with receiving beams identified by different UEs.

Description

Technical Field

[0001] The present disclosure relates generally to communication systems, and more particularly to wireless communications including layer 1 (L1) reporting. 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). 5G NR is part of the continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)) and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communication (mMTC), and ultra-reliable low latency communication (URLLC). Certain aspects of 5G NR may be based on 4G Long Term Evolution (LTE) standards. It is necessary to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the invention

[0004] The following presents a summary of one or more aspects in order to provide a basic understanding of these aspects. This summary is not an extensive review of all envisioned aspects. This summary is neither intended to identify the key or important elements of all aspects, nor to describe the scope of any or all aspects. Its only 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, computer readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The apparatus measures a channel measurement resource (CMR) for each of one or more downlink transmit beams. The apparatus sends a layer 1 (L1) measurement report, the report including one or more measurements for the CMR and a receive beam identifier (ID) for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs.

[0006] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a network node are provided. The apparatus obtains a layer 1 (L1) measurement report, the report including one or more measurements of a channel measurement resource (CMR) and a receive beam identifier (ID) of a receive beam at a user equipment (UE) for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs. The apparatus activates at least one transmit configuration indication (TCI) state having a quasi co-location (QCL) relationship with a receive beam at the UE.

[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 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 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 4Depicted are example artificial intelligence (AI) / machine learning (ML) algorithms.

[0015] Figure 5 is a diagram illustrating example communications between a base station and a UE for beamforming according to various aspects of the present disclosure.

[0016] Figure 6 is a diagram illustrating example AI / ML-based beam prediction.

[0017] Figure 7 is a diagram depicting example beam pair predictions.

[0018] Figure 8 is a diagram depicting an example enhanced L1 reporting based on beam pairs.

[0019] Fig. 9 is a diagram depicting the association between a UE Rx beam identifier and a UE Rx beam.

[0020] Fig.10 is a diagram depicting an example of compression of enhanced L1 reports.

[0021] Fig.11 is a diagram depicting another example of compression of enhanced L1 reports.

[0022] Fig.12 is a diagram depicting yet another example of compression of enhanced L1 reports.

[0023] Fig.13 is a diagram depicting different schemes for reporting compressed payloads.

[0024] Fig.14 is a diagram depicting an example of CSI report partitioning.

[0025] Fig.15 is a diagram depicting another example of CSI report partitioning.

[0026] Fig.16 is a diagram depicting an example of generating multiple CSI reports.

[0027] Fig.17 is a diagram describing example TCI state activation / switching for a beam pair.

[0028] Fig.18 An example communication flow between a UE and a base station is illustrated.

[0029] Fig.19 is a diagram illustrating an example of a TCI state according to the present disclosure.

[0030] Fig. 20is a diagram illustrating an example of a TCI state switching timeline according to the present disclosure.

[0031] Fig.21 is a diagram illustrating an example of predicting channel characteristics according to the present disclosure.

[0032] Fig. 22 is a diagram illustrating an example of using a semi-known TCI state according to the present disclosure.

[0033] Fig.23 is a flow chart of a method of wireless communication.

[0034] Fig.24 is a flow chart of another method of wireless communication.

[0035] Fig.25 are diagrams illustrating examples of hardware implementations for example apparatuses and / or network entities.

[0036] Fig.26 is a diagram illustrating an example of a hardware implementation for an example network entity. DETAILED DESCRIPTION

[0037] Beam management refers to the technology and process used to enable the transmission and reception of data on a relatively narrow beam. Predictive beam management can result in reduced power consumption and reduced overhead while improving accuracy, latency and throughput. The UE can be configured to report beam quality in the form of a report provided to the base station. However, the report sent by the UE to the base station may be based on the transmit (Tx) beam from the base station. The various aspects presented herein enable the base station to perform beam management by selecting a receive beam at the UE based on an L1 report including receive beam information associated with the L1 measurement. In some aspects, the L1 report can be used for base station assisted beam pair prediction. For example, the UE may measure the channel measurement resources (CMR) for each of one or more downlink transmit beams. The UE may send a layer 1 (L1) measurement report, which includes one or more measurements for the CMR and a receive beam identifier (ID) for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs. By using such L1 reports for ML model training purposes and at inference, L1 reports can reduce the number of beam scans during beam scanning and help the base station assist beam pair prediction. In this way, enhanced L1 reports can reduce latency and UE power consumption. In addition, other aspects described herein include report compression, CSI partitioning, and TCI state activation / switching based on enhanced L1 reports.

[0038] The specific embodiments described below in conjunction with the accompanying drawings are descriptions of various configurations and do not represent the only configurations with 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.

[0039] 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 can 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.

[0040] 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. The example of a processor includes a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, a gate logic component, a discrete hardware circuit and other suitable hardware configured to perform various functions 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 an instruction, an instruction set, a code, a code segment, a program code, a program, a subroutine, a software component, an application, a software application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a process, a function or any combination thereof.

[0041] 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. Storage media may be any available medium that can be accessed by a computer. By way of example, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical 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.

[0042] Although various aspects, implementations and / or use cases are described in this application by illustrating some examples, additional or different aspects, implementations and / or use cases may be generated in many different arrangements and scenarios. The various aspects, implementations and / or use cases described herein may be implemented across many different platform types, devices, systems, shapes, sizes and packaging arrangements. For example, aspects, implementations and / or use cases may be generated via integrated chip implementations and other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase devices, medical devices, 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 examples described may have a wide range of applicability. Aspects, implementations and / or use cases may range from chip-level or modular components to non-modular, non-chip-level 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 device in conjunction with the various aspects and features described may also include additional components and features for implementing and practicing the various aspects protected and described by the claims. For example, the transmission and reception of wireless signals include multiple components for analog and digital purposes (e.g., hardware components including antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc.). The various 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.

[0043] The deployment of a communication system (such as a 5G NR system) can be arranged with various components or constituent parts in a variety of ways. In a 5G NR system or network, a network node, a network entity, a mobility element of a network, a radio access network (RAN) node, a core network node, a network element or a network equipment (such as a base station (BS), or one or more units (or one or more components) 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 (for example, which may be referred to as a gNB), an access point (AP), a transmit receive point (TRP) or a cell, etc.) can be implemented as an aggregated base station (also called an independent BS or a monolithic BS) or a decomposed base station.

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

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

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

[0047] 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 these units or an associated processor or controller that provides instructions to the communication interface of these units may be configured to communicate with one or more of the other units via a transmission medium. For example, these units may include a wired interface configured to receive 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.

[0048] In some aspects, CU 110 may host one or more high-level 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 functions (i.e., central unit-user plane (CU-UP)), control plane functions (i.e., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 110 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 110 may be implemented to communicate with DU 130 for network control and signaling.

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

[0050] The low-layer functionality may be implemented by one or more RUs 140. In some deployments, a RU 140 controlled by a DU 130 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 140 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 140 may be controlled by the corresponding DU 130. In some scenarios, this configuration may enable the implementation of the DU 130 and the CU 110 in a cloud-based RAN architecture (such as a vRAN architecture).

[0051] 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 to instantiate virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 110, DU 130, RU 140, and near-RT RIC 125. In some specific implementations, the SMO framework 105 may communicate with hardware aspects of the 4G RAN, such as an open eNB (O-eNB) 111, via the O1 interface. 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 .

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

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

[0054] 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 be through one or more carriers. For each carrier allocated in a carrier aggregation of up to Yx MHz (x component carriers) for transmission in each direction, the base station 102 / UE 104 may use a spectrum of up to Y MHz (e.g., 5MHz, 10MHz, 15MHz, 20MHz, 100MHz, 400MHz, etc.) bandwidth. The carriers may be adjacent to each other 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).

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

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

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

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

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

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

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

[0062] 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, the LMF 166, the positioning determination entity (PDE), the serving mobile location center (SMLC), the mobile positioning center (MPC), etc. The GMLC 165 and the LMF 166 support UE location services. The GMLC 165 provides an interface for clients / applications (e.g., emergency services) to access UE positioning information. The LMF 166 receives measurements and assistance information from the NG-RAN and the UE 104 via the AMF 161 to calculate the positioning of the UE 104. The NG-RAN may determine the positioning of the UE 104 using one or more positioning methods. Positioning the UE 104 may involve signal measurements, positioning estimates, and optional speed calculations based on these measurements. Signal measurements may be performed by the UE 104 and / or the serving base station 102. The measured signals may be based on a satellite positioning system (SPS) 170 (e.g., one or more of a global navigation satellite system (GNSS), a global positioning system (GPS), a non-terrestrial network (NTN), or other satellite positioning / 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.

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

[0064] See again Figure 1 In some aspects, the UE 104 may include an L1 reporting component 198 configured to measure the CMR for each of one or more downlink transmit beams and send an L1 measurement report including one or more measurements for the CMR and a receive beam ID for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs. In some aspects, the base station 102 may include a receive beam indication component 199 configured to obtain an L1 measurement report including one or more measurements for the CMR and identifying a receive beam at the UE for each of the one or more measurements, and to activate at least one TCI state having a QCL relationship with the receive beam at the UE. 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.

[0065] Figure 2A FIG200 is a diagram illustrating an example of a first subframe within a 5G NR frame structure. Figure 2B FIG230 is a diagram illustrating an example of DL channels within a 5G NR subframe. Figure 2C FIG250 is a diagram illustrating an example of a second subframe within a 5G NR frame structure. Figure 2DFIG280 is a diagram illustrating an example of UL channels within a 5G NR subframe. The 5G NR frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to either DL or UL, or may be time division duplex (TDD), where for a particular set of subcarriers (carrier system bandwidth), subframes within that subcarrier set are dedicated to both DL and UL. Figure 2A , Figure 2C In the example provided, the 5G NR frame structure is assumed to be TDD, where subframe 4 is configured with slot format 28 (most of which are DL), where D is DL, U is UL, and F is flexible between DL / UL, and subframe 3 is configured with slot format 1 (all of which are UL). Although subframes 3 and 4 are shown as having slot formats 1 and 28, respectively, any particular subframe may be configured with any of the various available slot formats 0 to 61. Slot formats 0 and 1 are both DL and both 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.

[0066] FIG. 2A to FIG. 2D The frame structure is illustrated, and various aspects of the present disclosure may be applicable to other wireless communication technologies that may have different frame structures and / or different channels. A frame (10ms) may be divided into 10 subframes of the same size (1ms). Each subframe may include one or more time slots. A subframe may also include a microslot, which may include 7, 4 or 2 symbols. Each time slot may include 14 or 12 symbols, depending on whether the cyclic prefix (CP) is conventional or extended. For a conventional CP, each time slot may include 14 symbols, and for an extended CP, each time slot may include 12 symbols. The 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.

[0067]

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

[0069] A resource grid may be used to represent a 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.

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

[0071] Figure 2BExamples of various DL channels within a subframe of a frame are illustrated. A physical downlink control channel (PDCCH) carries DCI within one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE including six RE groups (REGs), each REG including 12 consecutive REs in an OFDM symbol of an RB. A PDCCH within a BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on a CORESET, wherein the PDCCH candidates have different DCI formats and different aggregation levels. Additional BWPs may be located at higher and / or lower frequencies on the channel bandwidth. A primary synchronization signal (PSS) may be within symbol 2 of a particular subframe of a frame. The PSS is used by UE 104 to determine subframe / symbol timing and physical layer identity. 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.

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

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

[0074] Figure 3 370 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 functions. Layer 3 includes a radio resource control (RRC) layer, and layer 2 includes a service data adaptation protocol (SDAP) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller / processor 375 provides RRC layer functions associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (encryption, decryption, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with delivery of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

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

[0076] At the UE 350, each receiver 354Rx receives a signal through its corresponding antenna 352. Each receiver 354Rx recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functionality associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial stream destined for the UE 350. If multiple spatial streams are destined for the UE 350, they can be 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 base station 310. The data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functions.

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

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

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

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

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

[0082] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to combine Figure 1 The L1 reporting component 198 is used to perform various aspects.

[0083] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to combine Figure 1 The receive beam indication component 199 performs various aspects.

[0084] Beam management refers to the techniques and processes used to enable the transmission and reception of data on a relatively narrow beam. Beam management provides both the base station antenna and the UE antenna with means to lock onto a beam that provides a path from the transmitter to the receiver. Beam management may involve beamforming, beam scanning, beam measurement, beam determination, and beam reporting. Beam scanning refers to the base station antenna transmitting a beam in a predetermined sequence for beam measurement at the UE. Beam measurement refers to the UE measuring the quality of the received beamformed signal. Beamforming determination refers to the UE selecting a beam based on the measured quality. Beam reporting refers to the UE reporting information to the base station based on the quality.

[0085] As described above, during beam measurement, the UE identifies the quality of the beam via measurements at the UE. The UE utilizes power and / or computational overhead to perform the measurements. Such power and / or computational overhead may adversely affect the accuracy of the measurements. In addition, latency and / or throughput may be affected by beam selection / reselection / recovery.

[0086] Predictive beam management in the time domain (TD), frequency domain (FD), and / or spatial domain (SD) can result in reduced power consumption and reduced overhead while improving accuracy, latency, and throughput. For example, by predicting unmeasured beam quality, power consumption and / or overhead at the UE can be reduced while increasing accuracy. In addition, by predicting future beam blockages and / or failures, latency and / or throughput can be improved. However, predicting future transmit beam quality may depend on the movement speed and / or trajectory of the UE, and predicting future receive beams may not properly account for interference. Therefore, it is challenging to predict future beams using statistical signaling processing methods.

[0087] Predictive beam management may involve the use of AI / ML models to address issues related to overhead, complexity, and latency. For example, an ML model may be trained to predict beam quality, candidate beams, beam failure, and / or beam blocking. In one example, beam quality may be a layer 1 reference signal received power (L1-RSRP) measurement or a layer 1 signal to interference plus noise ratio (L1-SINR) measurement. Predicting beam quality and / or candidate beams may result in reduced UE power consumption and / or reduced UE overhead in terms of radio signaling. Predicting beam failure and / or blocking may result in improved latency and / or throughput.

[0088] Predictions via the AI / ML model may be performed at the base station or at the UE. Generally speaking, a base station may have more computing resources available for prediction than those available to the UE. However, the UE may have access to more observations (e.g., measurements) than the base station. Therefore, the UE may generate more accurate predictions than those generated by the base station. However, the predictions performed by the UE consume power, which may be limited at the UE. The AI / ML model may be trained at the base station (or at some other computing device away from the UE). When the AI / ML model is trained at the base station, training data may be collected via an enhanced air interface or via an application layer method. When the AI / ML model is trained at the UE, additional UE computation, buffering, and data storage may be used for model training.

[0089] Figure 4 is an example of an AI / ML algorithm 400 that can be used in conjunction with wireless communication. The AI / ML algorithm 400 can include various functions, including data collection 402, model training function 404, model inference function 406, and participants 408.

[0090] Data collection 402 may be a function that provides input data to the model training function 404 and the model inference function 406. The data collection 402 function may include any form of data preparation, and it may not be specific to the specific implementation of the AI / ML algorithm (e.g., data preprocessing and cleaning, formatting, and transformation). Examples of input data may include, but are not limited to, channel state information (CSI) measurements from a UE or network node (such as L1-RSRP or L1-SINR), feedback from participants 408, and output from another AI / ML model. Data collection 402 may include training data and inference data, where training data refers to data to be transmitted as input to the AI / ML model training function 404, and inference data refers to data transmitted as input to the AI / ML model inference function 406.

[0091] The model training function 404 may be a function that performs ML model training, validation, and testing, which may generate model performance metrics as part of the model testing procedure. The model training function 404 may also be responsible for data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) based on the training data delivered or received from the data collection 402 function. The model training function 404 may deploy or update the trained, validated, and tested AI / ML model to the model inference function 406, and receive model performance feedback from the model inference function 406.

[0092] The model inference function 406 may be a function that provides an AI / ML model inference output (e.g., a prediction or decision). The model inference function 406 may also perform data preparation (e.g., data preprocessing and cleaning, formatting, and transformation) based on the inference data delivered from the data collection 402 function. The output of the model inference function 406 may include the inference output of the AI / ML model generated by the model inference function 406. The details of the inference output may be use case specific. For example, the output may include predicted L1-RSRP, predicted L1-SINR, predicted candidate beams, predicted beam failures, or predicted beam blocking. In some aspects, the participant may be a UE or a base station.

[0093] Model performance feedback may refer to information derived from model inference functionality 406 that may be applicable to improving the AI / ML model trained in model training functionality 404. Feedback from participants 408 or other network entities (via data collection 402 functionality) may be implemented for model inference functionality 406 to create model performance feedback.

[0094] Participants 408 may be functions that receive output from model inference function 406 and trigger or perform corresponding actions. Participants may trigger actions for network entities including other network entities or themselves. Participants 408 may also provide feedback information for model training function 404 or model inference function 406 to derive training or inference data or performance feedback. Feedback may be sent back to data collection 402.

[0095] The network may use machine learning algorithms, deep learning algorithms, neural networks, reinforcement learning, regression, boosting, or advanced signal processing methods for various aspects of wireless communication, including TCI state-based DCI selection to identify neighbor TCI candidates for autonomous TCI candidate set updates.

[0096] In some aspects described herein, the network may train one or more neural networks to learn the dependence of the quality of the measurement on various parameters. In addition, examples of machine learning models or neural networks that may be included in the network entity include artificial neural networks (ANNs); decision tree learning; convolutional neural networks (CNNs); deep learning architectures in which the outputs of the first layer of neurons become the inputs of the second layer of neurons, etc.; support vector machines (SVMs), for example, including a separating hyperplane (e.g., a decision boundary) for classifying data; regression analysis; Bayesian networks; genetic algorithms; deep convolutional networks (DCNs) configured with additional pooling and normalization layers; and deep belief networks (DBNs).

[0097] A machine learning model, such as an artificial neural network (ANN), may include a group of interconnected artificial neurons (e.g., a neuron model) and may be a computing device or may represent a method to be performed by a computing device. The connections of the neuron model may be modeled as weights. The machine learning model may provide predictive models, adaptive control, and other applications by training via a data set. The model may be adaptive based on external or internal information processed by the machine learning model. Machine learning may provide nonlinear statistical data models or decision making, and may model complex relationships between input data and output information.

[0098] The machine learning model may include multiple layers and / or operations, which may be formed by cascading one or more of the operations cited. Examples of operations that may be involved include: extraction of various features of data, convolution operations, fully connected operations that may be activated or deactivated, compression, decompression, quantization, flattening, etc. As used herein, the "layer" of the machine learning model can be used to represent operations on input data. For example, convolution layers and / or fully connected layers, etc. can be used to refer to associated operations on data input to the layer. Convolution A×B operations refer to operations that convert multiple input features A into multiple output features B. "Kernel size" may refer to the number of neighboring coefficients combined in a dimension. As used herein, "weights" can be used to represent one or more coefficients used in operations for combining individual rows and / or columns of input data in each layer. For example, a fully connected layer operation may have an output y, which is determined at least in part based on the sum of the product of the input matrix x and the weight A (which may be a matrix) and the bias value B (which may be a matrix). The term "weight" can generally be used herein to refer to both weights and bias values. Weights and biases are examples of parameters of a trained machine learning model.Different layers of a machine learning model can be trained separately.

[0099] Machine learning models may include various connectivity patterns, for example, including any of feedforward networks, hierarchies, recursive architectures, feedback connections, and the like. The connections between layers of a neural network may be fully connected or partially connected. In a fully connected network, a neuron in a first layer may communicate its output to each neuron in a second layer, and each neuron in a second layer may receive input from each neuron in the first layer. In a locally connected network, a neuron in a first layer may be connected to a limited number of neurons in a second layer. In some aspects, a convolutional network may be locally connected and configured with a shared connection strength associated with the input of each neuron in the second layer. A locally connected layer of a network may be configured so that each neuron in the layer has the same or similar connectivity pattern, but with different connection strengths.

[0100] A machine learning model or neural network may be trained. For example, a machine learning model may be trained based on supervised learning. During training, the machine learning model may be presented with inputs that the model uses to calculate to produce an output. The actual output may be compared to the target output, and the difference may be used to adjust the parameters of the machine learning model (such as weights and biases) to provide an output closer to the target output. Before training, the output may be incorrect or less accurate, and the error or difference between the actual output and the target output may be calculated. Then, the weights of the machine learning model may be adjusted so that the output is more closely aligned with the target. In order to adjust the weights, the learning algorithm may calculate the gradient vector of the weights. The gradient may indicate the amount by which the error will increase or decrease if the weights are slightly adjusted. At the top layer, the gradient may directly correspond to the value of the weights connecting the activated neurons in the penultimate layer and the neurons in the output layer. In the lower layers, the gradient may depend on the value of the weights and the calculated error gradients of the higher layers. Then, the weights may be adjusted to reduce the error or move the output closer to the target. This way of adjusting the weights may be referred to as back propagation through a neural network. The process may continue until the achievable error rate stops decreasing, or until the error rate has reached a target level.

[0101] These machine learning models may include computational complexity and a large number of processors for training machine learning models. The output of one node is connected as an input to another node. The connection between nodes may be referred to as an edge, and weights may be applied to the connection / edge to adjust the output from one node, which is used as an input to another node. Nodes may apply thresholds to determine whether or when to provide output to a connected node. The output of each node may be calculated as a nonlinear function of the sum of the inputs to the node. A neural network may include any number of nodes and any type of connection between the nodes. A neural network may include one or more hidden nodes. Nodes may be aggregated into layers, and different layers of a neural network may perform different kinds of transformations on the input. A signal may travel from an input at the first layer through multiple layers of a neural network to an output at the last layer of the neural network, and may traverse these layers multiple times.

[0102] As combined Figure 5 As described in example 500 of FIG. 1 , a base station 502 and a UE 504 may communicate on an active data / control beam for both DL and UL communications. The base station and / or the UE may use a beam failure recovery procedure to switch to a new beam direction. See Figure 5 , the base station 502 may send a beamformed signal to the UE 504 in one or more directions of directions 502a, 502b, 502c, 502d, 502e, 502f, 502g, 502h. The UE 504 may receive the beamformed signal from the base station 502 in one or more reception directions 504a, 504b, 504c, 504d. The UE 504 may also send a beamformed signal to the base station 502 in one or more directions of directions 504a-504d. The base station 502 may receive the beamformed signal from the UE 504 in one or more reception directions of reception directions 502a-502h. The base station 502 / UE 504 may perform beam training to determine the best reception direction and transmission direction of each of the base station 502 / UE 504. The transmission direction and reception direction of the base station 502 may be the same or different. The transmission direction and reception direction of the UE 504 may be the same or different.

[0103] In response to different conditions, the UE 504 may determine to switch beams, for example, between beams 502a-502h. The beam at the UE 504 may be used for reception of downlink communications and / or transmission of uplink communications. In some examples, the base station 502 may transmit a transmission that triggers beam switching of the UE 504. For example, the base station 502 may indicate a change in a transmit configuration indication (TCI) state, and in response, the UE 504 may switch to a new beam for a new TCI state of the base station 502. In some cases, the UE may receive a signal from the base station that is configured to trigger a change in a transmit configuration indication (TCI) state via, for example, a MAC control element (CE) command. The TCI state change may enable the UE to find the best UE receive beam corresponding to the TCI state from the base station and switch to such a beam. Switching beams may allow an enhanced or improved connection between the UE and the base station by ensuring that the transmitter and receiver communicate using the same configured beam set. In some aspects, a single MAC-CE command may be transmitted by the base station to trigger the change of the TCI state on multiple CCs.

[0104] The TCI state may include quasi-co-location (QCL) information, which the UE may use to derive timing / frequency errors and / or transmit / receive spatial filtering for transmitting / receiving signals. If the properties of the channel transmitting the symbols on one antenna port can be inferred from the channel transmitting the symbols on another antenna port, the two antenna ports are referred to as being quasi-co-located. The base station may indicate the TCI state to the UE as a transmission configuration indicating the QCL relationship between a signal (e.g., a reference signal) and the signal to be transmitted / received. For example, the TCI state may indicate the QCL relationship between the DL RS in an RS set and the PDSCH / PDCCH DM-RS port. The TCI state may provide information about different beam selections used by the UE to transmit / receive various signals. Example RSs may be SSBs, tracking reference signals (TRSs) and associated CSI-RSs for tracking, CSI-RSs for beam management, CSI-RSs for CQI management, DM-RSs associated with non-UE-specific reception on PDSCH, and a subset of the control resource set (CORESET) (which may be a full set), etc. The TCI state may be defined to represent at least one source RS to provide a reference (eg, UE assumption) for determining a quasi co-location (QCL) or spatial filter. For example, the TCI state may define a QCL assumption between a source RS and a target RS.

[0105] Prior to receiving the TCI state, the UE may assume that the antenna ports of one DM-RS port group of the PDSCH are spatially quasi-co-located (QCL) with the SSB determined in the initial access procedure for one or more of the following: Doppler shift, Doppler spread, average delay, delay spread, spatial Rx parameter set, etc. After receiving the new TCI state, the UE may assume that the antenna ports of one DM-RS port group of the PDSCH of the serving cell are QCLed with the RS in the RS set for the QCL type parameter given by the indicated TCI state. Regarding the QCL type, QCL type A may include Doppler shift, Doppler spread, average delay, and delay spread; QCL type B may include Doppler shift and Doppler spread; QCL type C may include Doppler shift and average delay; and QCL type D may include spatial Rx parameters (e.g., associated with beam information such as beamforming properties used to find a beam).

[0106] The UE may monitor the quality of the beam that the UE uses to communicate with the base station. For example, the UE may monitor the quality of the signal received via the receive beam. A beam failure detection (BFD) procedure may be used to identify problems with beam quality, and a beam failure recovery (BFR) procedure may be used when a beam failure is detected. The measurement may include deriving a metric similar to the signal to interference plus noise ratio (SINR) of the signal or the RSRP strength or block error rate (BLER) of a reference control channel selected by the base station and / or implicitly derived by the UE based on an existing RRC configuration. The UE may measure RS such as CSI-RS, synchronization signal blocks (SSBs), or other RSs for time and / or frequency tracking. The UE may receive an indication of a reference signal resource to be used to measure beam quality. The measurement may indicate the UE's ability to decode a transmission (e.g., a DL control transmission from a base station).

[0107] As proposed herein, the UE may be configured to report beam quality in the form of a report provided to a base station. For example, the UE may send an L1-RSRP report to the network based on measurements of SSBs received from the base station. For example, the UE may use a first number of bits to report the strongest SSBRI, and may use a smaller number of bits to report measurement information for one or more other SSBRIs. For example, the UE may use 7 bits to report the strongest SSBRI, thereby reporting RSRP in the range of [-140, -44] dBm in steps of 1 dBm. For other SSBRIs, the UE may use a smaller number of bits such as 4 bits to report the differential RSRP relative to the L1-RSRP measured for the strongest SSBRI as a reference. For example, the UE may use 4 bits to report other SSBRIs, thereby reporting the differential RSRP in the range of [0, -30] dB in steps of 2 dB and with reference to the L1-RSRP of the strongest SSBRI. A mapping may be defined, known, or provided between the codepoint for the larger bit indication of the strongest SSBRI, the codepoint for the smaller bit indication of the differential measurement of the other SSBRIs, and the actual RSRP value.

[0108] As described above, since the amount of computing resources and memory available to the base station is greater than that available to the UE, the base station may participate in predictive beam management. The base station may help the UE predict the quality of other beam pairs. However, the report sent by the UE to the base station may not have information about the receive (Rx) beam that the UE has measured for a specific transmit (Tx) beam. For example, the UE may use different Tx beams at multiple P / SP-SMR TD opportunities to measure the L1-RSRP for a specific Tx beam, and report the filtered L1-RSRP associated with different receive (Rx) beams for that Tx beam. Such methods may typically require a longer duration or UE filtering effort to determine the appropriate L1-RSRP for a specific Tx beam. The base station may find it challenging to predict the preferred beam pair for the UE. For example, an ML model trained based on data that does not include the Rx beam measured by the UE for the Tx beam may not accurately predict a preferred beam pair including a transmit beam from the base station and a receive beam at the UE. According to one aspect, the UE may report preliminary information about the UE's Rx beam information, such as shape, beam width and / or direction. The preliminary information may be indexed within the Rx beam reported by the UE. The base station may inform the UE of the beam to be measured and / or predicted.

[0109] To address these issues, an L1 report for base station assisted beam pair prediction is described herein, which reports measurement information with corresponding receive beam information. In some aspects, the L1 report may be referred to as an "enhanced L1 report". The L1 report includes an identifier of the Rx beam measured by the UE for measurements associated with a given Tx beam. The reported Rx beam information in the L1 report may be based on indexing the Rx beam reported by the UE. Training such as combining Figure 4 and / or Figure 6 The ML model described. At inference time, the ML model may output a preferred beam pair for transmit beams and receive beams based on the L1 report, where the prediction may be more accurate than the prediction output by the ML model without L1 report training. By using L1 reports for ML model training purposes and at inference time, such L1 reports may reduce the number of beam scans during beam scanning and help the base station assist in beam pair prediction. Therefore, L1 reporting and receive beam selection by the base station may reduce latency and UE power consumption. In addition, other aspects described herein may include report compression based on L1 reports, CSI partitioning, and TCI state activation / switching.

[0110] Figure 6 600 is a diagram illustrating an example AI / ML based beam prediction. As illustrated in diagram 600, L1-RSRP time series measurements 602 are generated by a UE (e.g., UE 104, UE 350, UE 504) for one or more channel resource indicator reference signals (CSI-RS) or synchronization signal blocks (SSBs). The L1-RSRP time series measurements 602 are provided as input to an ML model 604. The ML model 604 may be or include the method described above in Figure 4 When the ML model 604 is located at a base station (e.g., base station 102, base station 310, base station 502), the L1-RSRP time series measurement 602 is reported to the base station by the UE. When the ML model 604 is located at the UE, the L1-RSRP time series measurement 602 is measured by the UE.

[0111] The ML model 604 may be trained to perform different types of predictions. In one example, the ML model 604 is trained to predict future L1-RSRP 606 based on L1-RSRP time series measurements 602. In another example, the ML model 604 is trained to predict one or more candidate beams 608 based on L1-RSRP time series measurements 602. In yet another example, the ML model 604 is trained to predict beam failure and / or blocking 610. Predicting future L1-RSRP 606 and / or one or more candidate beams 608 may result in the UE having reduced power consumption and / or may reduce UE reference signal overhead. Predicting beam failure and / or blocking may improve latency and / or throughput. Although Figure 6 The use of L1-RSRP measurements is depicted, but it should be understood that other measurements such as L1-SINR measurements may be used in addition to or instead of L1-RSRP measurements.

[0112] Figure 7 7 is a diagram depicting an example beam pair prediction (e.g., 710) performed by a base station. As shown, the base station sends out a Tx beam 702, and the UE receives an Rx beam 704. Based on the L1 report including receive beam information for L1 measurement report described herein, the base station can predict that Tx beam 706 from Tx beam 702 and Rx beam 708 from Rx beam 704 will provide improved communication with the UE.

[0113] Figure 8 is a diagram 800 illustrating an example L1 report 802 based on a beam pair and including receive beam information for corresponding measurements. The UE may be configured to generate the L1 report 802 through at least one CSI reporting setting. Fig.18 An example communication flow 1800 between a UE 1802 and a base station 1804 is illustrated. As illustrated at 1806, a UE 1802 may receive a configuration from a base station 1804, and the configuration may include settings for L1 measurements and / or L1 measurement reports for the UE. For example, a reporting amount of at least one CSI report setting in the configuration at 1806 may include one or more L1-RSRPs and / or L1-SINRs associated with a specific number of downlink channel management resources (CMRs), with a CMR set associated with the CSI report setting and a CMR ID. The reporting amount of at least one CSI report setting also includes determining an Rx beam ID for each of the L1-RSRPs and / or L1-SINRs for each CMR. The CMR may include a CSI-RS resource and / or an SSB resource. For example, a CMR ID may correspond to an SSB ID or a CSI-RS ID. For example, an SSB ID or a CSI-RS ID may indicate a transmit beam of an SSB or CSI-RS from a base station. The L1 report 802 indicates the beam pairs for different CMRs, for example by including information indicating the Rx beam ID of the corresponding CMR ID indicating the Tx beam of the beam pair associated with the measurement. If different Rx beams are associated with the same CMR at a single reporting occasion (based on UE specific implementation), RSRP / SINR filtering may occur in TD.

[0114] exist Figure 8 In the example shown, the L1 report 802 includes an identifier of a first CMR 804 (eg, which may correspond to, for example, Figure 5 1) and the identifier of the fourth CMR 806 (e.g., which may correspond to, for example, Figure 5502f in the L1 report 802). The first CMR 804 and the fourth CMR 806 may correspond to the transmission of a reference signal (such as a CSI-RS or SSB using different Tx beams transmitted by the base station). The identifier of the first CMR 804 may be associated with the third Rx beam 808 (e.g., which may correspond to Figure 5 504a) and the fifth Rx beam 810 (eg, which may correspond to Figure 5 The identifier of the third Rx beam 808 may be associated with an L1-RSRP measurement 812 performed by the UE. The identifier of the fifth Rx beam 810 may be associated with an L1-RSRP measurement 814 performed by the UE. The identifier of the fourth CMR 806 may be associated with an identifier of the fifth Rx beam 816 and an identifier of the seventh Rx beam 818 (e.g., which may correspond to Figure 5 The identifier of the fifth Rx beam 816 may be associated with an L1-RSRP measurement 820 performed by the UE. The identifier of the seventh Rx beam 818 may be associated with an L1-RSRP measurement 822 performed by the UE. Fig.18 At 1808, the UE 1802 may perform measurements (e.g., such as L1-RSRP and / or L1-SINR) on one or more CMRs 1807. The UE 1802 may then send an L1 measurement report 1816 to the base station 1804, for example, based on the configuration 1806.

[0115] As discussed above, the L1 report 802 may be provided from the UE to the base station and may be used as an input to the ML model 824 at the base station. The ML model 824 may then output one or more predictions or beam selections (e.g., Tx-Rx beam pairs or Rx beam selections) based on the L1 report 802. The ML model 824 may include combining information about Figure 4 or Figure 6 Any of the aspects described in the ML model. In one example, the ML model 824 can be trained to predict the L1-RSRP 826 of a beam pair. In another example, the ML model 824 can be trained to predict candidate beams 828, such as including receive beams at the UE. In yet another example, the ML model 824 can be trained to predict beam failures and / or blockages 830. Fig.18 As shown, at 1818, the base station 1804 may select a beam based on a report that may indicate to the UE 1802 at 1820 to use a particular receive beam. Then, at 1822, the UE and the base station 1804 may communicate using the indicated receive beam or beam pair including the receive beam. For example, at 1822, the UE 1802 may receive downlink communications from the base station 1804 using the receive beam based on the indication received at 1820.

[0116] In some aspects, an association may be provided, configured, or known between an Rx beam ID (e.g., an Rx beam ID that the UE may indicate in an L1 measurement report) and a corresponding Rx beam at the UE. In some aspects, the UE may first indicate beam information about a set of Rx beams at the UE. For example, in Fig.18 In the example, UE 1802 may provide Rx beam information 1805 to base station 1804. Fig. 9 900 is a diagram depicting an association between a UE Rx beam identifier and a UE Rx beam. Diagram 900 includes first UE Rx beam information 902 for a set of Rx beams at a UE, which the UE may provide at 1805, for example. The first UE Rx beam information 902 includes information about an example group of eight Rx beams (e.g., 904, 906, 908, 910, 912, 914, 916, and 918) at the UE corresponding to the first number of Rx beams and information associated with each of the first number of Rx beams. The information may include absolute beam pointing direction and / or beam width information. At 1805, the UE (e.g., UE 104, UE 350, UE 504, UE 1802) may send the first UE Rx beam information 902 to a base station (e.g., base station 102, base station 310, base station 502). In some aspects, the UE may report the first UE Rx beam information 902 / 1805 as UE capability information in RRC signaling.

[0117] After receiving the information, the base station may select a specific subset (e.g., 904-918) of the set of Rx beam identifiers at the UE for the UE to report L1 measurements. For example, the base station may select some or all of the Rx beams 904-918. The base station may configure the UE via RRC (CSI reporting settings), MAC-CE (activation of semi-persistent (SP) CSI reporting), or DCI (triggering of aperiodic (AP) CSI reporting) 920 to provide L1 measurement reports for the indicated beam group, for example as a reporting configuration 922 indicating a second number of Rx beams indicated by the base station. For example, in Fig.18 In the configuration 1806, the UE 1802 may be instructed to measure and / or report L1 measurements (such as RSRP or SINR) for a set of candidate Rx beams, which is at least a subset of the Rx beam group for which the UE provided Rx beam information at 1805. Fig. 9 In the example shown, report configuration 922 identifies Rx beam 910, Rx beam 916, and Rx beam 918. Figure 8As described in , the UE may generate an L1 report (e.g., L1 report 802) for the indicated Rx beams corresponding to Rx beams 910, Rx beams 916, and Rx beams 918. In one example, the beams corresponding to Rx beams 910, Rx beams 916, and Rx beams 918 may be wide beams, and the beams corresponding to Rx beams 904, Rx beams 906, Rx beams 908, Rx beams 912, and Rx beams 914 may be narrow beams. By using report configuration 922, the base station may help the UE predict information related to narrow beams. Therefore, the UE may skip scanning the beams associated with each of Rx beams 904, Rx beams 906, Rx beam candidates 908, Rx beam candidates 912, and Rx beam candidates 914. In one aspect, the number of bits used to report the Rx beam identifier in the CSI report may be determined by the number of Rx beams indicated in the reporting configuration 922. For example, if the reporting configuration 922 indicates three beams (e.g., candidate beam 1, candidate beam 2, candidate beam 3), the UE may indicate the Rx beam ID in the L1 measurement report based on the set of three candidate beam IDs, instead of identifying the corresponding Rx beam from the set of eight beams in 902. In other examples, an association between a set of Rx beam IDs and each of the Rx beams at the UE may be provided, and the UE may indicate the corresponding Rx beam ID in the L1 measurement report for each measurement reported.

[0118] In one aspect, the MAC-CE activating the SP CSI report may indicate the second number of Rx beams, for example, at 922. In another aspect, the configuration for AP CSI reporting may configure the second number of Rx beams, for example, at 922, and the UE may identify such Rx beams when providing the AP CSI report to the base station. For example, the MAC-CE and / or configuration may correspond to Fig.18 In 1806.

[0119] In some aspects, prior to reporting the L1 measurement report at 1816 , the UE 1802 may compress at least a portion of the measurement report at 1810 . Fig.101000 is a diagram depicting an example of compressing an enhanced L1 report (e.g., L1 report 802 or 1816) generated by a UE (e.g., UE 104, UE 350, UE 504, UE 1802). Diagram 1000 shows that the UE can report an absolute L1-RSRP measurement 1002 (e.g., in L1 report 1816). The absolute L1-RSRP measurement 1002 can be associated with the strongest beam pair within a CSI report (or other L1 measurement report). Diagram 1000 shows that the UE can also report one or more differential L1-RSRP measurements 1004, 1006, 1008 for other beam pairs. Each of the differential L1-RSRP measurements 1004, 1006, 1008 refers to the difference between the absolute L1-RSRP measurement 1002 and a corresponding (e.g., non-strongest) L1-RSRP measurement. By using the differential measurements, the size of the enhanced L1 report can be reduced. Although diagram 1000 includes L1-RSRP measurements, it should be understood that L1-SINR measurements may be used in addition to or instead of L1-RSRP measurements. Although this example is described with respect to L1-RSRP measurements, these aspects may be similarly applied to L1-SINR measurements or other L1 measurements.

[0120] Fig.11 1 is a diagram 1100 depicting another example of compression of an L1 report (e.g., L1 report 802 or 1816) performed by a UE (e.g., UE 104, UE 350, UE 504, UE 1802). Diagram 1100 shows that the UE can report an absolute L1-RSRP measurement 1102. The absolute L1-RSRP measurement 1102 is associated with the strongest beam pair within the CSI report (from all CMRs). Diagram 1100 shows that the UE can also report first differential L1-RSRP measurements 1104, 1106, 1108, wherein each of the first differential L1-RSRP measurements 1104, 1106, 1108 relates to a different CMR, and wherein each of the first differential L1-RSRP measurements 1104, 1106, 1108 is associated with the strongest beam pair (i.e., a Tx beam and an Rx beam) for the corresponding CMR.

[0121] Diagram 1100 shows that the UE may also report second differential L1-RSRP measurements 1110, 1112, 1114, third differential L1-RSRP measurements 1116, 1118, and fourth differential L1-RSRP measurements 1120, 1122. Each of the second differential L1-RSRP measurements 1110, 1112, 1114 refers to the difference between the differential L1 RSRP measurement 1104 and the associated L1-RSRP measurement. In one example, the CMR associated with the L1-RSRP measurement 1104 includes the strongest beam pair, and therefore, the number of differential measurements in the second differential L1-RSRP measurements 1110, 1112, 1114 may be greater than the number of measurements of the third differential L1-RSRP measurements 1116, 1118 or the fourth differential L1-RSRP measurements 1120, 1122. Each of the third differential L1-RSRP measurements 1116, 1118 refers to the difference between the differential L1 RSRP measurement 1106 and the associated L1-RSRP measurement. Each of the fourth differential L1-RSRP measurements 1120, 1122 refers to the difference between the differential L1 RSRP measurement 1108 and the associated L1-RSRP measurement. By using differential measurements, the size of the enhanced L1 report can be reduced. Although the diagram 1100 includes L1-RSRP measurements, it should be understood that L1-SINR measurements can be used in addition to or instead of L1-RSRP measurements.

[0122] In one aspect, the UE may use different differential quantization tables (e.g., L1-RSRP or L1-SINR tables) for different reporting phases. For example, the UE may use a first differential quantization table to report the difference between the absolute L1-RSRP measurement 1102 and the first differential L1-RSRP measurements 1104, 1106, 1108, and may use a second differential quantization table to report the difference between the differential L1-RSRP measurement 1104 and the second differential L1-RSRP measurements 1110, 1112, 1114. The differential quantization table may include the number of bits allocated for reporting L1-RSRP / L1-SINR, the step size, and / or the dynamic range.

[0123] In one aspect, the UE may be configured to report a downlink CMR identifier and an Rx beam identifier for each beam pair. In one example, the UE may be configured to report a dedicated number of beam pairs for one downlink CMR via a CSI reporting setting. In this way, the UE may report downlink CMR identifiers for a set of beam pairs at a time, and then report the corresponding Rx beam identifier for each downlink CMR ID. On the other hand, the UE may be configured to report different numbers of beam pairs for different downlink CMRs. In one example, the UE may be configured to report four beam pairs for the DL-CMR with the strongest beam pair, and the UE may also be configured to report two beam pairs for the remaining downlink CMRs.

[0124] Fig.12 1200 is a diagram illustrating yet another example of compression of an L1 report that may be performed by a UE (e.g., UE 104, UE 350, UE 504, UE 1802). Diagram 1200 includes an original L1 report 1202 (e.g., L1 report 802 described above). As described above, the original L1 report 1202 may include L1-RSRP and / or L1-SINR 1204. The original L1 report 1202 may also include a CMR identifier and an Rx beam identifier 1206. The UE may provide the L1-RSRP and / or L1-SINR 1204 as input to a first encoder 1208. The first encoder 1208 generates an encoded L1-RSRP / L1-SINR 1204 based on the L1-RSRP and / or the L1-SINR 1210, wherein the encoded L1-RSRP / L1-SINR 1210 is a compressed version of the L1-RSRP and / or the L1-SINR 1204. The UE may also provide the CMR identifier and the Rx beam identifier 1206 as input to the second encoder 1212. The second encoder 1212 generates an encoded CMR identifier and an Rx beam identifier 1214 based on the CMR identifier and the Rx beam identifier 1206, wherein the encoded CMR identifier and the Rx beam identifier 1214 are compressed versions of the CMR identifier and the Rx beam identifier 1206. The UE may send the encoded L1-RSRP / L1-SINR 1210 and the encoded CMR identifier and the Rx beam identifier 1214 to a base station (e.g., the base station 102, the base station 310, the base station 502). The base station (e.g., 1804) may decode the encoded L1-RSRP / L1-SINR 1210 using a first decoder associated with the first encoder 1208 to obtain L1-RSRP and / or L1-SINR 1204. The base station may also decode the encoded CMR identifier and Rx beam identifier 1214 using a second decoder associated with the second encoder 1212 to obtain the CMR identifier and the Rx beam identifier 1206.

[0125] Fig.13 is a diagram depicting different schemes for reporting compressed payloads, such as at 1816 (eg, coded L1-RSRP / L1-SINR 1210 and coded CMR identifier and Rx beam identifier 1214, Fig.10 and Fig.11 1300 of differential reported L1-RSRP, etc. described in . A UE (e.g., UE 104, UE 350, UE 504) first reports the original payload length (of an uncompressed enhanced L1 report) or the compressed payload length (of a compressed enhanced L1 report) using a fixed bit width. The UE may explicitly report the payload size of the uncompressed L1 report and / or the payload size of the compressed report, or report from a plurality of pre-configured options in the CSI report settings for P / SP-CSI reporting or a triggered configuration in the AP-CSI report. The UE then reports the compressed payload to a base station (e.g., base station 102, base station 310, base station 502). In one aspect, if the compressed payload size is not reported, the compressed payload is reported via a fixed bit width. On the other hand, if the compressed payload size is reported, the compressed payload is reported with a variable bit width.

[0126] In the first scheme 1302, the input length of the compressed / uncompressed payload is variable and the output length is fixed. In the second scheme 1304, the input length of the compressed / uncompressed payload is fixed and the output length is variable. In the third scheme 1306, the input length of the compressed / uncompressed payload is variable and the output length is variable.

[0127] In one aspect, a base station 1804 (e.g., base station 102, base station 310, base station 502) may indicate / configure an associated decoder to a UE 1802, and the encoder is based on a UE specific implementation. In another aspect, the base station 1804 indicates / configures an encoder (e.g., a first encoder 1208 and a second encoder 1212) directly to the UE 1802. For example, at 1806, the base station 1804 may indicate / configure the UE 1802 with such information.

[0128] Fig.141400 is a diagram depicting an example of CSI report partitioning that may be performed by a UE (e.g., UE 104, UE 350, UE 504, UE 1802), for example, when sending an L1 measurement report 1816. Diagram 1400 includes a payload 1402 of a measurement report, such as 1816. Payload 1402 may be the L1 report 802 described above. UE 1802 may partition payload 1402 into a first CSI portion 1404 and a second CSI portion 1406. The first CSI portion 1404 may have a fixed payload size and a relatively high reliability, while the second CSI portion 1406 may have a variable payload size and a relatively low reliability. The first CSI portion 1404 may include an L1 report 1408 without a receive beam identifier (e.g., in some aspects, it may be referred to as a legacy L1 report) and the number of beam pairs evaluated for each CMR 1410. The L1 report 1408 may include the strongest L1-RSRP / L1-SINR measurement for each downlink CMR. The second CSI part 1406 may include a remaining component / information 1412, which includes measurements with corresponding receive beam identifiers. The UE 1802 may send the first CSI part 1404 and the second CSI part 1406 (e.g., as 1816) to the base station 1804 (e.g., base station 102, base station 310, base station 502).

[0129] Fig.15 1500 is a diagram illustrating another example of CSI report partitioning performed by a UE (e.g., UE 104, UE 350, UE 504). Diagram 1500 includes a payload 1502. Payload 1502 may be an enhanced L1 report 802 and / or a CSI report partitioned according to the above description. Fig.10 , Fig.11 , Fig.12 and / or Fig.13 The UE may divide the payload 1502 into a first CSI portion 1504 and a second CSI portion 1506. The first CSI portion 1504 includes a non-compressed L1 report payload size or a compressed payload size 1508. The second CSI portion 1506 includes a compressed payload 1510. The compressed payload may be as described above in Fig.10 , Fig.11 , Fig.12 and / or Fig.13 UE 1802 may send the first CSI part 1504 and the second CSI part 1506 (eg, as an L1 measurement report 1816) to a base station 1804 (eg, base station 102, base station 310, base station 502).

[0130] Fig.16FIG1600 is a diagram illustrating an example of generating multiple CSI reports by a UE (e.g., UE 104, UE 350, UE 504, UE 1802). FIG1600 includes a payload 1602. The payload 1602 may be or include an L1 report, an enhanced L1 report 802, and / or an L1 report according to the above. Fig.10 , Fig.11 , Fig.12 and / or Fig.13 Description of the compressed payload. The UE is configured to generate an L1 report 1604 and a residual component 1606 via multiple CSI reporting settings. Each L1 report in the L1 report 1604 may include the strongest L1-RSRP / L1-SINR measurement for each downlink CMR and an identifier for the corresponding CMR (which may be referred to as a first CSI report). Each residual component in the residual component 1606 (which may be referred to as a second CSI report) includes an enhanced L1 report (e.g., enhanced L1 report 802). In one aspect, the UE 1802 reports (e.g., at 1816) the L1 report 1604 with a first periodicity and reports the residual component 1606 with a second periodicity, wherein the first periodicity is less than the second periodicity. The most recent first CSI report may be used as a reference for the second CSI report.

[0131] As described in conjunction with 1818 and 1820, the base station 1804 may use the L1 measurement report 1816 to select a receive beam or a beam pair including a transmit beam and a receive beam for the UE 1802 to receive downlink communications from the base station 1804. At 1820, the base station 1804 may indicate the selected Rx beam to the UE. For example, the base station 1804 may indicate a TCI state to the UE 1802, the TCI state including a QCL relationship with the Rx beam at the UE 1802. Fig.171700 is a diagram illustrating an example TCI state activation / switching for a beam pair. Diagram 1700 depicts TCI state 1702. A UE (e.g., UE 104, UE 350, UE 504) may be configured with a first number of TCI states, wherein TCI state 1702 is included in the first number of TCI states, e.g., included in an RRC configuration such as configuration 1806. TCI state 1702 includes QCL information 1704. QCL information 1704 includes a UE Rx beam identifier 1706 and UE Rx beam information (which may be based on L1 report 802, e.g., 1805 as described above). QCL information 1704 may optionally include a downlink reference signal (DL-RS) identifier 1708. DL-RS identifier 1708 may be used to determine a Type A or Type C QCL. The TCI state 1702 may be activated via a known TCI state activation medium access control-control element (MAC-CE) or through other TCI state activation MAC-CEs.

[0132] In one aspect, a second number of TCI states (e.g., a subset of the first RRC configuration group of TCI states) may be activated for the UE 1802 via the MAC-CE 1814. At 1820, the base station 1804 may then indicate a specific TCI state from the MAC-CE activated TCI states. For example, at 1820, the base station 1804 may send a downlink grant DCI that schedules the PDSCH and indicates a TCI state that includes a QCL relationship with a specific Rx beam at the UE 1802.

[0133] Fig.19 is a diagram illustrating example 1900 of known TCI states according to the present disclosure.

[0134] A TCI state switch may involve a known TCI state and an unknown TCI state. A TCI state switch timeline may specify a delay between receiving a reference signal (RS) resource (e.g., CSI-RS, SSB) for an L1-RSRP measurement report for a target TCI state (activated TCI state) and completing an active TCI state switch. An RS resource is an RS in an activated TCI state or has been QCLed to an activated TCI state. Example 1900 shows that CSI-RS #5 is an RS and the activated TCI state to be applied to the TCI state switch is TCI state #3.

[0135] The TCI state switching timeline for a TCI state switching period may depend on whether the activated TCI state is known or unknown. The TCI state is known if multiple conditions are met. This may include: (Condition #1) If a TCI state switching command is received within a time period (e.g., 1280 milliseconds (ms)) after the last transmission of RS resources for beam reporting or measurement; (Condition #2) If the UE has sent at least 1 L1-RSRP report for the target TCI state before the TCI state switching command; (Condition #3) If the TCI state remains detectable during the TCI state switching period (e.g., from the timeslot carrying the TCI state activation MAC CE to the completion of the TCI switch); and (Condition #4) Whether the SSB associated with the TCI state remains detectable during the TCI switching period. If the signal-to-noise ratio (SNR) of the RS is greater than or equal to 3 decibels (dB), the RS can be detected by the UE. This does not mean that such RS has been transmitted. This can be verified by the UE via other RS ​​(e.g., DMRS). If these conditions are not met, the TCI state is unknown.

[0136] As indicated above, Fig.19 are provided as examples. Other examples may be relevant to Fig.19 Different than described.

[0137] Fig. 20 is a diagram illustrating an example of a TCI state switching timeline according to the present disclosure.

[0138] If the target TCI state (activated TCI state) is known (example 2000), then when a PDSCH communication carrying a MAC CE activation command is received at time slot n, the UE may be able to determine the target TCI state (activated TCI state) at time slot n+T HARQ +(3ms+TO k *(T first-SSB +T SSB-proc ))) The TCI state switch that occurs at the first time slot after the NR time slot length receives PDCCH communication with the target TCI state of the serving cell. The UE may be able to receive PDCCH communication with the old TCI state until time slot n+T HARQ +3ms. T first-SSB It can be the time from when the MAC CE activation command is decoded by the UE to when the first SSB is sent. The SSB can be QCL type A or QCL type C to the target TCI state. SSB-proc The SSB processing time can be 2ms. k May be 1 if the target TCI state is not in the active TCI state list for PDSCH, otherwise 0.

[0139] If the target TCI state is unknown (Examples 2002 and 2004), then upon receiving a PDSCH communication carrying a MAC CE activation command in time slot n, the UE may be able to determine the target TCI state in time slot n+T HARQ +(3ms+T L1-RSRP +TO uk *(T first-SSB +T SSB-proc ))) The TCI state switch that occurs at the first time slot after the NR time slot length receives PDCCH communication with the target TCI state of the serving cell. The UE may be able to receive PDCCH communication with the old TCI state until time slot n+T HARQ +(3ms+T L1-RSRP +TO uk *T first-SSB ) / NR time slot length. T L1-RSRP The time of L1-RSRP measurement for receive beam refinement in FR2 is defined as the periodicity of SSB / CSI-RS relative to the TCI state. T can be specified for SSB L1-RSPR_Measurement_Period_SSB and T for CSI-RS L1-RSRP_Measurement_Period_CSI-RS .TO uk It can be 1 for CSI-RS based L1-RSRP measurement and can be 0 for SSB based L1-RSRP measurement when TCI state switching involves QCL type D. When TCI state switching involves other QCL types, TO uk Can be 1.

[0140] For FR2 T L1-RSRP , for SSB as specified in different configurations, T L1-RSRP =T L1-RSPR_Measurement_Period_SSB , where the assumption factor M = 1, the beam scanning factor N = 8, and T Report = 0. For discontinuous reception (non-DRX) configuration, T L1-RSPR_Measurement_Period_SSB It can be T Report The maximum value (max) and (M×P×N)×T SSB For non-DRX configurations, it is assumed that the UE uses 8 SSB cycles to refine its transmit beam. For configurations with a DRX cycle ≤ 320 ms, T L1-RSPR_Measurement_Period_SSB It can be T Report The maximum value of ((1.5×M×P×N)×max(T DRX ,T SSB )). For configurations with a DRX cycle > 320ms, T L1-RSPR_Measurement_Period_SSB It can be ((1.5×M×P×N)×T DRX ) is the upper limit value. T SSB=ssb-periodicityServingCell can be configured with the periodicity of SSB-Index for L1-RSRP measurement. DRX It can be the DRX cycle length. Report Can be a configured periodicity for reporting.

[0141] For FR2 T L1-RSRP , for CSI-RS, T L1-RSRP =T L1-RSPR_Measurement_Period_CSI-RS , as specified in the different configurations, assuming M = 1 and T Report = 0. Higher layer parameter repetition may be set to on. For aperiodic CSI-RS, the number of resources in a resource set may be at least equal to MaxNumberRxBeam, which may be RRC configured for each band and may vary from 2 to 8. N res_per_set It can be the number of CSI-RS resources in the considered CSI-RS resource set. For non-DRX configuration, T L1-RSPR_Measurement_Period_CSI-RS It can be T Report The maximum value (max) and (M×P×N)×T CSI-RS For maxNumberRxBeam=N res_per_set , it can be assumed that the UE uses a periodic or semi-periodic (P / SP) CSI-RS cycle to refine its receive beam. For P / SP-CSI-RS with repetition set to on, N can be ceil(maxNumberRxBeam / N res_per_set ). For AP CSI-RS, assume maxNumberRxBeam≤N res_per_set , N can be 1. For P / SP CSI-RS, M can be 1. For configurations with a DRX cycle ≤ 320ms, T L1-RSPR_Measurement_Period_CSI-RS It can be T Report The maximum value of ((1.5×M×P×N)×max(T DRX ,T CSI-RS )). For configurations with a DRX cycle > 320ms, T L1-RSPR_Measurement_Period_CSI-RS It can be ((M×P×N)×T DRX ) is the upper limit value. T CSI-RS It may be the periodicity of the CSI-RS configured for L1-RSRP measurement. Assuming that the CSI-RS resources configured for L1-RSRP measurement are transmitted at density 3, this requirement may be applicable.

[0142] As indicated above, Fig. 20 are provided as examples. Other examples may be relevant to Fig. 20 Different than described.

[0143] Fig.21 is a diagram illustrating an example 2100 of predicting channel characteristics according to the present disclosure.

[0144] As shown in example 2100, the UE may have predicted channel characteristics regarding a particular SSB or CSI-RS and the appropriate receive spatial filters (relative to QCL type A / C / D) associated with such SSB or CSI-RS without actually measuring the SSB or CSI-RS. For example, for time domain beam prediction, the UE may predict future L1-RSRPs regarding the SSBs and optionally report the predicted L1-RSRPs without actually measuring them (compared to known TCI state condition #2). The UE may predict whether the strongest SSB will switch to another SSB in the future duration, rather than the most recent L1 measurement report. If there is no change, the UE may simply do nothing. If a change is predicted, the UE may request an AP / SP L1 measurement report on demand (compared to known TCI state condition #2). For spatial domain prediction, the UE may predict the L1-RSRP associated with a CSI-RS (e.g., with a periodicity of 2000ms) based on the SSB (e.g., with a periodicity of 20ms) without frequently measuring the CSI-RS (compared to known TCI state condition #1). Such cases are considered as unknown TCI states, but some delays are not necessary for such predictive beam management. For example, for SSB / CSI-RS, the UE can simply apply a predictive receive spatial filter without measuring SSB / CSI-RS. For CSI-RS, the UE can measure SSB again to verify QCL type A / C without actually measuring CSI-RS.

[0145] In other words, although the channel characteristics can be predicted, the TCI state can still be considered unknown under the current known TCI state conditions. This may introduce more delay.

[0146] As indicated above, Fig.21 are provided as examples. Other examples may be relevant to Fig.21 Different than described.

[0147] Fig. 22 2200 is a diagram illustrating an example of using a semi-known TCI state according to the present disclosure. Fig. 22 As shown, a network entity 2210 (eg, base station 110) and a UE 2220 (eg, UE 104) may communicate with each other.

[0148] According to various aspects described herein, a UE may use a semi-known TCI state predicted with respect to CSI-RS / SSB channel characteristics. The TCI state may be semi-known when the channel characteristics do not satisfy a known TCI state condition but satisfy a predicted condition. If the channel characteristics are predicted within the prediction duration, the predicted condition may be satisfied. If the activated TCI state is semi-known, the UE may use a TCI state switching timeline specific to the semi-known state. In this way, the predicted channel characteristics may be used to reduce latency rather than causing failures to the longer TCI state switching timeline for an unknown TCI state. For example, the TCI state switching timeline for a semi-known TCI state may remove L1. Alternatively, if the known TCI state condition is not satisfied but the predicted condition is satisfied, the UE may fall back to a known TCI state.

[0149] Example 2200 shows the use of a semi-known TCI state (e.g., TCI state #3). As shown in reference numeral 2225, the network entity 2210 may send a reference signal (e.g., CSI-RS, SSB). As shown in reference numeral 2230, the network entity 2210 may send a TCI state activation command (e.g., MAC CE). As shown in reference numeral 2235, the UE 2220 may identify the TCI state. The UE 2220 may identify the TCI state based at least in part on a TCI state activation command MAC CE that activates or updates the TCI state. The UE 2220 may identify the TCI state from an earlier MAC CE. The UE 2220 may identify the TCI state from a TCI state that is in an activated TCI state list. The UE 2220 may identify the TCI state from a TCI state that is not in an activated TCI state list. As shown in reference numeral 2240, the network entity 2210 may send a TCI state switch command (e.g., downlink control information (DCI)).

[0150] As indicated by reference numeral 2245, UE 2220 may determine that the TCI state is semi-known. That is, UE 2220 may determine that the known condition is not satisfied for TCI state #3. For example, a TCI state switching command may be received outside a time period (e.g., 1280ms) after a reference signal (e.g., CSI-RS#5) is received, and UE 2220 does not send a (conventional) L1-RSRP report for the target TCI state before the TCI state switching command. However, the prediction condition is satisfied. UE 2220 has predicted the channel characteristics associated with the reference signal in the TCI state (or has been RS QCL) for the prediction duration.

[0151] The prediction duration may be configured to be Xms before a TCI state switch command associated with the TCI state is received. The value of the prediction duration may be configured for a specific prediction scenario, and different values ​​of the prediction duration may be used for different prediction scenarios. For example, one scenario (e.g., beam change prediction / reporting) may be more suitable for a semi-static environment, making the prediction duration of that scenario longer than the prediction duration of other scenarios. Different values ​​may be specified in the standard, configured by the network entity 2210, or indicated by the network entity 2210 via an RRC message, MAC CE, or DCI. The UE 2220 may also send a preferred value for the prediction duration.

[0152] In some aspects, channel characteristics may include a predicted L1-RSRP reported without actually receiving RS or measuring RS. For example, UE 2220 may measure SSB (e.g., with a periodicity of 20ms) without measuring CSI-RS to identify or report the L1-RSRP of CSI-RS (e.g., with a periodicity of 2000ms). Channel characteristics may be based at least in part on a preference for sending a report using RS resources as a type D QCL source without sending an L1-RSRP report. For example, UE 2220 may report an SSB resource indicator (SSBRI) as a preferred type D-QCL source without reporting its L1-RSRP. Channel characteristics may be based at least in part on a preference for using a reference signal as a type D-QCL source (without sending the preference). For example, UE 2220 may send an L1-RSRP report of SSB#3 including the strongest L1-RSRP in time slot n, and if UE 2220 determines that the strongest SSB will become another SSB, UE 2220 may request an actual L1-RSRP report. UE 2220 may indicate a preference (which is agreed upon between UE 2220 and network entity 2210) to use SSB#3 as a Type D-QCL source without actually reporting its L1-RSRP.

[0153] As shown by reference numeral 2250, the UE 2220 may apply a TCI state switching timeline to a semi-known TCI state. The TCI state switching timeline may affect the delay or time between the time slot in which a TCI state activation command (MAC-CE) is received and the first TCI state switching command (DCI) associated with the TCI state. There may be a priority rule between semi-known and unknown. If a TCI state may be considered semi-known at a particular time, the TCI state may not be considered unknown until the semi-known condition is no longer met.

[0154] The UE 2220 and the network entity may apply TCI state switching according to the TCI state switching timeline of the semi-known TCI state. As shown by reference numeral 2255, the network entity 2210 may send communications (e.g., on the PDSCH) using the activated TCI state. The UE 2220 may receive communications using the activated TCI state. By using the TVCI state switching timeline of the semi-known state, latency may be reduced.

[0155] In some aspects, the UE 2220 may indicate (applicability indication) whether the semi-known TCI state is applicable to the UE 2220. For example, if the UE 2220 identifies that the reference signal in the TCI state is applicable to the semi-known condition, the UE 2220 may assume that the TCI state is applicable to the semi-known state. That is, the UE 2220 may determine that the TCI state can be a semi-known TCI state without signaling from the network entity 2210.

[0156] In some aspects, the UE 2220 may determine that the TCI state can be a semi-known TCI state based at least in part on signaling from the network entity 2210. The network entity 2210 may control the use of the semi-known TCI state. The network entity 2210 may indicate to the UE 2220 that the TCI state is applicable to the semi-known state. For example, the network entity 2210 may configure whether the semi-known state can be assumed or used by the UE 2220 via an RRC configuration for the TCI state or the TCI state activation command (which may override other RRC configurations for the TCI state). The network entity 2210 may also use a MAC CE to configure the UE 2220 to specifically activate a TCI state applicable to the semi-known state. The network entity 2210 may indicate the TCI state activated by such a MAC CE in a DCI (with a corresponding dedicated radio network temporary identifier (RNTI) or DCI format). For example, the DCI may also indicate the indicated TCI state identifier (ID) associated with the type of the TCI state activation command.

[0157] In some aspects, the UE 2220 may report whether the TCI state is applicable to the semi-known state. The UE 2220 may report a preference (preference indication) that the TCI state configured by the RRC may be assumed to be a semi-known state. The UE 2220 may report the UE report of one or more of the TCI states activated by the MAC CE and whether the semi-known state may be assumed together with an acknowledgment (ACK) about the TCI state activation MAC CE. This may be further based on overwriting the MAC CE indication by such UE report. The UE 2220 may report its preference about the value of X (e.g., different values ​​of X for different scenarios).

[0158] As indicated above, Fig. 22 are provided as examples. Other examples may vary from Fig. 22 Examples described.

[0159] For example, the timeline for applying the TCI state after the indication of the TCI state, for example at 1820, may be based on whether the TCI state is a known state, a semi-known state, or an unknown TCI state. If the known TCI state condition is not met but the predicted condition is met (considering whether the Rx beam has been addressed in the L1 report), the TCI state may be considered a semi-known TCI state. For example, the base station may help predict the Rx beam and may indicate a TCI state including an Rx beam ID, even though the UE has not yet reported the L1-RSRP / L1-SINR associated with the Rx beam because the UE may have explicitly reported the 1st number of Rx beams in the capability report. The UE may apply timeline parameters (such as Xms) for communication based on the semi-known TCI state after being indicated by the base station. The timeline parameters may be defined, configured by the base station, or reported by the UE.

[0160] Fig.23 2300 is a flow chart of a method of wireless communication. The method may be performed by a UE (e.g., UE 104, UE 350, UE 504, device 2504). In one example, the method (including the various configurations described below) may be performed by the L1 reporting component 198 described above. The method may be associated with various advantages for the UE, such as reduced UE power consumption and reduced latency (described in detail above). At 2302, the UE measures a CMR for each of one or more downlink transmit beams. For example, see Figure 6 , the UE generates L1-RSRP time series measurements 602 for one or more CSI-RS or SSBs.

[0161] At 2304, the UE sends an L1 measurement report including one or more measurements for the CMR and a receive beam ID for the receive beam for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs. Figure 8 , the UE sends a beam pair-based enhanced L1 report 802, and the enhanced L1 report 802 includes an identifier of the Rx beam (eg, an identifier of the third Rx beam 808).

[0162] In one configuration, the CMR may include at least one of a CSI-RS resource or an SSB resource, and each of the one or more measurements may include at least one of an L1-RSRP measurement or an L1-SINR measurement. Figure 8 , the enhanced L1 report 802 includes a L1-RSRP measurement (eg, the L1-RSRP measurement 812 ).

[0163] In one configuration, the UE may send information identifying a first set of receive beams at the UE prior to an L1 measurement report. The UE may receive a configuration for L1 measurement reporting that instructs the UE to report L1 measurements of a second set of receive beams, the second set of receive beams comprising at least a subset of the first set of receive beams at the UE. In such a configuration, the receive beam ID of the receive beam for each of the one or more measurements is based on the second set of receive beams indicated in the configuration. For example, see Fig. 9 , the UE may send the first UE Rx beam information 902. The UE may receive a configuration for L1 measurement reporting, which indicates that the UE will report L1 measurements for a second Rx beam (eg, a beam corresponding to Rx beam identifier 910, Rx beam identifier 916, and Rx beam identifier 918).

[0164] In one configuration, the information identifying the first set of receive beams at the UE includes at least one of beam pointing directions or beam width information. Fig. 9 , the first UE Rx beam information 902 may include information about the beam pointing direction or beam width.

[0165] In one configuration, this configuration may be used for semi-persistent CSI reporting, and the second set of receive beams is identified in the MAC-CE that activates the semi-persistent CSI reporting. Fig. 9 , the UE may be configured via MAC-CE (activate SP CSI reporting) to generate a reporting configuration 922, where the reporting configuration 922 corresponds to the second number of Rx beams.

[0166] In one configuration, the configuration is for aperiodic CSI reporting, and the second set of receive beams is identified in the configuration for aperiodic CSI reporting. Fig. 9 , the UE may be configured to generate a reporting configuration 922 via triggering an AP CSI report 920, wherein the reporting configuration 922 corresponds to a second number of Rx beams.

[0167] In one configuration, the L1 measurement report may include an absolute value of a first measurement for a first transmit and receive beam pair and a differential value for each of the one or more beam pairs relative to the absolute value of the first transmit and receive beam pair. Fig.10 , the UE may report absolute L1-RSRP measurements 1002 and differential L1-RSRP measurements 1004 , 1006 , 1008 .

[0168] In one configuration, the L1 measurement report may include: an absolute value of a first measurement of a first beam pair of a first CMR; a first differential value of a second CMR using a first receive beam, the first differential value relative to the absolute value of the first CMR; and a second differential value of a second CMR using a second receive beam, the second differential value relative to the first differential value. For example, see Fig.11 , the UE may report an absolute L1-RSRP measurement 1102 corresponding to the strongest beam pair among all CMRs, a differential L1-RSRP measurement 1104 relative to the absolute L1-RSRP 1104 and for a CMR different from the CMR corresponding to the absolute L1-RSRP measurement 1102, and a differential measurement 1110 relative to the differential L1-RSRP measurement 1104 and corresponding to the CMR used for the differential L1-RSRP measurement 1102.

[0169] In one configuration, the UE may report a CMR identifier ID and a receive beam ID for each of one or more measurements included in an L1 measurement report. Figure 8 , the enhanced L1-RSRP report includes an identifier of the first CMR 804 , an identifier of the third Rx beam 808 , and an L1-RSRP measurement 812 .

[0170] In one configuration, the UE may receive a configuration for reporting different numbers of beam pair measurements for different CMRs. Figure 8 , the UE may receive a configuration for reporting beam pairs for the first CMR 804 and the fourth CMR 806.

[0171] In one configuration, the UE may compress the payload of the L1 measurement report. In such a configuration, compressing the payload may include at least one of: encoding a first component of the L1 measurement report using a first encoder and encoding a second component of the L1 measurement report using a second encoder, performing variable length compression of the payload of the L1 measurement report and reporting a variable payload size using a fixed number of bits, or encoding the payload of the L1 measurement report based on an indication from a network entity of at least one of a decoder or an encoder. For example, see Fig.12 , the UE may provide L1-RSRP and / or L1-SINR 1204 as input to a first encoder 1208. The first encoder 1208 generates coded L1-RSRP / L1-SINR 1204 based on L1-RSRP and / or L1-SINR 1210. The UE may also provide CMR identifier and Rx beam identifier 1206 as input to a second encoder 1212. The second encoder 1212 generates coded CMR identifier and Rx beam identifier 1214 based on the CMR identifier and Rx beam identifier 1206. For example, see Fig.13, in the first scheme 1302, the input length of the compressed / uncompressed payload is variable and the output length is fixed.

[0172] In one configuration, the first encoder may compress one or more measurements in the L1 measurement report, and the second encoder may compress at least one of the CMR ID or the receive beam ID. Fig.12 , the UE may provide L1-RSRP and / or L1-SINR 1204 as input to a first encoder 1208, and the first encoder compresses the L1-RSRP and / or L1-SINR 1204, and the UE may also provide a CMR identifier and an Rx beam identifier 1206 as input to a second encoder 1212 that compresses the CMR identifier and the Rx beam identifier 1206.

[0173] In one configuration, a first portion of the L1 measurement payload may be reported in a first CSI portion, and a second portion of the L1 measurement payload may be reported in a second CSI portion. Fig.14 , the UE may divide the payload 1402 into a first CSI part 1404 and a second CSI part 1406 .

[0174] In one configuration, the first CSI portion may include the strongest L1 measurement for CMR based on the first receive beam, and the second CSI portion may include at least one additional L1 measurement for CMR based on at least one additional receive beam. Fig.14 , the first CSI part 1404 includes a legacy L1 report 1408 containing the strongest L1-RSRP / L1-SINR measurement for each downlink CMR. The second CSI part 1406 includes a remaining component / information 1412. The remaining component / information 1412 may include one or more additional L1 measurements for CMR based on another receive beam.

[0175] In one configuration, the first CSI portion may indicate a payload size of a second portion of the L1 measurement payload in the second CSI portion. Fig.15 , the first CSI part 1504 includes a non-compressed L1 report payload size or a compressed payload size 1508.

[0176] In one configuration, a first measurement for CMR and a first receive beam may be reported in a first CSI report, and at least one additional L1 measurement for CMR based on at least one additional receive beam may be reported in a second CSI report. Fig.16, the UE is configured via a plurality of CSI reporting settings to generate an L1 report 1604 and a remaining component 1606. Each of the L1 reports 1604 may include the strongest L1-RSRP / L1-SINR measurement for each downlink CMR and an identifier for the corresponding CMR (which may be referred to as a first CSI report). Each of the remaining components 1606 (which may be referred to as a second CSI report) includes an enhanced L1 report (e.g., enhanced L1 report 802).

[0177] In one configuration, the first CSI may have a different periodicity than the second CSI report. Fig.16 In one aspect, the UE reports the L1 report 1604 at a first periodicity and reports the remaining component 1606 at a second periodicity, wherein the first periodicity is less than the second periodicity. The most recent first CSI report may be used as a reference for the second CSI report.

[0178] In one configuration, a UE may receive a configuration of a set of TCI states having a QCL relationship with at least one receive beam at the UE. The UE may receive activation of at least one TCI state from the set of TCI states. The UE may communicate with a network entity using at least one receive beam having a QCL relationship with at least one TCI state activated for the UE. For example, see Fig.17 , a UE (e.g., UE 104, UE 350, UE 504) may be configured with a first number of TCI states, wherein TCI state 1702 is included in the first number of TCI states. TCI state 1702 includes QCL information 1704. QCL information 1704 includes a UE Rx beam identifier 1706 and UE Rx beam information (which may be based on the enhanced L1 report 802 as described above).

[0179] In one configuration, the UE may apply a switching timeline based on at least one TCI state satisfying a first set of conditions for a known state or a second set of conditions for a partially known state. Fig.19 and Fig. 20 , describes an example of switching timelines.

[0180] In one configuration, a first set of conditions for a known state may include receiving a TCI state switch command within a time period after a last reference signal for beam reporting or measurement, sending at least one layer 1 reference signal received power report for the TCI state before receiving the TCI state switch command, the TCI state remaining detectable during the TCI state switch period, and the synchronization signal blocks associated with the TCI state remaining detectable during the TCI state switch period. See, for example, Fig.19 and Fig. 22 , describes an example of the first set of conditions.

[0181] In one configuration, the second set of conditions for the partially known state may be based on the first set of conditions, except for at least one of the following: the UE does not perform measurement of SSB or CSI-RS after receiving a time slot in which the TCI state is activated and before receiving a DCI identifying the TCI state, the UE performs measurement of SSB but not CSI-RS after receiving a time slot in which the TCI state is activated and before receiving a DCI identifying the TCI state, or the UE performs measurement of SSB but not CSI-RS after receiving a time slot in which the TCI state is activated and before receiving a DCI identifying the TCI state. For example, see Figures 19 to 22 , describes an example of the second set of conditions.

[0182] Fig.24 2400 is a flowchart of a method of wireless communication. The method may be performed by a network node (e.g., base station 102, base station 310, base station 502, network entity 2602). In one example, the method (including the various configurations described below) may be performed by the receive beam indication component 199 described above. The method may be associated with various advantages for the network node, such as more accurate beam pair prediction (described in detail above). At 2402, the network node obtains an L1 measurement report, the report including one or more measurements for a CMR and a receive beam ID of a receive beam at a user equipment (UE) for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs. For example, see Figure 8 , the base station obtains an enhanced L1 report 802, and the enhanced L1 report 802 includes an identifier of the Rx beam.

[0183] At 2404, the network node activates at least one TCI state having a QCL relationship with a receive beam at the UE. Fig.17 , the network node activates TCI state 1702. TCI state 1702 includes QCL information 1704.

[0184] In one configuration, the network node may configure a set of TCI states having a QCL relationship with at least one receive beam at the UE. In such an aspect, at least one TCI state is activated from the set of TCI states configured for the UE. For example, see Fig.17 , TCI state 1702 can be part of a set of TCI states that have a QCL relationship with the receive beam at the UE.

[0185] In one configuration, the CMR may include at least one of a CSI-RS resource or an SSB resource. In such an aspect, each of the one or more measurements includes at least one of an L1-RSRP measurement or an L1-SINR measurement. For example, see Figure 8 , the enhanced L1 report 802 includes L1-RSRP measurements for different CMRs.

[0186] In one configuration, the network node may obtain information identifying a first set of receive beams at the UE prior to an L1 measurement report. In such a configuration, the network node may output a configuration for the L1 measurement report that instructs the UE to report L1 measurements of a second set of receive beams, the second set of receive beams comprising at least a subset of the first set of receive beams at the UE. The receive beam IDs of the receive beams for each of the one or more measurements are based on the second set of receive beams indicated in the configuration. For example, see Fig. 9 , the network node may obtain the first UE Rx beam information 902. The network node may output a report configuration 922.

[0187] In one configuration, the information identifying the first set of receive beams at the UE includes at least one of beam pointing directions or beam width information. Fig. 9 , the first UE Rx beam information 902 may include information about the beam pointing direction or beam width.

[0188] In one configuration, this configuration may be used for semi-persistent CSI reporting, and the second set of receive beams is identified in the MAC-CE that activates the semi-persistent CSI reporting. Fig. 9 , this configuration can be used for SP CSI reporting.

[0189] In one configuration, the configuration may be used for aperiodic CSI reporting, and the second set of receive beams is identified in the configuration for aperiodic CSI reporting. Fig. 9 , this configuration can be used for AP CSI reporting.

[0190] In one configuration, the L1 measurement report may include an absolute value of a first measurement for a first transmit and receive beam pair and a differential value for each of the one or more beam pairs relative to the absolute value of the first transmit and receive beam pair. Fig.10 , the network node may obtain absolute L1-RSRP measurements 1002 and differential L1-RSRP measurements 1004 , 1006 , 1008 .

[0191] In one configuration, the L1 measurement report may include: an absolute value of a first measurement of a first beam pair of a first CMR; a first differential value of a second CMR using a first receive beam, the first differential value relative to the absolute value of the first CMR; and a second differential value of a second CMR using a second receive beam, the second differential value relative to the first differential value. For example, see Fig.11 , the network node may obtain an absolute L1-RSRP measurement 1102 corresponding to the strongest beam pair among all CMRs, a differential L1-RSRP measurement 1104 relative to the absolute L1-RSRP 1104 and for a CMR different from the CMR corresponding to the absolute L1-RSRP measurement 1102, and a differential measurement 1110 relative to the differential L1-RSRP measurement 1104 and corresponding to the CMR used for the differential L1-RSRP measurement 1102.

[0192] In one configuration, the L1 measurement report may include a CMR identifier ID and a receive beam ID for each of the one or more measurements included in the L1 measurement report. Figure 8 , the enhanced L1-RSRP report includes an identifier of the first CMR 804 , an identifier of the third Rx beam 808 , and an L1-RSRP measurement 812 .

[0193] In one configuration, the network node may output a configuration for reporting different numbers of beam pair measurements for different CMRs. Figure 8 , the network node may output a configuration for reporting beam pairs for the first CMR 804 and the fourth CMR 806 .

[0194] In one configuration, the payload of the L1 measurement report may be compressed based on at least one of: a first component of the L1 measurement report encoded using a first encoder and a second component of the L1 measurement report encoded using a second encoder, variable length compression of the payload of the L1 measurement report and an indication of a variable payload size using a fixed number of bits, or the payload of the L1 measurement report encoded based on an indication from a network entity of at least one of a decoder or an encoder. For example, see Fig.12 , L1-RSRP and / or L1-SINR 1204 may be provided as input to a first encoder 1208. The first encoder 1208 generates an encoded L1-RSRP / L1-SINR 1204 based on the L1-RSRP and / or L1-SINR 1210. The CMR identifier and the Rx beam identifier 1206 may be provided as input to a second encoder 1212. The second encoder 1212 generates an encoded CMR identifier and an Rx beam identifier 1214 based on the CMR identifier and the Rx beam identifier 1206. For example, see Fig.13, in the first scheme 1302, the input length of the compressed / uncompressed payload is variable and the output length is fixed.

[0195] In one configuration, a first portion of the L1 measurement payload may be reported in a first CSI portion, and a second portion of the L1 measurement payload may be reported in a second CSI portion. Fig.14 , the payload 1402 may be reported in a first CSI portion 1404 and a second CSI portion 1406 .

[0196] In one configuration, the first CSI portion may include the strongest L1 measurement for CMR based on the first receive beam, and the second CSI portion may include at least one additional L1 measurement for CMR based on at least one additional receive beam. The first CSI portion 1404 includes a legacy L1 report 1408 containing the strongest L1-RSRP / L1-SINR measurement for each downlink CMR. The second CSI portion 1406 includes a remaining component / information 1412. The remaining component / information 1412 may include one or more additional L1 measurements for CMR based on another receive beam.

[0197] In one configuration, the first CSI portion may indicate a payload size of a second portion of the L1 measurement payload in the second CSI portion. Fig.15 , the first CSI part 1504 includes a non-compressed L1 report payload size or a compressed payload size 1508.

[0198] In one configuration, a first measurement for CMR and a first receive beam may be reported in a first CSI report, and at least one additional L1 measurement for CMR based on at least one additional receive beam may be reported in a second CSI report. Fig.16 , the network node may obtain L1 reports 1604 and remaining components 1606. Each L1 report in L1 reports 1604 may include the strongest L1-RSRP / L1-SINR measurement for each downlink CMR and an identifier for the corresponding CMR (which may be referred to as a first CSI report). Each remaining component in remaining components 1606 (which may be referred to as a second CSI report) includes an enhanced L1 report (e.g., enhanced L1 report 802).

[0199] In one configuration, the first CSI report may have a different periodicity than the second CSI report. Fig.16 In one aspect, the L1 report 1604 is reported at a first periodicity and the remaining component 1606 is reported at a second periodicity, wherein the first periodicity is less than the second periodicity. The most recent first CSI report may be used as a reference for the second CSI report.

[0200] Fig.252500 is a diagram illustrating an example of a hardware implementation for an apparatus 2504. The apparatus 2504 may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus 2504 may include a cellular baseband processor 2524 (also referred to as a modem) coupled to one or more transceivers 2522 (e.g., a cellular RF transceiver). The cellular baseband processor 2524 may include on-chip memory 2524'. In some aspects, the apparatus 2504 may also include one or more subscriber identity module (SIM) cards 2520 and an application processor 2506 coupled to a secure digital (SD) card 2508 and a screen 2510. The application processor 2506 may include on-chip memory 2506'. In some aspects, the device 2504 may also include a Bluetooth module 2512, a WLAN module 2514, an SPS module 2516 (e.g., a GNSS module), one or more sensor modules 2518 (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 2526, a power source 2530, and / or a camera 2532. The Bluetooth module 2512, the WLAN module 2514, and the SPS module 2516 may include an on-chip transceiver (TRX) (or in some cases, only a receiver (RX)). The Bluetooth module 2512, the WLAN module 2514, and the SPS module 2516 may include their own dedicated antennas and / or communicate using antennas 2580. The cellular baseband processor 2524 communicates with the UE 104 and / or with the RU associated with the network entity 2502 through the transceiver 2522 via one or more antennas 2580. The cellular baseband processor 2524 and the application processor 2506 may each include a computer-readable medium / memory 2524', 2506', respectively. The additional memory module 2526 may also be considered as a computer-readable medium / memory. Each computer-readable medium / memory 2524', 2506', 2526 may be non-transitory. The cellular baseband processor 2524 and the application processor 2506 are each responsible for general processing, including executing software stored on a computer-readable medium / memory. The software enables the cellular baseband processor 2524 / application processor 2506 to perform the various functions described above when executed by the cellular baseband processor 2524 / application processor 2506. The computer-readable medium / memory can also be used to store data manipulated by the cellular baseband processor 2524 / application processor 2506 when executing the software.The cellular baseband processor 2524 / application processor 2506 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 2504 may be a processor chip (modem and / or application) and include only the cellular baseband processor 2524 and / or the application processor 2506, while in another configuration, the device 2504 may be the entire UE (e.g., see. Figure 3 350) and includes additional modules of device 2504.

[0201] As discussed above, the L1 reporting component 198 is configured to measure the CMR for each of the one or more downlink transmit beams and send an L1 measurement report including one or more measurements for the CMR and a receive beam identifier (ID) for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams of different UE identities. The L1 reporting component 198 may be within the cellular baseband processor 2524, the application processor 2506, or within both the cellular baseband processor 2524 and the application processor 2506. The component 198 may be one or more hardware components that are specifically configured to perform the stated process / algorithms, implemented by one or more processors configured to perform the stated process / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. As shown, the device 2504 may include a variety of components configured for various functions. In one configuration, the apparatus 2504 (and specifically the cellular baseband processor 2524 and / or the application processor 2506) includes: a component for measuring a CMR for each of one or more downlink transmit beams; and a component for sending a layer 1 (L1) measurement report, the report including one or more measurements for the CMR and a receive beam identifier (ID) for the receive beam for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams of different UE identities. These components can be the L1 reporting component 198 of the apparatus 2504 configured to perform the functions recited by the components. As described above, the apparatus 2504 may include a TX processor 368, an RX processor 356, and a controller / processor 359. Therefore, in one configuration, these components can be the TX processor 368, the RX processor 356, and / or the controller / processor 359 configured to perform the functions recited by the components.

[0202] Fig.262600 is a diagram illustrating an example of a hardware implementation for a network entity 2602. The network entity 2602 may be a BS, a component of a BS, or may implement BS functionality. The network entity 2602 may include at least one of a CU 2610, a DU 2630, or a RU 2640. For example, depending on the layer functionality handled by the receive beam indication component 199, the network entity 2602 may include: a CU 2610; both a CU 2610 and a DU 2630; each of a CU 2610, a DU 2630, and a RU 2640; a DU 2630; both a DU 2630 and a RU 2640; or a RU 2640. The CU 2610 may include a CU processor 2612. The CU processor 2612 may include an on-chip memory 2612'. In some aspects, the CU 2610 may also include an additional memory module 2614 and a communication interface 2618. CU 2610 communicates with DU 2630 via a midhaul link, such as an F1 interface. DU 2630 may include a DU processor 2632. DU processor 2632 may include on-chip memory 2632'. In some aspects, DU 2630 may also include additional memory modules 2634 and a communication interface 2638. DU 2630 communicates with RU 2640 via a fronthaul link. RU 2640 may include a RU processor 2642. RU processor 2642 may include on-chip memory 2642'. In some aspects, RU 2640 may also include additional memory modules 2644, one or more transceivers 2646, antenna 2680, and communication interface 2648. RU 2640 communicates with UE 104. On-chip memory 2612', 2632', 2642' and additional memory modules 2614, 2634, 2644 may each be considered a computer-readable medium / memory. Each computer readable medium / memory can be non-transitory. Each processor in processors 2612, 2632, 2642 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.

[0203] As discussed above, the receive beam indication component 199 is configured to obtain an L1 measurement report including one or more measurements for CMR, and identify a receive beam at the UE for each of the one or more measurements, and activate at least one TCI state having a QCL relationship with the receive beam at the UE. The receive beam indication component 199 may be within one or more processors of one or more of the CU 2610, DU 2630, and RU 2640. The receive beam indication component 199 may be one or more hardware components that are specifically configured to perform the stated process / algorithms, implemented by one or more processors configured to perform the stated process / algorithms, stored in a computer-readable medium for implementation by one or more processors, or some combination thereof. The network entity 2602 may include a variety of components configured for various functions. In one configuration, the network entity 2602 includes: a component for obtaining an L1 measurement report including one or more measurements for CMR and identifying a receive beam at the UE for each of the one or more measurements; and a component for activating at least one TCI state having a QCL relationship with the receive beam at the UE. These means may be the receive beam indication component 199 of the network entity 2602 configured to perform the functions recited by these means. As described above, the network entity 2602 may include the TX processor 316, the RX processor 370, and the controller / processor 375. Thus, in one configuration, these means may be the TX processor 316, the RX processor 370, and / or the controller / processor 375 configured to perform the functions recited by the means.

[0204] As described above, the UE may be configured to report beam quality in the form of a report provided to the gNB. However, the report sent by the UE to the gNB may not have information about the receive (Rx) beam that the UE has measured with respect to a particular transmit (Tx) beam, which may adversely affect predictive beam management efforts. To address this issue, an enhanced L1 report for gNB-assisted beam pair prediction is described herein. For example, the UE measures a channel measurement resource (CMR) for each of one or more downlink transmit beams. The UE sends an L1 measurement report (i.e., an enhanced L1 report) that includes one or more measurements for the CMR and a receive beam identifier (ID) for the receive beam for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs. By using enhanced L1 reports for ML model training purposes and at the time of inference, such enhanced L1 reports can reduce the number of beam scans during beam scanning and help gNB-assisted beam pair prediction. In this way, enhanced L1 reports can reduce latency and UE power consumption. In addition, the UE may compress the enhanced L1 report using differential measurements and / or using an encoder, which may reduce the size of the enhanced L1 report, resulting in more efficient use of network resources. In addition to compression, the UE may also divide the enhanced L1 report into a first CSI part and a second CSI part, which may further reduce overhead. In addition, in addition to compression, the UE may also generate multiple CSI reports sent with different periodicities, which may further reduce overhead. In addition, information related to the enhanced L1 report may be used for TCI state activation / switching.

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

[0206] 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, wherein any such combination may contain one or more members of A, B, or C. A set should be interpreted as a set of elements, wherein 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 be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are covered by the claims. In addition, nothing disclosed herein is intended to be dedicated to the public, regardless of whether such disclosure is explicitly stated in the claims. Words such as "module", "mechanism", "element", "device" cannot replace the word "component". Therefore, no claim element will be understood as a component plus function unless the element is explicitly stated using the phrase "component for..."

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

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

[0209] Aspect 1 is a method for performing wireless communications at a user equipment (UE), the method comprising: measuring a channel measurement resource (CMR) for each of one or more downlink transmit beams; and sending a layer 1 (L1) measurement report, the report comprising one or more measurements for the CMR and a receive beam identifier (ID) for a receive beam for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs.

[0210] Aspect 2 is a method according to aspect 1, wherein the CMR includes at least one of a channel state information reference signal (CSI-RS) resource or a synchronization signal block (SSB) resource, and each of the one or more measurements includes at least one of an L1 reference signal received power (L1-RSRP) measurement or an L1 signal to interference plus noise ratio (L1-SINR) measurement.

[0211] Aspect 3 is a method according to any one of Aspects 1 to 2, the method further comprising: sending information identifying a first group of receive beams at the UE before the L1 measurement report; and receiving a configuration for the L1 measurement report, the configuration instructing the UE to report L1 measurements for a second group of receive beams, the second group of receive beams including at least a subset of the first group of receive beams at the UE, wherein the receive beam ID of the receive beam for each of the one or more measurements is based on the second group of receive beams indicated in the configuration.

[0212] Aspect 4 is a method according to any one of aspects 1 to 3, wherein the information identifying the first set of receive beams at the UE includes at least one of beam pointing direction or beam width information.

[0213] Aspect 5 is a method according to any one of Aspects 1 to 4, wherein the configuration is for semi-persistent channel state information (CSI) reporting, and the second set of receive beams is identified in a medium access control-control element (MAC-CE) that activates the semi-persistent CSI reporting.

[0214] Aspect 6 is a method according to any one of Aspects 1 to 4, wherein the configuration is used for non-periodic channel state information (CSI) reporting, and the second set of receive beams is identified in the configuration for the non-periodic CSI reporting.

[0215] Aspect 7 is a method according to any one of Aspects 1 to 6, wherein the L1 measurement report includes an absolute value of a first measurement of a first transmit and receive beam pair and a differential value of each of one or more beam pairs, wherein the differential value is relative to the absolute value of the first transmit and receive beam pair.

[0216] Aspect 8 is a method according to any one of Aspects 1 to 6, wherein the L1 measurement report includes: an absolute value of a first measurement of a first beam pair of a first CMR, a first differential value of a second CMR using a first receiving beam, the first differential value being relative to the absolute value of the first CMR; and a second differential value of the second CMR using a second receiving beam, the second differential value being relative to the first differential value.

[0217] Aspect 9 is a method according to any one of aspects 1 to 8, wherein the UE reports a CMR ID and a receive beam ID for each of the one or more measurements included in the L1 measurement report.

[0218] Aspect 10 is a method according to any one of aspects 1 to 9, the method further comprising: receiving a configuration for reporting different numbers of beam pair measurements for different CMRs.

[0219] Aspect 11 is a method according to any one of aspects 1 to 10, the method further comprising: compressing the payload of the L1 measurement report, including at least one of the following: encoding the first component of the L1 measurement report using a first encoder and encoding the second component of the L1 measurement report using a second encoder, performing variable length compression of the payload of the L1 measurement report and reporting a variable payload size using a fixed number of bits, or encoding the payload of the L1 measurement report based on an indication from a network entity of at least one of a decoder or an encoder.

[0220] Aspect 12 is a method according to any one of aspects 1 to 11, wherein the first encoder compresses the one or more measurements in the L1 measurement report, and the second encoder compresses at least one of a CMR ID or a receive beam ID.

[0221] Aspect 13 is a method according to any one of aspects 1 to 11, wherein the first part of the L1 measurement payload is reported in a first channel state information (CSI) part, and the second part of the L1 measurement payload is reported in a second CSI part.

[0222] Aspect 14 is a method according to any one of Aspects 1 to 11 and 13, wherein the first CSI part includes the strongest L1 measurement for the CMR based on a first receive beam, and the second CSI part includes at least one additional L1 measurement for the CMR based on at least one additional receive beam.

[0223] Aspect 15 is a method according to any one of aspects 1 to 11, 13 and 14, wherein the first CSI part indicates a payload size of the second part of the L1 measurement payload in the second CSI part.

[0224] Aspect 16 is a method according to any one of Aspects 1 to 11, wherein a first measurement for the CMR and a first receive beam is reported in a first channel state information (CSI) report, and at least one additional L1 measurement for the CMR based on at least one additional receive beam is reported in a second CSI report.

[0225] Aspect 17 is a method according to any one of aspects 1 to 11 and 15, wherein the first CSI report has a different periodicity from the second CSI report.

[0226] Aspect 18 is a method according to any one of Aspects 1 to 17, the method further comprising: receiving a configuration of a set of transmit configuration indication (TCI) states having a quasi co-location (QCL) relationship with at least one receive beam at the UE; receiving activation of at least one TCI state from the set of TCI states; and communicating with a network entity using at least one receive beam having the QCL relationship with the at least one TCI state activated for the UE.

[0227] Aspect 19 is a method according to any one of Aspects 1 to 18, the method further comprising: applying a switching timeline based on the at least one TCI state satisfying a first set of conditions for a known state or a second set of conditions for a partially known state.

[0228] Aspect 20 is a method according to any one of Aspects 1 to 19, wherein the first set of conditions for the known state includes: receiving a TCI state switching command within a time period after the last reference signal used for beam reporting or measurement; sending at least one layer 1 reference signal received power report for the TCI state before receiving the TCI state switching command; the TCI state remains detectable during the TCI state switching period; and the synchronization signal block associated with the TCI state remains detectable during the TCI state switching period.

[0229] Aspect 21 is a method according to any one of Aspects 1 to 20, wherein the second set of conditions for the partially known state is based on the first set of conditions, except for at least one of the following: the UE does not perform measurement of a synchronization signal block (SSB) or a channel state information reference signal (CSI-RS) after receiving a time slot in which the TCI state is activated and before receiving downlink control information (DCI) identifying the TCI state, the UE performs the measurement of the SSB but does not measure the CSI-RS after receiving a time slot in which the TCI state is activated and before receiving the DCI identifying the TCI state, or for at least one of the SSB or the CSI-RS, a timeline parameter is used for an unknown TCI state with a reduced receive beam scanning factor.

[0230] Aspect 22 is a method for performing wireless communications at a network node, the method comprising: obtaining a layer 1 (L1) measurement report, the report comprising one or more measurements of a channel measurement resource (CMR) and a receive beam identifier (ID) of a receive beam at a user equipment (UE) for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs; and activating at least one transmit configuration indication (TCI) state having a quasi co-location (QCL) relationship with the receive beam at the UE.

[0231] Aspect 23 is a method according to Aspect 22, the method further comprising: configuring a set of TCI states having a QCL relationship with at least one receive beam at the UE, wherein the at least one TCI state is activated from the set of TCI states configured for the UE.

[0232] Aspect 24 is a method according to aspect 22 or 23, the method also including the CMR including at least one of a channel state information reference signal (CSI-RS) resource or a synchronization signal block (SSB) resource, and each of the one or more measurements includes at least one of an L1 reference signal received power (L1-RSRP) measurement or an L1 signal to interference plus noise ratio (L1-SINR) measurement.

[0233] Aspect 25 is a method according to any one of Aspects 22 to 24, the method further comprising: obtaining information identifying a first group of receive beams at the UE before the L1 measurement report; and outputting a configuration for the L1 measurement report, the configuration indicating that the UE reports L1 measurements for a second group of receive beams, the second group of receive beams including at least a subset of the first group of receive beams at the UE, wherein the receive beam ID of the receive beam for each of the one or more measurements is based on the second group of receive beams indicated in the configuration.

[0234] Aspect 26 is a method according to any one of Aspects 22 to 25, the method also including the configuration being used for semi-persistent channel state information (CSI) reporting, and the second group of receive beams being identified in a medium access control-control element (MAC-CE) that activates the semi-persistent CSI reporting.

[0235] Aspect 27 is a method according to any one of Aspects 22 to 25, the method also including the configuration being used for non-periodic channel state information (CSI) reporting, and the second group of receiving beams being identified in the configuration for the non-periodic CSI reporting.

[0236] Aspect 28 is a method according to any one of aspects 22 to 27, wherein the information identifying the first set of receive beams at the UE includes at least one of beam pointing direction or beam width information.

[0237] Aspect 29 is a method according to any one of Aspects 22 to 28, wherein the L1 measurement report includes an absolute value of a first measurement of a first transmit and receive beam pair and a differential value of each of one or more beam pairs, wherein the differential value is relative to the absolute value of the first transmit and receive beam pair.

[0238] Aspect 30 is a method according to any one of Aspects 22 to 28, wherein the L1 measurement report includes: an absolute value of a first measurement of a first beam pair of a first CMR; a first differential value of a second CMR using a first receiving beam, the first differential value being relative to the absolute value of the first CMR, and a second differential value of the second CMR using a second receiving beam, the second differential value being relative to the first differential value.

[0239] Aspect 31 is a method according to any one of aspects 22 to 30, wherein the L1 measurement report includes a CMR identifier (ID) and a receive beam ID for each of the one or more measurements included in the L1 measurement report.

[0240] Aspect 32 is a method according to any one of aspects 22 to 31, the method further comprising outputting a configuration for reporting different numbers of beam pair measurements for different CMRs.

[0241] Aspect 33 is a method according to any one of aspects 22 to 32, wherein the payload of the L1 measurement report is compressed based on at least one of: a first component of the L1 measurement report encoded using a first encoder and a second component of the L1 measurement report encoded using a second encoder, variable length compression of the payload of the L1 measurement report and a first indication of a variable payload size using a fixed number of bits, or the payload of the L1 measurement report encoded based on a second indication from a network entity of at least one of a decoder or an encoder.

[0242] Aspect 34 is a method according to any one of aspects 22 to 32, wherein the first part of the L1 measurement payload is reported in a first channel state information (CSI) part, and the second part of the L1 measurement payload is reported in a second CSI part.

[0243] Aspect 35 is a method according to aspect 34, wherein the first CSI part includes the strongest L1 measurement for the CMR based on a first receive beam, and the second CSI part includes at least one additional L1 measurement for the CMR based on at least one additional receive beam.

[0244] Aspect 36 is a method according to aspect 34 or 35, wherein the first CSI part indicates a payload size of the second part of the L1 measurement payload in the second CSI part.

[0245] Aspect 37 is a method according to any one of Aspects 22 to 32, wherein a first measurement for the CMR and a first receive beam is reported in a first channel state information (CSI) report, and at least one additional L1 measurement for the CMR based on at least one additional receive beam is reported in a second CSI report.

[0246] Aspect 38 is a method according to aspect 37, wherein the first CSI report has a different periodicity than the second CSI report.

[0247] Aspect 39 is an apparatus for wireless communication at a user equipment (UE), the apparatus comprising a memory and at least one processor coupled to the memory and configured to perform a method according to any one of aspects 1 to 21.

[0248] Aspect 40 is an apparatus for wireless communication, the apparatus comprising means for performing the method according to any one of aspects 1 to 21.

[0249] Aspect 41 is an apparatus according to aspect 39 or 40, the apparatus further comprising at least one transceiver configured to send the L1 measurement report.

[0250] Aspect 42 is a non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform a method according to any one of aspects 1 to 21.

[0251] Aspect 43 is an apparatus for wireless communication at a network node, the apparatus comprising a memory and at least one processor, the at least one processor being coupled to the memory and configured to perform a method according to any one of aspects 22 to 38.

[0252] Aspect 44 is an apparatus for wireless communication, the apparatus comprising means for performing a method according to any one of aspects 22 to 38.

[0253] Aspect 45 is an apparatus according to aspect 43 or 44, the apparatus further comprising at least one transceiver configured to obtain an L1 measurement report.

[0254] Aspect 46 is a non-transitory computer-readable medium comprising instructions which, when executed by an apparatus, cause the apparatus to perform a method according to any one of aspects 22 to 38.

Claims

1. An apparatus for wireless communication at a user equipment (UE), the apparatus comprising: Memory; and at least one processor coupled to the memory and configured to: measuring a channel measurement resource (CMR) for each of the one or more downlink transmit beams; as well as A layer 1 (L1) measurement report is sent, the report including one or more measurements for the CMR and a receive beam identifier (ID) of a receive beam for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs.

2. The apparatus of claim 1 , wherein the CMR comprises at least one of a channel state information reference signal (CSI-RS) resource or a synchronization signal block (SSB) resource, and each of the one or more measurements comprises at least one of a L1 reference signal received power (L1-RSRP) measurement or a L1 signal to interference plus noise ratio (L1-SINR) measurement.

3. The apparatus of claim 1 , wherein the at least one processor is further configured to: sending information identifying a first set of receive beams at the UE before the L1 measurement report; and Receive a configuration for the L1 measurement report, the configuration instructing the UE to report L1 measurements for a second set of receive beams, the second set of receive beams comprising at least a subset of the first set of receive beams at the UE, wherein the receive beam ID of the receive beam for each of the one or more measurements is based on the second set of receive beams indicated in the configuration. 4 . The apparatus of claim 3 , wherein the information identifying the first set of receive beams at the UE comprises at least one of beam pointing direction or beam width information.

5. The apparatus of claim 3, wherein the configuration is for semi-persistent channel state information (CSI) reporting, and the second set of receive beams is identified in a medium access control-control element (MAC-CE) that activates the semi-persistent CSI reporting.

6. The apparatus of claim 3, wherein the configuration is for aperiodic channel state information (CSI) reporting, and the second set of receive beams is identified in the configuration for the aperiodic CSI reporting.

7. The apparatus according to claim 1, wherein the L1 measurement report comprises: the absolute value of the first measurement of the first transmit and receive beam pair, and A differential value for each of one or more beam pairs relative to the absolute value of the first transmit and receive beam pair.

8. The apparatus according to claim 1, wherein the L1 measurement report comprises: the absolute value of the first measurement of the first beam pair of the first CMR, a first differential value of a second CMR using a first receive beam, the first differential value relative to the absolute value of the first CMR, and A second differential value of the second CMR of a second receive beam is used, the second differential value being relative to the first differential value.

9. The apparatus of claim 1, wherein the UE reports a CMR ID and a receive beam ID for each of the one or more measurements included in the L1 measurement report.

10. The apparatus of claim 1, wherein the at least one processor is further configured to: A configuration is received for reporting different numbers of beam-pair measurements for different CMRs.

11. The apparatus of claim 1 , wherein the at least one processor is further configured to: Compressing the payload of the L1 measurement report includes at least one of the following: encoding a first component of the L1 measurement report using a first encoder and encoding a second component of the L1 measurement report using a second encoder, performing variable length compression of said payload of said L1 measurement report and reporting a variable payload size using a fixed number of bits, or The payload of the L1 measurement report is encoded based on an indication from a network entity of at least one of a decoder or an encoder.

12. The apparatus of claim 11, wherein the first encoder compresses the one or more measurements in the L1 measurement report, and the second encoder compresses at least one of a CMR ID or a receive beam ID.

13. The apparatus of claim 1, wherein a first portion of the L1 measurement payload is reported in a first channel state information (CSI) portion and a second portion of the L1 measurement payload is reported in a second CSI portion.

14. The apparatus of claim 13, wherein the first CSI part comprises the strongest L1 measurement for the CMR based on a first receive beam, and the second CSI part comprises at least one additional L1 measurement for the CMR based on at least one additional receive beam. 15 . The apparatus of claim 13 , wherein the first CSI part indicates a payload size of the second part of the L1 measurement payload in the second CSI part.

16. The apparatus of claim 1, wherein a first measurement for the CMR and a first receive beam is reported in a first channel state information (CSI) report, and at least one additional L1 measurement for the CMR based on at least one additional receive beam is reported in a second CSI report.

17. The apparatus of claim 16, wherein the first CSI report has a different periodicity than the second CSI report.

18. The apparatus of claim 1, wherein the at least one processor is further configured to: receiving a configuration of a set of transmit configuration indication (TCI) states having a quasi co-location (QCL) relationship with at least one receive beam at the UE; receiving activation of at least one TCI state from the set of TCI states; and Communicate with a network entity using at least one receive beam having the QCL relationship with the at least one TCI state activated for the UE.

19. The apparatus of claim 18, wherein the at least one processor is further configured to: A switching timeline is applied based on the at least one TCI state satisfying a first set of conditions for a known state or a second set of conditions for a partially known state.

20. The apparatus of claim 19, wherein the first set of conditions for the known state comprises: A TCI state switch command is received within the time period after the last reference signal used for beam reporting or measurement; sending at least one layer 1 reference signal received power report for the TCI state before receiving the TCI state switch command; The TCI state remains detectable during a TCI state switching period; and The synchronization signal block associated with the TCI state remains detectable during the TCI state switching period.

21. The apparatus of claim 20, wherein the second set of conditions for the partially known state is based on the first set of conditions, except for at least one of the following: The UE does not perform measurement of a synchronization signal block (SSB) or a channel state information reference signal (CSI-RS) after receiving a time slot in which a TCI state is activated and before receiving downlink control information (DCI) identifying the TCI state, The UE performs the measurement of the SSB but does not measure the CSI-RS after receiving the time slot in which the TCI state is activated and before receiving the DCI identifying the TCI state, or For at least one of the SSB or the CSI-RS, a timeline parameter is used for an unknown TCI state with a reduced receive beam scanning factor.

22. The apparatus according to claim 1, further comprising: At least one transceiver coupled to the at least one processor and configured to send the L1 measurement report.

23. A method of wireless communication at a user equipment (UE), the method comprising: measuring a channel measurement resource (CMR) for each of the one or more downlink transmit beams; as well as A layer 1 (L1) measurement report is sent, the report including one or more measurements for the CMR and a receive beam identifier (ID) of a receive beam for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs.

24. An apparatus for wireless communication at a network node, the apparatus comprising: Memory; and at least one processor coupled to the memory and configured to: obtaining a layer 1 (L1) measurement report, the report comprising one or more measurements for a channel measurement resource (CMR) and a receive beam identifier (ID) of a receive beam at a user equipment (UE) for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs; as well as Activate at least one transmit configuration indication (TCI) state that has a quasi co-site (QCL) relationship with the receive beam at the UE.

25. The apparatus of claim 24, wherein the at least one processor is further configured to: A set of TCI states having a QCL relationship with at least one receive beam at the UE is configured, wherein the at least one TCI state is activated from the set of TCI states configured for the UE.

26. The apparatus of claim 24, wherein the at least one processor is further configured to: obtaining information identifying a first set of receive beams at the UE prior to the L1 measurement report; and Output a configuration for the L1 measurement report, the configuration instructing the UE to report L1 measurements for a second set of receive beams, the second set of receive beams including at least a subset of the first set of receive beams at the UE, wherein the receive beam ID of the receive beam for each of the one or more measurements is based on the second set of receive beams indicated in the configuration.

27. The apparatus of claim 26, wherein the information identifying the first set of receive beams at the UE comprises at least one of beam pointing direction or beam width information.

28. The apparatus of claim 24, wherein the L1 measurement report comprises: the absolute value of the first measurement of the first transmit and receive beam pair, and A differential value for each of one or more beam pairs relative to the absolute value of the first transmit and receive beam pair.

29. The apparatus of claim 24, wherein a payload of the L1 measurement report is compressed based on at least one of: a first component of the L1 measurement report encoded using a first encoder and a second component of the L1 measurement report encoded using a second encoder, a first indication of variable length compression of said payload of said L1 measurement report and of a variable payload size using a fixed number of bits, or The payload of the L1 measurement report is encoded based on a second indication from a network entity of at least one of a decoder or an encoder.

30. A method for wireless communication at a network node, the method comprising: obtaining a layer 1 (L1) measurement report, the report comprising one or more measurements for a channel measurement resource (CMR) and a receive beam identifier (ID) of a receive beam at a user equipment (UE) for each of the one or more measurements, wherein different measurements associated with the same CMR are associated with receive beams identified by different UEs; as well as Activate at least one transmit configuration indication (TCI) state that has a quasi co-site (QCL) relationship with the receive beam at the UE.

Images