WO2025241080A1

WO2025241080A1 - Techniques for user equipment initiated beam reporting

Info

Publication number: WO2025241080A1
Application number: PCT/CN2024/094366
Authority: WO
Inventors: Fang Yuan; Wooseok Nam; Yan Zhou
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2024-05-21
Filing date: 2024-05-21
Publication date: 2025-11-27
Anticipated expiration: 2026-11-21

Abstract

Various aspects of the present disclosure generally relate to wireless communication. In some aspects, a user equipment (UE) may transmit, on a physical uplink control channel (PUCCH), a beam report message triggering a UE-initiated beam report identifying a measurement of a channel state information (CSI) reference signal (CSI-RS). The UE may receive, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered. Numerous other aspects are described.

Description

TECHNIQUES FOR USER EQUIPMENT INITIATED BEAM REPORTING

FIELD OF THE DISCLOSURE

Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods for user equipment (UE) initiated beam reporting.

DESCRIPTION OF RELATED ART

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.

These 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.

SUMMARY

Some aspects described herein relate to a method of wireless communication performed by a user equipment (UE) . The method may include transmitting, on a physical uplink control channel (PUCCH) , a beam report message triggering a UE-initiated beam report identifying a measurement of a channel state information (CSI) reference signal (CSI-RS) . The method may include receiving, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.

Some aspects described herein relate to a method of wireless communication performed by a network node. The method may include receiving, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS. The method may include transmitting, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.

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 transmit, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS. The set of instructions, when executed by one or more processors of the UE, may cause the UE to receive, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.

Some aspects described herein relate to a non-transitory computer-readable medium that stores a set of instructions for wireless communication by a network node. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS. The set of instructions, when executed by one or more processors of the network node, may cause the network node to transmit, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.

Some aspects described herein relate to a UE for wireless communication. The UE may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the UE to transmit, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS. The one or more processors may be configured to cause the UE to receive, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.

Some aspects described herein relate to a network node for wireless communication. The network node may include one or more memories and one or more processors coupled to the one or more memories. The one or more processors may be configured to cause the network node to receive, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS. The one or more processors may be configured to cause the network node to transmit, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS. The apparatus may include means for receiving, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.

Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS. The apparatus may include means for transmitting, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.

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.

Fig. 1 is a diagram illustrating an example of a wireless communication network, in accordance with the present disclosure.

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

Fig. 3 is a diagram illustrating an example disaggregated base station architecture, in accordance with the present disclosure.

Fig. 4 is a diagram illustrating examples of channel state information (CSI) reference signal (CSI-RS) beam management procedures, in accordance with the present disclosure.

Fig. 5 is a diagram illustrating an example associated with UE-initiated beam reporting, in accordance with the present disclosure.

Fig. 6 is a diagram illustrating an example process performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure.

Fig. 7 is a diagram illustrating an example process performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure.

Fig. 8 is a diagram of an example apparatus for wireless communication, in accordance with the present disclosure.

Fig. 9 is a diagram of an example apparatus for wireless communication, 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 numbers 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 application and design constraints imposed on the overall system.

A user equipment (UE) may transmit a beam report to a network node in connection with a beam management procedure, such as a beam selection procedure or a beam refinement procedure. In a beam management procedure, the network node may transmit a reference signal, such as a channel state information (CSI) reference signal (RS) (CSI-RS) , to the UE for measurement, and the UE may transmit the beam report to identify a measurement of the reference signal or a selection of a beam based on a measurement of the reference signal. The network node may initiate the beam management procedure in connection with access to network services or based on the network node determining that a triggering condition has been satisfied.

However, when a UE detects network conditions for which beam management may be performed, such as a quality of a current beam not satisfying a threshold quality level or the UE being in a mobility state, a delay associated with the UE waiting for the network node to initiate beam management may result in poor communication performance. For example, the UE may experience a radio link failure while waiting for the network node to initiate the beam management procedure, which may result in additional signaling for radio link failure recovery. Additionally, or alternatively, the UE may experience dropped communications associated with a delay in performing beam management and selecting a new beam.

Accordingly, some UEs may be configured for UE-initiated beam reporting (and associated beam management) , which may also be referred to as “event-driven” beam reporting. In UE-initiated beam reporting, the UE may detect satisfaction of one or more triggering conditions and may initiate beam management without waiting for the network node to detect satisfaction of the one or more triggering conditions and initiate beam management. UE-initiated beam management may, thus, reduce a latency associated with beam reporting and may facilitate fast beam switching, thereby improving communication performance. In this case, the UE may be configured with a set of events for which the UE can autonomously trigger beam reporting. Examples of events include a quality of a current beam being less than a quality threshold, a quality of at least one new beam being greater than a quality threshold, a quality of a new beam being better than a current beam (e.g., by a threshold amount) , or a combination thereof, among other examples.

To perform CSI beam reporting, such as for UE-initiated beam reporting of a CSI-RS, the UE may transmit a physical uplink control channel (PUCCH) message associated with indicating an initiation of the UE-initiated beam reporting and/or conveying one or more parameters associated with the UE-initiated beam reporting. In network node initiated CSI beam reporting, the network node may transmit downlink control information (DCI) with a CSI request field to convey a parameter relating to a CSI report. For example, when bits of the CSI request field are set to zero, the UE may interpret the CSI request field as indicating that no CSI is requested. When a number of CSI triggering states in a CSI trigger state list is greater than a threshold value, the UE may interpret the CSI request field as implicitly conveying a sub-selection indication (e.g., indicating one or more parameters for the UE to use to perform CSI beam reporting) . Alternatively, when the number of CSI triggering states is less than or equal to the threshold value, the UE may interpret the CSI request field as explicitly indicating a triggering state for CSI beam reporting.

The trigger state (or “triggering state” ) may indicate one or more actions that the UE is to perform in connection with CSI beam reporting, such as indicating an offset between transmission of a reference signal for measurement and transmission of a beam report conveying the measurement. Additional details regarding the CSI request field are described in 3GPP Technical Specification (TS) 38.214 Release 18, Version 18.2.0. Accordingly, it is desirable for the UE and the network node to be synchronized with respect to the trigger state to ensure that the UE can successfully measure a reference signal and transmit a report, and to ensure that the network node can successfully receive the report. However, when the network node receives an initial PUCCH transmission from the UE associated with indicating that the UE is initiating a UE-initiated beam report, the network node may lack information indicating for which cell the UE-initiated beam report is triggered or which event has occurred to trigger the UE-initiated beam report. The network node may set a first value for the CSI request field for a first cell or event and a second value for the CSI request field for a second cell or event. Accordingly, without information indicating the cell or event associated with the UE-initiated beam report, the network node may not set the CSI request field accurately for the UE-initiated beam report.

Further, for UE-initiated beam reporting, a UE may detect occurrences of a plurality of triggering events for which to initiate UE-initiated beam reporting. In such a case, the UE may use one or more CSI report configurations for transmitting one or more beam reports relating to the plurality of triggering events. However, the UE and the network node may lack a mapping of CSI report configurations to events. Accordingly, the UE and the network node may lack synchronization, which may result in dropped communications or excessive utilization of network resources associated with retransmission of dropped communications.

Various aspects relate generally to UE-initiated beam reporting. Some aspects more specifically relate to a network node providing a dedicated indicator for a CSI request field as a response to receiving a PUCCH conveying an indication of an initiation of UE-initiated beam reporting. For example, the network node may include a reserved CSI request codepoint or may select a dedicated CSI trigger state in DCI transmitted as a response to receiving the PUCCH. In this case, the UE and/or the network node may perform one or more synchronized CSI beam reporting actions, such as transmission of a reference signal, measurement of the reference signal, and/or reporting of a measurement in accordance with the reserved CSI request codepoint or dedicated CSI trigger state. Additionally, or alternatively, the network node may indicate a CSI report configuration that is dedicated for UE-initiated beam reporting, and the UE and the network node may perform a CSI beam reporting action in accordance with the CSI report configuration.

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 using a reserved codepoint, dedicated CSI trigger state, or dedicated CSI report configuration for UE-initiated beam reporting, the UE and the network node may maintain synchronization when the network node lacks information indicating a cell or event for which UE-initiated beam reporting is being performed. Additionally, or alternatively, by configuring a mapping of CSI report configurations to triggering events, the network node may identify which events map to which CSI reporting configurations, which may enable the network node to perform concurrent beam management for a plurality of events.

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.

Fig. 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, 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 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-a or 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 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. In some examples, a cell may not necessarily be stationary. For example, the geographic area of the cell may move according to the location of an associated mobile network node 110 (for example, a train, a satellite base station, an unmanned aerial vehicle, or a NTN 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 Fig. 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 channels may include one or more control channels and one or more data channels. A downlink control channel may be used to transmit DCI (for example, scheduling information, reference signals, and/or configuration information) from a network node 110 to a UE 120. A downlink data channel may be used to transmit downlink data (for example, user data associated with a UE 120) from a network node 110 to a UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCHs) , and downlink data channels may include one or more physical downlink shared channels (PDSCHs) . Uplink channels may similarly include one or more control channels and one or more data channels. An uplink control channel may be used to transmit uplink control information (UCI) (for example, reference signals and/or feedback corresponding to one or more downlink transmissions) from a UE 120 to a network node 110. An uplink data channel may be used to transmit uplink data (for example, user data associated with a UE 120) from a UE 120 to a network node 110. Uplink control channels may include one or more PUCCHs, and uplink data channels may include one or more physical uplink shared channels (PUSCHs) . The downlink and the uplink may each include a set of resources on which the network node 110 and the UE 120 may communicate.

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 (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 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 number 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.

As described above, in some aspects, the wireless communication network 100 may be, may include, or may be included in, an IAB network. In an IAB network, at least one network node 110 is an anchor network node that communicates with a core network. An anchor network node 110 may also be referred to as an IAB donor (or “IAB-donor” ) . The anchor network node 110 may connect to the core network via a wired backhaul link. For example, an Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, an anchor network node 110 may connect to one or more devices of the core network that provide a core access and mobility management function (AMF) . An IAB network also generally includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply as IAB nodes (or “IAB-nodes” ) . Each non-anchor network node 110 may communicate directly with the anchor network node 110 via a wireless backhaul link to access the core network, or may communicate indirectly with the anchor network node 110 via one or more other non-anchor network nodes 110 and associated wireless backhaul links that form a backhaul path to the core network. Some anchor network node 110 or other non-anchor network node 110 may also communicate directly with one or more UEs 120 via wireless access links that carry access traffic. In some examples, network resources for wireless communication (such as time resources, frequency resources, and/or spatial resources) may be shared between access links and backhaul links.

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 Fig. 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 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.

Some UEs 120 may be considered machine-type communication (MTC) UEs, evolved or enhanced machine-type communication (eMTC) , UEs, further enhanced eMTC (feMTC) UEs, or enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be simply referred to as “MTC UEs” . An MTC UE may be, may include, or may be included in or coupled with a robot, an uncrewed aerial vehicle, a remote device, a sensor, a meter, a monitor, and/or a location tag. Some UEs 120 may be considered IoT devices and/or may be implemented as NB-IoT (narrowband IoT) devices. An IoT UE or NB-IoT device may be, may include, or may be included in or coupled with an industrial machine, an appliance, a refrigerator, a doorbell camera device, a home automation device, and/or a light fixture, among other examples. Some UEs 120 may be considered Customer Premises Equipment, which may include telecommunications devices that are installed at a customer location (such as a home or office) to enable access to a service provider's network (such as included in or in communication with the wireless communication network 100) .

Some UEs 120 may be classified according to different categories in association with different complexities and/or different capabilities. UEs 120 in a first category may facilitate massive IoT in the wireless communication network 100, and may offer low complexity and/or cost relative to UEs 120 in a second category. UEs 120 in a second category may include mission-critical IoT devices, legacy UEs, baseline UEs, high-tier UEs, advanced UEs, full-capability UEs, and/or premium UEs that are capable of URLLC, enhanced mobile broadband (eMBB) , and/or precise positioning in the wireless communication network 100, among other examples. A third category of UEs 120 may have mid-tier complexity and/or capability (for example, a capability between UEs 120 of the first category and UEs 120 of the second capability) . A UE 120 of the third category may be referred to as a reduced capacity UE ( “RedCap UE” ) , a mid-tier UE, an NR-Light UE, and/or an NR-Lite UE, among other examples. RedCap UEs may bridge a gap between the capability and complexity of NB-IoT devices and/or eMTC UEs, and mission-critical IoT devices and/or premium UEs. RedCap UEs may include, for example, wearable devices, IoT devices, industrial sensors, and/or cameras that are associated with a limited bandwidth, power capacity, and/or transmission range, among other examples. RedCap UEs may support healthcare environments, building automation, electrical distribution, process automation, transport and logistics, and/or smart city deployments, among other examples.

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 various examples, the UEs 120 may transmit and receive sidelink communications using peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and/or vehicle-to-pedestrian (V2P) protocols) , and/or mesh network communication protocols. In some deployments and configurations, a network node 110 may schedule and/or allocate resources for sidelink communications between UEs 120 in the wireless communication network 100. In some other deployments and configurations, a UE 120 (instead of a network node 110) may perform, or collaborate or negotiate with one or more other UEs to perform, scheduling operations, resource selection operations, and/or other operations for sidelink communications.

In various examples, some of the network nodes 110 and the UEs 120 of the wireless communication network 100 may be configured for full-duplex operation in addition to half-duplex operation. A network node 110 or a UE 120 operating in a half-duplex mode may perform only one of transmission or reception during time resources, such as during slots, symbols, or other time periods. Half-duplex operation may involve time-division duplexing (TDD) , in which DL transmissions of the network node 110 and UL transmissions of the UE 120 do not occur in the same time resources (that is, the transmissions do not overlap in time) . In contrast, a network node 110 or a UE 120 operating in a full-duplex mode can transmit and receive communications concurrently (for example, in the same time resources) . By operating in a full-duplex mode, network nodes 110 and/or UEs 120 may generally increase the capacity of the network and the radio access link. In some examples, full-duplex operation may involve frequency-division duplexing (FDD) , in which DL transmissions of the network node 110 are performed in a first frequency band or on a first component carrier and transmissions of the UE 120 are performed in a second frequency band or on a second component carrier different than the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for a UE 120 but not for a network node 110. For example, a UE 120 may simultaneously transmit an UL transmission to a first network node 110 and receive a DL transmission from a second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for a network node 110 but not for a UE 120. For example, a network node 110 may simultaneously transmit a DL transmission to a first UE 120 and receive an UL transmission from a second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both a network node 110 and a UE 120.

In some examples, the UEs 120 and the network nodes 110 may perform MIMO communication. “MIMO” generally refers to transmitting or receiving multiple signals (such as multiple layers or multiple data streams) simultaneously over the same time and frequency resources. MIMO techniques generally exploit multipath propagation. MIMO may be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO may support simultaneous transmission to multiple receivers, referred to as multi-user MIMO (MU-MIMO) . Some RATs may employ advanced MIMO techniques, such as mTRP operation (including redundant transmission or reception on multiple TRPs) , reciprocity in the time domain or the frequency domain, single-frequency-network (SFN) transmission, or non-coherent joint transmission (NC-JT) .

In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may transmit, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS; and receive, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.

In some aspects, the network node 110 may include a communication manager 150. As described in more detail elsewhere herein, the communication manager 150 may receive, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS; and transmit, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.

As indicated above, Fig. 1 is provided as an example. Other examples may differ from what is described with regard to Fig. 1.

Fig. 2 is a diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network.

As shown in Fig. 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, ” “a/the controller/processor, ” or the like (in the singular) should be understood to refer to any one or more of the processors described in connection with Fig. 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 Fig. 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 Fig. 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-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.

A downlink signal may include a DCI communication, a MAC control element (MAC-CE) communication, an RRC communication, a downlink reference signal, or another type of downlink communication. Downlink signals may be transmitted on a PDCCH, a PDSCH, and/or on another downlink channel. A downlink signal may carry one or more transport blocks (TBs) of data. A TB may be a unit of data that is transmitted over an air interface in the wireless communication network 100. A data stream (for example, from the data source 212) may be encoded into multiple TBs for transmission over the air interface. The number of TBs used to carry the data associated with a data stream may be associated with a TB size common to the multiple TBs. The TB size may be based on or otherwise associated with radio channel conditions of the air interface, the MCS used for encoding the data, the downlink resources allocated for transmitting the data, and/or another parameter. In general, the larger the TB size, the greater the amount of data that can be transmitted in a single transmission, which reduces signaling overhead. However, larger TB sizes may be more prone to transmission and/or reception errors than smaller TB sizes, but such errors may be mitigated by more robust error correction techniques.

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 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 discrete Fourier transform (DFT) spread (s) orthogonal frequency division multiplexing (OFDM (DFT-s-OFDM) or cyclic prefix (CP) OFDM (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 UCI communication, a MAC-CE communication, an RRC communication, or another type of uplink communication. Uplink signals may be transmitted on a PUSCH, a PUCCH, and/or another type of uplink channel. An uplink signal may carry one or more 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 Fig. 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. In some implementations, antenna elements may be individually selected or deselected for directional transmission of a signal (or signals) by controlling amplitudes of one or more corresponding amplifiers and/or phases of the signal (s) to form one or more beams. The shape of a beam (such as the amplitude, width, and/or presence of side lobes) and/or the direction of a beam (such as an angle of the beam relative to a surface of an antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and/or amplitudes of the multiple signals relative to each other.

Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, a UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or a different number of antenna elements. As another example, a network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or a different number of antenna elements. Generally, a larger number of antenna elements may provide increased control over parameters for beam generation relative to a smaller number of antenna elements, whereas a smaller number of antenna elements may be less complex to implement and may use less power than a larger number of antenna elements. Multiple antenna elements may support multiple-layer transmission, in which a first layer of a communication (which may include a first data stream) and a second layer of a communication (which may include a second data stream) are transmitted using the same time and frequency resources with spatial multiplexing.

In some aspects, the controller/processor 280 may be a component of a processing system. A processing system may generally be a system or a series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the UE 120) . For example, a processing system of the UE 120 may be a system that includes the various other components or subcomponents of the UE 120.

The processing system of the UE 120 may interface with one or more other components of the UE 120, may process information received from one or more other components (such as inputs or signals) , or may output information to one or more other components. For example, a chip or modem of the UE 120 may include a processing system, a first interface to receive or obtain information, and a second interface to output, transmit, or provide information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, such that the UE 120 may receive information or signal inputs, and the information may be passed to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, such that the UE 120 may transmit information output from the chip or modem. A person having ordinary skill in the art will readily recognize that the second interface also may obtain or receive information or signal inputs, and the first interface also may output, transmit, or provide information.

In some aspects, the controller/processor 240 may be a component of a processing system. A processing system may generally be a system or a series of machines or components that receives inputs and processes the inputs to produce a set of outputs (which may be passed to other systems or components of, for example, the network node 110) . For example, a processing system of the network node 110 may be a system that includes the various other components or subcomponents of the network node 110.

The processing system of the network node 110 may interface with one or more other components of the network node 110, may process information received from one or more other components (such as inputs or signals) , or may output information to one or more other components. For example, a chip or modem of the network node 110 may include a processing system, a first interface to receive or obtain information, and a second interface to output, transmit, or provide information. In some examples, the first interface may be an interface between the processing system of the chip or modem and a receiver, such that the network node 110 may receive information or signal inputs, and the information may be passed to the processing system. In some examples, the second interface may be an interface between the processing system of the chip or modem and a transmitter, such that the network node 110 may transmit information output from the chip or modem. A person having ordinary skill in the art will readily recognize that the second interface also may obtain or receive information or signal inputs, and the first interface also may output, transmit, or provide information.

While blocks in Fig. 2 are illustrated as distinct components, the functions described above with respect to the blocks may be implemented in a single hardware, software, or combination component or in various combinations of components. For example, the functions described with respect to the transmit processor 264, the receive processor 258, and/or the TX MIMO processor 266 may be performed by or under the control of the controller/processor 280.

Fig. 3 is a diagram illustrating an example disaggregated base station architecture 300, in accordance with the present disclosure. One or more components of the example disaggregated base station architecture 300 may be, may include, or may be included in one or more network nodes (such one or more network nodes 110) . The disaggregated base station architecture 300 may include a CU 310 that can communicate directly with a core network 320 via a backhaul link, or that can communicate indirectly with the core network 320 via one or more disaggregated control units, such as a Non-RT RIC 350 associated with a Service Management and Orchestration (SMO) Framework 360 and/or a Near-RT RIC 370 (for example, via an E2 link) . The CU 310 may communicate with one or more DUs 330 via respective midhaul links, such as via F1 interfaces. Each of the DUs 330 may communicate with one or more RUs 340 via respective fronthaul links. Each of the RUs 340 may communicate with one or more UEs 120 via respective RF access links. In some deployments, a UE 120 may be simultaneously served by multiple RUs 340.

Each of the components of the disaggregated base station architecture 300, including the CUs 310, the DUs 330, the RUs 340, the Near-RT RICs 370, the Non-RT RICs 350, and the SMO Framework 360, may include one or more interfaces or may be coupled with one or more interfaces for receiving or transmitting signals, such as data or information, via a wired or wireless transmission medium.

In some aspects, the CU 310 may be logically split into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. A CU-UP unit may communicate bidirectionally with a CU-CP unit via an interface, such as the E1 interface when implemented in an O-RAN configuration. The CU 310 may be deployed to communicate with one or more DUs 330, as necessary, for network control and signaling. Each DU 330 may correspond to a logical unit that includes one or more base station functions to control the operation of one or more RUs 340. For example, a DU 330 may host various layers, such as an RLC layer, a MAC layer, or one or more PHY layers, such as one or more high PHY layers or one or more low PHY layers. Each layer (which also may be referred to as a module) may be implemented with an interface for communicating signals with other layers (and modules) hosted by the DU 330, or for communicating signals with the control functions hosted by the CU 310. Each RU 340 may implement lower layer functionality. In some aspects, real-time and non-real-time aspects of control and user plane communication with the RU (s) 340 may be controlled by the corresponding DU 330.

The SMO Framework 360 may support RAN deployment and provisioning of non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO Framework 360 may support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operations and maintenance interface, such as an O1 interface. For virtualized network elements, the SMO Framework 360 may interact with a cloud computing platform (such as an open cloud (O-Cloud) platform 390) to perform network element life cycle management (such as to instantiate virtualized network elements) via a cloud computing platform interface, such as an O2 interface. A virtualized network element may include, but is not limited to, a CU 310, a DU 330, an RU 340, a non-RT RIC 350, and/or a Near-RT RIC 370. In some aspects, the SMO Framework 360 may communicate with a hardware aspect of a 4G RAN, a 5G NR RAN, and/or a 6G RAN, such as an open eNB (O-eNB) 380, via an O1 interface. Additionally or alternatively, the SMO Framework 360 may communicate directly with each of one or more RUs 340 via a respective O1 interface. In some deployments, this configuration can enable each DU 330 and the CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.

The Non-RT RIC 350 may include or may implement a logical function that enables non-real-time control and optimization of RAN elements and resources, AI/ML workflows including model training and updates, and/or policy-based guidance of applications and/or features in the Near-RT RIC 370. The Non-RT RIC 350 may be coupled to or may communicate with (such as via an A1 interface) the Near-RT RIC 370. The Near-RT RIC 370 may include or may implement a logical function that enables near-real-time control and optimization of RAN elements and resources via data collection and actions via an interface (such as via an E2 interface) connecting one or more CUs 310, one or more DUs 330, and/or an O-eNB with the Near-RT RIC 370.

In some aspects, to generate AI/ML models to be deployed in the Near-RT RIC 370, the Non-RT RIC 350 may receive parameters or external enrichment information from external servers. Such information may be utilized by the Near-RT RIC 370 and may be received at the SMO Framework 360 or the Non-RT RIC 350 from non-network data sources or from network functions. In some examples, the Non-RT RIC 350 or the Near-RT RIC 370 may tune RAN behavior or performance. For example, the Non-RT RIC 350 may monitor long-term trends and patterns for performance and may employ AI/ML models to perform corrective actions via the SMO Framework 360 (such as reconfiguration via an O1 interface) or via creation of RAN management policies (such as A1 interface policies) .

The network node 110, the controller/processor 240 of the network node 110, the UE 120, the controller/processor 280 of the UE 120, the CU 310, the DU 330, the RU 340, or any other component (s) of Figs. 1, 2, or 3 may implement one or more techniques or perform one or more operations associated with UE-initiated beam reporting, 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) (or combinations of components) of Fig. 2, the CU 310, the DU 330, or the RU 340 may perform or direct operations of, for example, process 600 of Fig. 6, process 700 of Fig. 7, 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 310, the DU 330, or the RU 340. 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 310, the DU 330, or the RU 340, may cause the one or more processors to perform process 600 of Fig. 6, process 700 of Fig. 7, 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, the UE includes means for transmitting, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS; and/or means for receiving, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered. 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, the network node includes means for receiving, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS; and/or means for transmitting, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered. The means for the network node to perform operations described herein may include, for example, one or more of communication manager 150, transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, controller/processor 240, memory 242, or scheduler 246.

Fig. 4 is a diagram illustrating examples 400, 410, and 420 of CSI-RS beam management procedures, in accordance with the present disclosure. As shown in Fig. 4, examples 400, 410, and 420 include a UE 120 in communication with a network node 110 in a wireless network (e.g., wireless network 100) . However, the devices shown in Fig. 4 are provided as examples, and the wireless network may support communication and beam management between other devices (e.g., between a UE 120 and a network node 110 or TRP, between a mobile termination node and a control node, between an 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 (e.g., an RRC connected state) .

As shown in Fig. 4, example 400 may include a network node 110 (e.g., 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 400 depicts a first beam management procedure (e.g., 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 Fig. 4 and example 400, 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 (e.g., using RRC signaling) , semi-persistent (e.g., using MAC-CE signaling) , and/or aperiodic (e.g., using DCI) .

The first beam management procedure may include the network node 110 performing beam sweeping over multiple transmit (Tx) beams 402. The network node 110 may transmit a CSI-RS 404 using each transmit beam 402 for beam management. To enable the UE 120 to perform receive (Rx) beam sweeping, the network node may use a transmit beam 402 to transmit (e.g., with repetitions) each CSI-RS 404 at multiple times within the same RS resource set so that the UE 120 can sweep through receive beams 406 in multiple transmission instances. For example, if the network node 110 has a set of N transmit beams 402 and the UE 120 has a set of M receive beams 406, the CSI-RS 404 may be transmitted on each of the N transmit beams 402 M times so that the UE 120 may receive M instances of the CSI-RS 404 per transmit beam 402. In other words, for each transmit beam 402 of the network node 110, the UE 120 may perform beam sweeping through the receive beams 406 of the UE 120. As a result, the first beam management procedure may enable the UE 120 to measure a CSI-RS 404 on different transmit beams 402 using different receive beams 406 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 400 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 Fig. 4, example 410 may include a network node 110 and a UE 120 communicating to perform beam management using CSI-RSs. Example 410 depicts a second beam management procedure (e.g., 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 Fig. 4 and example 410, CSI-RSs 414 may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs 414 may be configured to be aperiodic (e.g., using DCI) . The second beam management procedure may include the network node 110 performing beam sweeping over one or more transmit beams 412. The one or more transmit beams 412 may be a subset of all transmit beams 402 associated with the network node 110 (e.g., 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 414 using each transmit beam 412 of the one or more transmit beams 412 for beam management. The UE 120 may measure each CSI-RS 414 using a single (e.g., a same) receive beam 416 (e.g., 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 412 based at least in part on measurements of the CSI-RSs 414 (e.g., measured by the UE 120 using the single receive beam 416) reported by the UE 120.

As shown in Fig. 4, example 420 depicts a third beam management procedure (e.g., 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 Fig. 4 and example 420, one or more CSI-RSs 424 may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs may be configured to be aperiodic (e.g., using DCI) . The third beam management process may include the network node 110 transmitting the one or more CSI-RSs 424 using a single transmit beam 422 (e.g., 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 422 to transmit (e.g., with repetitions) CSI-RS 424 at multiple times within the same RS resource set so that UE 120 can sweep through one or more receive beams 426 in multiple transmission instances. The one or more receive beams 426 may be a subset of all receive beams 406 associated with the UE 120 (e.g., 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 426 based at least in part on reported measurements received from the UE 120 (e.g., of the CSI-RS 424 of the transmit beam 422 using the one or more receive beams 426) .

As indicated above, Fig. 4 is provided as an example of beam management procedures. Other examples of beam management procedures may differ from what is described with respect to Fig. 4. 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.

As described above, in a beam management procedure, a network node may transmit a reference signal, such as a CSI-RS, to a UE for measurement, and the UE may transmit a beam report. The beam report may identify a measurement of the reference signal or a selection of a beam based on a measurement of the reference signal. The network node may initiate the beam management procedure in connection with a request for access to network services or based on the network node determining that a triggering condition has been satisfied.

To perform CSI beam reporting, such as for UE-initiated beam reporting of a CSI-RS, the UE may transmit a PUCCH message associated with indicating an initiation of the UE-initiated beam reporting and/or conveying one or more parameters associated with the UE-initiated beam reporting. In network node initiated CSI beam reporting, the network node may transmit DCI with a CSI request field to convey a parameter relating to a CSI report. For example, when bits of the CSI request field are set to zero, the UE may interpret the CSI request field as indicating that no CSI is requested. When a number of CSI triggering states in a CSI trigger state list is greater than a threshold value, the UE may interpret the CSI request field as implicitly conveying a sub-selection indication (e.g., indicating one or more parameters for the UE to use to perform CSI beam reporting) . Alternatively, when the number of CSI triggering states is less than or equal to the threshold value, the UE may interpret the CSI request field as explicitly indicating a triggering state for CSI beam reporting.

The trigger state (or “triggering state” ) may indicate one or more actions that the UE is to perform in connection with CSI beam reporting, such as indicating an offset between transmission of a reference signal for measurement and transmission of a beam report conveying the measurement. Additional details regarding the CSI request field are described in 3GPP TS 38.214 Release 18, Version 18.2.0. Accordingly, it is desirable for the UE and the network node to be synchronized with respect to the trigger state to ensure that the UE can successfully measure a reference signal and transmit a report, and to ensure that the network node can successfully receive the report. However, when the network node receives an initial PUCCH transmission from the UE associated with indicating that the UE is initiating a UE-initiated beam report, the network node may lack information indicating for which cell the UE-initiated beam report is triggered or which event has occurred to trigger the UE-initiated beam report. The network node may set a first value for the CSI request field for a first cell or event and a second value for the CSI request field for a second cell or event. Accordingly, without information indicating the cell or event associated with the UE-initiated beam report, the network node may not set the CSI request field accurately for the UE-initiated beam report.

Fig. 5 is a diagram illustrating an example 500 associated with UE-initiated beam reporting, in accordance with the present disclosure. As shown in Fig. 5, example 500 includes communication between a network node 110 and a UE 120.

As further shown in Fig. 5, and by reference number 510, the UE 120 may detect a triggering event. For example, the UE 120 may determine that one or more criteria for UE-initiated beam reporting are satisfied. As examples, the triggering event may include a quality (e.g., an RSRQ or layer 1 (L1) RSRP) of a current beam being less than a threshold level. Additionally, or alternatively, the event may include a quality of a new beam (e.g., a beam to which the UE 120 may switch to using) having a quality at least a configured value better than a current beam (e.g., an RSRP of a new beam being greater than an RSRP of a current beam by at least a configured amount) . Additionally, or alternatively, the event may include a quality of a new beam being greater than or equal to a threshold level. Additionally, or alternatively, the event may include a combination of a set of criteria, such as a current beam having a quality worse than a first threshold value and a new beam having a quality better than a second threshold value. Additionally, or alternatively, the event may include a quality of at least one beam being at least a threshold level better than a quality of a reference signal derived from an activated transmission configuration indicator (TCI) state with a worst quality or best quality. Additionally, or alternatively, the event may include at least a threshold number of beams having respective qualities better than a quality of a current beam. Additionally, or alternatively, the event may include a quality of a new beam being at least a threshold level better than a number of a configured reference signal (e.g., a synchronization signal block or CSI-RS) .

In some aspects, the UE 120 may determine one or more parameters for detecting a triggering event based on received configuration information. For example, for an event in which a configured number N of new beams have RSRPs that are better than an RSRP of a current beam, the UE 120 may receive configuration information, from the network node 110, identifying the configured number N that the UE 120 is to use. Additionally, or alternatively, the UE 120 may determine the configured number N based on a default value (e.g., a default value of 1) . Additionally, or alternatively, the UE 120 may determine the configured number N based on a number of beams that are configured for reporting in a CSI report configuration. For example, the UE 120 may receive a CSI report configuration identifying a set of K beams and may use the number of beams K as the configured number N.

In some aspects, the UE 120 may detect an event with respect to a TCI state. For example, when a beam is associated with a better quality than a current activated TCI, the UE 120 may detect an event. In some aspects, the UE 120 may detect an event based on a TCI that is selected having a worst quality or a best quality among measured beams (e.g., based on an RRC configuration) . In this case, when the UE 120 transmits a beam report, as described herein, the UE 120 may indicate which TCI state is selected and may report a measured reference signal and metric associated with a selected TCI state.

In some aspects, the UE 120 may determine a configuration of one or more values for one or more events on a configured basis. For example, the UE 120 may determine a value for an event on a per BWP basis, a per component carrier (CC) basis, or a per frequency band basis. Additionally, or alternatively, the UE 120 may determine a value for an event on a per event basis (e.g., the UE 120 may be configured with different threshold values for different events) . Additionally, or alternatively, the UE 120 may determine a value for an event on a per CSI report configuration basis.

As further shown in Fig. 5, and by reference number 520, the UE 120 may transmit a PUCCH communication. For example, based on detecting a triggering event, the UE 120 may transmit a beam report message, via a PUCCH, to initiate UE-initiated beam reporting. In this case, the UE 120 may include information identifying a type of event that has occurred, cell on which an event has occurred, or another indication associated with initiating the UE-initiated beam reporting.

In some aspects, the UE 120 may include an indicator of an event that has occurred in a payload of the PUCCH beam reporting message. For example, the UE 120 may include a one-bit indicator indicating whether or not at least one event has been detected. Additionally, or alternatively, the UE 120 may include a multi-bit indicator to provide additional granularity regarding a number of events that have been detected. For example, the UE 120 may provide a two-bit indicator to indicate the number of events detected with respect to two threshold values. In other words, the UE 120 may indicate “00” to indicate no event detected, “01” to indicate less than or equal to a first number of events detected, “10” to indicate greater than the first number and less than or equal to a second number of events detected, and “11” to indicate greater than the second number of events detected. In this case, the first number and second number may be default values or configured values (e.g., configured by the network node 110 in configuration signaling) .

Additionally, or alternatively, the UE 120 may provide a two-bit indicator to indicate a payload size with respect to two threshold values. In other words, the UE 120 may indicate “00” to indicate no event detected, “01” to indicate less than or equal to a first payload size, “10” to indicate greater than the first payload size and less than or equal to a second payload size, and “11” to indicate greater than the second payload size. Additionally, or alternatively, the UE 120 may include one or more bit (or multi-bit) indicators to indicate one or more other parameters, such as one or more event types. In this case, the UE 120 may indicate “00” to indicate no event detected and may indicate “01, ” “10, ” and “11” to indicate a first, second, or third type of event, respectively. Although a configured set of bit indicators are described, it is contemplated that other sets of bit indicators or interpretations are possible. For example, the UE 120 may include a multi-bit indicator to identify a carrier identifier or event identifier for a detected event.

As further shown in Fig. 5, and by reference number 530, the UE 120 may receive a DCI communication. For example, the UE 120 may receive DCI with one or more fields associated with UE-initiated beam reporting. In some aspects, the UE 120 may receive DCI that includes a CSI request field for the UE-initiated beam reporting. For example, the UE 120 may receive DCI that includes a CSI request field with a configured CSI request codepoint that is reserved in the CSI request field for UE-initiated beam reporting. In other words, a codepoint in the CSI request field, such as a first codepoint or a last codepoint is reserved for conveying a value associated with setting one or more parameters or providing an indication for UE-initiated beam reporting.

Additionally, or alternatively, the UE 120 may receive DCI with a CSI request field associated with selecting a CSI trigger state. For example, the UE 120 may interpret the CSI request field as including a value associated with selecting a CSI trigger state that is dedicated for UE-initiated beam reporting. Additionally, or alternatively, the UE 120 may receive an indication of a CSI report configuration dedicated for UE-initiated beam reporting. For example, the UE 120 may receive DCI, with a CSI trigger state, that conveys a CSI request and that triggers one or more CSI reports. In this case, at least one of the triggered CSI reports is associated with a CSI report configuration for UE-initiated beam reporting. In some aspects, the CSI report configuration may be non-event-specific. In other words, when the network node 110 does not receive information (e.g., in the PUCCH beam report message) indicating an event that triggered the UE-initiated beam reporting, the network node 110 may provide a CSI report configuration that is not specific to an event (and the UE 120 may apply to the event that the UE 120 has detected) .

In some aspects, the UE 120 may receive DCI requesting transmission of a UE-initiated beam report in a scheduled uplink resource. For example, the UE 120 may receive DCI with a CSI request field (e.g., as a response to transmission of the PUCCH beam report message) and may interpret the DCI as conveying an indication of a single UE-initiated beam report in a scheduled uplink resource. In this case, the CSI request field may be associated with a single trigger state and the single trigger state may be associated with a plurality of CSI report configurations for the UE-initiated beam report, but only a single CSI report configuration may be enabled for the UE-initiated beam report.

Accordingly, the UE 120 may select the single, enabled CSI report configuration associated with the indicated trigger state for determining a configuration of a transmission of a CSI beam report. In a scenario in which a plurality of events have been detected, the UE 120 may associate the single CSI report configuration with an event that has a highest priority (or in accordance with a default association, such as an event with a lowest index value) . Additionally, or alternatively, the UE 120 may receive DCI indicating a configured number (e.g., a plurality) of UE-initiated beam reports are to be transmitted in a scheduled uplink resource. In this case, the configured number of CSI report configurations may be enabled and associated with the single trigger state. In the scenario in which a plurality of events have been detected, the UE 120 may associate the configured number of CSI report configurations with the configured number of events (of the plurality of events) .

In some aspects, the UE 120 (and the network node 110) may be configured with a mapping between CSI report configurations and events for UE-initiated beam reporting. For example, the UE 120 may use a one-to-one mapping in which one CSI report configuration is associated with only one event. In this case, the UE 120 may report a CSI report configuration identifier in a CSI report to identify a detected event. Additionally, or alternatively, the UE 120 may use a one-to-many mapping in which one CSI reporting configuration is associated with a plurality of events. In this case, a maximum number M of events that can be associated with a single CSI reporting configuration may be a network node 110 configured value or based on a UE capability. In some aspects, when using a one-to-many mapping, the UE 120 may generate a beam report with an explicit event identifier and CSI report configuration identifier. In this case, the event identifier may be a value in a range of 0 to M –1, which is specific to a CSI report configuration. Additionally, or alternatively, the UE 120 may report one or more event identifiers and a CSI report configuration identifier. In this case, the UE 120 may include a bitmap of length M, with a bit set to 1 indicating which event is detected for the CSI report configuration. In some aspects, the UE 120 may report one or more event identifiers, but may omit reporting of a CSI report configuration identifier. For example, the UE 120 may include a globally unique event identifier (e.g., each event identifier is unique across a plurality of possible CSI report configuration identifiers) , such that the network node 110 may determine the event and the report configuration based on the globally unique event identifier.

In some aspects, the UE 120 may determine a UCI configuration for a UE-initiated beam report in a scheduled uplink resource. For example, the UE 120 may apply, for each event that is to be reported in a scheduled uplink resource, a UCI configuration. In some aspects, the UCI configuration may specify a CSI reporting format. For example, the UE 120 may determine, based on the DCI, a UCI configuration of a maximum number of reference signals that are to be reported in a scheduled uplink resource. Additionally, or alternatively, the UE 120 may determine a maximum number of metrics that are to be reported. Accordingly, if an event is associated with, for example, 4 reference signals or metrics and the DCI indicates reporting of 2 reference signals or metrics, the UE 120 may generate a beam report that identifies only 2 reference signals or metrics of the 4 reference signals or metrics (e.g., a first 2 reference signals or metrics or a best 2 references signals or metrics) . Alternatively, if an event is associated with, for example, 2 reference signals or metrics and the DCI indicates reporting of 4 reference signals or metrics, the UE 120 may generate a beam report that identifies the 2 reference signals or metrics and includes padding bits to have a size of 4 reference signals or metrics.

In some aspects, the UE 120 may determine a UCI configuration of a CSI reporting payload size based on the DCI. For example, the UE 120 may determine a maximum size of CSI reporting payload or a maximum number of UE-initiated CSI reports of a reference CSI reporting formats. In this case, if an event is to trigger reporting with 44 bits and the DCI selects only 11 bits, the UE 120 may report only 11 bits (e.g., a first 11 bits) . Alternatively, if an event is to trigger reporting with 11 bits and the DCI selects 44 bits, the UE 120 may add 33 padding bits to the 11 bits associated with the event. In a scenario in which there are a plurality of events of reporting, the UE 120 may apply the maximum size separately to each event that is to be reported in the same CSI report. Alternatively, the UE 120 may apply the maximum size jointly to each event that is to be reported in the same CSI report.

In some aspects, the UE 120 may determine the UCI configuration for a scheduled UL resource based on a default configuration. For example, the UE 120 may determine the UCI configuration based on a reference CSI reporting format. In this case, the default configuration may identify a configured content for beam reporting, such as the UE 120 being configured to report a carrier identifier (e.g., a CC identifier, an event identifier, a report configuration identifier, a reference signal identifier, and a reference signal metric, among other examples) . Additionally, or alternatively, the UE 120 may receive RRC signaling identifying a configuration, such as on a per BWP or per carrier basis. In this case, each BWP or carrier may have a different UCI configuration and the UE 120 may select a UCI configuration for generating a beam report based on a BWP or carrier on which the beam reporting is to be conveyed. Additionally, or alternatively, the UE 120 may determine the UCI configuration based on the received DCI. For example, the DCI may indicate one or more parameters of the UCI configuration. Additionally, or alternatively, the DCI may select a UCI configuration from a plurality of possible UCI configurations. For example, the UE 120 may be configured with a plurality of UCI configurations (e.g., via RRC signaling) and may receive DCI that includes a codepoint associating with indicating a UCI configuration of the plurality of UCI configurations.

In some aspects, a measurement of a reference signal may map to a configured carrier (e.g., for cross-carrier beam reporting) . For example, the UE 120 and/or the network node 110 may be configured such that measurement of a downlink reference signal associated with a single report configuration is to be from only a single CC or is to be from one or more CCs. Additionally, or alternatively, the UE 120 and/or the network node 110 may be configured such that measurement of a downlink reference signal associated with a single event is to be from a single CC or is to be from one or more CCs.

As further shown in Fig. 5, and by reference number 540, the UE 120 and/or the network node 110 may perform one or more beam management operations. For example, the UE 120 may transmit a UE-initiated beam report in a scheduled uplink resource in accordance with the DCI (and a UCI configuration determined based on the DCI) . Additionally, or alternatively, the network node 110 may, based on receiving the UE-initiated beam report, select or refine a beam for subsequent communications.

As indicated above, Fig. 5 is provided as an example. Other examples may differ from what is described with respect to Fig. 5.

Fig. 6 is a diagram illustrating an example process 600 performed, for example, at a UE or an apparatus of a UE, in accordance with the present disclosure. Example process 600 is an example where the apparatus or the UE (e.g., UE 120) performs operations associated with UE-initiated beam reporting.

As shown in Fig. 6, in some aspects, process 600 may include transmitting, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS (block 610) . For example, the UE (e.g., using transmission component 804 and/or communication manager 806, depicted in Fig. 8) may transmit, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS, as described above. In some aspects, the operation of block 610 may be performed by the transmission component 804 of the Fig. 8.

As further shown in Fig. 6, in some aspects, process 600 may include receiving, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered (block 620) . For example, the UE (e.g., using reception component 802 and/or communication manager 806, depicted in Fig. 8) may receive, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered, as described above. In some aspects, the operation of block 620 may be performed by the reception component 802 of the Fig. 8.

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

In a first aspect, process 600 includes performing a CSI reporting operation associated with the UE-initiated beam report and in accordance with the CSI request field.

In a second aspect, alone or in combination with the first aspect, the CSI request field includes a CSI request codepoint value that maps to the UE-initiated beam report.

In a third aspect, alone or in combination with one or more of the first and second aspects, the CSI request field includes an indication of a CSI trigger state associated with the UE-initiated beam report.

In a fourth aspect, alone or in combination with one or more of the first through third aspects, the CSI request field includes an indication for a CSI report configuration associated with the UE-initiated beam report.

In a fifth aspect, alone or in combination with one or more of the first through fourth aspects, the CSI request field includes an indication of a single UE-initiated beam report associated with a scheduled uplink resource.

In a sixth aspect, alone or in combination with one or more of the first through fifth aspects, the CSI request field includes an indication of a number of UE-initiated beam reports associated with a scheduled uplink resource.

In a seventh aspect, alone or in combination with one or more of the first through sixth aspects, a UCI configuration for the UE-initiated beam report scheduled in an uplink resource is associated with a content of the CSI request field.

In an eighth aspect, alone or in combination with one or more of the first through seventh aspects, the UCI configuration is associated with a configured CSI reporting format.

In a ninth aspect, alone or in combination with one or more of the first through eighth aspects, the UCI configuration includes an indication of at least one of a maximum size of a CSI reporting payload, or a maximum number of UE-initiated CSI reports.

In a tenth aspect, alone or in combination with one or more of the first through ninth aspects, the UCI configuration includes at least one of a default configuration, a radio resource control configuration, or a downlink control information selection.

In an eleventh aspect, alone or in combination with one or more of the first through tenth aspects, a mapping of a CSI report configuration to the event associated with the UE-initiated beam report is on a one-to-one basis or a one-to-many basis.

In a twelfth aspect, alone or in combination with one or more of the first through eleventh aspects, the beam report message includes an indication of one or more event identifiers and one or more CSI report configuration identifiers.

In a thirteenth aspect, alone or in combination with one or more of the first through twelfth aspects, the beam report message includes an indication of one or more event identifiers, wherein each event identifier, of the one or more event identifiers, is unique across a plurality of different CSI report configuration identifiers.

In a fourteenth aspect, alone or in combination with one or more of the first through thirteenth aspects, the beam report message includes a multi-bit indicator associated with a number of detected events associated with the UE-initiated beam reporting, wherein the multi-bit indicator identifies the number of detected events with respect to two threshold values.

In a fifteenth aspect, alone or in combination with one or more of the first through fourteenth aspects, the beam report message includes a multi-bit indicator associated with a type of detected event associated with the UE-initiated beam reporting.

In a sixteenth aspect, alone or in combination with one or more of the first through fifteenth aspects, the beam report message includes a multi-bit indicator associated with an event identifier or a carrier identifier associated with a detected event for the UE-initiated beam reporting.

In a seventeenth aspect, alone or in combination with one or more of the first through sixteenth aspects, the event for which the UE-initiated beam reporting is triggered is configured based at least in part on a default configuration or a received configuration.

In an eighteenth aspect, alone or in combination with one or more of the first through seventeenth aspects, a parameter relating to the event for which the UE-initiated beam reporting is triggered is configured based at least in part on a default configuration or a received configuration, and the parameter is configured on at least one of a per carrier basis, a per event basis, or a per CSI report configuration basis.

In a nineteenth aspect, alone or in combination with one or more of the first through eighteenth aspects, each event or report configuration associated with the UE-initiated beam reporting is associated with a single carrier or a plurality of carriers.

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

Fig. 7 is a diagram illustrating an example process 700 performed, for example, at a network node or an apparatus of a network node, in accordance with the present disclosure. Example process 700 is an example where the apparatus or the network node (e.g., network node 110) performs operations associated with UE-initiated beam reporting.

As shown in Fig. 7, in some aspects, process 700 may include receiving, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS (block 710) . For example, the network node (e.g., using reception component 902 and/or communication manager 906, depicted in Fig. 9) may receive, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS, as described above. In some aspects, the operation of block 710 may be performed by the reception component 902 of the Fig. 9.

As further shown in Fig. 7, in some aspects, process 700 may include transmitting, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered (block 720) . For example, the network node (e.g., using transmission component 904 and/or communication manager 906, depicted in Fig. 9) may transmit, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered, as described above. In some aspects, the operation of block 720 may be performed by the transmission component 904 of the Fig. 9.

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

In a first aspect, process 700 includes performing a CSI reporting operation associated with the UE-initiated beam report and in accordance with the CSI request field.

Although Fig. 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 Fig. 7. Additionally, or alternatively, two or more of the blocks of process 700 may be performed in parallel.

Fig. 8 is a diagram of an example apparatus 800 for wireless communication, in accordance with the present disclosure. The apparatus 800 may be a UE, or a UE may include the apparatus 800. In some aspects, the apparatus 800 includes a reception component 802, a transmission component 804, and/or a communication manager 806, which may be in communication with one another (for example, via one or more buses and/or one or more other components) . In some aspects, the communication manager 806 is the communication manager 140 described in connection with Fig. 1. As shown, the apparatus 800 may communicate with another apparatus 808, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 802 and the transmission component 804.

In some aspects, the apparatus 800 may be configured to perform one or more operations described herein in connection with Fig. 5. Additionally, or alternatively, the apparatus 800 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6, process 700 of Fig. 7, or a combination thereof. In some aspects, the apparatus 800 and/or one or more components shown in Fig. 8 may include one or more components of the UE described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 8 may be implemented within one or more components described in connection with Fig. 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 802 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 808. The reception component 802 may provide received communications to one or more other components of the apparatus 800. In some aspects, the reception component 802 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 of the apparatus 800. In some aspects, the reception component 802 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, one or more memories, or a combination thereof, of the UE described in connection with Fig. 2.

The transmission component 804 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 808. In some aspects, one or more other components of the apparatus 800 may generate communications and may provide the generated communications to the transmission component 804 for transmission to the apparatus 808. In some aspects, the transmission component 804 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 808. In some aspects, the transmission component 804 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, one or more memories, or a combination thereof, of the UE described in connection with Fig. 2. In some aspects, the transmission component 804 may be co-located with the reception component 802 in one or more transceivers.

The communication manager 806 may support operations of the reception component 802 and/or the transmission component 804. For example, the communication manager 806 may receive information associated with configuring reception of communications by the reception component 802 and/or transmission of communications by the transmission component 804. Additionally, or alternatively, the communication manager 806 may generate and/or provide control information to the reception component 802 and/or the transmission component 804 to control reception and/or transmission of communications.

The transmission component 804 may transmit, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS. The reception component 802 may receive, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered. The communication manager 806 may perform a CSI reporting operation associated with the UE-initiated beam report and in accordance with the CSI request field.

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

Fig. 9 is a diagram of an example apparatus 900 for wireless communication, in accordance with the present disclosure. The apparatus 900 may be a network node, or a network node may include the apparatus 900. In some aspects, the apparatus 900 includes a reception component 902, a transmission component 904, and/or a communication manager 906, which may be in communication with one another (for example, via one or more buses and/or one or more other components) . In some aspects, the communication manager 906 is the communication manager 150 described in connection with Fig. 1. As shown, the apparatus 900 may communicate with another apparatus 908, such as a UE or a network node (such as a CU, a DU, an RU, or a base station) , using the reception component 902 and the transmission component 904.

In some aspects, the apparatus 900 may be configured to perform one or more operations described herein in connection with Fig. 5. Additionally, or alternatively, the apparatus 900 may be configured to perform one or more processes described herein, such as process 600 of Fig. 6, process 700 of Fig. 7, or a combination thereof. In some aspects, the apparatus 900 and/or one or more components shown in Fig. 9 may include one or more components of the network node described in connection with Fig. 2. Additionally, or alternatively, one or more components shown in Fig. 9 may be implemented within one or more components described in connection with Fig. 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 902 may receive communications, such as reference signals, control information, data communications, or a combination thereof, from the apparatus 908. The reception component 902 may provide received communications to one or more other components of the apparatus 900. In some aspects, the reception component 902 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 of the apparatus 900. In some aspects, the reception component 902 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, one or more memories, or a combination thereof, of the network node described in connection with Fig. 2. In some aspects, the reception component 902 and/or the transmission component 904 may include or may be included in a network interface. The network interface may be configured to obtain and/or output signals for the apparatus 900 via one or more communications links, such as a backhaul link, a midhaul link, and/or a fronthaul link.

The transmission component 904 may transmit communications, such as reference signals, control information, data communications, or a combination thereof, to the apparatus 908. In some aspects, one or more other components of the apparatus 900 may generate communications and may provide the generated communications to the transmission component 904 for transmission to the apparatus 908. In some aspects, the transmission component 904 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 908. In some aspects, the transmission component 904 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, one or more memories, or a combination thereof, of the network node described in connection with Fig. 2. In some aspects, the transmission component 904 may be co-located with the reception component 902 in one or more transceivers.

The communication manager 906 may support operations of the reception component 902 and/or the transmission component 904. For example, the communication manager 906 may receive information associated with configuring reception of communications by the reception component 902 and/or transmission of communications by the transmission component 904. Additionally, or alternatively, the communication manager 906 may generate and/or provide control information to the reception component 902 and/or the transmission component 904 to control reception and/or transmission of communications.

The reception component 902 may receive, on a PUCCH, a beam report message triggering a UE-initiated beam report identifying a measurement of a CSI-RS. The transmission component 904 may transmit, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered. The communication manager 906 may perform a CSI reporting operation associated with the UE-initiated beam report and in accordance with the CSI request field.

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

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, on a physical uplink control channel (PUCCH) , a beam report message triggering a UE-initiated beam report identifying a measurement of a channel state information (CSI) reference signal (CSI-RS) ; and receiving, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.

Aspect 2: The method of Aspect 1, further comprising: performing a CSI reporting operation associated with the UE-initiated beam report and in accordance with the CSI request field.

Aspect 3: The method of any of Aspects 1-2, wherein the CSI request field includes a CSI request codepoint value that maps to the UE-initiated beam report.

Aspect 4: The method of any of Aspects 1-3, wherein the CSI request field includes an indication of a CSI trigger state associated with the UE-initiated beam report.

Aspect 5: The method of any of Aspects 1-4, wherein the CSI request field includes an indication for a CSI report configuration associated with the UE-initiated beam report.

Aspect 6: The method of any of Aspects 1-5, wherein the CSI request field includes an indication of a single UE-initiated beam report associated with a scheduled uplink resource.

Aspect 7: The method of any of Aspects 1-6, wherein the CSI request field includes an indication of a number of UE-initiated beam reports associated with a scheduled uplink resource.

Aspect 8: The method of any of Aspects 1-7, wherein an uplink control information (UCI) configuration for the UE-initiated beam report scheduled in an uplink resource is associated with a content of the CSI request field.

Aspect 9: The method of Aspect 8, wherein the UCI configuration is associated with a configured CSI reporting format.

Aspect 10: The method of Aspect 8, wherein the UCI configuration includes an indication of at least one of: a maximum size of a CSI reporting payload, or a maximum number of UE-initiated CSI reports.

Aspect 11: The method of Aspect 8, wherein the UCI configuration includes at least one of: a default configuration, a radio resource control configuration, or a downlink control information selection.

Aspect 12: The method of any of Aspects 1-11, wherein a mapping of a CSI report configuration to the event associated with the UE-initiated beam report is on a one-to-one basis or a one-to-many basis.

Aspect 13: The method of any of Aspects 1-12, wherein the beam report message includes an indication of one or more event identifiers and one or more CSI report configuration identifiers.

Aspect 14: The method of any of Aspects 1-13, wherein the beam report message includes an indication of one or more event identifiers, wherein each event identifier, of the one or more event identifiers, is unique across a plurality of different CSI report configuration identifiers.

Aspect 15: The method of any of Aspects 1-14, wherein the beam report message includes a multi-bit indicator associated with a number of detected events associated with the UE-initiated beam reporting, wherein the multi-bit indicator identifies the number of detected events with respect to two threshold values.

Aspect 16: The method of any of Aspects 1-15, wherein the beam report message includes a multi-bit indicator associated with a type of detected event associated with the UE-initiated beam reporting.

Aspect 17: The method of any of Aspects 1-16, wherein the beam report message includes a multi-bit indicator associated with an event identifier or a carrier identifier associated with a detected event for the UE-initiated beam reporting.

Aspect 18: The method of any of Aspects 1-17, wherein the event for which the UE-initiated beam reporting is triggered is configured based at least in part on a default configuration or a received configuration.

Aspect 19: The method of any of Aspects 1-18, wherein a parameter relating to the event for which the UE-initiated beam reporting is triggered is configured based at least in part on a default configuration or a received configuration, and wherein the parameter is configured on at least one of: a per carrier basis, a per event basis, or a per CSI report configuration basis.

Aspect 20: The method of any of Aspects 1-19, wherein each event or report configuration associated with the UE-initiated beam reporting is associated with a single carrier or a plurality of carriers.

Aspect 21: A method of wireless communication performed by a network node, comprising: receiving, on a physical uplink control channel (PUCCH) , a beam report message triggering a UE-initiated beam report identifying a measurement of a channel state information (CSI) reference signal (CSI-RS) ; and transmitting, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.

Aspect 22: The method of Aspect 21, further comprising: performing a CSI reporting operation associated with the UE-initiated beam report and in accordance with the CSI request field.

Aspect 23: The method of any of Aspects 21-22, wherein the CSI request field includes a CSI request codepoint value that maps to the UE-initiated beam report.

Aspect 24: The method of any of Aspects 21-23, wherein the CSI request field includes an indication of a CSI trigger state associated with the UE-initiated beam report.

Aspect 25: The method of any of Aspects 21-24, wherein the CSI request field includes an indication for a CSI report configuration associated with the UE-initiated beam report.

Aspect 26: The method of any of Aspects 21-25, wherein the CSI request field includes an indication of a single UE-initiated beam report associated with a scheduled uplink resource.

Aspect 27: The method of any of Aspects 21-26, wherein the CSI request field includes an indication of a number of UE-initiated beam reports associated with a scheduled uplink resource.

Aspect 28: The method of any of Aspects 21-27, wherein an uplink control information (UCI) configuration for the UE-initiated beam report scheduled in an uplink resource is associated with a content of the CSI request field.

Aspect 29: The method of Aspect 28, wherein the UCI configuration is associated with a configured CSI reporting format.

Aspect 30: The method of Aspect 28, wherein the UCI configuration includes an indication of at least one of: a maximum size of a CSI reporting payload, or a maximum number of UE-initiated CSI reports.

Aspect 31: The method of Aspect 28, wherein the UCI configuration includes at least one of: a default configuration, a radio resource control configuration, or a downlink control information selection.

Aspect 32: The method of any of Aspects 21-31, wherein a mapping of a CSI report configuration to the event associated with the UE-initiated beam report is on a one-to-one basis or a one-to-many basis.

Aspect 33: The method of any of Aspects 21-32, wherein the beam report message includes an indication of one or more event identifiers and one or more CSI report configuration identifiers.

Aspect 34: The method of any of Aspects 21-33, wherein the beam report message includes an indication of one or more event identifiers, wherein each event identifier, of the one or more event identifiers, is unique across a plurality of different CSI report configuration identifiers.

Aspect 35: The method of any of Aspects 21-34, wherein the beam report message includes a multi-bit indicator associated with a number of detected events associated with the UE-initiated beam reporting, wherein the multi-bit indicator identifies the number of detected events with respect to two threshold values.

Aspect 36: The method of any of Aspects 21-35, wherein the beam report message includes a multi-bit indicator associated with a type of detected event associated with the UE-initiated beam reporting.

Aspect 37: The method of any of Aspects 21-36, wherein the beam report message includes a multi-bit indicator associated with an event identifier or a carrier identifier associated with a detected event for the UE-initiated beam reporting.

Aspect 38: The method of any of Aspects 21-37, wherein the event for which the UE-initiated beam reporting is triggered is configured based at least in part on a default configuration or a received configuration.

Aspect 39: The method of any of Aspects 21-38, wherein a parameter relating to the event for which the UE-initiated beam reporting is triggered is configured based at least in part on a default configuration or a received configuration, and wherein the parameter is configured on at least one of: a per carrier basis, a per event basis, or a per CSI report configuration basis.

Aspect 40: The method of any of Aspects 21-39, wherein each event or report configuration associated with the UE-initiated beam reporting is associated with a single carrier or a plurality of carriers.

Aspect 41: 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-40.

Aspect 42: 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-40.

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

Aspect 44: 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-40.

Aspect 45: 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-40.

Aspect 46: 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-40.

Aspect 47: 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-40.

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, firmware, or a combination of hardware and software. As used herein, a processor is implemented in hardware, firmware, or a combination of hardware and software. As used herein, the phrase “based on” is intended to be broadly construed to mean “based at least in part on. ” 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, 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.

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 (for example, related items, unrelated items, or a combination of related and unrelated 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 also may have B) . Further, 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” ) .

The various illustrative logics, logical blocks, modules, circuits and algorithm processes described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. The interchangeability of hardware and software has been described generally, in terms of functionality, and illustrated in the various illustrative components, blocks, modules, circuits and processes described herein. Whether such functionality is implemented in hardware or software depends upon the application and design constraints imposed on the overall system.

The hardware and data processing apparatus used to implement the various illustrative logics, logical blocks, modules and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose single-or multi-chip processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some aspects, processes and methods may be performed by circuitry that is specific to a given function.

In one or more aspects, the functions described may be implemented in hardware, digital electronic circuitry, computer software, firmware, including the structures disclosed in this specification and their structural equivalents thereof, or in any combination thereof. Aspects of the subject matter described in this specification also can be implemented as one or more computer programs (such as one or more modules of computer program instructions) encoded on a computer storage media for execution by, or to control the operation of, a data processing apparatus.

If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. The processes of a method or algorithm disclosed herein may be implemented in a processor-executable software module which may reside on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that can be enabled to transfer a computer program from one place to another. A storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer. Also, any connection can be properly termed a computer-readable medium. Disk and disc, as used herein, includes compact disc (CD) , laser disc, optical disc, digital versatile disc (DVD) , floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the media described herein should also be included within the scope of computer-readable media. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and instructions on a machine readable medium and computer-readable medium, which may be incorporated into a computer program product.

Various modifications to the aspects described in this disclosure may be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the spirit or scope of this disclosure. Thus, the claims are not intended to be limited to the aspects shown herein, but are to be accorded the widest scope consistent with this disclosure, the principles and the novel features disclosed herein.

Additionally, a person having ordinary skill in the art will readily appreciate, the terms “upper” and “lower” are sometimes used for ease of describing the figures, and indicate relative positions corresponding to the orientation of the figure on a properly oriented page, and may not reflect the proper orientation of any device as implemented.

Certain features that are described in this specification in the context of separate aspects also can be implemented in combination in a single aspect. Conversely, various features that are described in the context of a single aspect also can be implemented in multiple aspects separately or in any suitable subcombination. Moreover, although features may be described as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in an order, this should not be understood as requiring that such operations be performed in the order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. Further, the drawings may schematically depict one more example processes in the form of a flow diagram. However, other operations that are not depicted can be incorporated in the example processes that are schematically illustrated. For example, one or more additional operations can be performed before, after, simultaneously, or between any of the illustrated operations. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the aspects described should not be understood as requiring such separation in all aspects, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products. Additionally, other aspects are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results.

Claims

A user equipment (UE) for wireless communication, comprising:

one or more memories; and

one or more processors, coupled to the one or more memories, individually or collectively configured to cause the UE to:

transmit, on a physical uplink control channel (PUCCH) , a beam report message triggering a UE-initiated beam report identifying a measurement of a channel state information (CSI) reference signal (CSI-RS) ; and

receive, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.
The UE of claim 1, wherein the one or more processors are further configured to cause the UE to:

perform a CSI reporting operation associated with the UE-initiated beam report and in accordance with the CSI request field.
The UE of claim 1, wherein the CSI request field includes a CSI request codepoint value that maps to the UE-initiated beam report.
The UE of claim 1, wherein the CSI request field includes an indication of a CSI trigger state associated with the UE-initiated beam report.
The UE of claim 1, wherein the CSI request field includes an indication for a CSI report configuration associated with the UE-initiated beam report.
The UE of claim 1, wherein the CSI request field includes an indication of a single UE-initiated beam report associated with a scheduled uplink resource.
The UE of claim 1, wherein the CSI request field includes an indication of a number of UE-initiated beam reports associated with a scheduled uplink resource.
The UE of claim 1, wherein an uplink control information (UCI) configuration for the UE-initiated beam report scheduled in an uplink resource is associated with a content of the CSI request field.
The UE of claim 8, wherein the UCI configuration is associated with a configured CSI reporting format.
The UE of claim 8, wherein the UCI configuration includes an indication of at least one of:

a maximum size of a CSI reporting payload, or

a maximum number of UE-initiated CSI reports.
The UE of claim 8, wherein the UCI configuration includes at least one of:

a default configuration,

a radio resource control configuration, or

a downlink control information selection.
The UE of claim 1, wherein a mapping of a CSI report configuration to the event associated with the UE-initiated beam report is on a one-to-one basis or a one-to-many basis.
The UE of claim 1, wherein the beam report message includes an indication of one or more event identifiers and one or more CSI report configuration identifiers.
The UE of claim 1, wherein the beam report message includes an indication of one or more event identifiers, wherein each event identifier, of the one or more event identifiers, is unique across a plurality of different CSI report configuration identifiers.
The UE of claim 1, wherein the beam report message includes a multi-bit indicator associated with a number of detected events associated with the UE-initiated beam reporting,

wherein the multi-bit indicator identifies the number of detected events with respect to two threshold values.
The UE of claim 1, wherein the beam report message includes a multi-bit indicator associated with a type of detected event associated with the UE-initiated beam reporting.
The UE of claim 1, wherein the beam report message includes a multi-bit indicator associated with an event identifier or a carrier identifier associated with a detected event for the UE-initiated beam reporting.
The UE of claim 1, wherein the event for which the UE-initiated beam reporting is triggered is configured based at least in part on a default configuration or a received configuration.
A network node for wireless communication, comprising:

one or more memories; and

one or more processors, coupled to the one or more memories, individually or collectively configured to cause the network node to:

receive, on a physical uplink control channel (PUCCH) , a beam report message triggering a UE-initiated beam report identifying a measurement of a channel state information (CSI) reference signal (CSI-RS) ; and

transmit, as a response to receiving the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.
A method of wireless communication performed by a user equipment (UE) , comprising:

transmitting, on a physical uplink control channel (PUCCH) , a beam report message triggering a UE-initiated beam report identifying a measurement of a channel state information (CSI) reference signal (CSI-RS) ; and

receiving, as a response to transmitting the beam report message, downlink control information conveying a CSI request field associated with an identification of an event for which the UE-initiated beam report is triggered.