WO2025111776A1

WO2025111776A1 - User-equipment-initiated beam report request

Info

Publication number: WO2025111776A1
Application number: PCT/CN2023/134598
Authority: WO
Inventors: Fang Yuan; Yan Zhou
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2023-11-28
Filing date: 2023-11-28
Publication date: 2025-06-05
Anticipated expiration: 2026-05-28

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may transmit a UE-initiated beam report request. The UE may generate, in association with the UE-initiated beam report request, a beam report using Layer 1 (L1) measurements. The UE may receive a channel state information (CSI) request. The UE may transmit the beam report in accordance with reception of the CSI request. Numerous other aspects are described.

Description

USER-EQUIPMENT-INITIATED BEAM REPORT REQUEST

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods for using a user-equipment-initiated beam report request.

BACKGROUND

Wireless communication systems are widely deployed to provide various services that may include carrying voice, text, messaging, video, data, and/or other traffic. The services may include unicast, multicast, and/or broadcast services, among other examples. Typical wireless communication systems may employ multiple-access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (for example, time domain resources, frequency domain resources, spatial domain resources, and/or device transmit power, among other examples) . Examples of such multiple-access RATs 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.

The above multiple-access RATs have been adopted in various telecommunication standards to provide common protocols that enable different wireless communication devices to communicate on a municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR) . NR, which may also be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) . NR (and other mobile broadband evolutions beyond NR) may be designed to better support Internet of things (IoT) and reduced capability device deployments, industrial connectivity, millimeter wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployment, sidelink and other device-to-device direct communication technologies (for example, cellular vehicle-to-everything (CV2X) communication) , massive multiple-input multiple-output (MIMO) , disaggregated network architectures and network topology expansions, multiple-subscriber implementations, high-precision positioning, and/or radio frequency (RF) sensing, among other examples. As the demand for mobile broadband access continues to increase, further improvements in NR may be implemented, and other radio access technologies such as 6G may be introduced, to further advance mobile broadband evolution.

In a legacy channel state information (CSI) procedure, a user equipment (UE) may receive and measure a reference signal, such as a CSI reference signal (CSI-RS) , on a channel and then provide a beam report (CSI report) . A network entity may use the CSI for scheduling communications on the channel. With the legacy CSI procedure, only upon receiving a CSI request from the network entity is the UE is aware of an initiative to measure a CSI-RS and report CSI. The UE uses a CSI processing time between the CSI request and the beam report to process the measurement and generate the beam report.

SUMMARY

Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE) . The method may include obtaining Layer 1 (L1) measurements. The method may include transmitting a UE-initiated beam report request. The method may include generating, in association with the UE-initiated beam report request, a beam report using the L1 measurements. The method may include receiving a channel state information (CSI) request. The method may include transmitting the beam report based at least in part on the receiving the CSI request.

Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include receiving a UE-initiated beam report request. The method may include transmitting a CSI request based at least in part on the receiving the UE-initiated beam report request. The method may include receiving the beam report.

Some aspects described herein relate to a method of wireless communication performed by a UE. The method may include obtaining L1 measurements. The method may include transmitting, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell identifier (ID) or a bandwidth part (BWP) ID.

Some aspects described herein relate to a method of wireless communication performed by a network entity. The method may include obtaining L1 measurements. The method may include receiving, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID.

Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be configured to obtain L1 measurements. The one or more processors may be configured to transmit a UE-initiated beam report request. The one or more processors may be configured to generate, in association with the UE-initiated beam report request, a beam report using the L1 measurements. The one or more processors may be configured to receive a CSI request. The one or more processors may be configured to transmit the beam report in accordance with reception of the CSI request.

Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive a UE-initiated beam report request. The one or more processors may be configured to transmit a CSI request in accordance with reception of the UE-initiated beam report request. The one or more processors may be configured to receive the beam report.

Some aspects described herein relate to an apparatus for wireless communication at a UE. The apparatus may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be configured to obtain L1 measurements. The one or more processors may be configured to transmit, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID.

Some aspects described herein relate to an apparatus for wireless communication at a network entity. The apparatus may include one or more memories storing processor-executable code and one or more processors coupled to the one or more memories. The one or more processors may be configured to receive a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to obtain L1 measurements. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit a UE-initiated beam report request. The set of instructions, when executed by one or more processors of the UE, may cause the UE to generate, in association with the UE-initiated beam report request, a beam report using the L1 measurements. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive a CSI request. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit the beam report in accordance with reception of the CSI request.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to receive a UE-initiated beam report request. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to transmit a CSI request in accordance with reception of the UE-initiated beam report request. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to receive the beam report.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a UE. The set of instructions, when executed by one or more processors of the UE, may cause the UE to obtain L1 measurements. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network entity. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to obtain L1 measurements. The set of instructions, when executed by one or more processors of the network entity, may cause the network entity to receive a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for obtaining L1 measurements. The apparatus may include means for transmitting a UE-initiated beam report request. The apparatus may include means for generating, in association with the UE-initiated beam report request, a beam report using the L1 measurements. The apparatus may include means for receiving a CSI request. The apparatus may include means for transmitting the beam report in accordance with reception of the CSI request.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving a UE-initiated beam report request. The apparatus may include means for transmitting a CSI request in accordance with reception of the UE-initiated beam report request. The apparatus may include means for receiving the beam report.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for obtaining L1 measurements. The apparatus may include means for transmitting, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for obtaining L1 measurements. The apparatus may include means for receiving, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID.

Aspects of the present disclosure may generally be implemented by or as a method, apparatus, system, computer program product, non-transitory computer-readable medium, user equipment, base station, network node, network entity, wireless communication device, and/or processing system as substantially described with reference to, and as illustrated by, the specification and accompanying drawings.

The foregoing paragraphs of this section have broadly summarized some aspects of the present disclosure. These and additional aspects and associated advantages will be described hereinafter. The disclosed aspects may be used as a basis for modifying or designing other aspects for carrying out the same or similar purposes of the present disclosure. Such equivalent aspects do not depart from the scope of the appended claims. Characteristics of the aspects disclosed herein, both their organization and method of operation, together with associated advantages, will be better understood from the following description when considered in connection with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The appended drawings illustrate some aspects of the present disclosure, but are not limiting of the scope of the present disclosure because the description may enable other aspects. Each of the drawings is provided for purposes of illustration and description, and not as a definition of the limits of the claims. The same or similar reference numbers in different drawings may identify the same or similar elements.

Figure 1 is a diagram illustrating an example of a wireless communication network.

Figure 2 is a diagram illustrating an example network node in communication with an example user equipment (UE) in a wireless network.

Figure 3 is a diagram illustrating examples of channel state information (CSI) reference signal (CSI-RS) beam management procedures.

Figure 4 is a diagram illustrating an example of a timeline for a legacy CSI procedure.

Figure 5 is a diagram illustrating an example of a timeline for a UE-initiated beam report.

Figure 6 is a diagram illustrating an example of a call flow involving a UE-initiated beam report request.

Figure 7 is a flowchart illustrating an example process performed, for example, at a UE or an apparatus of a UE that supports the use of a UE-initiated beam report request.

Figure 8 is a flowchart illustrating an example process performed, for example, at a network entity or an apparatus of a network entity that supports the use of a UE-initiated beam report request.

Figure 9 is a flowchart illustrating an example process performed, for example, at a UE or an apparatus of a UE that supports the transmission of additional information in a UE-initiated beam report request.

Figure 10 is a flowchart illustrating an example process performed, for example, at a network entity or an apparatus of a network entity that supports the reception of additional information in a UE-initiated beam report request.

Figure 11 is a diagram of an example apparatus for wireless communication that supports the use of a UE-initiated beam report request in accordance with the present disclosure.

Figure 12 is a diagram of an example apparatus for wireless communication that supports a UE-initiated beam report request in accordance with the present disclosure.

Figure 13 is a diagram of an example apparatus for wireless communication that supports the use of a UE-initiated beam report request in accordance with the present disclosure.

Figure 14 is a diagram of an example apparatus for wireless communication that supports a UE-initiated beam report request in accordance with the present disclosure.

DETAILED DESCRIPTION

Various aspects of the present disclosure are described hereinafter with reference to the accompanying drawings. However, aspects of the present disclosure may be embodied in many different forms and is not to be construed as limited to any specific aspect illustrated by or described with reference to an accompanying drawing or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art may appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using various combinations or quantities of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover an apparatus having, or a method that is practiced using, other structures and/or functionalities in addition to or other than the structures and/or functionalities with which various aspects of the disclosure set forth herein may be practiced. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.

Several aspects of telecommunication systems will now be presented with reference to various methods, operations, apparatuses, and techniques. These methods, operations, apparatuses, and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as “elements” ) . These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.

In a legacy channel state information (CSI) procedure, a user equipment (UE) may receive and measure a reference signal, such as a CSI reference signal (CSI-RS) , on a channel and then provide a beam report (CSI report) . A network entity may use the CSI for scheduling communications on the channel.

With a legacy CSI procedure, only upon receiving a CSI request from a network entity is a UE aware of an initiative to measure a CSI-RS and report CSI. This means the UE uses a CSI processing time between the CSI request and the beam report to process the measurement and generate the beam report. The CSI processing time in the legacy CSI procedure can add latency to the transmission of the beam report.

Various aspects relate generally to wireless communications between a UE and a network entity (for example, a gNB) . Some aspects more specifically relate to reporting CSI for a channel. In some aspects, a UE may initiate a beam report (for example, a CSI report) . The UE may perform a Layer 1 (L1) measurement and transmit a UE-initiated beam report request to the network entity. The UE may generate and store a beam report after sending the UE-initiated beam report request. When the UE receives the CSI request in downlink control information (DCI) from the network entity, the UE may provide the beam report sooner than in a legacy CSI procedure, since the beam report has already been processed.

Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by provide the beam report sooner, the described techniques can be used to reduce latency in CSI reporting as compared to a legacy CSI procedure that does not use a UE-initiated beam report request.

In some aspects, the UE may have a valid time duration to save a beam report after sending the corresponding UE-initiated beam report request. The valid time duration may help with the efficiency of beam reports. The valid time duration may start at the UE-initiated beam report request. Within the time duration, the beam report is valid, and the network entity may transmit the CSI request. The UE may not save the beam report outside of the valid time duration. In some aspects, outside of the valid time duration, the network entity may not transmit the CSI request to get the beam report. In some aspects, outside of the valid time duration, the network entity may transmit the CSI request to get the beam report, but the UE may treat the CSI request as a CSI request for a legacy CSI procedure. By using the valid time duration, the UE may not store and send a beam report (and the network entity may not request the beam report) if the time since the UE-initiated beam report request is too long to be accurate, is not significantly reducing the CSI processing time, or is going to result in the use of resources that are to be used for other operations. As a result, processing resources and signaling resources are conserved. The reduced CSI processing timeline may also be protected.

In some aspects, the UE may transmit various information in the UE-initiated beam report request. For example, the UE may include a cell identifier (ID) to identify the cell of the beam report. The UE may include a bandwidth part identifier (BWP ID) to identify a BWP associated with the beam report. The UE may include a beam report ID, such as for a beam report configuration (for example, CSI report configuration) . The information may be explicitly signaled or implicitly signaled. The information may assist the network entity with issuing the appropriate CSI request. This can help improve communications, which reduces latency and conserves processing resources and signaling resources.

Multiple-access radio access technologies (RATs) have been adopted in various telecommunication standards to provide common protocols that enable wireless communication devices to communicate on a municipal, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) . 5G NR supports various technologies and use cases including enhanced mobile broadband (eMBB) , ultra-reliable low-latency communication (URLLC) , massive machine-type communication (mMTC) , millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV) .

As the demand for broadband access increases and as technologies supported by wireless communication networks evolve, further technological improvements may be adopted in or implemented for 5G NR or future RATs, such as 6G, to further advance the evolution of wireless communication for a wide variety of existing and new use cases and applications. Such technological improvements may be associated with new frequency band expansion, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, disaggregated network architectures and network topology expansion, device aggregation, advanced duplex communication, sidelink and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced capability (RedCap) UE functionality, industrial connectivity, multiple-subscriber implementations, high-precision positioning, radio frequency (RF) sensing, and/or artificial intelligence or machine learning (AI/ML) , among other examples. These technological improvements may support use cases such as wireless backhauls, wireless data centers, extended reality (XR) and metaverse applications, meta services for supporting vehicle connectivity, holographic and mixed reality communication, autonomous and collaborative robots, vehicle platooning and cooperative maneuvering, sensing networks, gesture monitoring, human-brain interfacing, digital twin applications, asset management, and universal coverage applications using non-terrestrial and/or aerial platforms, among other examples. The methods, operations, apparatuses, and techniques described herein may enable one or more of the foregoing technologies and/or support one or more of the foregoing use cases.

Figure 1 is a diagram illustrating an example of a wireless communication network 100 in accordance with the present disclosure. The wireless communication network 100 may be or may include elements of a 5G (or NR) network or a 6G network, among other examples. The wireless communication network 100 may include multiple network nodes 110, shown as a network node (NN) 110a, a network node 110b, a network node 110c, and a network node 110d. The network nodes 110 may support communications with multiple UEs 120, shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e.

The network nodes 110 and the UEs 120 of the wireless communication network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, carriers, and/or channels. For example, devices of the wireless communication network 100 may communicate using one or more operating bands. In some aspects, multiple wireless networks 100 may be deployed in a given geographic area. Each wireless communication network 100 may support a particular radio access technology (RAT) (which may also be referred to as an air interface) and may operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include a 4G RAT, a 5G/NR RAT, and/or a 6G RAT, among other examples. In some examples, when multiple RATs are deployed in a given geographic area, each RAT in the geographic area may operate on different frequencies to avoid interference with one another.

Various operating bands have been defined as frequency range designations FR1 (410 MHz through 7.125 GHz) , FR2 (24.25 GHz through 52.6 GHz) , FR3 (7.125 GHz through 24.25 GHz) , FR4a or FR4-1 (52.6 GHz through 71 GHz) , FR4 (52.6 GHz through 114.25 GHz) , and FR5 (114.25 GHz through 300 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles, despite being different than the extremely high frequency (EHF) band (30 GHz through 300 GHz) , which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies, which include FR3. Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. Thus, “sub-6 GHz, ” if used herein, may broadly refer to frequencies that are less than 6 GHz, that are within FR1, and/or that are included in mid-band frequencies. Similarly, the term “millimeter wave, ” if used herein, may broadly refer to frequencies that are included in mid-band frequencies, that are within FR2, FR4, FR4-aor FR4-1, or FR5, and/or that are within the EHF band. Higher frequency bands may extend 5G NR operation, 6G operation, and/or other RATs beyond 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 may implement dynamic spectrum sharing (DSS) , in which multiple RATs (for example, 4G/LTE and 5G/NR) are implemented with dynamic bandwidth allocation (for example, based on user demand) in a single frequency band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR4-a, FR4-1, and/or FR5) may be modified, and techniques described herein may be applicable to those modified frequency ranges.

A network node 110 may include one or more devices, components, or systems that enable communication between a UE 120 and one or more devices, components, or systems of the wireless communication network 100. A network node 110 may be, may include, or may also be referred to as an NR network node, a 5G network node, a 6G network node, a Node B, an eNB, a gNB, an access point (AP) , a transmission reception point (TRP) , a mobility element, a core, a network entity, a network element, a network equipment, and/or another type of device, component, or system included in a radio access network (RAN) .

A network node 110 may be implemented as a single physical node (for example, a single physical structure) or may be implemented as two or more physical nodes (for example, two or more distinct physical structures) . For example, a network node 110 may be a device or system that implements part of a radio protocol stack, a device or system that implements a full radio protocol stack (such as a full gNB protocol stack) , or a collection of devices or systems that collectively implement the full radio protocol stack. For example, and as shown, a network node 110 may be an aggregated network node (having an aggregated architecture) , meaning that the network node 110 may implement a full radio protocol stack that is physically and logically integrated within a single node (for example, a single physical structure) in the wireless communication network 100. For example, an aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a full radio protocol stack to enable or facilitate communication between a UE 120 and a core network of the wireless communication network 100.

Alternatively, and as also shown, a network node 110 may be a disaggregated network node (sometimes referred to as a disaggregated base station) , meaning that the network node 110 may implement a radio protocol stack that is physically distributed and/or logically distributed among two or more nodes in the same geographic location or in different geographic locations. For example, a disaggregated network node may have a disaggregated architecture. In some deployments, disaggregated network nodes 110 may be used in an integrated access and backhaul (IAB) network, in an open radio access network (O-RAN) (such as a network configuration in compliance with the O-RAN Alliance) , or in a virtualized radio access network (vRAN) , also known as a cloud radio access network (C-RAN) , to facilitate scaling by separating base station functionality into multiple units that can be individually deployed.

The network nodes 110 of the wireless communication network 100 may include one or more central units (CUs) , one or more distributed units (DUs) , and/or one or more radio units (RUs) . A CU may host one or more higher layer control functions, such as radio resource control (RRC) functions, packet data convergence protocol (PDCP) functions, and/or service data adaptation protocol (SDAP) functions, among other examples. A DU may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and/or one or more higher physical (PHY) layers depending, at least in part, on a functional split, such as a functional split defined by the 3GPP. In some examples, a DU also may host one or more lower PHY layer functions, such as a fast Fourier transform (FFT) , an inverse FFT (iFFT) , beamforming, physical random access channel (PRACH) extraction and filtering, and/or scheduling of resources for one or more UEs 120, among other examples. An RU may host RF processing functions or lower PHY layer functions, such as an FFT, an iFFT, beamforming, or PRACH extraction and filtering, among other examples, according to a functional split, such as a lower layer functional split. In such an architecture, each RU can be operated to handle over the air (OTA) communication with one or more UEs 120.

In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and/or one or more RUs. Additionally or alternatively, a network node 110 may include one or more Near-Real Time (Near-RT) RAN Intelligent Controllers (RICs) and/or one or more Non-Real Time (Non-RT) RICs. In some examples, a CU, a DU, and/or an RU may be implemented as a virtual unit, such as a virtual central unit (VCU) , a virtual distributed unit (VDU) , or a virtual radio unit (VRU) , among other examples. A virtual unit may be implemented as a virtual network function, such as associated with a cloud deployment.

Some network nodes 110 (for example, a base station, an RU, or a TRP) may provide communication coverage for a particular geographic area. In the 3GPP, the term “cell” can refer to a coverage area of a network node 110 or to a network node 110 itself, depending on the context in which the term is used. A network node 110 may support one or multiple (for example, three) cells. In some examples, a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG) ) . A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node.

The wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, aggregated network nodes, and/or disaggregated network nodes, among other examples. In the example shown in Figure 1, the network node 110a may be a macro network node for a macro cell 130a, the network node 110b may be a pico network node for a pico cell 130b, and the network node 110c may be a femto network node for a femto cell 130c. Various different types of network nodes 110 may generally transmit at different power levels, serve different coverage areas, and/or have different impacts on interference in the wireless communication network 100 than other types of network nodes 110. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts) , whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts) .

In some examples, a network node 110 may be, may include, or may operate as an RU, a TRP, or a base station that communicates with one or more UEs 120 via a radio access link (which may be referred to as a “Uu” link) . The radio access link may include a downlink and an uplink. “Downlink” (or “DL” ) refers to a communication direction from a network node 110 to a UE 120, and “uplink” (or “UL” ) refers to a communication direction from a UE 120 to a network node 110. Downlink and uplink resources may include time domain resources (frames, subframes, slots, and/or symbols) , frequency domain resources (frequency bands, component carriers, subcarriers, resource blocks, and/or resource elements) , and/or spatial domain resources (particular transmit directions and/or beam parameters) . Frequency domain resources of some bands may be subdivided into bandwidth parts (BWPs) . A BWP may be a continuous block of frequency domain resources (for example, a continuous block of resource blocks) that are allocated for one or more UEs 120. A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and the downlink BWP may be the same BWP or different BWPs) . A BWP may be dynamically configured (for example, by a network node 110 transmitting a downlink control information (DCI) configuration to the one or more UEs 120) and/or reconfigured, which means that a BWP can be adjusted in real-time (or near-real-time) based on changing network conditions in the wireless communication network 100 and/or based on the specific requirements of the one or more UEs 120. This enables more efficient use of the available frequency domain resources in the wireless communication network 100 because fewer frequency domain resources may be allocated to a BWP for a UE 120 (which may reduce the quantity of frequency domain resources that a UE 120 is required to monitor) , leaving more frequency domain resources to be spread across multiple UEs 120. Thus, BWPs may also assist in the implementation of lower-capability UEs 120 by facilitating the configuration of smaller bandwidths for communication by such UEs 120.

In some examples, any network node 110 that relays communications may be referred to as a relay network node, a relay station, or simply as a relay. A relay may receive a transmission of a communication from an upstream station (for example, another network node 110 or a UE 120) and transmit the communication to a downstream station (for example, a UE 120 or another network node 110) . In this case, the wireless communication network 100 may include or be referred to as a “multi-hop network. ” In the example shown in Figure 1, the network node 110d (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. Additionally or alternatively, a UE 120 may be or may operate as a relay station that can relay transmissions to or from other UEs 120. A UE 120 that relays communications may be referred to as a UE relay or a relay UE, among other examples.

The UEs 120 may be physically dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. A UE 120 may be, may include, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. A UE 120 may be, include, or be coupled with a cellular phone (for example, a smart phone) , a personal digital assistant (PDA) , a wireless modem, a wireless communication device, a handheld device, a laptop computer, a cordless phone, a wireless local loop (WLL) station, a tablet, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (for example, a smart watch, smart clothing, smart glasses, a smart wristband, and/or smart jewelry, such as a smart ring or a smart bracelet) , an entertainment device (for example, a music device, a video device, and/or a satellite radio) , an extended reality (XR) device, a vehicular component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device) , a UE function of a network node, and/or any other suitable device or function that may communicate via a wireless medium.

A UE 120 and/or a network node 110 may include one or more chips, system-on-chips (SoCs) , chipsets, packages, or devices that individually or collectively constitute or comprise a processing system. The processing system includes processor (or “processing” ) circuitry in the form of one or multiple processors, microprocessors, processing units (such as central processing units (CPUs) , graphics processing units (GPUs) , neural processing units (NPUs) and/or digital signal processors (DSPs) ) , processing blocks, application-specific integrated circuits (ASIC) , programmable logic devices (PLDs) (such as field programmable gate arrays (FPGAs) ) , or other discrete gate or transistor logic or circuitry (all of which may be generally referred to herein individually as “processors” or collectively as “the processor” or “the processor circuitry” ) . One or more of the processors may be individually or collectively configurable or configured to perform various functions or operations described herein. A group of processors collectively configurable or configured to perform a set of functions may include a first processor configurable or configured to perform a first function of the set and a second processor configurable or configured to perform a second function of the set, or may include the group of processors all being configured or configurable to perform the set of functions. The processing system may further include memory circuitry in the form of one or more memory devices, memory blocks, memory elements or other discrete gate or transistor logic or circuitry, each of which may include tangible storage media such as random-access memory (RAM) or read-only memory (ROM) , or combinations thereof (all of which may be generally referred to herein individually as “memories” or collectively as “the memory” or “the memory circuitry” ) . One or more of the memories may be coupled (for example, operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) with one or more of the processors and may individually or collectively store processor-executable code (such as software) that, when executed by one or more of the processors, may configure one or more of the processors to perform various functions or operations described herein. Additionally or alternatively, in some examples, one or more of the processors may be preconfigured to perform various functions or operations described herein without requiring configuration by software. The processing system may further include or be coupled with one or more modems (such as a Wi-Fi (for example, IEEE compliant) modem or a cellular (for example, 3GPP 4G LTE, 5G, or 6G compliant) modem) . In some implementations, one or more processors of the processing system include or implement one or more of the modems. The processing system may further include or be coupled with multiple radios (collectively “the radio” ) , multiple RF chains, or multiple transceivers, each of which may in turn be coupled with one or more of multiple antennas. In some implementations, one or more processors of the processing system include or implement one or more of the radios, RF chains or transceivers. The UE 120 may include or may be included in a housing that houses components associated with the UE 120 including the processing system.

In some examples, two or more UEs 120 (for example, shown as UE 120a and UE 120e) may communicate directly with one another using sidelink communications (for example, without communicating by way of a network node 110 as an intermediary) . As an example, the UE 120a may directly transmit data, control information, or other signaling as a sidelink communication to the UE 120e. This is in contrast to, for example, the UE 120a first transmitting data in an UL communication to a network node 110, which then transmits the data to the UE 120e in a DL communication.

In some aspects, a UE (for example, UE 120) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may obtain L1 measurements. The communication manager 140 may transmit a UE-initiated beam report request. The communication manager 140 may generate, in association with the UE-initiated beam report request, a beam report using the L1 measurements. The communication manager 140 may receive a CSI request. The communication manager 140 may transmit the beam report in accordance with reception of the CSI request.

In some aspects, the communication manager 140 may obtain L1 measurements. The communication manager 140 may transmit a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, a network entity (for example, a network node 110) may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive a UE-initiated beam report request. The communication manager 150 may transmit, in association with the L1 measurements, a CSI request in accordance with reception of the UE-initiated beam report request. The communication manager 150 may receive the beam report.

In some aspects, the communication manager 150 may obtain L1 measurements. The communication manager 150 may receive, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID. Additionally or alternatively, the communication manager 150 may perform one or more other operations described herein.

Figure 2 is a diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network in accordance with the present disclosure.

As shown in Figure 2, the network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a through 232t, where t ≥ 1) , a set of antennas 234 (shown as 234a through 234v, where v ≥ 1) , a MIMO detector 236, a receive processor 238, a data sink 239, a controller/processor 240, a memory 242, a communication unit 244, a scheduler 246, and/or a communication manager 150, among other examples. In some configurations, one or a combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 214, and/or the TX MIMO processor 216 may be included in a transceiver of the network node 110. The transceiver may be under control of and used by one or more processors, such as the controller/processor 240, and in some aspects in conjunction with processor-readable code stored in the memory 242, to perform aspects of the methods, processes, and/or operations described herein. In some aspects, the network node 110 may include one or more interfaces, communication components, and/or other components that facilitate communication with the UE 120 or another network node.

The terms “processor, ” “controller, ” or “controller/processor” may refer to one or more controllers and/or one or more processors. For example, reference to “a/the processor” or “a/the controller/processor” (in the singular) should be understood to refer to any one or more of the processors described in connection with Figure 2, such as a single processor or a combination of multiple different processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Figure 2. For example, one or more processors of the network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and/or controller/processor 240. Similarly, one or more processors of the UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and/or controller/processor 280.

In some aspects, a single processor may perform all of the operations described as being performed by the one or more processors. In some aspects, a first set of (one or more) processors of the one or more processors may perform a first operation described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second operation described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Figure 2. For example, operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.

For downlink communication from the network node 110 to the UE 120, the transmit processor 214 may receive data ( “downlink data” ) intended for the UE 120 (or a set of UEs that includes the UE 120) from the data source 212 (such as a data pipeline or a data queue) . In some examples, the transmit processor 214 may select one or more MCSs for the UE 120 in accordance with one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process the data (for example, including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCS (s) selected for the UE 120 to generate data symbols. The transmit processor 214 may process system information (for example, semi-static resource partitioning information (SRPI) ) and/or control information (for example, CQI requests, grants, and/or upper layer signaling) and provide overhead symbols and/or control symbols. The transmit processor 214 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS) , a demodulation reference signal (DMRS) , or a CSI reference signal (CSI-RS) ) and/or synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signals (SSS) ) .

The TX MIMO processor 216 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, T output symbol streams) to the set of modems 232. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 232. Each modem 232 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for orthogonal frequency division multiplexing ( (OFDM) ) to obtain an output sample stream. Each modem 232 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain a time domain downlink signal. The modems 232a through 232t may together transmit a set of downlink signals (for example, T downlink signals) via the corresponding set of antennas 234.

For uplink communication from the UE 120 to the network node 110, uplink signals from the UE 120 may be received by an antenna 234, may be processed by a modem 232 (for example, a demodulator component, shown as DEMOD, of a modem 232) , may be detected by the MIMO detector 236 (for example, a receive (Rx) MIMO processor) if applicable, and/or may be further processed by the receive processor 238 to obtain decoded data and/or control information. The receive processor 238 may provide the decoded data to a data sink 239 (which may be a data pipeline, a data queue, and/or another type of data sink) and provide the decoded control information to a processor, such as the controller/processor 240.

The network node 110 may use the scheduler 246 to schedule one or more UEs 120 for downlink or uplink communications. In some aspects, the scheduler 246 may use DCI to dynamically schedule DL transmissions to the UE 120 and/or UL transmissions from the UE 120. In some examples, the scheduler 246 may allocate recurring time domain resources and/or frequency domain resources that the UE 120 may use to transmit and/or receive communications using an RRC configuration (for example, a semi-static configuration) , for example, to perform semi-persistent scheduling (SPS) or to configure a configured grant (CG) for the UE 120.

One or more of the transmit processor 214, the TX MIMO processor 216, the modem 232, the antenna 234, the MIMO detector 236, the receive processor 238, and/or the controller/processor 240 may be included in an RF chain of the network node 110. An RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs) , and/or other devices that convert between an analog signal (such as for transmission or reception via an air interface) and a digital signal (such as for processing by one or more processors of the network node 110) . In some aspects, the RF chain may be or may be included in a transceiver of the network node 110.

In some examples, the network node 110 may use the communication unit 244 to communicate with a core network and/or with other network nodes. The communication unit 244 may support wired and/or wireless communication protocols and/or connections, such as Ethernet, optical fiber, common public radio interface (CPRI) , and/or a wired or wireless backhaul, among other examples. The network node 110 may use the communication unit 244 to transmit and/or receive data associated with the UE 120 or to perform network control signaling, among other examples. The communication unit 244 may include a transceiver and/or an interface, such as a network interface.

The UE 120 may include a set of antennas 252 (shown as antennas 252a through 252r, where r ≥ 1) , a set of modems 254 (shown as modems 254a through 254u, where u ≥ 1) , a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller/processor 280, a memory 282, and/or a communication manager 140, among other examples. One or more of the components of the UE 120 may be included in a housing 284. In some aspects, one or a combination of the antenna (s) 252, the modem (s) 254, the MIMO detector 256, the receive processor 258, the transmit processor 264, or the TX MIMO processor 266 may be included in a transceiver that is included in the UE 120. The transceiver may be under control of and used by one or more processors, such as the controller/processor 280, and in some aspects in conjunction with processor-readable code stored in the memory 282, to perform aspects of the methods, processes, or operations described herein. In some aspects, the UE 120 may include another interface, another communication component, and/or another component that facilitates communication with the network node 110 and/or another UE 120.

For downlink communication from the network node 110 to the UE 120, the set of antennas 252 may receive the downlink communications or signals from the network node 110 and may provide a set of received downlink signals (for example, R received signals) to the set of modems 254. For example, each received signal may be provided to a respective demodulator component (shown as DEMOD) of a modem 254. Each modem 254 may use the respective demodulator component to condition (for example, filter, amplify, downconvert, and/or digitize) a received signal to obtain input samples. Each modem 254 may use the respective demodulator component to further demodulate or process the input samples (for example, for OFDM) to obtain received symbols. The MIMO detector 256 may obtain received symbols from the set of modems 254, may perform MIMO detection on the received symbols if applicable, and may provide detected symbols. The receive processor 258 may process (for example, decode) the detected symbols, may provide decoded data for the UE 120 to the data sink 260 (which may include a data pipeline, a data queue, and/or an application executed on the UE 120) , and may provide decoded control information and system information to the controller/processor 280.

For uplink communication from the UE 120 to the network node 110, the transmit processor 264 may receive and process data ( “uplink data” ) from a data source 262 (such as a data pipeline, a data queue, and/or an application executed on the UE 120) and control information from the controller/processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and/or other types of control information. In some aspects, the receive processor 258 and/or the controller/processor 280 may determine, for a received signal (such as received from the network node 110 or another UE) , one or more parameters relating to transmission of the uplink communication. The one or more parameters may include a reference signal received power (RSRP) parameter, a received signal strength indicator (RSSI) parameter, a reference signal received quality (RSRQ) parameter, a channel quality indicator (CQI) parameter, or a transmit power control (TPC) parameter, among other examples. The control information may include an indication of the RSRP parameter, the RSSI parameter, the RSRQ parameter, the CQI parameter, the TPC parameter, and/or another parameter. The control information may facilitate parameter selection and/or scheduling for the UE 120 by the network node 110.

The transmit processor 264 may generate reference symbols for one or more reference signals, such as an uplink DMRS, an uplink sounding reference signal (SRS) , and/or another type of reference signal. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the set of modems 254 (for example, for DFT-s-OFDM or CP-OFDM) . The TX MIMO processor 266 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and/or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, U output symbol streams) to the set of modems 254. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 254. Each modem 254 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 254 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and/or upconvert) the output sample stream to obtain an uplink signal.

The modems 254a through 254u may transmit a set of uplink signals (for example, R uplink signals or U uplink symbols) via the corresponding set of antennas 252. An uplink signal may include a uplink control information (UCI) communication, a MAC CE communication, an RRC communication, or another type of uplink communication. Uplink signals may be transmitted on a physical uplink shared channel (PUSCH) , a physical uplink control channel (PUCCH) , and/or another type of uplink channel. An uplink signal may carry one or more transport blocks (TBs) of data. Sidelink data and control transmissions (that is, transmissions directly between two or more UEs 120) may generally use similar techniques as were described for uplink data and control transmission, and may use sidelink-specific channels such as a physical sidelink shared channel (PSSCH) , a physical sidelink control channel (PSCCH) , and/or a physical sidelink feedback channel (PSFCH) .

One or more antennas of the set of antennas 252 or the set of antennas 234 may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled with one or more transmission or reception components, such as one or more components of Figure 2. As used herein, “antenna” can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. “Antenna panel” can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters of the group of antennas. “Antenna module” may refer to circuitry including one or more antennas, which may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device. In some examples, each of the antenna elements of an antenna 234 or an antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. The antenna elements may include patch antennas, dipole antennas, and/or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. A spacing between antenna elements may be such that signals with a desired wavelength transmitted separately by the antenna elements may interact or interfere constructively and destructively along various directions (such as to form a desired beam) . For example, given an expected range of wavelengths or frequencies, the spacing may provide a quarter wavelength, a half wavelength, or another fraction of a wavelength of spacing between neighboring antenna elements to allow for the desired constructive and destructive interference patterns of signals transmitted by the separate antenna elements within that expected range.

The amplitudes and/or phases of signals transmitted via antenna elements and/or sub-elements may be modulated and shifted relative to each other (such as by manipulating phase shift, phase offset, and/or amplitude) to generate one or more beams, which is referred to as beamforming. The term “beam” may refer to a directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. “Beam” may also generally refer to a direction associated with such a directional signal transmission, a set of directional resources associated with the signal transmission (for example, an angle of arrival, a horizontal direction, and/or a vertical direction) , and/or a set of parameters that indicate one or more aspects of a directional signal, a direction associated with the signal, and/or a set of directional resources associated with the signal.

The network entity (for example, network node 110) , the controller/processor 240 of the network node 110, the UE 120, the controller/processor 280 of the UE 120, a CU, a DU, an RU, or any other component (s) of Figures 1 or 2 may implement one or more techniques or perform one or more operations associated with using a UE-initiated beam report request, as described in more detail elsewhere herein. For example, the controller/processor 240 of the network node 110, the controller/processor 280 of the UE 120, any other component (s) of Figure 2, the CU, the DU, or the RU may perform or direct operations of, for example, process 700 of Figure 7, process 800 of Figure 8, process 900 of Figure 9, process 1000 of Figure 10, or other processes as described herein (alone or in conjunction with one or more other processors) . The memory 242 may store data and program codes for the network node 110, the network node 110, the CU, the DU, or the RU. The memory 282 may store data and program codes for the UE 120. In some examples, the memory 242 or the memory 282 may include a non-transitory computer-readable medium storing a set of instructions (for example, code or program code) for wireless communication. The memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types) . The memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same type or of different types) . For example, the set of instructions, when executed (for example, directly, or after compiling, converting, or interpreting) by one or more processors of the network node 110, the UE 120, the CU, the DU, or the RU, may cause the one or more processors to perform process 700 of Figure 7, process 800 of Figure 8, process 900 of Figure 9, process 1000 of Figure 10, or other processes as described herein. In some examples, executing instructions may include running the instructions, converting the instructions, compiling the instructions, and/or interpreting the instructions, among other examples.

In some aspects, a UE (for example, a UE 120) includes means for obtaining L1 measurements; means for transmitting a UE-initiated beam report request; means for generating, in association with the UE-initiated beam report request, a beam report using the L1 measurements; means for receiving a CSI request; and/or means for transmitting the beam report in accordance with reception of the CSI request.

In some aspects, the UE includes means for obtaining L1 measurements; and/or means for transmitting, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID. The means for the UE to perform operations described herein may include, for example, one or more of communication manager 140, antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, controller/processor 280, or memory 282.

In some aspects, a network entity (for example, a network node 110) includes means for receiving a UE-initiated beam report request; means for transmitting a CSI request in accordance with reception of the UE-initiated beam report request; and/or means for receiving the beam report.

In some aspects, the network entity includes means for obtaining L1 measurements; and/or means for receiving, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID. In some aspects, the means for the network entity to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 220, TX MIMO processor 230, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

Figure 3 is a diagram illustrating examples 300, 310, and 320 of CSI-RS beam management procedures, in accordance with the present disclosure. As shown in Figure 3, examples 300, 310, and 320 include a UE 120 in communication with a network entity (for example, network node 110) in a wireless network (for example, wireless communication network 100) . However, the devices shown in Figure 3 are provided as examples, and the wireless network may support communication and beam management between other devices (for example, between a UE 120 and a network node 110 or transmit receive point (TRP) , between a mobile termination node and a control node, between an integrated access and backhaul (IAB) child node and an IAB parent node, and/or between a scheduled node and a scheduling node) . In some aspects, the UE 120 and the network node 110 may be in a connected state (for example, an RRC connected state) .

As shown in Figure 3, example 300 may include a network node 110 (for example, one or more network node devices such as an RU, a DU, and/or a CU, among other examples) and a UE 120 communicating to perform beam management using CSI-RSs. Example 300 depicts a first beam management procedure (for example, P1 CSI-RS beam management) . The first beam management procedure may be referred to as a beam selection procedure, an initial beam acquisition procedure, a beam sweeping procedure, a cell search procedure, and/or a beam search procedure. As shown in Figure 3 and example 300, CSI-RSs may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs may be configured to be periodic (for example, using RRC signaling) , semi-persistent (for example, using media access control (MAC) control element (MAC CE) signaling) , and/or aperiodic (for example, using DCI) .

The first beam management procedure may include the network node 110 performing beam sweeping over multiple transmit (Tx) beams. The network node 110 may transmit a CSI-RS using each transmit beam for beam management. To enable the UE 120 to perform receive (Rx) beam sweeping, the network node may use a transmit beam to transmit (for example, with repetitions) each CSI-RS at multiple times within the same reference signal (RS) resource set so that the UE 120 can sweep through receive beams in multiple transmission instances. For example, if the network node 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the CSI-RS may be transmitted on each of the N transmit beams M times so that the UE 120 may receive M instances of the CSI-RS per transmit beam. In other words, for each transmit beam of the network node 110, the UE 120 may perform beam sweeping through the receive beams of the UE 120. As a result, the first beam management procedure may enable the UE 120 to measure a CSI-RS on different transmit beams using different receive beams to support selection of network node 110 transmit beams/UE 120 receive beam (s) beam pair (s) . The UE 120 may report the measurements to the network node 110 to enable the network node 110 to select one or more beam pair (s) for communication between the network node 110 and the UE 120. While example 300 has been described in connection with CSI-RSs, the first beam management process may also use synchronization signal blocks (SSBs) for beam management in a similar manner as described above.

As shown in Figure 3, example 310 may include a network node 110 and a UE 120 communicating to perform beam management using CSI-RSs. Example 310 depicts a second beam management procedure (for example, P2 CSI-RS beam management) . The second beam management procedure may be referred to as a beam refinement procedure, a network node beam refinement procedure, a TRP beam refinement procedure, and/or a transmit beam refinement procedure. As shown in Figure 3 and example 310, CSI-RSs may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs may be configured to be aperiodic (for example, using DCI) . The second beam management procedure may include the network node 110 performing beam sweeping over one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with the network node 110 (for example, determined based at least in part on measurements reported by the UE 120 in connection with the first beam management procedure) . The network node 110 may transmit a CSI-RS using each transmit beam of the one or more transmit beams for beam management. The UE 120 may measure each CSI-RS using a single (for example, a same) receive beam (for example, determined based at least in part on measurements performed in connection with the first beam management procedure) . The second beam management procedure may enable the network node 110 to select a best transmit beam based at least in part on measurements of the CSI-RSs (for example, measured by the UE 120 using the single receive beam) reported by the UE 120.

As shown in Figure 3, example 320 depicts a third beam management procedure (for example, P3 CSI-RS beam management) . The third beam management procedure may be referred to as a beam refinement procedure, a UE beam refinement procedure, and/or a receive beam refinement procedure. As shown in Figure 3 and example 320, one or more CSI-RSs may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs may be configured to be aperiodic (for example, using DCI) . The third beam management process may include the network node 110 transmitting the one or more CSI-RSs using a single transmit beam (for example, determined based at least in part on measurements reported by the UE 120 in connection with the first beam management procedure and/or the second beam management procedure) . To enable the UE 120 to perform receive beam sweeping, the network node may use a transmit beam to transmit (for example, with repetitions) CSI-RS at multiple times within the same RS resource set so that UE 120 can sweep through one or more receive beams in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with the UE 120 (for example, determined based at least in part on measurements performed in connection with the first beam management procedure and/or the second beam management procedure) . The third beam management procedure may enable the network node 110 and/or the UE 120 to select a best receive beam based at least in part on reported measurements received from the UE 120 (for example, of the CSI-RS of the transmit beam using the one or more receive beams) .

The UE 120 may transmit the beam reports in UCI. The network initiates the beam reports. Future beam reports may be initiated by the UE 120. However, if UE-initiated beam reports are transmitted as legacy UCI, the beam reports may consume more resources for UCI than what would be expected.

As indicated above, Figure 3 is provided as an example of beam management procedures. Other examples of beam management procedures may differ from what is described with respect to Figure 3. For example, the UE 120 and the network node 110 may perform the third beam management procedure before performing the second beam management procedure, and/or the UE 120 and the network node 110 may perform a similar beam management procedure to select a UE transmit beam.

Figure 4 is a diagram illustrating an example 400 of a timeline for a legacy CSI procedure, in accordance with the present disclosure.

In a legacy CSI procedure, a UE may measure a reference signal (for example, a CSI-RS) and provide a beam report only after receiving a CSI request in DCI from a network entity (for example, a gNB) . For example, a network entity may transmit a CSI request field in DCI that triggers a beam report or multiple beam reports to be transmitted on a PUSCH. The UE may later provide a valid beam report for the n-th triggered report.

Example 400 shows a timeline for the legacy CSI procedure. After transmitting DCI 402 with a CSI request, the network entity 410 may transmit a CSI-RS. The UE 420 may perform an L1 measurement 404 of the CSI-RS. The UE 420 may expect to have time to perform the L1 measurement 404 and compute CSI for the beam report 406 (for example, CSI report, L1 report on PUSCH) . The first uplink symbol to carry the corresponding beam report 406 (including an effect of a timing advance) starts no earlier than at symbol Z_ref. The first uplink symbol to carry the n-th beam report (including the effect of the timing advance) starts no earlier than at symbol Z'_ref (n) . The CSI processing time may be represented as T'_proc, _CSI = Z' (2048 + 144) ·K2^-μ ·T_c. Z' and Z may be the numbers of symbols for a CSI computation delay requirement. 144 may be a symbol duration, including a cyclic prefix. K2 may be the offset between the downlink slot where the PDCCH (DCI) for uplink scheduling is received and the uplink slot where the uplink data is to be sent on the PUSCH, and μ may be an index for a table used for determining the number of symbols for the CSI computation delay requirement. The coherence time T_c may be the time domain dual of Doppler spread and may be used to characterize the time varying nature of the frequency. The processing time between reception of the DCI and the transmission of the CSI report on the PUSCH may be represented as T_proc, _CSI = Z (2048 + 144) ·K2^-μ ·T_c + T_switch, where T_switch may be equal to the switching gap duration.

The UE 420 in the timeline for the legacy CSI procedure is aware of an initiative to measure the CSI-RS and report CSI only upon receiving the DCI 402 with the CSI request. This means the UE 420 uses a CSI processing time between the CSI request and the beam report 406. The CSI processing time in this legacy CSI procedure can add latency to the transmission of the beam report 406.

Figure 5 is a diagram illustrating an example 500 of a timeline for a UE-initiated beam report, in accordance with the present disclosure.

According to various aspects described herein, a UE may initiate a beam report (for example, CSI report, L1 report on PUSCH) . The UE may perform an L1 measurement and transmit a UE-initiated beam report request to a network entity. The UE may generate and store a beam report after sending the UE-initiated beam report request. When the UE receives the CSI request in DCI from the network entity, the UE may provide the beam report sooner than in a legacy CSI procedure, as the beam report has already been processed. This results in a reduced CSI processing timeline (Z_ref, _new) between the CSI request and the beam report, as compared to the timeline of the legacy CSI procedure that does not use the UE-initiated beam report request.

Example 500 shows that a UE 520 (for example, a UE 120) may obtain an L1 measurement 502 of a reference signal (for example, CSI-RS) from a network entity 510 (for example, network node 110) . The UE 520 may transmit a UE-initiated beam report request 504. The UE 520 may generate and store a beam report 508 for the L1 measurement 502 before receiving a CSI request. The network entity 510 may transmit DCI 506 with the CSI request. The UE 520 may transmit the stored beam report 508. Because the UE 520 had generated and stored the beam report 508 in association with the UE-initiated beam report request 504, the UE 520 may provide the beam report 508 with a reduced CSI processing time as compared to the legacy CSI procedure shown by example 530. As a result, latency in reporting CSI is reduced.

In some aspects, the UE 520 may have a valid time duration 512 to save a beam report after sending the corresponding UE-initiated beam report request. The valid time duration 512 may help with the efficiency of beam reports. The valid time duration 512 may start at the UE-initiated beam report request 504. The length of the valid time duration 512 may be configured and/or may be subject to a UE capability for processing and storing beam reports. Within the time duration, the beam report is valid, and the network entity 510 may transmit the DCI 506 with the CSI request. The UE 520 may not save the beam report outside of the valid time duration 512. In some aspects, outside of the valid time duration 512, the network entity 510 may not transmit the CSI request to get the beam report. In some aspects, outside of the valid time duration 512, the network entity 510 may transmit the CSI request to get the beam report, but the UE 520 may treat the CSI request as a CSI request for a legacy CSI procedure. By using the valid time duration 512, the UE 520 may not store and send a beam report (and the network entity 510 may not request the beam report) if the time since the UE-initiated beam report request 504 is too long for the report to be accurate, is not significantly reducing the CSI processing time, or is going to result in the use of resources that are to be used for other operations. As a result, processing resources and signaling resources are conserved. The reduced CSI processing timeline may also be protected.

In some aspects, the UE 520 may transmit various information in the UE-initiated beam report request 504. For example, the UE 520 may include a cell ID to identify the cell of the beam report 508. The UE 520 may include a BWP ID to identify the BWP associated with the beam report 508. The UE 520 may include a beam report ID, such as for a beam report configuration (for example, a CSI report configuration) . The UE 520 may transmit such information using a bitmap-based ID mapping or an explicit ID. The information may assist the network entity with issuing the appropriate CSI request. This can help improve communications, which reduces latency and conserves processing resources and signaling resources.

In some aspects, the information may be implicitly signaled. Different IDs may be mapped to different request resources or occasions. For example, a resource or occasion may be associated with a particular cell ID, BWP ID, and/or beam report ID, and the use of the resource or occasion may indicate the ID. When the UE-initiated beam report request 504 is specific only to a local cell, a local BWP, and/or a predetermined beam report, the corresponding ID may be ignored.

Figure 6 is a diagram illustrating an example 600 of a call flow involving a UE-initiated beam report request.

In a first operation 605, the network entity 510 may transmit a reference signal, such as a CSI-RS (or multiple CSI-RSs) . In a second operation 610, the UE 520 may obtain one or more measurements of the CSI-RS, such as L1 measurements (for example, L1-RSRP, L1-RSRQ, L1 signal-to-interference-plus-noise ratio (SINR) ) . In a third operation 615, the UE 520 may transmit a UE-initiated beam report request. The UE 520 may transmit the request based at least in part on a CSI report configuration and/or one or more traffic conditions (for example, an amount of data to be transmitted above a threshold) and/or channel conditions (for example, an error rate above a threshold, a signal strength below a threshold) . The request may include a cell ID, a BWP ID, and/or a beam report ID. In some aspects, the request may be in association with the L1 measurements. That is, the request may be a result of the L1 measurements or a result of obtaining the L1 measurements.

In a fourth operation 620, the UE 520 may generate a beam report using the measurements. The UE 520 may generate the beam report in association with the UE-initiated beam report request. That is, the beam report may correspond to the request or may be because of the request. The beam report may be a CSI report or an L1 report on the PUSCH. The UE 520 may generate the beam report using the CSI report configuration.

In a fifth operation 625, the network entity 510 may transmit DCI with a CSI request. In a sixth operation 630, the UE 520 may transmit the beam report that was initiated by the UE 520. As a result, the time between the CSI request and the beam report may be shorter than during a legacy CSI procedure.

In some aspects, the UE 520 may transmit the beam report within a valid time duration 612. The network entity 510 may transmit a configuration for the valid time duration 612. The network entity 510 may transmit the CSI request within the valid time duration 612 and not outside the valid time duration 612. If the network entity 510 is to transmit the CSI request outside of the valid time duration 612, the UE 520 may follow the legacy CSI procedure.

Figure 7 is a flowchart illustrating an example process 700 performed, for example, at a UE or an apparatus of a UE that supports the use of a UE-initiated beam report request in accordance with the present disclosure. Example process 700 is an example where the apparatus or the UE (for example, UE 120, UE 520) performs operations associated with UE-initiated beam report requests.

As shown in Figure 7, in some aspects, process 700 may include obtaining L1 measurements (block 710) . For example, the UE (such as by using communication manager 140 or reception component 1102, depicted in Figure 11) may obtain L1 measurements, as described above.

As further shown in Figure 7, in some aspects, process 700 may include transmitting a UE-initiated beam report request (block 720) . For example, the UE (such as by using communication manager 140, request component 1108, or transmission component 1104, depicted in Figure 11) may transmit a UE-initiated beam report request, as described above.

As further shown in Figure 7, in some aspects, process 700 may include generating, in association with the UE-initiated beam report request, a beam report using the L1 measurements (block 730) . For example, the UE (such as by using communication manager 140 or report component 1110, depicted in Figure 11) may generate, in association with the UE-initiated beam report request, a beam report using the L1 measurements, as described above.

As further shown in Figure 7, in some aspects, process 700 may include receiving a CSI request (block 740) . For example, the UE (such as by using communication manager 140 or reception component 1102, depicted in Figure 11) may receive a CSI request, as described above.

As further shown in Figure 7, in some aspects, process 700 may include transmitting the beam report in accordance with reception of the CSI request (block 750) . For example, the UE (such as by using communication manager 140 or transmission component 1104 and/or report component 1110, depicted in Figure 11) may transmit the beam report in accordance with reception of the CSI request, as described above.

Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

In a first additional aspect, process 700 includes receiving an indication of a valid time duration for which the beam report is valid after transmission of the UE-initiated beam report request.

In a second additional aspect, alone or in combination with the first aspect, generating the beam report includes generating the beam report within the valid time duration after the transmission of the UE-initiated beam report request.

In a third additional aspect, alone or in combination with one or more of the first and second aspects, the UE-initiated beam report request includes a cell ID.

In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the UE-initiated beam report request includes a BWP ID.

In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the UE-initiated beam report request includes a beam report ID.

Although Figure 7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.

Figure 8 is a flowchart illustrating an example process 800 performed, for example, at a network entity or an apparatus of a network entity that supports a UE-initiated beam report request in accordance with the present disclosure. Example process 800 is an example where the apparatus or the network entity (for example, network node 110, network entity 510) performs operations associated with a UE-initiated beam report request.

As shown in Figure 8, in some aspects, process 800 may include receiving a UE-initiated beam report request (block 810) . For example, the network entity (such as by using communication manager 150, request component 1208, and/or reception component 1202, depicted in Figure 12) may receive a UE-initiated beam report request, as described above.

As further shown in Figure 8, in some aspects, process 800 may include transmitting a CSI request in accordance with reception of the UE-initiated beam report request (block 820) . For example, the network entity (such as by using communication manager 150, report component 1210, and/or transmission component 1204, depicted in Figure 12) may transmit a CSI request in accordance with reception of the UE-initiated beam report request, as described above.

As further shown in Figure 8, in some aspects, process 800 may include receiving the beam report (block 830) . For example, the network entity (such as by using communication manager 150, report component 1210, and/or reception component 1202, depicted in Figure 12) may receive the beam report, as described above.

Process 800 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

In a first additional aspect, process 800 includes transmitting an indication of a valid time duration for which the beam report is valid after transmission of the UE-initiated beam report request.

In a second additional aspect, alone or in combination with the first aspect, transmitting the CSI request includes transmitting the CSI request during the valid time duration and not outside of the valid time duration.

In a third additional aspect, alone or in combination with one or more of the first and second aspects, transmitting the CSI request includes transmitting the CSI request independent of the valid time duration.

In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the UE-initiated beam report request includes a cell ID.

In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the UE-initiated beam report request includes a BWP ID.

In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the UE-initiated beam report request includes a beam report ID.

Although Figure 8 shows example blocks of process 800, in some aspects, process 800 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 8. Additionally or alternatively, two or more of the blocks of process 800 may be performed in parallel.

Figure 9 is a flowchart illustrating an example process 900 performed, for example, at a UE or an apparatus of a UE that supports the transmission of additional information in a UE-initiated beam report request in accordance with the present disclosure. Example process 900 is an example where the apparatus or the UE (for example, UE 120, UE 520) performs operations associated with the transmission of additional information in a UE-initiated beam report request.

As shown in Figure 9, in some aspects, process 900 may include obtaining L1 measurements (block 910) . For example, the UE (such as by using communication manager 140 or request component 1308, depicted in Figure 13) may obtain L1 measurements, as described above.

As further shown in Figure 9, in some aspects, process 900 may include transmitting, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID (block 920) . For example, the UE (such as by using communication manager 140, request component 1308, and/or transmission component 1304, depicted in Figure 13) may transmit, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID, as described above.

Process 900 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

In a first additional aspect, the UE-initiated beam report request includes the cell ID.

In a second additional aspect, alone or in combination with the first aspect, the UE-initiated beam report request indicates a request resource associated with the cell ID.

In a third additional aspect, alone or in combination with one or more of the first and second aspects, the UE-initiated beam report request includes the BWP ID.

In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the UE-initiated beam report request indicates a request resource associated with the BWP ID.

In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the UE-initiated beam report request includes a beam report configuration.

In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, the UE-initiated beam report indicates the one or more of the cell ID or the BWP ID via a bitmap.

Although Figure 9 shows example blocks of process 900, in some aspects, process 900 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 9. Additionally or alternatively, two or more of the blocks of process 900 may be performed in parallel.

Figure 10 is a flowchart illustrating an example process 1000 performed, for example, at a network entity or an apparatus of a network entity that supports the reception of additional information in a beam report in accordance with the present disclosure. Example process 1000 is an example where the apparatus or the network entity (for example, network node 110, network entity 510) performs operations associated with the reception of additional information in a beam report.

As shown in Figure 10, in some aspects, process 1000 may include obtaining L1 measurements (block 1010) . For example, the network entity (such as by using communication manager 150, request component 1408, and/or reception component 1402, depicted in Figure 14) may obtain L1 measurements, as described above.

As further shown in Figure 10, in some aspects, process 1000 may include receiving, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID (block 1020) . For example, the network entity (such as by using communication manager 150 or reception component 1402, depicted in Figure 14) may receive, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID, as described above.

Process 1000 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.

Although Figure 10 shows example blocks of process 1000, in some aspects, process 1000 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 10. Additionally or alternatively, two or more of the blocks of process 1000 may be performed in parallel.

Figure 11 is a diagram of an example apparatus 1100 for wireless communication that supports the use of a UE-initiated beam report request in accordance with the present disclosure. The apparatus 1100 may be a UE, or a UE may include the apparatus 1100. In some aspects, the apparatus 1100 includes a reception component 1102, a transmission component 1104, and a communication manager 140, which may be in communication with one another (for example, via one or more buses) . As shown, the apparatus 1100 may communicate with another apparatus 1106 (such as a UE, a network node, or another wireless communication device) using the reception component 1102 and the transmission component 1104.

In some aspects, the apparatus 1100 may be configured to and/or operable to perform one or more operations described herein in connection with Figures 1-6. Additionally or alternatively, the apparatus 1100 may be configured to and/or operable to perform one or more processes described herein, such as process 700 of Figure 7. In some aspects, the apparatus 1100 may include one or more components of the UE described above in connection with Figure 2.

The reception component 1102 may receive communications, such as reference signals, control information, and/or data communications, from the apparatus 1106. The reception component 1102 may provide received communications to one or more other components of the apparatus 1100, such as the communication manager 140. In some aspects, the reception component 1102 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components. In some aspects, the reception component 1102 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, and/or one or more memories of the UE described above in connection with Figure 2.

The transmission component 1104 may transmit communications, such as reference signals, control information, and/or data communications, to the apparatus 1106. In some aspects, the communication manager 140 may generate communications and may transmit the generated communications to the transmission component 1104 for transmission to the apparatus 1106. In some aspects, the transmission component 1104 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1106. In some aspects, the transmission component 1104 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, and/or one or more memories of the UE described above in connection with Figure 2. In some aspects, the transmission component 1104 may be co-located with the reception component 1102 in one or more transceivers.

The communication manager 140 may obtain L1 measurements. The communication manager 140 may transmit or may cause the transmission component 1104 to transmit a UE-initiated beam report request. The communication manager 140 may generate, in association with the UE-initiated beam report request, a beam report using the L1 measurements. The communication manager 140 may receive or may cause the reception component 1102 to receive a CSI request. The communication manager 140 may transmit or may cause the transmission component 1104 to transmit the beam report in accordance with reception of the CSI request. In some aspects, the communication manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 140.

The communication manager 140 may include one or more controllers/processors and one or more memories of the UE described above in connection with Figure 2. In some aspects, the communication manager 140 includes a set of components, such as a request component 1108, and/or a report component 1110. Alternatively, the set of components may be separate and distinct from the communication manager 140. In some aspects, one or more components of the set of components may include or may be implemented within one or more controllers/processors and one or more memories of the UE described above in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The number and arrangement of components shown in Figure 11 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Figure 11. Furthermore, two or more components shown in Figure 11 may be implemented within a single component, or a single component shown in Figure 11 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 11 may perform one or more functions described as being performed by another set of components shown in Figure 11.

Figure 12 is a diagram of an example apparatus 1200 for wireless communication that supports a UE-initiated beam report request in accordance with the present disclosure. The apparatus 1200 may be a network entity, or a network entity may include the apparatus 1200. In some aspects, the apparatus 1200 includes a reception component 1202, a transmission component 1204, and a communication manager 150, which may be in communication with one another (for example, via one or more buses) . As shown, the apparatus 1200 may communicate with another apparatus 1206 (such as a UE, a network node, or another wireless communication device) using the reception component 1202 and the transmission component 1204.

In some aspects, the apparatus 1200 may be configured to and/or operable to perform one or more operations described herein in connection with Figures 1-6. Additionally or alternatively, the apparatus 1200 may be configured to and/or operable to perform one or more processes described herein, such as process 800 of Figure 8. In some aspects, the apparatus 1200 may include one or more components of the network entity described above in connection with Figure 2.

The reception component 1202 may receive communications, such as reference signals, control information, and/or data communications, from the apparatus 1206. The reception component 1202 may provide received communications to one or more other components of the apparatus 1200, such as the communication manager 150. In some aspects, the reception component 1202 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components. In some aspects, the reception component 1202 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, and/or one or more memories of the network entity described above in connection with Figure 2.

The transmission component 1204 may transmit communications, such as reference signals, control information, and/or data communications, to the apparatus 1206. In some aspects, the communication manager 150 may generate communications and may transmit the generated communications to the transmission component 1204 for transmission to the apparatus 1206. In some aspects, the transmission component 1204 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1206. In some aspects, the transmission component 1204 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, and/or one or more memories of the network entity described above in connection with Figure 2. In some aspects, the transmission component 1204 may be co-located with the reception component 1202 in one or more transceivers.

The communication manager 150 may receive or may cause the reception component 1202 to receive a UE-initiated beam report request. The communication manager 150 may transmit or may cause the transmission component 1204 to transmit a CSI request in accordance with reception of the UE-initiated beam report request. The communication manager 150 may receive or may cause the reception component 1202 to receive the beam report. In some aspects, the communication manager 150 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 150.

The communication manager 150 may include one or more controllers/processors, one or more memories, one or more schedulers, and/or one or more communication units of the network entity described above in connection with Figure 2. In some aspects, the communication manager 150 includes a set of components, such as a request component 1208, and/or a report component 1210. Alternatively, the set of components may be separate and distinct from the communication manager 150. In some aspects, one or more components of the set of components may include or may be implemented within one or more controllers/processors, one or more memories, one or more schedulers, and/or one or more communication units of the network entity described above in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The reception component 1202 may receive a UE-initiated beam report request. The transmission component 1204 may transmit a CSI request in accordance with reception of the UE-initiated beam report request. The reception component 1202 may receive the beam report.

The transmission component 1204 may transmit an indication of a valid time duration for which the beam report is valid after transmission of the UE-initiated beam report request.

The number and arrangement of components shown in Figure 12 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Figure 12. Furthermore, two or more components shown in Figure 12 may be implemented within a single component, or a single component shown in Figure 12 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 12 may perform one or more functions described as being performed by another set of components shown in Figure 12.

Figure 13 is a diagram of an example apparatus 1300 for wireless communication that supports the use of a UE-initiated beam report request in accordance with the present disclosure. The apparatus 1300 may be a UE, or a UE may include the apparatus 1300. In some aspects, the apparatus 1300 includes a reception component 1302, a transmission component 1304, and a communication manager 140, which may be in communication with one another (for example, via one or more buses) . As shown, the apparatus 1300 may communicate with another apparatus 1306 (such as a UE, a network node, or another wireless communication device) using the reception component 1302 and the transmission component 1304.

In some aspects, the apparatus 1300 may be configured to and/or operable to perform one or more operations described herein in connection with Figures 1-6. Additionally or alternatively, the apparatus 1300 may be configured to and/or operable to perform one or more processes described herein, such as process 900 of Figure 9. In some aspects, the apparatus 1300 may include one or more components of the UE described above in connection with Figure 2.

The reception component 1302 may receive communications, such as reference signals, control information, and/or data communications, from the apparatus 1306. The reception component 1302 may provide received communications to one or more other components of the apparatus 1300, such as the communication manager 140. In some aspects, the reception component 1302 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components. In some aspects, the reception component 1302 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, and/or one or more memories of the UE described above in connection with Figure 2.

The transmission component 1304 may transmit communications, such as reference signals, control information, and/or data communications, to the apparatus 1306. In some aspects, the communication manager 140 may generate communications and may transmit the generated communications to the transmission component 1304 for transmission to the apparatus 1306. In some aspects, the transmission component 1304 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1306. In some aspects, the transmission component 1304 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, and/or one or more memories of the UE described above in connection with Figure 2. In some aspects, the transmission component 1304 may be co-located with the reception component 1302 in one or more transceivers.

The communication manager 140 may obtain L1 measurements. The communication manager 140 may, in association with the L1 measurements, transmit or may cause the transmission component 1304 to transmit a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID. In some aspects, the communication manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 140.

The communication manager 140 may include one or more controllers/processors and one or more memories of the UE described above in connection with Figure 2. In some aspects, the communication manager 140 includes a set of components, such as a request component 1308. Alternatively, the set of components may be separate and distinct from the communication manager 140. In some aspects, one or more components of the set of components may include or may be implemented within one or more controllers/processors and one or more memories of the UE described above in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The request component 1308 may obtain L1 measurements. The request component 1308 and the transmission component 1304 may transmit a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID.

The number and arrangement of components shown in Figure 13 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Figure 13. Furthermore, two or more components shown in Figure 13 may be implemented within a single component, or a single component shown in Figure 13 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 13 may perform one or more functions described as being performed by another set of components shown in Figure 13.

Figure 14 is a diagram of an example apparatus 1400 for wireless communication that supports a UE-initiated beam report request in accordance with the present disclosure. The apparatus 1400 may be a network entity, or a network entity may include the apparatus 1400. In some aspects, the apparatus 1400 includes a reception component 1402, a transmission component 1404, and a communication manager 150, which may be in communication with one another (for example, via one or more buses) . As shown, the apparatus 1400 may communicate with another apparatus 1406 (such as a UE, a network node, or another wireless communication device) using the reception component 1402 and the transmission component 1404.

In some aspects, the apparatus 1400 may be configured to and/or operable to perform one or more operations described herein in connection with Figures 1-6. Additionally or alternatively, the apparatus 1400 may be configured to and/or operable to perform one or more processes described herein, such as process 1000 of Figure 10. In some aspects, the apparatus 1400 may include one or more components of the network entity described above in connection with Figure 2.

The reception component 1402 may receive communications, such as reference signals, control information, and/or data communications, from the apparatus 1406. The reception component 1402 may provide received communications to one or more other components of the apparatus 1400, such as the communication manager 150. In some aspects, the reception component 1402 may perform signal processing on the received communications (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, de-mapping, equalization, interference cancellation, or decoding, among other examples) , and may provide the processed signals to the one or more other components. In some aspects, the reception component 1402 may include one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receive processors, one or more controllers/processors, and/or one or more memories of the network entity described above in connection with Figure 2.

The transmission component 1404 may transmit communications, such as reference signals, control information, and/or data communications, to the apparatus 1406. In some aspects, the communication manager 150 may generate communications and may transmit the generated communications to the transmission component 1404 for transmission to the apparatus 1406. In some aspects, the transmission component 1404 may perform signal processing on the generated communications (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, among other examples) , and may transmit the processed signals to the apparatus 1406. In some aspects, the transmission component 1404 may include one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers/processors, and/or one or more memories of the network entity described above in connection with Figure 2. In some aspects, the transmission component 1404 may be co-located with the reception component 1402 in one or more transceivers.

The communication manager 150 may obtain L1 measurements. The communication manager 150 may, in association with the L1 measurements, receive or may cause the reception component 1402 to receive a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID. In some aspects, the communication manager 150 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 150.

The communication manager 150 may include one or more controllers/processors, one or more memories, one or more schedulers, and/or one or more communication units of the network entity described above in connection with Figure 2. In some aspects, the communication manager 150 includes a set of components, such as a request component 1408. Alternatively, the set of components may be separate and distinct from the communication manager 150. In some aspects, one or more components of the set of components may include or may be implemented within one or more controllers/processors, one or more memories, one or more schedulers, and/or one or more communication units of the network entity described above in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.

The request component 1408 may obtain L1 measurements. The request component 1408 and the reception component 1402 may receive a UE-initiated beam report request that indicates one or more of a cell ID or a BWP ID.

The number and arrangement of components shown in Figure 14 are provided as an example. In practice, there may be additional components, fewer components, different components, or differently arranged components than those shown in Figure 14. Furthermore, two or more components shown in Figure 14 may be implemented within a single component, or a single component shown in Figure 14 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 14 may perform one or more functions described as being performed by another set of components shown in Figure 14.

The following provides an overview of some Aspects of the present disclosure:

Aspect 1: A method of wireless communication performed by a user equipment (UE) , comprising: transmitting a UE-initiated beam report request; generating, in association with the UE-initiated beam report request, a beam report using Layer 1 (L1) measurements; receiving a channel state information (CSI) request; and transmitting the beam report based at least in part on the receiving the CSI request.

Aspect 2: The method of Aspect 1, further comprising receiving an indication of a valid time duration for which the beam report is valid after transmission of the UE-initiated beam report request.

Aspect 3: The method of Aspect 2, wherein generating the beam report includes generating the beam report within the valid time duration after the transmission of the UE-initiated beam report request.

Aspect 4: The method of any of Aspects 1-3, wherein the UE-initiated beam report request includes a cell identifier.

Aspect 5: The method of any of Aspects 1-4, wherein the UE-initiated beam report request includes a bandwidth part identifier.

Aspect 6: The method of any of Aspects 1-5, wherein the UE-initiated beam report request includes a beam report identifier.

Aspect 7: A method of wireless communication performed by a network entity, comprising: receiving a user equipment (UE) -initiated beam report request; and transmitting a channel state information (CSI) request based at least in part on the receiving the UE-initiated beam report request.

Aspect 8: The method of Aspect 7, further comprising transmitting an indication of a valid time duration for which the beam report is valid after transmission of the UE-initiated beam report request.

Aspect 9: The method of Aspect 8, wherein transmitting the CSI request includes transmitting the CSI request during the valid time duration and not outside of the valid time duration.

Aspect 10: The method of Aspect 8, wherein transmitting the CSI request includes transmitting the CSI request independent of the valid time duration.

Aspect 11: The method of any of Aspects 7-10, wherein the UE-initiated beam report request includes a cell identifier.

Aspect 12: The method of any of Aspects 7-11, wherein the UE-initiated beam report request includes a bandwidth part identifier.

Aspect 13: The method of any of Aspects 7-12, wherein the UE-initiated beam report request includes a beam report identifier.

Aspect 14: A method of wireless communication performed by a user equipment (UE) , comprising: obtaining Layer 1 (L1) measurements; and transmitting, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell identifier (ID) or a bandwidth part (BWP) ID.

Aspect 15: The method of Aspect 14, wherein the UE-initiated beam report request includes the cell ID.

Aspect 16: The method of any of Aspects 14-15, wherein the UE-initiated beam report request indicates a request resource associated with the cell ID.

Aspect 17: The method of any of Aspects 14-16, wherein the UE-initiated beam report request includes the BWP ID.

Aspect 18: The method of any of Aspects 14-17, wherein the UE-initiated beam report request indicates a request resource associated with the BWP ID.

Aspect 19: The method of any of Aspects 14-18, wherein the UE-initiated beam report request includes a beam report ID.

Aspect 20: The method of any of Aspects 14-19, wherein the UE-initiated beam report request includes a beam report configuration.

Aspect 21: The method of any of Aspects 14-20, wherein UE-initiated beam report indicates the one or more of the cell ID or the BWP ID via a bitmap.

Aspect 22: A method of wireless communication performed by a network entity, comprising: obtaining Layer 1 (L1) measurements; and receiving, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell identifier (ID) or a bandwidth part (BWP) ID.

Aspect 23: The method of Aspect 22, wherein the UE-initiated beam report request includes the cell ID.

Aspect 24: The method of any of Aspects 22-23, wherein the UE-initiated beam report request indicates a request resource associated with the cell ID.

Aspect 25: The method of any of Aspects 22-24, wherein the UE-initiated beam report request includes the BWP ID.

Aspect 26: The method of any of Aspects 22-25, wherein the UE-initiated beam report request indicates a request resource associated with the BWP ID.

Aspect 27: The method of any of Aspects 22-26, wherein the UE-initiated beam report request includes a beam report ID.

Aspect 28: The method of any of Aspects 22-27, wherein the UE-initiated beam report request includes a beam report configuration.

Aspect 29: The method of any of Aspects 22-28, wherein UE-initiated beam report indicates the one or more of the cell ID or the BWP ID via a bitmap.

Aspect 30: An apparatus for wireless communication at a device, the apparatus comprising one or more processors; one or more memories coupled with the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method of one or more of Aspects 1-29.

Aspect 31: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors configured to cause the device to perform the method of one or more of Aspects 1-29.

Aspect 32: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-29.

Aspect 33: A non-transitory computer-readable medium storing code for wireless communication, the code comprising instructions executable by one or more processors to perform the method of one or more of Aspects 1-29.

Aspect 34: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method of one or more of Aspects 1-29.

Aspect 35: A device for wireless communication, the device comprising a processing system that includes one or more processors and one or more memories coupled with the one or more processors, the processing system configured to cause the device to perform the method of one or more of Aspects 1-29.

Aspect 36: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors individually or collectively configured to cause the device to perform the method of one or more of Aspects 1-29.

The foregoing disclosure provides illustration and description but is not intended to be exhaustive or to limit the aspects to the precise forms disclosed. Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the aspects.

As used herein, the term “component” is intended to be broadly construed as hardware or a combination of hardware and at least one of software or firmware. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware or a combination of hardware and software. It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.

As used herein, “satisfying a threshold” may, depending on the context, refer to a value being greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, or not equal to the threshold, among other examples.

As used herein, the term “determine” or “determining” encompasses a wide variety of actions and, therefore, “determining” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure) , identifying, inferring, ascertaining, measuring, and the like. Also, “determining” can include receiving (such as receiving information or receiving an indication) , accessing (such as accessing data stored in memory) , transmitting (such as transmitting information) and the like. Also, “determining” can include resolving, selecting, obtaining, choosing, establishing and other such similar actions. The term “identify” or “identifying” also encompasses a wide variety of actions and, therefore, “identifying” can include calculating, computing, processing, deriving, investigating, looking up (such as via looking up in a table, a database or another data structure) , inferring, ascertaining, measuring, and the like. Also, “identifying” can include receiving (such as receiving information or receiving an indication) , accessing (such as accessing data stored in memory) , transmitting (such as transmitting information) and the like. Also, “identifying” can include resolving, selecting, obtaining, choosing, establishing and other such similar actions.

As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (for example, a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c) .

No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more. ” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more. ” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more. ” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has, ” “have, ” “having, ” and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B) . Further, as used herein, “based on”is intended to be interpreted in the inclusive sense, unless otherwise explicitly indicated. For example, “based on” may be used interchangeably with “based at least in part on, ” “associated with” , or “in accordance with” unless otherwise explicitly indicated. Specifically, unless a phrase refers to “based on only ‘a, ’ ” or the equivalent in context, whatever it is that is “based on ‘a, ’ ” or “based at least in part on ‘a, ’ ” may be based on “a” alone or based on a combination of “a” and one or more other factors, conditions or information. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and/or, ” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of” ) . It should be understood that “one or more” is equivalent to “at least one. ”

Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.

Claims

An apparatus for wireless communication at a user equipment (UE) , comprising:

one or more memories storing processor-executable code; and

one or more processors coupled to the one or more memories, at least one processor of the one or more processors configured to cause the UE to:

transmit a UE-initiated beam report request;

generate, in association with the UE-initiated beam report request, a beam report using Layer 1 (L1) measurements;

receive a channel state information (CSI) request; and

transmit the beam report in accordance with reception of the CSI request.
The apparatus of claim 1, wherein at least one processor of the one or more processors is configured to cause the UE to receive an indication of a valid time duration for which the beam report is valid after transmission of the UE-initiated beam report request.
The apparatus of claim 2, wherein to generate the beam report, at least one processor of the one or more processors is configured to cause the UE to generate the beam report within the valid time duration after the transmission of the UE-initiated beam report request.
The apparatus of claim 1, wherein the UE-initiated beam report request includes a cell identifier.
The apparatus of claim 1, wherein the UE-initiated beam report request includes a bandwidth part identifier.
The apparatus of claim 1, wherein the UE-initiated beam report request includes a beam report identifier.
An apparatus for wireless communication at a network entity, comprising:

one or more memories storing processor-executable code; and

one or more processors coupled to the one or more memories, at least one processor of the one or more processors configured to cause the network entity to:

receive a user equipment (UE) -initiated beam report request; and

transmit a channel state information (CSI) request in accordance with reception of the UE-initiated beam report request.
The apparatus of claim 7, wherein at least one processor of the one or more processors is configured to cause the network entity to transmit an indication of a valid time duration for which the beam report is valid after transmission of the UE-initiated beam report request.
The apparatus of claim 8, wherein to transmit the CSI request, at least one processor of the one or more processors is configured to cause the network entity to transmit the CSI request during the valid time duration and not outside of the valid time duration.
The apparatus of claim 8, wherein to transmit the CSI request, wherein at least one processor of the one or more processors is configured to cause the network entity to transmit the CSI request independent of the valid time duration.
The apparatus of claim 7, wherein the UE-initiated beam report request includes at least one of a cell identifier (ID) , a bandwidth part identifier, or a beam report identifier.
An apparatus for wireless communication at a user equipment (UE) , comprising:

one or more memories storing processor-executable code; and

one or more processors coupled to the one or more memories, at least one processor of the one or more processors configured to cause the UE to:

obtain Layer 1 (L1) measurements; and

transmit, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell identifier (ID) or a bandwidth part (BWP) ID.
The apparatus of claim 12, wherein the UE-initiated beam report request includes the cell ID.
The apparatus of claim 12, wherein the UE-initiated beam report request indicates a request resource associated with the cell ID.
The apparatus of claim 12, wherein the UE-initiated beam report request includes the BWP ID.
The apparatus of claim 12, wherein the UE-initiated beam report request indicates a request resource associated with the BWP ID.
The apparatus of claim 12, wherein the UE-initiated beam report request includes a beam report ID.
The apparatus of claim 12, wherein the UE-initiated beam report request includes a beam report configuration.
The apparatus of claim 12, wherein UE-initiated beam report indicates the one or more of the cell ID or the BWP ID via a bitmap.
An apparatus for wireless communication at a network entity, comprising:

one or more memories storing processor-executable code; and

one or more processors coupled to the one or more memories, at least one processor of the one or more processors configured to cause the network entity to:

obtain Layer 1 (L1) measurements; and

receive, in association with the L1 measurements, a UE-initiated beam report request that indicates one or more of a cell identifier (ID) or a bandwidth part (BWP) ID.
The apparatus of claim 20, wherein the UE-initiated beam report request includes the cell ID.
The apparatus of claim 20, wherein the UE-initiated beam report request indicates a request resource associated with the cell ID.
The apparatus of claim 20, wherein the UE-initiated beam report request includes the BWP ID.
The apparatus of claim 20, wherein the UE-initiated beam report request indicates a request resource associated with the BWP ID.
The apparatus of claim 20, wherein the UE-initiated beam report request includes a beam report ID.
The apparatus of claim 20, wherein the UE-initiated beam report request includes a beam report configuration.
The apparatus of claim 20, wherein UE-initiated beam report indicates the one or more of the cell ID or the BWP ID via a bitmap.