Reference signal set configuration for event-driven channel state information report
Event-driven CSI reporting with separate RS sets for serving and non-serving beams addresses high overhead and inaccurate beam measurements, enhancing network performance through optimized and timely beam reporting.
Patent Information
- Application Number
- PCT/CN2024/085748
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-04-03
- Publication Date
- 2025-10-09
AI Technical Summary
Existing wireless communication systems face high signaling overhead and potential beam measurement inaccuracies due to frequent CSI reporting or infrequent beam reporting, leading to network performance degradation.
Configuring user equipment (UE) with event-driven CSI reporting using separate RS sets for serving and non-serving beams to detect triggering events, allowing timely and optimized beam reporting.
Reduces reporting overhead and latency while ensuring timely beam measurements, improving network performance by enabling more accurate and efficient beam management.
Smart Images

Figure CN2024085748_09102025_PF_FP_ABST
Abstract
Description
REFERENCE SIGNAL SET CONFIGURATION FOR EVENT-DRIVEN CHANNEL STATE INFORMATION REPORT
[0001] FIELD OF THE DISCLOSURE
[0002] Aspects of the present disclosure generally relate to wireless communication and specifically relate to techniques, apparatuses, and methods associated with reference signal set configuration for an event-driven channel state information report.BACKGROUND
[0003] 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.
[0004] The above multiple-access RATs have been adopted in various telecommunication standards to provide common protocols that enable different wireless communication devices to communicate on a municipal, national, regional, or global level. An example telecommunication standard is New Radio (NR) . NR, which may also be referred to as 5G, is part of a continuous mobile broadband evolution promulgated by the Third Generation Partnership Project (3GPP) . NR (and other mobile broadband evolutions beyond NR) may be designed to better support Internet of things (IoT) and reduced capability device deployments, industrial connectivity, millimeter wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployment, sidelink and other device-to-device direct communication technologies (for example, cellular vehicle-to-everything (CV2X) communication) , massive multiple-input multiple-output (MIMO) , disaggregated network architectures and network topology expansions, multiple-subscriber implementations, high-precision positioning, and / or radio frequency (RF) sensing, among other examples. As the demand for mobile broadband access continues to increase, further improvements in NR may be implemented, and other radio access technologies such as 6G may be introduced, to further advance mobile broadband evolution.
[0005] In some wireless communication networks, a network node may configure a user equipment (UE) to perform certain measurements and provide reports of the measurements, such as for a purpose of beam selection by the UE and / or the network node. For example, the network node may configure the UE to perform measurements using one or more channel state information (CSI) reference signal (CSI-RS) resources, among other examples, and / or to report the measurements using one or more CSI reports. In some examples, such as examples in which the UE is configured to provide semi-persistent and / or periodic CSI reports for numerous beams, providing the various CSI reports may result in high signaling overhead and / or colliding CSI reports (for example, multiple CSI reports scheduled to be transmitted in uplink resources in which at least one orthogonal frequency division multiplexing (OFDM) symbol overlaps) . Additionally or alternatively, for aperiodic CSI reporting, a network node may separately request each CSI report, resulting in the network node and / or the UE consuming significant signaling resources. On the other hand, if less frequent beam reporting is configured at the UE, the network node may not be provided with timely beam measurements and / or the network node may be provided with outdated beam measurements, resulting in network performance degradation.SUMMARY
[0006] Some aspects described herein relate to a user equipment (UE) for wireless communication. The UE may include a processing system that includes one or more processors and one or more memories coupled with the one or more processors. The processing system may be configured to cause the UE to receive, from a network node, configuration information for an event-driven channel state information (CSI) report, the configuration information indicating at least one of a first reference signal (RS) set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The processing system may be configured to cause the UE to transmit, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0007] Some aspects described herein relate to a network node for wireless communication. The network node may include a processing system that includes one or more processors and one or more memories coupled with the one or more processors. The processing system may be configured to cause the network node to transmit, to a UE, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The processing system may be configured to cause the network node to receive, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0008] Some aspects described herein relate to a method of wireless communication by a UE. The method may include receiving, from a network node, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The method may include transmitting, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0009] Some aspects described herein relate to a method of wireless communication by a network node. The method may include transmitting, to a UE, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The method may include receiving, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0010] 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 receive, from a network node, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The set of instructions, when executed by one or more processors of the UE, may cause the UE to transmit, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0011] 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 transmit, to a UE, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The set of instructions, when executed by one or more processors of the network node, may cause the network node to receive, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0012] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for receiving, from a network node, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The apparatus may include means for transmitting, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0013] Some aspects described herein relate to an apparatus for wireless communication. The apparatus may include means for transmitting, to a UE, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The apparatus may include means for receiving, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0014] 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.
[0015] 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
[0016] 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.
[0017] Figure 1 is a diagram illustrating an example of a wireless communication network in accordance with the present disclosure.
[0018] Figure 2 is a diagram illustrating an example network node in communication with an example user equipment (UE) in a wireless network in accordance with the present disclosure.
[0019] Figure 3 is a diagram illustrating an example disaggregated base station architecture in accordance with the present disclosure.
[0020] Figure 4 is a diagram illustrating examples of channel state information (CSI) reference signal (CSI-RS) beam management procedures in accordance with the present disclosure.
[0021] Figure 5 is a diagram illustrating an example associated with reference signal (RS) set configuration for an event-driven CSI report in accordance with the present disclosure.
[0022] Figure 6 is a flowchart illustrating an example process performed, for example, at a UE or an apparatus of a UE that supports RS set configuration for an event-driven CSI report in accordance with the present disclosure.
[0023] Figure 7 is a flowchart illustrating an example process performed, for example, at a network node or an apparatus of a network node that supports RS set configuration for an event-driven CSI report in accordance with the present disclosure.
[0024] Figure 8 is a diagram of an example apparatus for wireless communication that supports RS set configuration for an event-driven CSI report in accordance with the present disclosure.
[0025] Figure 9 is a diagram of an example apparatus for wireless communication that supports RS set configuration for an event-driven CSI report in accordance with the present disclosure.DETAILED DESCRIPTION
[0026] Various aspects of the present disclosure are described hereinafter with reference to the accompanying drawings. However, aspects of the present disclosure may be embodied in many different forms and is not to be construed as limited to any specific aspect illustrated by or described with reference to an accompanying drawing or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art. One skilled in the art may appreciate that the scope of the disclosure is intended to cover any aspect of the disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of the disclosure. For example, an apparatus may be implemented or a method may be practiced using various combinations or quantities of the aspects set forth herein. In addition, the scope of the disclosure is intended to cover an apparatus having, or a method that is practiced using, other structures and / or functionalities in addition to or other than the structures and / or functionalities with which various aspects of the disclosure set forth herein may be practiced. Any aspect of the disclosure disclosed herein may be embodied by one or more elements of a claim.
[0027] Several aspects of telecommunication systems will now be presented with reference to various methods, operations, apparatuses, and techniques. These methods, operations, apparatuses, and techniques will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, modules, components, circuits, steps, processes, or algorithms (collectively referred to as “elements” ) . These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
[0028] In some examples, a user equipment (UE) may be configured to transmit one or more channel state information (CSI) reports based at least in part on the UE identifying that some condition has been satisfied and / or that a certain event has taken place. In some examples, configuring a UE to transmit one or more CSI reports based at least in part on the UE identifying that some condition has been satisfied and / or that a certain event has taken place may be referred to as “UE-initiated CSI reporting” and / or “event-driven CSI reporting, ” and thus the one or more CSI reports transmitted by the UE in such scenarios may be referred to as “UE-initiated CSI reports” and / or “event-driven CSI reports. ” In some examples, triggering events for triggering event-driven CSI reports may be based on or otherwise associated with measurements (for example, layer 1 (L1) reference signal received power (RSRP) measurements) on one or more current beams (for example, serving beams) and / or measurements on one or more new beams (for example, non-serving beams) . Configuring a UE to transmit one or more event-driven CSI reports may result in beam reporting optimization, because a UE may provide timely beam reports to a network node with reduced reporting overhead. Put another way, because in some examples the UE may have better and / or more timely knowledge of beam quality changes, a UE-initiated beam reporting procedure may result in more timely beam reports and reduced reporting overhead. For example, when a UE determines that one or more current beams have become poor, the UE can trigger beam reporting, without the network needing to configure and / or trigger frequent reporting.
[0029] In some examples, a CSI report framework (for example, for a periodic, semi-persistent, or aperiodic CSI report) , may define a single CSI resource as a channel measurement resource (CMR) , for which the UE measures the channel status and generates the CSI report accordingly. In addition to the CMR, a CSI resource for interference management (for example, an interference management resource (IMR) ) may be optionally configured. However, such a CSI report framework does not specify resources to be measured for detecting a triggering event for an event-driven CSI report. Furthermore, the single CSI resource configuration in such a CSI report framework cannot be used to specify different groups of reference signals (RSs) to be used for serving beam and non-serving beam measurements, which may be required for some event-driven CSI report triggering events.
[0030] Various aspects relate generally to configuration of RS sets for event-driven CSI reports. Some aspects more specifically relate to configuring RS sets to be measured by a UE to detect a triggering event associated with an event-driven CSI report. In some aspects, a UE may receive, from a network node, configuration information for an event-driven CSI report. The configuration information may indicate a first RS set associated with one or more serving beams and / or a second RS set associated with one or more non-serving beams. The first RS set and / or the second RS set may indicate RSs to be used, by the UE, for detecting a triggering event associated with the event-driven CSI report. The UE may detect the triggering event based on or otherwise associated with measurements of RSs in the first RS set and / or the second RS set, and the UE may transmit, to the network node, an event-driven CSI report in connection with detecting the triggering event. In some examples, the configuration information may indicate both the first RS set and the second RS set, and the detection of the triggering event may be based on or otherwise associated with measurements of RSs in the first RS set and the second RS set.
[0031] Particular aspects of the subject matter described in this disclosure can be implemented to realize one or more of the following potential advantages. In some examples, by configuring the first RS set and / or the second RS set for detection of the triggering event, the described techniques can be used to configure resources to be measured for triggering an event-driven CSI report. In this way, the described techniques enable event-driven CSI reporting, resulting in more timely beam reporting and reduced reporting overhead and / or latency. In some examples, by indicating both the first RS set associated with one or more serving beams and the second RS set associated with one or more non-serving beams in the configuration information for the an event-driven CSI report, the described techniques can be used to enable an event-driven CSI reporting triggered by a triggering event that is based on or otherwise associated with measurements of one or more serving beams and one or more non-serving beams, which may result in reduced latency and / or signaling overhead for beam management procedures involving beam refinement and / or beam switching.
[0032] 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) .
[0033] 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.
[0034] Figure 1 is a diagram illustrating an example of a wireless communication network 100 in accordance with the present disclosure. The wireless communication network 100 may be or may include elements of a 5G (or NR) network or a 6G network, among other examples. The wireless communication network 100 may include multiple network nodes 110, shown as a network node (NN) 110a, a network node 110b, a network node 110c, and a network node 110d. The network nodes 110 may support communications with multiple UEs 120, shown as a UE 120a, a UE 120b, a UE 120c, a UE 120d, and a UE 120e.
[0035] The network nodes 110 and the UEs 120 of the wireless communication network 100 may communicate using the electromagnetic spectrum, which may be subdivided by frequency or wavelength into various classes, bands, carriers, and / or channels. For example, devices of the wireless communication network 100 may communicate using one or more operating bands. In some aspects, multiple wireless networks 100 may be deployed in a given geographic area. Each wireless communication network 100 may support a particular 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.
[0036] Various operating bands have been defined as frequency range designations FR1 (410 MHz through 7.125 GHz) , FR2 (24.25 GHz through 52.6 GHz) , FR3 (7.125 GHz through 24.25 GHz) , FR4a or FR4-1 (52.6 GHz through 71 GHz) , FR4 (52.6 GHz through 114.25 GHz) , and FR5 (114.25 GHz through 300 GHz) . Although a portion of FR1 is greater than 6 GHz, FR1 is often referred to (interchangeably) as a “Sub-6 GHz” band in some documents and articles. Similarly, FR2 is often referred to (interchangeably) as a “millimeter wave” band in some documents and articles, despite being different than the extremely high frequency (EHF) band (30 GHz through 300 GHz) , which is identified by the International Telecommunications Union (ITU) as a “millimeter wave” band. The frequencies between FR1 and FR2 are often referred to as mid-band frequencies, which include FR3. Frequency bands falling within FR3 may inherit FR1 characteristics or FR2 characteristics, and thus may effectively extend features of FR1 or FR2 into mid-band frequencies. Thus, “sub-6 GHz, ” if used herein, may broadly refer to frequencies that are less than 6 GHz, that are within FR1, and / or that are included in mid-band frequencies. Similarly, the term “millimeter wave, ” if used herein, may broadly refer to frequencies that are included in mid-band frequencies, that are within FR2, FR4, FR4-aor FR4-1, or FR5, and / or that are within the EHF band. Higher frequency bands may extend 5G NR operation, 6G operation, and / or other RATs beyond 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 may implement dynamic spectrum sharing (DSS) , in which multiple RATs (for example, 4G / LTE and 5G / NR) are implemented with dynamic bandwidth allocation (for example, based on user demand) in a single frequency band. It is contemplated that the frequencies included in these operating bands (for example, FR1, FR2, FR3, FR4, FR4-a, FR4-1, and / or FR5) may be modified, and techniques described herein may be applicable to those modified frequency ranges.
[0037] 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) .
[0038] 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.
[0039] 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.
[0040] 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.
[0041] 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.
[0042] Some network nodes 110 (for example, a base station, an RU, or a TRP) may provide communication coverage for a particular geographic area. In the 3GPP, the term “cell” can refer to a coverage area of a network node 110 or to a network node 110 itself, depending on the context in which the term is used. A network node 110 may support one or multiple (for example, three) cells. In some examples, a network node 110 may provide communication coverage for a macro cell, a pico cell, a femto cell, or another type of cell. A macro cell may cover a relatively large geographic area (for example, several kilometers in radius) and may allow unrestricted access by UEs 120 with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs 120 with service subscriptions. A femto cell may cover a relatively small geographic area (for example, a home) and may allow restricted access by UEs 120 having association with the femto cell (for example, UEs 120 in a closed subscriber group (CSG) ) . A network node 110 for a macro cell may be referred to as a macro network node. A network node 110 for a pico cell may be referred to as a pico network node. A network node 110 for a femto cell may be referred to as a femto network node or an in-home network node. 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 an NTN network node) .
[0043] The wireless communication network 100 may be a heterogeneous network that includes network nodes 110 of different types, such as macro network nodes, pico network nodes, femto network nodes, relay network nodes, aggregated network nodes, and / or disaggregated network nodes, among other examples. In the example shown in Figure 1, the network node 110a may be a macro network node for a macro cell 130a, the network node 110b may be a pico network node for a pico cell 130b, and the network node 110c may be a femto network node for a femto cell 130c. Various different types of network nodes 110 may generally transmit at different power levels, serve different coverage areas, and / or have different impacts on interference in the wireless communication network 100 than other types of network nodes 110. For example, macro network nodes may have a high transmit power level (for example, 5 to 40 watts) , whereas pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (for example, 0.1 to 2 watts) .
[0044] 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 downlink control information (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 physical uplink control channels (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.
[0045] Downlink and uplink resources may include time domain resources (frames, subframes, slots, and / or symbols) , frequency domain resources (frequency bands, component carriers, subcarriers, resource blocks, and / or resource elements) , and / or spatial domain resources (particular transmit directions and / or beam parameters) . Frequency domain resources of some bands may be subdivided into bandwidth parts (BWPs) . A BWP may be a continuous block of frequency domain resources (for example, a continuous block of resource blocks) that are allocated for one or more UEs 120. A UE 120 may be configured with both an uplink BWP and a downlink BWP (where the uplink BWP and the downlink BWP may be the same BWP or different BWPs) . A BWP may be dynamically configured (for example, by a network node 110 transmitting a DCI configuration to the one or more UEs 120) and / or reconfigured, which means that a BWP can be adjusted in real-time (or near-real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of the one or more UEs 120. This enables more efficient use of the available frequency domain resources in the wireless communication network 100 because fewer frequency domain resources may be allocated to a BWP for a UE 120 (which may reduce the quantity of frequency domain resources that a UE 120 is required to monitor) , leaving more frequency domain resources to be spread across multiple UEs 120. Thus, BWPs may also assist in the implementation of lower-capability UEs 120 by facilitating the configuration of smaller bandwidths for communication by such UEs 120.
[0046] 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.
[0047] In some examples, any network node 110 that relays communications may be referred to as a relay network node, a relay station, or simply as a relay. A relay may receive a transmission of a communication from an upstream station (for example, another network node 110 or a UE 120) and transmit the communication to a downstream station (for example, a UE 120 or another network node 110) . In this case, the wireless communication network 100 may include or be referred to as a “multi-hop network. ” In the example shown in Figure 1, the network node 110d (for example, a relay network node) may communicate with the network node 110a (for example, a macro network node) and the UE 120d in order to facilitate communication between the network node 110a and the UE 120d. Additionally or alternatively, a UE 120 may be or may operate as a relay station that can relay transmissions to or from other UEs 120. A UE 120 that relays communications may be referred to as a UE relay or a relay UE, among other examples.
[0048] 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.
[0049] 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.
[0050] 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.
[0051] 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) .
[0052] 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.
[0053] 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.
[0054] 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 particular time resources, such as during particular 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.
[0055] 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) .
[0056] In some aspects, the UE 120 may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may receive, from a network node, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams; and transmit, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set. Additionally, or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0057] 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 transmit, to a UE, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams; and receive, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set. Additionally, or alternatively, the communication manager 150 may perform one or more other operations described herein.
[0058] Figure 2 is a diagram illustrating an example network node 110 in communication with an example UE 120 in a wireless network in accordance with the present disclosure.
[0059] As shown in Figure 2, the network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a through 232t, where t ≥ 1) , a set of antennas 234 (shown as 234a through 234v, where v ≥ 1) , a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, a scheduler 246, and / or a communication manager 150, among other examples. In some configurations, one or a combination of the antenna (s) 234, the modem (s) 232, the MIMO detector 236, the receive processor 238, the transmit processor 214, and / or the TX MIMO processor 216 may be included in a transceiver of the network node 110. The transceiver may be under control of and used by one or more processors, such as the controller / processor 240, and in some aspects in conjunction with processor-readable code stored in the memory 242, to perform aspects of the methods, processes, and / or operations described herein. In some aspects, the network node 110 may include one or more interfaces, communication components, and / or other components that facilitate communication with the UE 120 or another network node.
[0060] 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 Figure 2, such as a single processor or a combination of multiple different processors. Reference to “one or more processors” should be understood to refer to any one or more of the processors described in connection with Figure 2. For example, one or more processors of the network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of the UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.
[0061] In some aspects, a single processor may perform all of the operations described as being performed by the one or more processors. In some aspects, a first set of (one or more) processors of the one or more processors may perform a first operation described as being performed by the one or more processors, and a second set of (one or more) processors of the one or more processors may perform a second operation described as being performed by the one or more processors. The first set of processors and the second set of processors may be the same set of processors or may be different sets of processors. Reference to “one or more memories” should be understood to refer to any one or more memories of a corresponding device, such as the memory described in connection with Figure 2. For example, operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or different subsets of the one or more memories.
[0062] For downlink communication from the network node 110 to the UE 120, the transmit processor 214 may receive data ( “downlink data” ) intended for the UE 120 (or a set of UEs that includes the UE 120) from the data source 212 (such as a data pipeline or a data queue) . In some examples, the transmit processor 214 may select one or more MCSs for the UE 120 in accordance with one or more channel quality indicators (CQIs) received from the UE 120. The network node 110 may process the data (for example, including encoding the data) for transmission to the UE 120 on a downlink in accordance with the MCS (s) selected for the UE 120 to generate data symbols. The transmit processor 214 may process system information (for example, semi-static resource partitioning information (SRPI) ) and / or control information (for example, CQI requests, grants, and / or upper layer signaling) and provide overhead symbols and / or control symbols. The transmit processor 214 may generate reference symbols for reference signals (for example, a cell-specific reference signal (CRS) , a demodulation reference signal (DMRS) , or a CSI reference signal (CSI-RS) ) and / or synchronization signals (for example, a primary synchronization signal (PSS) or a secondary synchronization signals (SSS) ) .
[0063] 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.
[0064] 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 quantity of TBs used to carry the data associated with a particular 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.
[0065] 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.
[0066] 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.
[0067] 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.
[0068] 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.
[0069] 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.
[0070] 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.
[0071] 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 an 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.
[0072] The transmit processor 264 may generate reference symbols for one or more reference signals, such as an uplink DMRS, an uplink sounding reference signal (SRS) , and / or another type of reference signal. The symbols from the transmit processor 264 may be precoded by the TX MIMO processor 266, if applicable, and further processed by the set of modems 254 (for example, for DFT-s-OFDM or CP-OFDM) . The TX MIMO processor 266 may perform spatial processing (for example, precoding) on the data symbols, the control symbols, the overhead symbols, and / or the reference symbols, if applicable, and may provide a set of output symbol streams (for example, U output symbol streams) to the set of modems 254. For example, each output symbol stream may be provided to a respective modulator component (shown as MOD) of a modem 254. Each modem 254 may use the respective modulator component to process (for example, to modulate) a respective output symbol stream (for example, for OFDM) to obtain an output sample stream. Each modem 254 may further use the respective modulator component to process (for example, convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.
[0073] 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) .
[0074] One or more antennas of the set of antennas 252 or the set of antennas 234 may include, or may be included within, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, among other examples. An antenna panel, an antenna group, a set of antenna elements, or an antenna array may include one or more antenna elements (within a single housing or multiple housings) , a set of coplanar antenna elements, a set of non-coplanar antenna elements, or one or more antenna elements coupled with one or more transmission or reception components, such as one or more components of Figure 2. As used herein, “antenna” can refer to one or more antennas, one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays. “Antenna panel” can refer to a group of antennas (such as antenna elements) arranged in an array or panel, which may facilitate beamforming by manipulating parameters of the group of antennas. “Antenna module” may refer to circuitry including one or more antennas, which may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.
[0075] 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.
[0076] 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.
[0077] 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.
[0078] Figure 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.
[0079] 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.
[0080] 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.
[0081] 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.
[0082] 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.
[0083] 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) .
[0084] 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 Figures 1, 2, or 3 may implement one or more techniques or perform one or more operations associated with RS set configuration for an event-driven CSI report, as described in more detail elsewhere herein. For example, the controller / processor 240 of the network node 110, the controller / processor 280 of the UE 120, any other component (s) of Figure 2, the CU 310, the DU 330, or the RU 340 may perform or direct operations of, for example, process 600 of Figure 6, process 700 of Figure 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 Figure 6, process 700 of Figure 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.
[0085] In some aspects, the UE 120 includes means for receiving, from a network node, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams; and / or means for transmitting, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set. The means for the UE 120 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.
[0086] In some aspects, the network node 110 includes means for transmitting, to a UE, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams; and / or means for receiving, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set. 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.
[0087] Figure 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 Figure 4, examples 400, 410, and 420 include a UE 120 in communication with a network node 110 in a wireless communication network (for example, wireless communication network 100) . However, the devices shown in Figure 4 are provided as examples, and the wireless communication network may support communication and beam management between other devices (for example, 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 examples, the UE 120 and the network node 110 may be in a connected state (for example, an RRC connected state) .
[0088] As shown in Figure 4, example 400 may include a network node 110 (for example, one or more network node devices such as an RU, a DU, and / or a CU, among other examples) and a UE 120 communicating to perform beam management using CSI-RSs. Example 400 depicts a first beam management procedure (for example, P1 CSI-RS beam management) . The first beam management procedure may be referred to as a beam selection procedure, an initial beam acquisition procedure, a beam sweeping procedure, a cell search procedure, and / or a beam search procedure. As shown in Figure 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 (for example, using RRC signaling) , semi-persistent (for example, using MAC-CE signaling) , and / or aperiodic (for example, using DCI) .
[0089] The first beam management procedure may include the network node 110 performing beam sweeping over multiple transmit (Tx) beams. The network node 110 may transmit a CSI-RS using each transmit beam for beam management. To enable the UE 120 to perform receive (Rx) beam sweeping, the network node may use a transmit beam to transmit (for example, with repetitions) each CSI-RS at multiple times within the same RS resource set so that the UE 120 can sweep through receive beams in multiple transmission instances. For example, if the network node 110 has a set of N transmit beams and the UE 120 has a set of M receive beams, the CSI-RS may be transmitted on each of the N transmit beams M times so that the UE 120 may receive M instances of the CSI-RS per transmit beam. In other words, for each transmit beam of the network node 110, the UE 120 may perform beam sweeping through the receive beams of the UE 120. As a result, the first beam management procedure may enable the UE 120 to measure a CSI-RS on different transmit beams using different receive beams to support selection of network node 110 transmit beams / UE 120 receive beam (s) beam pair (s) . The UE 120 may report the measurements to the network node 110 to enable the network node 110 to select one or more beam pair (s) for communication between the network node 110 and the UE 120. While example 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.
[0090] As shown in Figure 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 (for example, P2 CSI-RS beam management) . The second beam management procedure may be referred to as a beam refinement procedure, a network node beam refinement procedure, a TRP beam refinement procedure, and / or a transmit beam refinement procedure. As shown in Figure 4 and example 410, CSI-RSs may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs may be configured to be aperiodic (for example, using DCI) . The second beam management procedure may include the network node 110 performing beam sweeping over one or more transmit beams. The one or more transmit beams may be a subset of all transmit beams associated with the network node 110 (for example, determined based at least in part on measurements reported by the UE 120 in connection with the first beam management procedure) . The network node 110 may transmit a CSI-RS using each transmit beam of the one or more transmit beams for beam management. The UE 120 may measure each CSI-RS using a single (for example, a same) receive beam (for example, determined based at least in part on measurements performed in connection with the first beam management procedure) . The second beam management procedure may enable the network node 110 to select a best transmit beam based at least in part on measurements of the CSI-RSs (for example, measured by the UE 120 using the single receive beam) reported by the UE 120.
[0091] As shown in Figure 4, example 420 depicts a third beam management procedure (for example, P3 CSI-RS beam management) . The third beam management procedure may be referred to as a beam refinement procedure, a UE beam refinement procedure, and / or a receive beam refinement procedure. As shown in Figure 4 and example 420, one or more CSI-RSs may be configured to be transmitted from the network node 110 to the UE 120. The CSI-RSs may be configured to be aperiodic (for example, using DCI) . The third beam management process may include the network node 110 transmitting the one or more CSI-RSs using a single transmit beam (for example, determined based at least in part on measurements reported by the UE 120 in connection with the first beam management procedure and / or the second beam management procedure) . To enable the UE 120 to perform receive beam sweeping, the network node may use a transmit beam to transmit (for example, with repetitions) CSI-RS at multiple times within the same RS resource set so that UE 120 can sweep through one or more receive beams in multiple transmission instances. The one or more receive beams may be a subset of all receive beams associated with the UE 120 (for example, determined based at least in part on measurements performed in connection with the first beam management procedure and / or the second beam management procedure) . The third beam management procedure may enable the network node 110 and / or the UE 120 to select a best receive beam based at least in part on reported measurements received from the UE 120 (for example, of the CSI-RS of the transmit beam using the one or more receive beams) .
[0092] As indicated above, Figure 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 Figure 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.
[0093] In some examples, such as examples in which the UE 120 is configured to provide semi-persistent and / or periodic CSI reports for numerous beams, providing the various CSI reports may resulting in high signaling overhead and / or colliding CSI reports (for example, multiple CSI reports scheduled to be transmitted in uplink resources in which at least one OFDM symbol overlaps) . Additionally, or alternatively, for aperiodic CSI reporting, a network node 110 may separately request each CSI report, resulting in the network node and / or the UE 120 consuming significant signaling resources. On the other hand, if less frequent beam reporting is configured at the UE 120, the network node 110 may not be provided timely beam measurements and / or the network node may be provided with outdated beam measurements, resulting in network performance degradation.
[0094] Accordingly, in some examples a UE 120 may be configured to transmit one or more CSI reports based at least in part on the UE 120 identifying that some condition has been satisfied and / or that a certain event has taken place (for example, a UE 120 may be configured to perform UE-initiated CSI reporting and / or event-driven CSI reporting, and / or the UE 120 may be configured to transmit UE-initiated CSI reports and / or event-driven CSI reports) . Put another way, the UE 120 may be configured to detect whether a triggering event associated with an event-driven CSI report (sometimes referred to herein as a “beam-reporting trigger condition” ) has taken place, such as by monitoring RSs (for example, CSI-RSs, among other examples) to assess if a beam-reporting trigger condition has been met, and to transmit an event-driven CSI report (for example, using a MAC-CE communication and / or a UCI communication, among other examples) when the event has occurred. In some examples, a beam-reporting trigger condition may be associated with a quality of a current (serving) beam (for example, determined using one or more of an RSRP measurement, an RSSI measurement, a RSRQ measurement, a signal-to-noise ratio (SNR) measurement, a signal-to-interference-plus-noise ratio (SINR) measurement, and / or a similar measurement) becoming worse than a certain threshold. In some other examples, a beam-reporting trigger condition may be associated with a quality of at least one new (non-serving) beam becoming a threshold value better than the current (serving) beam. In some other examples, a beam-reporting trigger condition may be associated with a quality of a new (non-serving) beam becoming better than a certain threshold. In some other examples, a beam-reporting trigger condition may be associated with a quality of a current (serving) beam becoming worse than a first threshold and a quality of at least one new (non-serving) beam becoming better than a second threshold.
[0095] In some examples, configuring a UE 120 to transmit one or more UE-initiated CSI reports and / or one or more event-driven CSI reports may result in beam reporting optimization because the UE 120 may provide timely beam reports to a network node 110 with reduced reporting overhead. Put another way, because in some examples the UE 120 may have better and / or more timely knowledge of beam quality changes, a UE-initiated beam reporting procedure may result in more timely beam reports and reduced reporting overhead. For example, when the UE 120 determines that one or more current beams become poor, the UE 120 can trigger beam reporting without the network needing to configure and / or trigger frequent reporting.
[0096] In some examples, a CSI report framework (for example, for a periodic, semi-persistent, or aperiodic CSI report) , may define a single CSI resource as a CMR, for which the UE 120 measures the channel status and generates the CSI report accordingly. In addition to the CMR, a CSI resource may be optionally configuration as an IMR. However, such a CSI report framework does not specify resources to be measured for detecting a triggering event for an event-driven CSI report. Furthermore, the single CSI resource configuration in such a CSI report framework cannot be used to specify different groups of RSs to be used for serving beam and non-serving beam measurements, which may be required for some event-driven CSI report triggering events.
[0097] Some implementations described herein enable configuration of RS sets for event-driven CSI reports. In some aspects, a UE may receive, from a network node, configuration information for an event-driven CSI report. The configuration information may indicate a first RS set associated with one or more serving beams and / or a second RS set associated with one or more non-serving beams. The first RS set and / or the second RS set may indicate RSs to be used, by the UE, for detecting of a triggering event associated with the event-driven CSI report. The UE may detect the triggering event based on or otherwise associated with measurements of RSs in the first RS set and / or the second RS set, and the UE may transmit, to the network node, an event-driven CSI report in connection with detecting the triggering event. In this way, event-driven CSI reporting is enabled, resulting in more timely beam reporting and reduced reporting overhead and / or latency.
[0098] Figure 5 is a diagram illustrating an example 500 associated with RS set configuration for an event-driven CSI report in accordance with the present disclosure. As shown in Figure 5, a network node 110 (for example, a base station, a CU, a DU, and / or an RU) may communicate with a UE 120. In some aspects, the UE 120 may communicate with one or more network nodes 110. In some aspects, the network node 110 and the UE 120 may be part of a wireless network (for example, wireless communication network 100) . The UE 120 and the network node 110 may have established a wireless connection prior to operations shown in Figure 5. In some aspects, the UE 120 and the network node 110 may be associated with, and / or may be configured to communicate using, beamforming communications.
[0099] As shown in Figure 5, in some aspects, in a first operation 505, the UE 120 may transmit, and the network node 110 may receive, capability information. The capability information may indicate whether the UE 120 supports a feature and / or one or more parameters related to the feature. For example, the capability information may indicate a capability of the UE 120 to perform event-driven CSI reporting and / or one or more parameters related to a capability of the UE 120 to perform event-driven CSI reporting. One or more operations described herein may be based on or otherwise associated with the capability information transmitted by the UE 120. For example, the UE 120 may perform a communication in accordance with the capability information, or may receive configuration information that is in accordance with the capability information. In some aspects, the capability information may indicate that the UE 120 supports event-driven CSI reporting.
[0100] As further shown in Figure 5, in a second operation 510, the network node 110 may transmit, and the UE 120 may receive, configuration information for an event-driven CSI report. In some aspects, the UE 120 may receive the configuration information via one or more of system information (for example, a master information block (MIB) and / or a system information block (SIB) , among other examples) , RRC signaling, one or more MAC-CEs, and / or DCI, among other examples.
[0101] In some aspects, the configuration information may indicate one or more candidate configurations and / or communication parameters. In some aspects, the one or more candidate configurations and / or communication parameters may be selected, activated, and / or deactivated by a subsequent indication (for example, one or more subsequent indications discussed in connection with the third operation 515) . For example, the subsequent indication may select a candidate configuration and / or communication parameter from the one or more candidate configurations and / or communication parameters. In some aspects, the subsequent indication may include a dynamic indication, such as one or more MAC-CEs and / or one or more DCI messages, among other examples.
[0102] In some aspects, the configuration information for the event-driven CSI report may indicate a trigger event associated with the event-driven CSI report. Additionally or alternatively, the configuration information for the event-driven CSI report may indicate uplink resources to be used to transmit the event-driven CSI report responsive to, based on, or otherwise associated with detection of the trigger event. In some aspects, the trigger event may be based on measurements of RSs corresponding to one or more serving beams (for example, one or more current beams serving the UE 120) and / or one or more non-serving beams (for example, new beams and / or neighbor beams to the one or more serving beams) . In some examples, the triggering event associated with the event-driven CSI report may be when a measurement (for example, an L1-RSRP measurement) on at least one serving beam fails to satisfy (for example, becomes worse than) a threshold. In some examples, the triggering event associated with the event-driven CSI report may be when a measurement (for example, an L1-RSRP measurement) on at least one non-serving beam becomes better (for example, greater) than a measurement (for example, an L1-RSRP measurement) on at least one serving beam by at least an offset. In some examples, the triggering event associated with the event-driven CSI report may be when a measurement (for example, an L1-RSRP measurement) of a non-serving beam satisfies (for example, becomes better than) a threshold. In some examples, the triggering event associated with the event-driven CSI report may be when a measurement (for example, an L1-RSRP measurement) on at least one serving beam fails to satisfy (for example, becomes worse than) a first threshold, and a measurement (for example, an L1-RSRP measurement) on at least one non-serving beam satisfies (for example, becomes better than) a second threshold. In some examples, the triggering event associated with the event-driven CSI report may be when an order of beam qualities (for example, based on or associated with L1-RSRP measurements or other measurements) of multiple measured beams (for example, serving beams and / or non-serving beams) changes since a previous report. In some examples, the triggering event associated with the event-driven CSI report may be when a poor decoding quality (for example, persistent decoding failure) has been detected / observed with at least one serving beam. In some aspects, the configuration information may indicate configurations for multiple event-driven CSI reports, each associated with a respective event trigger. For example, the configuration information may configure the UE 120 to detect one or more event triggers (for example, one or more of the event triggers described above) and transmit respective event-driven CSI reports associated with one or more event triggers.
[0103] In some aspects, the configuration information for an event-driven CSI report may indicate at least one of a first RS set (Set A) or a second RS set (Set B) for detection of the triggering event associated with the event-driven CSI report. Set A may be associated with one or more serving beams (for example, one or more current beams serving the UE 120) . For example, Set A may indicate a set of RSs, associated with one or more serving beams, that includes one or more RSs that are to be used (for example, monitored and / or measured) by the UE 120 to detect the triggering event. Set B may be associated with one or more non-serving beams (for example, new beams and / or neighbor beams) . For example, Set B may indicate a set of RSs, associated with one or more non-serving beams, that includes one or more RSs that are to be used (for example, monitored and / or measured) by the UE 120 to detect the triggering event. In some aspects, the configuration information may indicate separate Set A and / or Set B RSs for each triggering event configured for the UE 120 (for example, for each respective event-driven CSI report associated each triggering event) . In such examples, the configuration information for an event-driven CSI report associated with an event that is based on or otherwise associated with measurements on serving beams and non-serving beams may indicate both Set A and Set B. Additionally or alternatively, the configuration information for an event-driven CSI report associated with an event that is based on or otherwise associated with only measurements on serving beams or non-serving beams may indicate only Set A or Set B. In some other aspects, the configuration information may indicate Set A RSs and Set B RSs that are to be used for detection of multiple different triggering events associated with respective event-driven CSI reports. In such examples, the configuration information indicating each triggering event may indicate whether the triggering event is detected using only Set A, only Set B, or Set A and Set B.
[0104] In some aspects, the two RS sets (Set A and Set B) may be considered as RS groups. That is, Set A may be a first RS group and set B may be a second RS group. In some aspects, the configuration information may explicitly indicate Set A and / or Set B. That is, the configuration information may explicitly indicate / identify the RSs included in Set A and / or the RSs included in Set B. In some examples, the RSs in Set A and / or Set B may be defined as SSBs, non-zero-power CSI-RSs (NZP-CSI-RSs) , or a combination / mix of SSBs and NZP-CSI-RSs. For example, Set A may include one or more SSBs and / or one or more NZP-CSI-RSs, and Set B may include one or more SSBs and / or one or more NZP-CSI-RSs.
[0105] In some aspects, the configuration information may indicate Set A and / or Set B in an implicit manner. For example, the configuration information may include configurations of two RS sets without indicating which RS set is Set A (the RS set associated with the one or more serving beams) and which RS set is Set B (the RS set associated with the one or more non-serving beams) , and the UE 120 may determine Set A and Set B based on or otherwise in association with an implicit rule. In some examples, the configuration information may include a first configuration associated with Set A (for example, indicating one or more RSs included in Set A) and a second configuration associated with Set B (for example, indicating one or more RSs included in Set B) , and an order of the first configuration and the second configuration in the configuration information may indicate that the first configuration is associated with Set A and the second configuration is associated with Set B. For example, the RS set configuration listed first in the configuration information may be the first configuration associated with Set A, and the RS set configuration listed second in the configuration information may be the second configuration associated with Set B.
[0106] In some aspects, a configuration of one RS set (for example, Set A or Set B) may be omitted from the configuration information for the event-driven CSI report, and the omission of the configuration for the RS set from the configuration information for the event-driven CSI report may indicate (for example, to the UE 120) that a default RS set is to be used for that RS set. For example, in connection with the UE 120 determining that explicit configuration for one of the RS sets (Set A or Set B) is omitted from the configuration information associated with the event-driven CSI report (for example, an event-driven CSI-report associated with a triggering event based on or otherwise associated with measurements of serving beams and non-serving beams) , the UE 120 may use a default RS set as the RS set for which the configuration is omitted from the configuration information. In some examples, the default RS set for Set A (for example, to be used when a first configuration associated with Set A is omitted from the configuration information) may include one or more beams / RSs associated with a current transmission configuration indicator (TCI) state and / or a beam / RS associated with a control resource set (CORESET) type 0 (CORESET0) . In such examples, if the first configuration for Set A is not present in the configuration information, the UE 120 may use the one or more beams / RSs associated with the current TCI state and / or a beam / RS associated with CORESET0 for one or more serving beam measurements associated with detecting the triggering event.
[0107] In some other examples, when a configuration of one RS set (for example, Set A or Set B) is omitted from the configuration information for the event-driven CSI report omit, the default RS set to be used for measurements associated with that RS set may be an existing RS set configured for another purpose, such as an RS set associated with beam failure detection (BFD) or beam failure recovery (BFR) . For example, if the configuration information omits a first configuration for Set A, the UE 120 may use a first RS set associated with BFD or BFR as the default RS set for the serving beam measurements. Additionally or alternatively, if the configuration information omits a second configuration for Set B, the UE 120 may use a second RS set associated with BFD or BFR as the default RS set for the non-serving beam measurements. In some aspects, instead of explicit Set A and Set B signaling via RRC (for example, in the configuration information) , existing RS sets, such as RS sets configured for BFD and / or BFR, may be reused for Set A and Set B.
[0108] In some aspects, a triggering event associated with an event-driven CSI report may be based on or otherwise associated with serving beam measurements on one or more serving beams. For example, the triggering event may be detected in connection with a measurement (for example, an L1-RSRP measurement) on a serving beam being worse than (for example, less than) a threshold. In such examples, measurement results from one or more RSs in Set A may be used by the UE 120 for detection of the triggering condition. In some examples, the UE 120 may use all of the RSs in Set A to perform the serving beam measurements associated with detecting the triggering event. That is, the configuration information may configure the UE 120 to use all of the RSs in Set A for the serving beam measurements associated with detecting the triggering event. In some other examples, the network node 110 may transmit, and the UE 120 may receive, signaling including an indication of a subset of RSs from Set A (asubset of the RSs included in Set A) to be used for detection of the triggering event, and the UE 120 may use the indicated subset of RSs from Set A for the serving beam measurements associated with detecting the triggering event. For example, the indication of the subset of RSs from Set A to be used for detecting the triggering event may be transmitted via RRC signaling (for example, the indication of the subset of RSs may be included in the configuration information associated with a certain triggering event or event-driven CSI, or the indication of the subset of RSs may be transmitted via subsequent RRC signaling) . Additionally or alternatively, the indication of the subset of RSs from Set A to be used for detecting the triggering event may be indicated (for example, dynamically indicated) via a MAC-CE or DCI that is transmitted by the network node 110 and received by the UE 120 (for example, as discussed in connection with the third operation 515) . In some other examples, the UE 120 may use one or more RSs, from Set A, that are associated with (or correspond to) one or more activated TCI states for the UE 120 to perform the serving beam measurements associated with detecting the triggering event. In some examples, the configuration or determination of which RSs from Set A are to be used by the UE 120 for the serving beam measurements may be based on or otherwise associated with a combination of the various options / examples discussed above. For example, the UE 120 may initially use the RSs, from Set A, that correspond to the activated TCI states to perform the serving beam measurements associated with detecting the triggering event, until the UE 120 receives a dynamic indication (for example, a MAC-CE) that specifies a subset of RSs from Set A. In this example, the UE 120 receives the dynamic indication, and the UE 120 may then use the specified subset of RSs from set A for the serving beam measurements associated with detecting the triggering event.
[0109] In some aspects, a triggering event associated with an event-driven CSI report may be based on or otherwise associated with non-serving beam measurements on one or more non-serving beams. For example, the triggering event may be detected in connection with a measurement (for example, an L1-RSRP measurement) on a non-serving beam being better than (for example, greater than) a threshold. In such examples, measurement results from one or more RSs in Set B may be used by the UE 120 for detection of the triggering condition. In some examples, the UE 120 may use all of the RSs in Set B to perform the non-serving beam measurements associated with detecting the triggering event. That is, the configuration information may configure the UE 120 to use all of the RSs in Set B for the non-serving bean measurements associated with detecting the triggering event. In some other examples, the network node 110 may transmit, and the UE 120 may receive, signaling including an indication of a subset of RSs from Set B (asubset of the RSs included in Set B) to be used for detection of the triggering event, and the UE 120 may use the indicated subset of RSs from Set B for the non-serving beam measurements associated with detecting the triggering event. For example, the indication of the subset of RSs from Set B to be used for detecting the triggering event may be transmitted via RRC signaling (for example, the indication of the subset of RSs may be included in the configuration information associated with a certain triggering event or event-driven CSI, or the indication of the subset of RSs may be transmitted via subsequent RRC signaling) . Additionally or alternatively, the indication of the subset of RSs from Set B to be used for detecting the triggering event may be indicated (for example, dynamically indicated) via a MAC-CE or DCI that is transmitted by the network node 110 and received by the UE 120 (for example, as discussed in connection with the third operation 515) . In some examples, the configuration or determination of which RSs from Set B are to be used by the UE 120 for the non-serving beam measurements may be based on or otherwise associated with a combination of the various options / examples discussed above.
[0110] In some aspects, a triggering event associated with an event-driven CSI report may be based on or otherwise associated with serving beam measurements and non-serving beam measurements. For example, the triggering event may be detected in connection with a measurement on a serving beam being worse than a first threshold and a measurement on a non-serving beam being better than a second threshold. In another example, the triggering event may be detected in connection with a measurement on a non-serving beam being better than a measurement on a serving beam by at least a certain offset. In such examples, measurement results from one or more RSs in Set A and one or more RSs in Set B may be used by the UE 120 for detection of the triggering condition. In some examples, the UE 120 may use all of the RSs in Set A and / or all of the RSs in Set B to perform the measurements associated with detecting the triggering event. That is, the configuration information may configure the UE 120 to use all of the RSs in Set A and / or all of the RSs in Set B for the measurements associated with detecting the triggering event. In some other examples, the network node 110 may transmit, and the UE 120 may receive, signaling including an indication of a subset of RSs from Set A and / or a subset of RSs from Set B to be used for detection of the triggering event, and the UE 120 may use the indicated subset of RSs from Set A and / or the indicated subset of RSs from Set B for the measurements associated with detecting the triggering event. For example, the indication of the subset of RSs from Set A and / or the subset of RSs from Set B to be used for detecting the triggering event may be transmitted via RRC signaling (for example, the indication of the subset (s) of RSs from Set A and / or Set B may be included in the configuration information associated with a certain triggering event or event-driven CSI, or the indication of the subset (s) of RSs from Set A and / or Set B may be transmitted via subsequent RRC signaling) . Additionally or alternatively, the indication of the subset of RSs from Set A and / or the subset of RSs from Set B to be used for detecting the triggering event may be indicated (for example, dynamically indicated) via a MAC-CE or DCI that is transmitted by the network node 110 and received by the UE 120 (for example, as discussed in connection with the third operation 515) . In some other examples, the UE 120 may use one or more RSs, from Set A, that are associated with (or correspond to) one or more activated TCI states for the UE 120 to perform the serving beam measurements associated with detecting the triggering event. In some examples, the configuration or determination / selection of which RSs from Set A are to be used by the UE 120 for the serving beam measurements may be independent of the configuration or determination of which RSs from Set B are to be used by the UE 120 for the non-serving beam measurements. Different options / examples, of the various options / examples discussed above, may be used for indicating or determining the selection of which RSs from Set A are to be used and for indicating or determining the selection of which RSs from Set B are to be used. In some examples, the configuration or determination of which RSs from Set A are to be used by the UE 120 for the serving beam measurements and / or which RSs from Set B are to be used by the UE 120 for the non-serving beam measurements may be based on or otherwise associated with a combination of the various options / examples discussed above.
[0111] In some aspects, the configuration information for the event-driven CSI report may indicate multiple sub-configurations associated with the triggering event. In such examples, each sub-configuration, of the multiple sub-configurations, may include (or correspond to) a respective combination of RS sets (for example, Set A and / or Set B) or a respective one or more RSs included in Set A and / or Set B. For example, each sub-configuration may correspond to a different combination of which RSs are to be used for detecting the triggering event associated with the event-driven CSI report. In some aspects, each sub-configuration, of the multiple sub-configurations, may indicate at least one respective threshold and / or a respective offset value to be used for detecting the triggering event based on or otherwise in association with measurements of the one or more RSs associated with that sub-configuration. For example, each sub-configuration may indicate a respective threshold (for example, for a triggering event that is detected when one or more beam measurements are better than or worse than the threshold) , respective first and / or second thresholds (for example, for a triggering event that is detected when a serving beam measurement is worse than the first threshold and a non-serving beam measurement is better than the second threshold) , or a respective offset value (for example, for a triggering event that is detected when a non-serving beam measurement is better than a serving beam measurement by at least the offset value) , depending on the triggering event. Accordingly, the configuration information may configure the UE 120 to apply different thresholds and / or offset values for different RS sets and / or different combinations of RSs from Set A and / or Set B within one CSI reporting event configuration (for example, one event-driven CSI report configuration and / or one triggering event configuration) .
[0112] In some aspects, the configuration information may indicate an RS set (Set C) that includes Set A and Set B. For example, the configuration information may configure the UE 120 with a single RS set (Set C) that encompasses the RSs from both Set A (for example, the RSs associated with one or more serving beams) and Set B (for example, the RSs associated with one or more non-serving beams) . For example, Set C may be a third RS set, Set A (the first RS set) may be a first subset of Set C (for example, a first subset of the RSs included in Set C) , and Set B (the second RS set) may be a second subset of Set C (for example, a second subset of the RSs included in Set C) . In some aspects, the configuration information may explicitly indicate / identify the RSs included in Set C. In some examples, the RSs in Set C may be defined as SSBs, NZP-CSI-RSs, or a combination / mix of SSBs and NZP-CSI-RSs. For example, Set C may include one or more SSBs and / or one or more NZP-CSI-RSs.
[0113] In some aspects, the classification of RSs associated with serving beams and RSs associated with non-serving beams in Set C (for example, which RSs from Set C are included in Set A and which RSs from Set C are included in Set B) may be explicitly signaled (for example, semi-statically configured) via RRC signaling transmitted by the network node 110 and received by the UE 120. For example, an RRC information element (IE) for Set C that is included in the configuration information may include information that identifies a first subset of RSs associated with one or more serving beams (for example, the subset of RSs from Set C that are included in Set A) and a second subset of RSs associated with one or more non-serving beams (for example, the subset of RSs from Set C that are included in Set B) .
[0114] In some aspects, the classification of RSs associated with serving beams and RSs associated with non-serving beams in Set C (for example, which RSs from Set C are included in Set A and which RSs from Set C are included in Set B) may be explicitly signaled via a dynamic indication transmitted by the network node 110 and received by the UE 120. For example, the dynamic indication may be signaled via a MAC-CE or DCI. The dynamic indication may indicate at least one of the first subset of RSs (for example, the subset of RSs from Set C that are included in Set A) or the second subset of RSs (for example, the subset of RSs from Set C that are included in Set B) . In some examples, the network node 110 may transmit, and the UE 120 may receive, a MAC-CE or DCI that explicitly indicates a first subset of RSs to be used for serving beam measurements (for example, the first subset of RSs from Set C that are included in Set A) and a second subset of RSs to be used for non-serving beam measurements (for example, the second subset of RSs from Set C that are included in Set B) . In some other examples, the network node 110 may transmit, and the UE 120 may receive, a MAC-CE or DCI that explicitly indicates a subset of RSs to be used for serving beam measurements (for example, the first subset of RSs from Set C that are included in Set A) , which may implicitly indicate to the UE 120 that the remaining RSs in Set C are to be used as the subset of RSs for non-serving beam measurements (for example, the second subset of RSs from Set C that are included in Set B) . Alternatively, the MAC-CE or DCI may explicitly indicate a subset of RSs to be used for non-serving beam measurements (for example, the second subset of RSs from Set C that are included in Set B) , which may implicitly indicate to the UE 120 that the remaining RSs in Set C are to be used as the subset of RSs for serving beam measurements (for example, the first subset of RSs from Set C that are included in Set A) .
[0115] In some aspects, the configuration information may implicitly indicate the classification of RSs associated with serving beams and RSs associated with non-serving beams in Set C (for example, which RSs from Set C are included in Set A and which RSs from Set C are included in Set B) . For example, the UE 120 may determine which of the RSs from Set C are associated with serving beam measurements and which of the RSs from Set C are associated with non-serving beam measurements in accordance with an implicit rule. In some examples, the UE 120 may determine that one or more RSs, from Set C, that are associated with (or correspond to) one or more activated TCI states for the UE 120 are to be used for serving beam measurements (for example, are included in the first subset of RSs from Set C that are included in Set A) , and the UE 120 may determine that the remaining RSs from Set C (for example, one or more remaining RSs from Set C that are not included in the first subset of RSs) are to be used for non-serving beam measurements (for example, are included in the second subset of RSs from Set C that are included in Set B) . In some aspects, the classification of RSs associated with serving beams and RSs associated with non-serving beams in Set C (for example, which RSs from Set C are included in Set A and which RSs from Set C are included in Set B) may be explicitly and / or implicitly signaled using a combination of any of the examples / options discussed above. In some other aspects, instead of explicitly signaling Set C via RRC (for example, in the configuration information) , an existing RS set, such as an RS set configured for BFD or BFR, may be reused for Set C.
[0116] In some aspects, the configuration information may indicate another RS set (Set D) that defines one or more IMRs to be used for one or more interference measurements associated with detecting a triggering event. Set D may be referred to as an IMR RS set. In some examples, the configuration information for an event-driven CSI report may indicate that Set D in connection with the triggering event associated with the event-driven CSI report is detected based on or in association with one or more interference measurements. In such examples, Set D may indicate one or more IMRs to be used for the interference measurement (for example, SINR measurements) associated with detecting the triggering event. In some aspects, the configuration information for an event-driven CSI report associated with a triggering event that is triggered based on or otherwise in association with one or more serving beam measurements (for example, L1-RSRP measurements) and one or more interference measurements (for example, L1-SINR measurements) may indicate Set A (for example, one or more RSs to be used for the serving beam measurements) and Set D (for example, one or more IMRs to be used for the interference measurements) . In some other aspects, the configuration information for an event-driven CSI report associated with a triggering event that is triggered based on or otherwise in association with one or more serving beam measurements (for example, L1-RSRP measurements) , one or more non-serving measurements (for example, L1-RSRP measurements) , and one or more interference measurements (for example, L1-SINR measurements) may indicate Set A (for example, one or more RSs to be used for the serving beam measurements) , Set B (for example, one or more RSs to be used for the non-serving beam measurements) and Set D (for example, one or more IMRs to be used for the interference measurements) . In some other aspects, the configuration information for an event-driven CSI report associated with a triggering event that is triggered based on or otherwise in association with one or more serving beam measurements (for example, L1-RSRP measurements) , one or more non-serving measurements (for example, L1-RSRP measurements) , and one or more interference measurements (for example, L1-SINR measurements) may indicate Set C (for example, including a first subset of RSs to be used for the serving beam measurements and a second subset of RSs to be used for the non-serving beam measurements) and Set D (for example, one or more IMRs to be used for the interference measurements) .
[0117] As further shown in Figure 5, in some aspects, in a third operation 515, the network node 110 may transmit, and the UE 120 may receive, one or more indications associated with the first RS set (Set A) and / or the second RS set (Set B) .
[0118] In some aspects, the one or more indications, transmitted by the network node 110 and received by the UE 120, may include an indication of which one or more RSs of Set A are to be used for serving beam measurements for detecting the triggering event and / or which one or more RSs of Set B are to be used for non-serving beam measurements for detecting the triggering event. In some examples, the network node 110 may transmit, and the UE 120 may receive, via RRC signaling, an indication (for example, a semi-static configuration) of a subset of RSs from Set A and / or a subset RSs from Set B to be used for detecting the triggering event. In some examples, the network node 110 may transmit, and the UE 120 may receive, via a MAC-CE or DCI, an indication (for example, a dynamic indication) of a subset of RSs from Set A and / or a subset RSs from Set B to be used for detecting the triggering event.
[0119] In some aspects, in an example in which the configuration information indicates Set C, the one or more indications, transmitted by the network node 110 and received by the UE 120, may include an indication of which one or more RSs of Set C are to be used for serving beam measurements for detecting the triggering event and / or which one or more RSs of Set C are to be used for non-serving beam measurements for detecting the triggering event. In some examples, the network node 110 may transmit, and the UE 120 may receive, a dynamic indication (for example, via a MAC-CE or DCI) that explicitly indicates a first subset of RSs from Set C to be used for serving beam measurements and a second subset of RSs from Set C to be used for non-serving beam measurements. In some other examples, the network node 110 may transmit, and the UE 120 may receive, a dynamic indication (for example, via a MAC-CE or DCI) , that explicitly indicates a first subset of RSs from Set C to be used for serving beam measurements. In such examples, the explicit indication of the first subset of RSs from Set C may implicitly indicate, to the UE 120, that the remaining RSs in Set C (other than the RSs in the first subset of RSs) are included in a second subset of RSs to be used for non-serving beam measurements. In some other examples, the network node 110 may transmit, and the UE 120 may receive, a dynamic indication (for example, via a MAC-CE or DCI) , that explicitly indicates a second subset of RSs from Set C to be used for non-serving beam measurements. In such examples, the explicit indication of the second subset of RSs from Set C may implicitly indicate, to the UE 120, that the remaining RSs in Set C (other than the RSs in the second subset of RSs) are included in a first subset of RSs to be used for serving beam measurements.
[0120] In some aspects, in an example in which the configuration information indicates multiple sub-configurations associated with the triggering event, the one or more indications, transmitted by the network node 110 and received by the UE 120, may include an indication of one or more sub-configurations of the multiple sub-configurations associated with the triggering event, to be used by the UE 120 for detecting the triggering event. For example, the network node 110 may transmit, and the UE 120 may receive, a dynamic indication (for example, via a MAC-CE of DCI) that activates or selects one or more sub-configurations of the multiple sub-configurations indicated in the configuration information for a triggering event. In some aspects, the one or more indications, transmitted by the network node 110 and received by the UE 120, may include an indication (for example, a dynamic indication transmitted via a MAC-CE or DCI) that activates event-based CSI reporting associated with one or more triggering events for the UE 120.
[0121] As further shown in Figure 5, in a fourth operation 520, the network node 110 may transmit, and the UE 120 may receive, one more RSs associated with detecting the triggering event by the UE 120. For example, the network node 110 may transmit RSs associated with serving beams and / or non-serving beams to be measured by the UE 120 in accordance with the configuration information associated with the event-driven CSI report discussed in connection with the second operation 510 and / or the one or more indications discussed in connection with the third operation 515. In some aspects, the network node 110 may transmit one or more RSs included in Set A and / or one or more RSs included in Set B. In some aspects, the network node 110 may transmit one or more RSs included in Set C. In some aspects, the network node 110 may transmit one or more RSs included in Set D in addition to one or more RSs included in Set A and / or one or more RSs included in Set B. In some aspects, the network node 110 may transmit one or more RSs included in Set D in addition to one or more RSs included in Set C. In some aspects, the network node 110 may transmit RSs associated with detection, by the UE 120, of multiple triggering events associated with respective event-driven CSI reports. In some aspects, different RSs may be transmitted by different network nodes 110. For example, an RS associated with a non-serving beam (for example, an RS included in Set B) may be transmitted by the same network node 110 or a different network node 110 as an RS associated with a serving beam.
[0122] As further shown in Figure 5, in a fifth operation 525, the UE 120 may measure the RSs associated with detecting the triggering event. For example, the UE 120 may measure RSs associated with serving beams and / or non-serving beams in accordance with the configuration information associated with the event-driven CSI report discussed in connection with the second operation 510 and / or the one or more indications discussed in connection with the third operation 515. In some examples, the UE 120 may perform RSRP measurements (for example, L1-RSRP measurements) on the RSs associated with the serving beams and / or the RSs associated with the non-serving beams. Additionally or alternatively, the UE may measure and / or determine other parameters, such as an RSSI parameter, an RSRQ parameter, an SNR parameter, an SINR parameter, and / or a similar parameter for one or more of the RSs associated with the serving beams and / or the RSs associated with the non-serving beams. In some aspects, the RSs measured by the UE 120 and / or the measurements performed by the UE 120 may be based on or otherwise associated with the triggering event associated with the event-driven CSI report. In some aspects, the UE 120 may measure RSs and / or perform measurements associated with detecting one or more triggering events associated with respective event-driven CSI reports.
[0123] In some aspects, the UE 120 may perform measurements (for example, serving beam measurements) of one or more RSs included in Set A and / or measurements (for example non-serving beam measurements) of one or more RSs included in Set B. For example, as discussed above in connection with the second operation 510 and the third operation 515, the UE 120 may use all or a subset of the RSs included in Set A to perform serving beam measurements, and / or the UE 120 may use all or a subset of the RSs included in Set B to perform non-serving beam measurements. In some aspects, in an example in which the configuration information indicates Set C, the UE 120 may perform serving beam measurements using a first subset of RSs from Set C, and the UE 120 may perform non-serving beam measurements using a second subset of RSs from Set C.
[0124] In some aspects, in an example in which a triggering event is based on or otherwise associated with one or more interference measurements, and the configuration information indicates Set D (for example, a set of IMRs) , the UE 120 may perform interference measurements (for example, SINR measurements) using the one or more IMRs included in Set D. For example, the UE 120 may perform the interference measurements using the IMRs included in Set D in addition to the serving beam measurements performed on the RSs associated with the one or more serving beams (for example, the RSs included in Set A or the first subset of Set C) and / or the non-serving beam measurements performed on the RSs associated with the one or more non-serving beams (for examples, the RSs included in Set B or the second subset of Set C) .
[0125] As further shown in Figure 5, in a sixth operation 530, the UE 120 may detect the triggering event associated with the event-driven CSI report based on or otherwise in association with the measurements of the RSs.
[0126] In some aspects, the UE 120 may detect the triggering event in association with detecting / determining that a measurement (for example, an L1-RSRP measurement) of at least one RS associated with a serving beam fails to satisfy (for example, is less than) a threshold. In some aspects, the UE 120 may detect the triggering event in association with detecting / determining that a measurement (for example, an L1-RSRP measurement) of at least one RS associated with a non-serving beam is better (for example, greater) than a measurement (for example, an L1-RSRP measurement) of at least one RS associated with a serving beam by at least a certain offset value. In some examples, the UE 120 may detect the triggering event in association with detecting / determining that a measurement (for example, an L1-RSRP measurement) of at least one RS associated with a non-serving beam satisfies (for example, is greater than) a threshold. In some examples, the UE 120 may detect the triggering event in association with detecting / determining that a measurement (for example, an L1-RSRP measurement) of at least one RS associated with a serving beam fails to satisfy (for example, is less than) a first threshold and a measurement (for example, an L1-RSRP measurement) of at least one RS associated with a non-serving beam satisfies (for example, is greater than) a second threshold. In some examples, the UE 120 may detect the triggering event in association with detecting / determining that an order of beam qualities (for example, based on or associated with L1-RSRP measurements or other measurements) of multiple measured beams (for example, serving beams and / or non-serving beams) has changed since a previous CSI report (for example, a previous event-driven CSI report) .
[0127] In some other aspects, the triggering event associated with the event-driven CSI report may be based on otherwise associated with one or more interference measurements (for example, L1-SINR measurements) in addition to one or more serving beam and / or non-serving beam measurements (for example, L1-RSRP measurements) . In such examples, the UE 120 may detect the triggering event in association with interference measurements of one or more IMRs (for example, included in Set D) , measurements of one or more RSs associated with one or more serving and / or non-serving beams, and one or more thresholds or offset values associated with detecting the triggering event. In some aspects, the UE 120 may detect multiple triggering events associated with respective event-driven CSI reports.
[0128] As further shown in Figure 5, in a seventh operation 535, the UE 120 may transmit, and the network node 110 may receive, an event-driven CSI report in connection with detecting the triggering event associated with the event-driven CSI report. In some aspects, the UE 120 may transmit the event-driven CSI report via uplink resources configured (for example, indicated in the configuration information) for event-driven CSI report transmission. In some aspects, the event-driven CSI report may include one or more measurements (for example, serving beam, non-serving beam, and / or interference measurements) that triggered transmission of the event-driven CSI report (for example, that cause the UE 120 to detect the triggering event) . Additionally, or alternatively, the event-driven CSI report may include other CSI parameters in addition to (or instead of) the one or more measurements that triggered the transmission of the event-driven CSI report.
[0129] As further shown in Figure 5, in some aspects, in an eighth operation 540, the UE 120 may transmit, and the network node 110 may receive, a request to trigger one or more additional CSI reports. For example, the request may be a UE-initiated CSI report request that is transmitted to the network node 110 to request that the network node 110 trigger transmission of one or more additional CSI reports by the UE 120. The UE 120 may transmit the request to trigger one or more additional CSI reports in connection with detection of the triggering event by the UE 120. In some aspects, the UE 120 may transmit the request to trigger one or more additional CSI reports in connection with the UE 120 detecting multiple triggering events associated with event-driven CSI reporting (for example, the triggering event associated with the event-driven CSI report transmitted by the UE 120 and one or more other triggering events associated with event-driven CSI reporting) . For example, the UE 120 may transmit the request to trigger one or more additional CSI reports when the UE 120 detects multiple triggering events, but the UE 120 does not have sufficient uplink resources allocated to transmit the multiple event-driven CSI reports that are triggered by the multiple triggering events.
[0130] In some aspects, the UE 120 may determine / decide whether to transmit the request to trigger additional CSI reports based on or otherwise in association with measurements performed by the UE 120 on one or more RSs associated with serving beams, predicted measurement results associated with one or more RSs associated with serving beams, measurements performed by the UE 120 on one or more RSs associated with non-serving beams, predicted measurement results associated with one or more RSs associated with non-serving beams, or any combination thereof. In some examples, the UE 120 may use the predicted measurement results associated with the serving and / or non-serving RSs in a case in which the UE 120 supports AI / ML functionality for predicting beam measurements.
[0131] In some aspects, the UE 120 may transmit the request to trigger one or more additional CSI reports as a stand-alone message. For example, the UE 120 may transmit the request as a stand-alone message via PUCCH UCI, PUSCH UCI, a PUSCH MAC- CE, or a PRACH transmission. In some other aspects, the request to trigger one or more additional CSI reports may be included in (for example, piggy-backed into) the event-driven CSI report transmitted by the UE 120 (for example, in the seventh operation 535) . For example, the event-driven CSI report may include a bit that is set to a value (for example, 1) to indicate a request for the network node 110 to trigger one or more additional CSI reports.
[0132] In some aspects, the request to trigger one or more additional CSI reports (for example, the request indicated in a stand-alone message or included in the event-driven CSI report) may indicate one or more RSs associated with the one or more additional CSI reports. For example, the request may include RS subset information that indicates one or more subsets of RSs (for example, subsets of Set A, Set B, or Set C) that are measured to detect one or more triggering events in addition to the triggering event for which the event-driven CSI report was transmitted by the UE 120 (for example, one or more triggering events that were detected, but for which the UE 120 was not able to transmit the corresponding event-driven CSI reports) .
[0133] As further shown in Figure 5, in some aspects, in a ninth operation 545, the network node 110 may transmit, and the UE 120 may receive, signaling to trigger one or more additional CSI reports. For example, the network node 110 may transmit the signaling to trigger the one or more semi-persistent or aperiodic CSI reports for the UE 120 in connection with receiving, from the UE 120, the request to trigger one or more additional CSI reports. In some aspects, the RS information (for example, the RS subset information) included in the request may be used by the network node 110 for triggering the subsequent semi-persistent or aperiodic CSI reports for the UE 120. For example, the network node 110 may use the RS information to determine whether to trigger one or more additional CSI reports for the UE 120, how many additional CSI reports to trigger for the UE 120, and / or what type of CSI reports (for example, semi-persistent or aperiodic) to trigger for the UE 120, among other examples.
[0134] As further shown in Figure 5, in some aspects, in a tenth operation 550, the UE 120 may transmit, and the network node 110, may receive one or more additional CSI reports. For example, the UE 120 may transmit the one or more semi-persistent or aperiodic CSI reports in response to, based on, or otherwise associated with the signaling, received from the network node 110, triggering the one or more semi-persistent or aperiodic CSI reports.
[0135] Figure 6 is a flowchart illustrating an example process 600 performed, for example, at a UE or an apparatus of a UE that supports RS set configuration for an event-driven CSI report in accordance with the present disclosure. Example process 600 is an example where the apparatus or the UE (for example, UE 120) performs operations associated with RS set configuration for an event-driven CSI report.
[0136] As shown in Figure 6, in some aspects, process 600 may include receiving, from a network node, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams (block 610) . For example, the UE (such as by using communication manager 140 or reception component 802, depicted in Figure 8) may receive, from a network node, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams, as described above.
[0137] As further shown in Figure 6, in some aspects, process 600 may include transmitting, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set (block 620) . For example, the UE (such as by using communication manager 140 or transmission component 804, depicted in Figure 8) may transmit, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set, as described above.
[0138] Process 600 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
[0139] In a first additional aspect, process 600 includes detecting the triggering event in association with the measurements of the at least one of the one or more RSs included in the first RS set or the one or more RSs included in the second RS set.
[0140] In a second additional aspect, alone or in combination with the first aspect, the first RS set includes at least one of one or more SSBs or one or more NZP-CSI-RSs, and the second RS set includes at least one of one or more SSBs or one or more NZP-CSI-RSs.
[0141] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the configuration information includes a first configuration associated with the first RS set and a second configuration associated with the second RS set, and an order of the first configuration and the second configuration in the configuration information indicates that the first configuration is associated with the first RS set and the second configuration is associated with the second RS set.
[0142] In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the configuration information omits a configuration associated with one of the first RS set or the second RS set, and omission of the configuration from the configuration information indicates a default RS set for the one of the first RS set or the second RS set.
[0143] In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the configuration omitted from the configuration information is a first configuration associated with the first RS set, and the default RS set includes at least one of a current serving beam, one or more beams associated with a current TCI state, or a beam associated with a CORESET0.
[0144] In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the default RS set is an RS set associated with BFD or BFR.
[0145] In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, the detection of the triggering event is in association with measurements of the one or more RSs included in the first RS set.
[0146] In an eighth additional aspect, alone or in combination with one or more of the first through seventh aspects, the one or more RSs included in the first RS set includes all RSs included in the first RS set.
[0147] In a ninth additional aspect, alone or in combination with one or more of the first through eighth aspects, process 600 includes receiving, from the network node, an indication of a subset of RSs included in the first RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the first RS set includes the subset of RSs included in the first RS set.
[0148] In a tenth additional aspect, alone or in combination with one or more of the first through ninth aspects, receiving the indication includes receiving the indication of the subset of RSs included in the first RS set via RRC signaling, a MAC-CE, or DCI.
[0149] In an eleventh additional aspect, alone or in combination with one or more of the first through tenth aspects, the one or more RSs included in the first RS set includes one or more RSs, in the first RS set, associated with one or more activated TCI states.
[0150] In a twelfth additional aspect, alone or in combination with one or more of the first through eleventh aspects, the detection of the triggering event is in association with the measurements of the one or more RSs included in the first RS set and measurements of the one or more RSs included in the second RS set.
[0151] In a thirteenth additional aspect, alone or in combination with one or more of the first through twelfth aspects, the one or more RSs included in the second RS set include all RSs included in the second RS set.
[0152] In a fourteenth additional aspect, alone or in combination with one or more of the first through thirteenth aspects, process 600 includes receiving, from the network node, an indication of a subset of RSs included in the second RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the second RS set includes the subset of RSs included in second first RS set.
[0153] In a fifteenth additional aspect, alone or in combination with one or more of the first through fourteenth aspects, receiving the indication includes receiving the indication of the subset of RSs included in the second RS set via RRC signaling, a MAC-CE, or DCI.
[0154] In a sixteenth additional aspect, alone or in combination with one or more of the first through fifteenth aspects, the detection of the triggering event is in association with measurements of the one or more RSs included in the first RS set and the one or more RSs included in the second RS set, wherein the one or more RSs included in the first RS set include all RSs included in the first RS set, a subset of RSs included in the first RS set indicated via signaling from the network node, or one or more RSs, included in the first RS set, associated with one or more activated TCI states, and wherein the one or more RSs included in the second RS set include all RSs included in the second RS set, or a subset of RSs included in the second RS set indicated via signaling from the network node.
[0155] In a seventeenth additional aspect, alone or in combination with one or more of the first through sixteenth aspects, the configuration information indicates a plurality of sub-configurations associated with the triggering event, wherein each sub-configuration, of the plurality of sub-configurations, includes one or more RSs from at least one of the first RS set or the second RS set to be used for detection of the triggering event, and wherein the configuration information indicates at least one of a respective threshold or a respective offset value for each sub-configuration of the plurality of sub-configurations.
[0156] In an eighteenth additional aspect, alone or in combination with one or more of the first through seventeenth aspects, the configuration information includes a configuration of a third RS set, wherein the first RS set is a first subset of RSs included in the third RS set, and wherein the second RS set is a second subset of RSs included in the third RS set.
[0157] In a nineteenth additional aspect, alone or in combination with one or more of the first through eighteenth aspects, the third RS set includes at least one of one or more SSBs or one or more NZP-CSI-RSs.
[0158] In a twentieth additional aspect, alone or in combination with one or more of the first through nineteenth aspects, the configuration information includes information identifying the first subset of RSs and the second subset of RSs.
[0159] In a twenty-first additional aspect, alone or in combination with one or more of the first through twentieth aspects, process 600 includes receiving a dynamic indication indicating at least one of the first subset of RSs or the second subset of RSs.
[0160] In a twenty-second additional aspect, alone or in combination with one or more of the first through twenty-first aspects, the first subset of RSs includes one or more RSs, from the third RS set, associated with one or more activated TCI states, and the second subset of RSs includes one or more remaining RSs, from the third RS set, that are not included in the first subset of RSs.
[0161] In a twenty-third additional aspect, alone or in combination with one or more of the first through twenty-second aspects, process 600 includes transmitting, to the network node and in connection with the detection of the triggering event, a request to trigger one or more additional CSI reports.
[0162] In a twenty-fourth additional aspect, alone or in combination with one or more of the first through twenty-third aspects, transmitting the request to trigger the one or more additional CSI reports includes transmitting the request to trigger the one or more additional CSI reports in connection with the detection of the triggering event and detection of one or more other triggering events associated with event-driven CSI reporting.
[0163] In a twenty-fifth additional aspect, alone or in combination with one or more of the first through twenty-fourth aspects, transmitting the request to trigger the one or more additional CSI reports includes transmitting the request via PUCCH UCI, PUSCH UCI, a PUSCH MAC-CE, or a PRACH.
[0164] In a twenty-sixth additional aspect, alone or in combination with one or more of the first through twenty-fifth aspects, the request to trigger the one or more additional CSI reports is included in the event-driven CSI report.
[0165] In a twenty-seventh additional aspect, alone or in combination with one or more of the first through twenty-sixth aspects, the request to trigger the one or more additional CSI reports indicates one or more RSs associated with the one or more additional CSI reports.
[0166] In a twenty-eighth additional aspect, alone or in combination with one or more of the first through twenty-seventh aspects, process 600 includes receiving, from the network node and in association with the request, signaling triggering one or more semi-persistent or aperiodic CSI reports.
[0167] In a twenty-ninth additional aspect, alone or in combination with one or more of the first through twenty-eighth aspects, the configuration information indicates an IMR RS set associated with one or more interference measurements for detection of the triggering event associated with the event-driven CSI report.
[0168] Although Figure 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 Figure 6. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.
[0169] Figure 7 is a flowchart illustrating an example process 700 performed, for example, at a network node or an apparatus of a network node that supports RS set configuration for an event-driven CSI report in accordance with the present disclosure. Example process 700 is an example where the apparatus or the network node (for example, network node 110) performs operations associated with RS set configuration for an event-driven CSI report.
[0170] As shown in Figure 7, in some aspects, process 700 may include transmitting, to a UE, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams (block 710) . For example, the network node (such as by using communication manager 150 or transmission component 904, depicted in Figure 9) may transmit, to a UE, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams, as described above.
[0171] As further shown in Figure 7, in some aspects, process 700 may include receiving, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set (block 720) . For example, the network node (such as by using communication manager 150 or reception component 902, depicted in Figure 9) may receive, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set, as described above.
[0172] Process 700 may include additional aspects, such as any single aspect or any combination of aspects described below or in connection with one or more other processes described elsewhere herein.
[0173] In a first additional aspect, the first RS set includes at least one of one or more SSBs or one or more NZP-CSI-RSs, and the second RS set includes at least one of one or more SSBs or one or more NZP-CSI-RSs.
[0174] In a second additional aspect, alone or in combination with the first aspect, the configuration information includes a first configuration associated with the first RS set and a second configuration associated with the second RS set, and an order of the first configuration and the second configuration in the configuration information indicates that the first configuration is associated with the first RS set and the second configuration is associated with the second RS set.
[0175] In a third additional aspect, alone or in combination with one or more of the first and second aspects, the configuration information omits a configuration associated with one of the first RS set or the second RS set, and omission of the configuration from the configuration information indicates a default RS set for the one of the first RS set or the second RS set.
[0176] In a fourth additional aspect, alone or in combination with one or more of the first through third aspects, the configuration omitted from the configuration information is a first configuration associated with the first RS set, and the default RS set includes at least one of a current serving beam, one or more beams associated with a current TCI state, or a beam associated with a CORESET0.
[0177] In a fifth additional aspect, alone or in combination with one or more of the first through fourth aspects, the default RS set is an RS set associated with BFD or BFR.
[0178] In a sixth additional aspect, alone or in combination with one or more of the first through fifth aspects, the detection of the triggering event is in association with measurements of the one or more RSs included in the first RS set.
[0179] In a seventh additional aspect, alone or in combination with one or more of the first through sixth aspects, the one or more RSs included in the first RS set includes all RSs included in the first RS set.
[0180] In an eighth additional aspect, alone or in combination with one or more of the first through seventh aspects, process 700 includes transmitting, to the UE, an indication of a subset of RSs included in the first RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the first RS set includes the subset of RSs included in the first RS set.
[0181] In a ninth additional aspect, alone or in combination with one or more of the first through eighth aspects, transmitting the indication includes transmitting the indication of the subset of RSs included in the first RS set via RRC signaling, a MAC-CE, or DCI.
[0182] In a tenth additional aspect, alone or in combination with one or more of the first through ninth aspects, the one or more RSs included in the first RS set includes one or more RSs, in the first RS set, associated with one or more activated TCI states.
[0183] In an eleventh additional aspect, alone or in combination with one or more of the first through tenth aspects, the detection of the triggering event is in association with the measurements of the one or more RSs included in the first RS set and measurements of the one or more RSs included in the second RS set.
[0184] In a twelfth additional aspect, alone or in combination with one or more of the first through eleventh aspects, the one or more RSs included in the second RS set include all RSs included in the second RS set.
[0185] In a thirteenth additional aspect, alone or in combination with one or more of the first through twelfth aspects, process 700 includes transmitting, to the UE, an indication of a subset of RSs included in the second RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the second RS set includes the subset of RSs included in second first RS set.
[0186] In a fourteenth additional aspect, alone or in combination with one or more of the first through thirteenth aspects, transmitting the indication includes transmitting the indication of the subset of RSs included in the second RS set via RRC signaling, a MAC-CE, or DCI.
[0187] In a fifteenth additional aspect, alone or in combination with one or more of the first through fourteenth aspects, the detection of the triggering event is in association with measurements of the one or more RSs included in the first RS set and the one or more RSs included in the second RS set, wherein the one or more RSs included in the first RS set include all RSs included in the first RS set, a subset of RSs included in the first RS set indicated via signaling from the network node, or one or more RSs, included in the first RS set, associated with one or more activated TCI states, and wherein the one or more RSs included in the second RS set include all RSs included in the second RS set, or a subset of RSs included in the second RS set indicated via signaling from the network node.
[0188] In a sixteenth additional aspect, alone or in combination with one or more of the first through fifteenth aspects, the configuration information indicates a plurality of sub-configurations associated with the triggering event, wherein each sub-configuration, of the plurality of sub-configurations, includes one or more RSs from at least one of the first RS set or the second RS set to be used for detection of the triggering event, and wherein the configuration information indicates at least one of a respective threshold or a respective offset value for each sub-configuration of the plurality of sub-configurations.
[0189] In a seventeenth additional aspect, alone or in combination with one or more of the first through sixteenth aspects, the configuration information includes a configuration of a third RS set, wherein the first RS set is a first subset of RSs included in the third RS set, and wherein the second RS set is a second subset of RSs included in the third RS set.
[0190] In an eighteenth additional aspect, alone or in combination with one or more of the first through seventeenth aspects, the third RS set includes at least one of one or more SSBs or one or more NZP-CSI-RSs.
[0191] In a nineteenth additional aspect, alone or in combination with one or more of the first through eighteenth aspects, the configuration information includes information identifying the first subset of RSs and the second subset of RSs.
[0192] In a twentieth additional aspect, alone or in combination with one or more of the first through nineteenth aspects, process 700 includes transmitting a dynamic indication indicating at least one of the first subset of RSs or the second subset of RSs.
[0193] In a twenty-first additional aspect, alone or in combination with one or more of the first through twentieth aspects, the first subset of RSs includes one or more RSs, from the third RS set, associated with one or more activated TCI states, and the second subset of RSs includes one or more remaining RSs, from the third RS set, that are not included in the first subset of RSs.
[0194] In a twenty-second additional aspect, alone or in combination with one or more of the first through twenty-first aspects, process 700 includes receiving, from the UE and in connection with the detection of the triggering event by the UE, a request to trigger one or more additional CSI reports.
[0195] In a twenty-third additional aspect, alone or in combination with one or more of the first through twenty-second aspects, receiving the request to trigger the one or more additional CSI reports includes receiving the request to trigger the one or more additional CSI reports in connection with detection of the triggering event and one or more other triggering events associated with event-driven CSI reporting.
[0196] In a twenty-fourth additional aspect, alone or in combination with one or more of the first through twenty-third aspects, receiving the request to trigger the one or more additional CSI reports includes receiving the request via PUCCH UCI, PUSCH UCI, a PUSCH MAC-CE, or a PRACH.
[0197] In a twenty-fifth additional aspect, alone or in combination with one or more of the first through twenty-fourth aspects, the request to trigger the one or more additional CSI reports is included in the event-driven CSI report.
[0198] In a twenty-sixth additional aspect, alone or in combination with one or more of the first through twenty-fifth aspects, the request to trigger the one or more additional CSI reports indicates one or more RSs associated with the one or more additional CSI reports.
[0199] In a twenty-seventh additional aspect, alone or in combination with one or more of the first through twenty-sixth aspects, process 700 includes transmitting, to the UE and in association with the request, signaling triggering one or more semi-persistent or aperiodic CSI reports.
[0200] In a twenty-eighth additional aspect, alone or in combination with one or more of the first through twenty-seventh aspects, the configuration information indicates an IMR RS set associated with one or more interference measurements for detection of the triggering event associated with the event-driven CSI report.
[0201] Although Figure 7 shows example blocks of process 700, in some aspects, process 700 may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in Figure 7. Additionally or alternatively, two or more of the blocks of process 700 may be performed in parallel.
[0202] Figure 8 is a diagram of an example apparatus 800 for wireless communication that supports RS set configuration for an event-driven CSI report 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 a communication manager 140, which may be in communication with one another (for example, via one or more buses) . As shown, the apparatus 800 may communicate with another apparatus 806 (such as a UE, a network node, or another wireless communication device) using the reception component 802 and the transmission component 804.
[0203] In some aspects, the apparatus 800 may be configured to and / or operable to perform one or more operations described herein in connection with Figure 5. Additionally or alternatively, the apparatus 800 may be configured to and / or operable to perform one or more processes described herein, such as process 600 of Figure 6. In some aspects, the apparatus 800 may include one or more components of the UE described above in connection with Figure 2.
[0204] The reception component 802 may receive communications, such as reference signals, control information, and / or data communications, from the apparatus 806. The reception component 802 may provide received communications to one or more other components of the apparatus 800, such as the communication manager 140. 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. 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, and / or one or more memories of the UE described above in connection with Figure 2.
[0205] The transmission component 804 may transmit communications, such as reference signals, control information, and / or data communications, to the apparatus 806. In some aspects, the communication manager 140 may generate communications and may transmit the generated communications to the transmission component 804 for transmission to the apparatus 806. 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 806. 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, and / or one or more memories of the UE described above in connection with Figure 2. In some aspects, the transmission component 804 may be co-located with the reception component 802 in one or more transceivers.
[0206] The communication manager 140 may receive or may cause the reception component 802 to receive, from a network node, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The communication manager 140 may transmit or may cause the transmission component 804 to transmit, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set. In some aspects, the communication manager 140 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 140.
[0207] The communication manager 140 may include one or more controllers / processors and / or one or more memories of the UE described above in connection with Figure 2. In some aspects, the communication manager 140 includes a set of components, such as an event trigger detection component 808. Alternatively, the set of components may be separate and distinct from the communication manager 140. In some aspects, one or more components of the set of components may include or may be implemented within one or more controllers / processors and / or one or more memories of the UE described above in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.
[0208] The reception component 802 may receive, from a network node, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The transmission component 804 may transmit, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0209] The event trigger detection component 808 may detect the triggering event in association with the measurements of the at least one of the one or more RSs included in the first RS set or the one or more RSs included in the second RS set.
[0210] The reception component 802 may receive, from the network node, an indication of a subset of RSs included in the first RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the first RS set includes the subset of RSs included in the first RS set.
[0211] The reception component 802 may receive, from the network node, an indication of a subset of RSs included in the second RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the second RS set includes the subset of RSs included in second first RS set.
[0212] The reception component 802 may receive a dynamic indication indicating at least one of the first subset of RSs or the second subset of RSs.
[0213] The transmission component 804 may transmit, to the network node and in connection with the detection of the triggering event, a request to trigger one or more additional CSI reports.
[0214] The reception component 802 may receive, from the network node and in association with the request, signaling triggering one or more semi-persistent or aperiodic CSI reports.
[0215] The number and arrangement of components shown in Figure 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 Figure 8. Furthermore, two or more components shown in Figure 8 may be implemented within a single component, or a single component shown in Figure 8 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 8 may perform one or more functions described as being performed by another set of components shown in Figure 8.
[0216] Figure 9 is a diagram of an example apparatus 900 for wireless communication that supports RS set configuration for an event-driven CSI report 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 a communication manager 150, which may be in communication with one another (for example, via one or more buses) . As shown, the apparatus 900 may communicate with another apparatus 906 (such as a UE, a network node, or another wireless communication device) using the reception component 902 and the transmission component 904.
[0217] In some aspects, the apparatus 900 may be configured to and / or operable to perform one or more operations described herein in connection with Figure 5. Additionally or alternatively, the apparatus 900 may be configured to and / or operable to perform one or more processes described herein, such as process 700 of Figure 7. In some aspects, the apparatus 900 may include one or more components of the network node described above in connection with Figure 2.
[0218] The reception component 902 may receive communications, such as reference signals, control information, and / or data communications, from the apparatus 906. The reception component 902 may provide received communications to one or more other components of the apparatus 900, such as the communication manager 150. 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. 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, and / or one or more memories of the network node described above in connection with Figure 2.
[0219] The transmission component 904 may transmit communications, such as reference signals, control information, and / or data communications, to the apparatus 906. In some aspects, the communication manager 150 may generate communications and may transmit the generated communications to the transmission component 904 for transmission to the apparatus 906. 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 906. 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, and / or one or more memories of the network node described above in connection with Figure 2. In some aspects, the transmission component 904 may be co-located with the reception component 902 in one or more transceivers.
[0220] The communication manager 150 may transmit or may cause the transmission component 904 to transmit, to a UE, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The communication manager 150 may receive or may cause the reception component 902 to receive, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set. In some aspects, the communication manager 150 may perform one or more operations described elsewhere herein as being performed by one or more components of the communication manager 150.
[0221] The communication manager 150 may include one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units of the network node described above in connection with Figure 2. In some aspects, the communication manager 150 includes a set of components, such as a determination component 908. Alternatively, the set of components may be separate and distinct from the communication manager 150. In some aspects, one or more components of the set of components may include or may be implemented within one or more controllers / processors, one or more memories, one or more schedulers, and / or one or more communication units of the network node described above in connection with Figure 2. Additionally or alternatively, one or more components of the set of components may be implemented at least in part as software stored in one or more memories. For example, a component (or a portion of a component) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the functions or operations of the component.
[0222] The transmission component 904 may transmit, to a UE, configuration information for an event-driven CSI report, the configuration information indicating at least one of a first RS set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams. The reception component 902 may receive, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0223] The determination component 908 may determine the configuration information to be transmitted to the UE.
[0224] The transmission component 904 may transmit, to the UE, an indication of a subset of RSs included in the first RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the first RS set includes the subset of RSs included in the first RS set.
[0225] The transmission component 904 may transmit, to the UE, an indication of a subset of RSs included in the second RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the second RS set includes the subset of RSs included in second first RS set.
[0226] The transmission component 904 may transmit a dynamic indication indicating at least one of the first subset of RSs or the second subset of RSs.
[0227] The reception component 902 may receive, from the UE and in connection with the detection of the triggering event by the UE, a request to trigger one or more additional CSI reports.
[0228] The transmission component 904 may transmit, to the UE and in association with the request, signaling triggering one or more semi-persistent or aperiodic CSI reports.
[0229] The number and arrangement of components shown in Figure 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 Figure 9. Furthermore, two or more components shown in Figure 9 may be implemented within a single component, or a single component shown in Figure 9 may be implemented as multiple, distributed components. Additionally or alternatively, a set of (one or more) components shown in Figure 9 may perform one or more functions described as being performed by another set of components shown in Figure 9.
[0230] The following provides an overview of some Aspects of the present disclosure:
[0231] Aspect 1: A method of wireless communication by a user equipment (UE) , comprising: receiving, from a network node, configuration information for an event-driven channel state information (CSI) report, the configuration information indicating at least one of a first reference signal (RS) set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams; and transmitting, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0232] Aspect 2: The method of Aspect 1, further comprising: detecting the triggering event in association with the measurements of the at least one of the one or more RSs included in the first RS set or the one or more RSs included in the second RS set.
[0233] Aspect 3: The method of any of Aspects 1-2, wherein the first RS set includes at least one of one or more synchronization signal blocks (SSBs) or one or more non-zero-power CSI-RSs (NZP-CSI-RSs) , and wherein the second RS set includes at least one of one or more SSBs or one or more NZP-CSI-RSs.
[0234] Aspect 4: The method of any of Aspects 1-3, wherein the configuration information includes a first configuration associated with the first RS set and a second configuration associated with the second RS set, and wherein an order of the first configuration and the second configuration in the configuration information indicates that the first configuration is associated with the first RS set and the second configuration is associated with the second RS set.
[0235] Aspect 5: The method of any of Aspects 1-3, wherein the configuration information omits a configuration associated with one of the first RS set or the second RS set, and wherein omission of the configuration from the configuration information indicates a default RS set for the one of the first RS set or the second RS set.
[0236] Aspect 6: The method of Aspect 5, wherein the configuration omitted from the configuration information is a first configuration associated with the first RS set, and wherein the default RS set includes at least one of a current serving beam, one or more beams associated with a current transmission configuration indicator (TCI) state, or a beam associated with a control resource set type 0 (CORESET0) .
[0237] Aspect 7: The method of Aspect 5, wherein the default RS set is an RS set associated with beam failure detection (BFD) or beam failure recovery (BFR) .
[0238] Aspect 8: The method of any of Aspects 1-7, wherein the detection of the triggering event is in association with measurements of the one or more RSs included in the first RS set.
[0239] Aspect 9: The method of Aspect 8, wherein the one or more RSs included in the first RS set includes all RSs included in the first RS set.
[0240] Aspect 10: The method of Aspect 8, further comprising: receiving, from the network node, an indication of a subset of RSs included in the first RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the first RS set includes the subset of RSs included in the first RS set.
[0241] Aspect 11: The method of Aspect 10, wherein receiving the indication comprises: receiving the indication of the subset of RSs included in the first RS set via radio resource control (RRC) signaling, a medium access control (MAC) control element (MAC-CE) , or downlink control information (DCI) .
[0242] Aspect 12: The method of Aspect 8, wherein the one or more RSs included in the first RS set includes one or more RSs, in the first RS set, associated with one or more activated transmission configuration indicator (TCI) states.
[0243] Aspect 13: The method of any of Aspects 8-12, wherein the detection of the triggering event is in association with the measurements of the one or more RSs included in the first RS set and measurements of the one or more RSs included in the second RS set.
[0244] Aspect 14: The method of Aspect 13, wherein the one or more RSs included in the second RS set include all RSs included in the second RS set.
[0245] Aspect 15: The method of Aspect 13, further comprising: receiving, from the network node, an indication of a subset of RSs included in the second RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the second RS set includes the subset of RSs included in second first RS set.
[0246] Aspect 16: The method of Aspect 15, wherein receiving the indication comprises: receiving the indication of the subset of RSs included in the second RS set via radio resource control (RRC) signaling, a medium access control (MAC) control element (MAC-CE) , or downlink control information (DCI) .
[0247] Aspect 17: The method of any of Aspects 1-16, wherein the detection of the triggering event is in association with measurements of the one or more RSs included in the first RS set and the one or more RSs included in the second RS set, wherein the one or more RSs included in the first RS set include: all RSs included in the first RS set, a subset of RSs included in the first RS set indicated via signaling from the network node, or one or more RSs, included in the first RS set, associated with one or more activated transmission configuration indicator (TCI) states, and wherein the one or more RSs included in the second RS set include: all RSs included in the second RS set, or a subset of RSs included in the second RS set indicated via signaling from the network node.
[0248] Aspect 18: The method of any of Aspects 1-17, wherein the configuration information indicates a plurality of sub-configurations associated with the triggering event, wherein each sub-configuration, of the plurality of sub-configurations, includes one or more RSs from at least one of the first RS set or the second RS set to be used for detection of the triggering event, and wherein the configuration information indicates at least one of a respective threshold or a respective offset value for each sub-configuration of the plurality of sub-configurations.
[0249] Aspect 19: The method of any of Aspects 1-18, wherein the configuration information includes a configuration of a third RS set, wherein the first RS set is a first subset of RSs included in the third RS set, and wherein the second RS set is a second subset of RSs included in the third RS set.
[0250] Aspect 20: The method of Aspect 19, wherein the third RS set includes at least one of one or more synchronization signal blocks (SSBs) or one or more non-zero-power CSI-RSs (NZP-CSI-RSs) .
[0251] Aspect 21: The method of any of Aspects 19-20, wherein the configuration information includes information identifying the first subset of RSs and the second subset of RSs.
[0252] Aspect 22: The method of any of Aspects 19-20, further comprising: receiving a dynamic indication indicating at least one of the first subset of RSs or the second subset of RSs.
[0253] Aspect 23: The method of any of Aspects 19-20, wherein the first subset of RSs includes one or more RSs, from the third RS set, associated with one or more activated transmission configuration indicator (TCI) states, and wherein the second subset of RSs includes one or more remaining RSs, from the third RS set, that are not included in the first subset of RSs.
[0254] Aspect 24: The method of any of Aspects 1-23, further comprising: transmitting, to the network node and in connection with the detection of the triggering event, a request to trigger one or more additional CSI reports.
[0255] Aspect 25: The method of Aspect 24, wherein transmitting the request to trigger the one or more additional CSI reports comprises: transmitting the request to trigger the one or more additional CSI reports in connection with the detection of the triggering event and detection of one or more other triggering events associated with event-driven CSI reporting.
[0256] Aspect 26: The method of any of Aspects 24-25, wherein transmitting the request to trigger the one or more additional CSI reports comprises: transmitting the request via physical uplink control channel (PUCCH) uplink control information (UCI) , physical uplink shared channel (PUSCH) UCI, a PUSCH medium access control (MAC) control element (MAC-CE) , or a physical random access channel (PRACH) .
[0257] Aspect 27: The method of any of Aspects 24-25, wherein the request to trigger the one or more additional CSI reports is included in the event-driven CSI report.
[0258] Aspect 28: The method of any of Aspects 24-27, wherein the request to trigger the one or more additional CSI reports indicates one or more RSs associated with the one or more additional CSI reports.
[0259] Aspect 29: The method of any of Aspects 24-28, further comprising: receiving, from the network node and in association with the request, signaling triggering one or more semi-persistent or aperiodic CSI reports.
[0260] Aspect 30: The method of any of Aspects 1-29, wherein the configuration information indicates an interference measurement resource (IMR) RS set associated with one or more interference measurements for detection of the triggering event associated with the event-driven CSI report.
[0261] Aspect 31: A method of wireless communication by a network node, comprising: transmitting, to a user equipment (UE) , configuration information for an event-driven channel state information (CSI) report, the configuration information indicating at least one of a first reference signal (RS) set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams; and receiving, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
[0262] Aspect 32: The method of Aspect 31, wherein the first RS set includes at least one of one or more synchronization signal blocks (SSBs) or one or more non-zero-power CSI-RSs (NZP-CSI-RSs) , and wherein the second RS set includes at least one of one or more SSBs or one or more NZP-CSI-RSs.
[0263] Aspect 33: The method of any of Aspects 31-32, wherein the configuration information includes a first configuration associated with the first RS set and a second configuration associated with the second RS set, and wherein an order of the first configuration and the second configuration in the configuration information indicates that the first configuration is associated with the first RS set and the second configuration is associated with the second RS set.
[0264] Aspect 34: The method of any of Aspects 31-32, wherein the configuration information omits a configuration associated with one of the first RS set or the second RS set, and wherein omission of the configuration from the configuration information indicates a default RS set for the one of the first RS set or the second RS set.
[0265] Aspect 35: The method of Aspect 34, wherein the configuration omitted from the configuration information is a first configuration associated with the first RS set, and wherein the default RS set includes at least one of a current serving beam, one or more beams associated with a current transmission configuration indicator (TCI) state, or a beam associated with a control resource set type 0 (CORESET0) .
[0266] Aspect 36: The method of Aspect 34, wherein the default RS set is an RS set associated with beam failure detection (BFD) or beam failure recovery (BFR) .
[0267] Aspect 37: The method of any of Aspects 31-36, wherein the detection of the triggering event is in association with measurements of the one or more RSs included in the first RS set.
[0268] Aspect 38: The method of Aspect 37, wherein the one or more RSs included in the first RS set includes all RSs included in the first RS set.
[0269] Aspect 39: The method of Aspect 37, further comprising: transmitting, to the UE, an indication of a subset of RSs included in the first RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the first RS set includes the subset of RSs included in the first RS set.
[0270] Aspect 40: The method of Aspect 39, wherein transmitting the indication comprises: transmitting the indication of the subset of RSs included in the first RS set via radio resource control (RRC) signaling, a medium access control (MAC) control element (MAC-CE) , or downlink control information (DCI) .
[0271] Aspect 41: The method of Aspect 37, wherein the one or more RSs included in the first RS set includes one or more RSs, in the first RS set, associated with one or more activated transmission configuration indicator (TCI) states.
[0272] Aspect 42: The method of any of Aspects 37-41, wherein the detection of the triggering event is in association with the measurements of the one or more RSs included in the first RS set and measurements of the one or more RSs included in the second RS set.
[0273] Aspect 43: The method of Aspect 42, wherein the one or more RSs included in the second RS set include all RSs included in the second RS set.
[0274] Aspect 44: The method of Aspect 42, further comprising: transmitting, to the UE, an indication of a subset of RSs included in the second RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the second RS set includes the subset of RSs included in second first RS set.
[0275] Aspect 45: The method of Aspect 44, wherein transmitting the indication comprises: transmitting the indication of the subset of RSs included in the second RS set via radio resource control (RRC) signaling, a medium access control (MAC) control element (MAC-CE) , or downlink control information (DCI) .
[0276] Aspect 46: The method of any of Aspects 31-45, wherein the detection of the triggering event is in association with measurements of the one or more RSs included in the first RS set and the one or more RSs included in the second RS set, wherein the one or more RSs included in the first RS set include: all RSs included in the first RS set, a subset of RSs included in the first RS set indicated via signaling from the network node, or one or more RSs, included in the first RS set, associated with one or more activated transmission configuration indicator (TCI) states, and wherein the one or more RSs included in the second RS set include: all RSs included in the second RS set, or a subset of RSs included in the second RS set indicated via signaling from the network node.
[0277] Aspect 47: The method of any of Aspects 31-46, wherein the configuration information indicates a plurality of sub-configurations associated with the triggering event, wherein each sub-configuration, of the plurality of sub-configurations, includes one or more RSs from at least one of the first RS set or the second RS set to be used for detection of the triggering event, and wherein the configuration information indicates at least one of a respective threshold or a respective offset value for each sub-configuration of the plurality of sub-configurations.
[0278] Aspect 48: The method of any of Aspects 31-47, wherein the configuration information includes a configuration of a third RS set, wherein the first RS set is a first subset of RSs included in the third RS set, and wherein the second RS set is a second subset of RSs included in the third RS set.
[0279] Aspect 49: The method of Aspect 48, wherein the third RS set includes at least one of one or more synchronization signal blocks (SSBs) or one or more non-zero-power CSI-RSs (NZP-CSI-RSs) .
[0280] Aspect 50: The method of any of Aspects 48-49, wherein the configuration information includes information identifying the first subset of RSs and the second subset of RSs.
[0281] Aspect 51: The method of any of Aspects 48-49, further comprising: transmitting a dynamic indication indicating at least one of the first subset of RSs or the second subset of RSs.
[0282] Aspect 52: The method of any of Aspects 48-49, wherein the first subset of RSs includes one or more RSs, from the third RS set, associated with one or more activated transmission configuration indicator (TCI) states, and wherein the second subset of RSs includes one or more remaining RSs, from the third RS set, that are not included in the first subset of RSs.
[0283] Aspect 53: The method of any of Aspects 31-52, further comprising: receiving, from the UE and in connection with the detection of the triggering event by the UE, a request to trigger one or more additional CSI reports.
[0284] Aspect 54: The method of Aspect 53, wherein receiving the request to trigger the one or more additional CSI reports comprises: receiving the request to trigger the one or more additional CSI reports in connection with detection, by the UE, of the triggering event and one or more other triggering events associated with event-driven CSI reporting.
[0285] Aspect 55: The method of any of Aspects 53-54, wherein receiving the request to trigger the one or more additional CSI reports comprises: receiving the request via physical uplink control channel (PUCCH) uplink control information (UCI) , physical uplink shared channel (PUSCH) UCI, a PUSCH medium access control (MAC) control element (MAC-CE) , or a physical random access channel (PRACH) .
[0286] Aspect 56: The method of any of Aspects 53-54, wherein the request to trigger the one or more additional CSI reports is included in the event-driven CSI report.
[0287] Aspect 57: The method of any of Aspects 53-56, wherein the request to trigger the one or more additional CSI reports indicates one or more RSs associated with the one or more additional CSI reports.
[0288] Aspect 58: The method of any of Aspects 53-57, further comprising: transmitting, to the UE and in association with the request, signaling triggering one or more semi-persistent or aperiodic CSI reports.
[0289] Aspect 59: The method of any of Aspects 31-58, wherein the configuration information indicates an interference measurement resource (IMR) RS set associated with one or more interference measurements for detection of the triggering event associated with the event-driven CSI report.
[0290] Aspect 60: 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-59.
[0291] Aspect 61: 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-59.
[0292] Aspect 62: An apparatus for wireless communication, the apparatus comprising at least one means for performing the method of one or more of Aspects 1-59.
[0293] Aspect 63: 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-59.
[0294] Aspect 64: 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-59.
[0295] Aspect 65: 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-59.
[0296] Aspect 66: 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-59.
[0297] 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.
[0298] As used herein, the term “component” is intended to be broadly construed as hardware or a combination of hardware and at least one of software or firmware. “Software” shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, or functions, among other examples, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. As used herein, a “processor” is implemented in hardware or a combination of hardware and software. It will be apparent that systems or methods described herein may be implemented in different forms of hardware or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems or methods is not limiting of the aspects. Thus, the operation and behavior of the systems or methods are described herein without reference to specific software code, because those skilled in the art will understand that software and hardware can be designed to implement the systems or methods based, at least in part, on the description herein. A component being configured to perform a function means that the component has a capability to perform the function, and does not require the function to be actually performed by the component, unless noted otherwise.
[0299] 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.
[0300] As used herein, a phrase referring to “at least one of” a list of items refers to any combination of those items, including single members. As an example, “at least one of: a, b, or c” is intended to cover a, b, c, a + b, a + c, b + c, and a + b + c, as well as any combination with multiples of the same element (for example, a + a, a + a + a, a + a + b, a + a + c, a + b + b, a + c + c, b + b, b + b + b, b + b + c, c + c, and c + c + c, or any other ordering of a, b, and c) .
[0301] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more. ” Further, as used herein, the article “the” is intended to include one or more items referenced in connection with the article “the” and may be used interchangeably with “the one or more. ” Furthermore, as used herein, the terms “set” and “group” are intended to include one or more items and may be used interchangeably with “one or more. ” Where only one item is intended, the phrase “only one” or similar language is used. Also, as used herein, the terms “has, ” “have, ” “having, ” and similar terms are intended to be open-ended terms that do not limit an element that they modify (for example, an element “having” A may also have B) . Further, the phrase “based on” is intended to mean “based on or otherwise in association with” unless explicitly stated otherwise. Also, as used herein, the term “or” is intended to be inclusive when used in a series and may be used interchangeably with “and / or, ” unless explicitly stated otherwise (for example, if used in combination with “either” or “only one of” ) . It should be understood that “one or more” is equivalent to “at least one. ”
[0302] Even though particular combinations of features are recited in the claims or disclosed in the specification, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically recited in the claims or disclosed in the specification. The disclosure of various aspects includes each dependent claim in combination with every other claim in the claim set.
Claims
1.A user equipment (UE) for wireless communication, 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 UE to:receive, from a network node, configuration information for an event-driven channel state information (CSI) report, the configuration information indicating at least one of a first reference signal (RS) set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams; andtransmit, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.2.The UE of claim 1, wherein the processing system is further configured to cause the UE to:detect the triggering event in association with the measurements of the at least one of the one or more RSs included in the first RS set or the one or more RSs included in the second RS set.3.The UE of claim 1, wherein the first RS set includes at least one of one or more synchronization signal blocks (SSBs) or one or more non-zero-power CSI-RSs (NZP-CSI-RSs) , andwherein the second RS set includes at least one of one or more SSBs or one or more NZP-CSI-RSs.4.The UE of claim 1, wherein the detection of the triggering event is in association with measurements of the one or more RSs included in the first RS set.5.The UE of claim 4, wherein the one or more RSs included in the first RS set includes all RSs included in the first RS set.6.The UE of claim 4, wherein the processing system is further configured to cause the UE to:receive, from the network node, an indication of a subset of RSs included in the first RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the first RS set includes the subset of RSs included in the first RS set.7.The UE of claim 4, wherein the one or more RSs included in the first RS set includes one or more RSs, in the first RS set, associated with one or more activated transmission configuration indicator (TCI) states.8.The UE of claim 4, wherein the detection of the triggering event is in association with the measurements of the one or more RSs included in the first RS set and measurements of the one or more RSs included in the second RS set.9.The UE of claim 8, wherein the one or more RSs included in the second RS set include all RSs included in the second RS set.10.The UE of claim 8, wherein the processing system is further configured to cause the UE to:receive, from the network node, an indication of a subset of RSs included in the second RS set to be used for the detection of the triggering event, wherein the one or more RSs included in the second RS set includes the subset of RSs included in second first RS set.11.The UE of claim 1, wherein the detection of the triggering event is in association with measurements of the one or more RSs included in the first RS set and the one or more RSs included in the second RS set,wherein the one or more RSs included in the first RS set include:all RSs included in the first RS set,a subset of RSs included in the first RS set indicated via signaling from the network node, orone or more RSs, included in the first RS set, associated with one or more activated transmission configuration indicator (TCI) states, and wherein the one or more RSs included in the second RS set include:all RSs included in the second RS set, ora subset of RSs included in the second RS set indicated via signaling from the network node.12.The UE of claim 1, wherein the configuration information indicates a plurality of sub-configurations associated with the triggering event,wherein each sub-configuration, of the plurality of sub-configurations, includes one or more RSs from at least one of the first RS set or the second RS set to be used for detection of the triggering event, andwherein the configuration information indicates at least one of a respective threshold or a respective offset value for each sub-configuration of the plurality of sub-configurations.13.The UE of claim 1, wherein the configuration information includes a configuration of a third RS set, wherein the first RS set is a first subset of RSs included in the third RS set, and wherein the second RS set is a second subset of RSs included in the third RS set.14.The UE of claim 13, wherein the configuration information includes information identifying the first subset of RSs and the second subset of RSs.15.The UE of claim 13, wherein the processing system is further configured to cause the UE to:receive a dynamic indication indicating at least one of the first subset of RSs or the second subset of RSs.16.The UE of claim 13, wherein the first subset of RSs includes one or more RSs, from the third RS set, associated with one or more activated transmission configuration indicator (TCI) states, and wherein the second subset of RSs includes one or more remaining RSs, from the third RS set, that are not included in the first subset of RSs.17.The UE of claim 1, wherein the processing system is further configured to cause the UE to:transmit, to the network node and in connection with the detection of the triggering event, a request to trigger one or more additional CSI reports.18.The UE of claim 1, wherein the configuration information indicates an interference measurement resource (IMR) RS set associated with one or more interference measurements for detection of the triggering event associated with the event-driven CSI report.19.A network node for wireless communication, 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 network node to:transmit, to a user equipment (UE) , configuration information for an event-driven channel state information (CSI) report, the configuration information indicating at least one of a first reference signal (RS) set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams; andreceive, from the UE, the event-driven CSI report in connection with detection, by the UE, of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.20.A method of wireless communication by a user equipment (UE) , comprising:receiving, from a network node, configuration information for an event-driven channel state information (CSI) report, the configuration information indicating at least one of a first reference signal (RS) set or a second RS set for detection of a triggering event associated with the event-driven CSI report, wherein the first RS set is associated with one or more serving beams and the second RS set is associated with one or more non-serving beams; andtransmitting, to the network node, the event-driven CSI report in connection with detection of the triggering event in association with measurements of at least one of one or more RSs included in the first RS set or one or more RSs included in the second RS set.
Citation Information
Patent Citations
Beam failure reporting
CN116438838A
Method and apparatus for controlling aperiodic signals and reporting in positioning
CN116508287A
Flexible measurement reporting in multi-radio access technology scenarios
WO2019066712A1
Multi-beam CSI feedback
WO2020018258A1
Techniques for event-triggered beam group reporting
WO2023130305A1