Methods, apparatuses, and systems for user equipment initiated beam management (UEIBM) with a single bit uplink channel and multiple report configurations

Abstract

Methods, apparatuses, and systems provide recovery for UEIBM. In the context of a method, the method includes receiving downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting; determining that one or more triggering conditions associated with one or more configurations of the plurality of configurations are satisfied; and transmitting, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations of the one or more configurations.

Description

METHODS, APPARATUSES, AND SYSTEMS FOR USER EQUIPMENT INITIATED BEAM MANAGEMENT (UEIBM) WITH A SINGLE BIT UPLINK CHANNEL AND MULTIPLE REPORT CONFIGURATIONSRELATED APPLICATION

[0001] This application claims priority to EP Application No. 25166195.5 filed March 26, 2025, which is incorporated herein by reference in its entirety.TECHNOLOGICAL FIELD

[0002] The present disclosure relates generally to techniques for user equipment (UE) initiated beam management (UEIBM) and, more particularly, to techniques for UEIBM with a single bit uplink channel and multiple report configurations.BACKGROUND

[0003] In some wireless communication systems, beam management is used for maintaining reliable communication within a network. A UE may be configured to support one or more beam management procedures to improve beam selection for communication with one or more network nodes. In accordance with a beam management procedure, the UE may perform measurements to assess a quality of one or more beams used for the communication with the one or more network nodes. The UE may report information pertaining to the quality of the beam(s) to a network node, which may use the reported information for beam selection.BRIEF SUMMARY

[0004] Methods, apparatuses, and systems are disclosed to provide for UEIBM. In this regard, the method, apparatus and system are configured to provide for UEIBM with a single bit uplink channel and multiple report configurations, which may improve resource utilization and increase a performance of UEIBM at a UE.

[0005] In an example embodiment, an apparatus is provided that includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to receive downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting. The apparatus is also caused to determine that one or more triggering conditions associated with one or more configurations of the plurality of configurations are satisfied and transmit, in afirst uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations of the one or more configurations.

[0006] In some embodiments, the single bit has a first value that indicates the number of configurations by indicating that one or more triggering conditions associated with one configuration of the plurality of configurations are satisfied, or the single bit has a second value that indicates the number of configurations by indicating that one or more triggering conditions associated with more than one configuration of the plurality of configurations are satisfied.

[0007] In an example embodiment, the single bit has a first value that indicates the number of configurations by indicating that one or more triggering conditions associated with up to a pre-determined number of configurations are satisfied, or the single bit has a second value that indicates the number of configurations by indicating that one or more triggering conditions associated with more than the pre-determined number of configurations are satisfied. The instructions, when executed by the at least one processor, may cause the apparatus at least to receive second control signaling that indicates the pre-determined number of configurations. In an example embodiment, the pre-determined number of configurations is one of a set of numbers configured for the event triggered CSI reporting.

[0008] In an example embodiment, the plurality of configurations is associated with one or more types of events. The instructions, when executed by the at least one processor, cause the apparatus of an example embodiment at least to transmit, via a second uplink channel associated with the first uplink channel, a number of event triggered CSI reports corresponding to the number of configurations. In an example embodiment, the first uplink channel includes a first physical uplink control channel (PUCCH), and the second uplink channel includes a second PUCCH or a physical uplink shared channel (PUSCH).

[0009] In another embodiment, an apparatus is provided that includes at least one processor and at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to transmit downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting and to receive, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied.

[0010] In one embodiment, the single bit has a first value that indicates the number of configurations by indicating that one or more triggering conditions associated with one configuration of the plurality of configurations are satisfied, or the single bit has a secondvalue that indicates the number of configurations by indicating that one or more triggering conditions associated with more than one configuration of the plurality of configurations are satisfied. In another embodiment, the single bit has a first value that indicates the number of configurations by indicating that one or more triggering conditions associated with up to a pre-determined number of configurations are satisfied, or the single bit has a second value that indicates the number of configurations by indicating that one or more triggering conditions associated with more than the pre-determined number of configurations are satisfied. In this embodiment, the instructions, when executed by the at least one processor, may cause the apparatus at least to transmit second control signaling that indicates the predetermined number of configurations.

[0011] In an example embodiment, the pre-determined number of configurations is one of a set of numbers configured for the event triggered CSI reporting. The plurality of configurations may be associated with one or more types of events. In an example embodiment, the instructions, when executed by the at least one processor, cause the apparatus at least to receive, via a second uplink channel associated with the first uplink channel, a number of event triggered CSI reports corresponding to the number of configurations. In this embodiment, the first uplink channel may include a first physical uplink control channel (PUCCH), and the second uplink channel may include a second PUCCH or a physical uplink shared channel (PUSCH).

[0012] In an example embodiment, a method is provided that includes receiving downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting. The method also includes determining that one or more triggering conditions associated with one or more configurations of the plurality of configurations are satisfied and transmitting, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations of the one or more configurations.

[0013] In another embodiment, a method is provided that includes transmitting downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting. The method also includes receiving, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied.

[0014] In an example embodiment, a non-transitory computer readable storage medium is provided that includes computer instructions that, when executed by an apparatus, cause the apparatus at least to receive downlink control signaling that indicates a plurality ofconfigurations for event triggered channel state information (CSI) reporting. The computer instructions, when executed by the apparatus, also cause the apparatus to determine that one or more triggering conditions associated with one or more configurations of the plurality of configurations are satisfied and transmit, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations of the one or more configurations.

[0015] In another embodiment, a non-transitory computer readable storage medium is provided that includes computer instructions that, when executed by an apparatus, cause the apparatus at least to transmit downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting. The instructions, when executed by the apparatus, also cause the apparatus to receive, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied.

[0016] In an example embodiment, an apparatus is provided that includes means for receiving downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting. The apparatus also includes means for determining that one or more triggering conditions associated with one or more configurations of the plurality of configurations are satisfied and means for transmitting, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations of the one or more configurations.

[0017] In another embodiment, an apparatus is provided that includes means for transmitting downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting. The apparatus also includes means for receiving, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied.

[0018] The above summary is provided merely for purposes of summarizing some example embodiments to provide a basic understanding of some aspects of the disclosure. Accordingly, it will be appreciated that the above-described embodiments are merely examples and should not be construed to narrow the scope of the disclosure in any way. It will also be appreciated that the scope of the disclosure encompasses many potential embodiments in addition to those summarized here, some of which will be further described below.BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Having thus described certain example embodiments of the present disclosure in general terms, reference will hereinafter be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

[0020] FIG. 1 illustrates an example diagram of a communication system to which one or more examples disclosed herein may be applied;

[0021] FIG. 2 illustrates an example timing diagram to which one or more examples disclosed herein may be applied;

[0022] FIGs. 3 through 5 illustrate example signaling diagrams to which one or more examples disclosed herein may be applied;

[0023] FIG. 6 illustrates an example block diagram of an apparatus to which one or more examples disclosed herein may be applied; and

[0024] FIGs. 7 and 8 illustrate example flowcharts of methods to which one or more examples disclosed herein may be applied.DET AIDED DESCRIPTION

[0025] The following embodiments are exemplary. Although the specification may refer to “an”, “one”, or “some” embodiment(s) in several locations of the text, this does not necessarily mean that each reference is made to the same embodiment(s), or that a particular feature only applies to a single embodiment. Single features of different embodiments may also be combined to provide other embodiments. Further, when a particular feature, structure, or characteristic is described in connection of an embodiment, it is within the knowledge of one skilled in the art to apply such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. It shall be understood that although the terms “first,” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.

[0026] For the purposes of the present disclosure, the phrases “at least one of A or B”, “at least one of A and B”, and “A and / or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and / or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B, and C).

[0027] Certain embodiments described may be implemented in a communication network, such as any of the following radio access technologies (RATs): wireless fidelity (Wi-Fi), BLUETOOTH, Worldwide Interoperability for Micro-wave Access (WiMAX),Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, and enhanced LTE (eLTE), 5G (also called NR), or any future radio access technology (RAT) such as 6G. Moreover, communication within the communication network may utilize any suitable wireless communication technology, including but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), MIMO, Orthogonal Frequency Division Multiplexing (OFDM), and / or Discrete Fourier Transform spread OFDM (DFT-s-OFDM).

[0028] As used herein, the term “network device” or “network node” refers to a node in a communication network via which user equipment may access the network and / or which is capable of controlling radio communication and managing radio resources within a cell. The network node or network device may be referred to as a base station (BS), an access point (AP), an access node, or a transmission reception point (TRP). The network device may be, depending on the applied technology, for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geostationary orbit (GEO) satellite, or an aircraft network device.

[0029] Moreover, in connection of split radio access network (RAN), the network device may refer to a centralized unit (CU) of a base station and / or a distributed unit (DU) of a base station. An interface between CU and DU may be referred to as an Fl interface in NR. In the split RAN architecture, node operations may be carried out, at least partly, in the central / centralized unit, CU, (e.g., server, host or node) operationally coupled to the DU, (e.g., a radio head / node). One CU may control one or more DUs, acting at least as transmit / receive (Tx / Rx) nodes. In at least one embodiment, the DUs may include e.g., a radio link control (RLC), medium access control (MAC) layer and a physical (PHY) layer, whereas the CU may include the layers above RLC layer, such as a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer and an internet protocol (IP) layer. The PHY layer may also be referred to as Layer 1 (LI). That is, LI may include the PHY layer. Additionally, Layer 2 (L2) may include the RLC layer and the MAC layer. Otherfunctional splits are possible too. In practice, any processing task may be performed in either the CU or the DU and the boundary where the responsibility is shifted between the CU and the DU may depend on the applied implementation.

[0030] The term “core network entity,” and the like, refers to entities, nodes, or network functions used to support one or more functionalities of a core network, such as an evolved packet core (EPC). In some examples, a core network entity includes a mobility management entity (MME) and / or a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signaling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to / from the terminal devices. The 5G specifications specify the core network as a 5G core (5GC). Additionally, or alternatively, a core network entity may include an access and mobility management function (AMF), a user plane function / gateway (UPF), and / or one or more other functions, such as a location management function (LMF). The AMF may handle termination of non-access stratum (NAS) signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The UPF node may support packet routing and forwarding, packet inspection and quality of service (QoS) handling, for example. The EMF supports the positioning architecture of the network. The LMF may determine the position of a mobile device (e.g., a UE) based on measurements and / or assistance information obtained at the LMF, for example, from a network entity (e.g., a RAN) serving the mobile device and / or the mobile device itself. In some examples, the LMF may obtain the measurements and / or assistance information via the AMF.

[0031] The term “terminal device,” refers to any end device that may be capable of wireless communication. By way of example, a terminal device may be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), or a Mobile Station (MS). The terminal device may include a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, Universal Serial Bus (USB) dongles, an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating inan industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like.

[0032] The term “resource”, as used herein, may refer to one or more radio resources in time domain, in frequency domain, in space domain, and / or in code domain. Some examples of resources include e.g., a physical resource block (PRB), a radio frame, a subframe, a time slot, a subband, a frequency region, a sub-carrier, a beam, etc. The term “transmission” and / or “reception” may refer to wirelessly transmitting and / or receiving via a wireless propagation channel on one or more radio resources.

[0033] FIG. 1 illustrates an example diagram of a communication system 100 (e.g., a communication network) to which one or more examples disclosed herein may be applied. The communication system (also referred to herein as a cellular communication network or system) may include a network node 110 providing one or more cells, such as source cell 101, and a network node 112 providing one or more other cells, such as target cell 102. Each cell may be, e.g., a macro cell, a micro cell, femto, or a pico cell, for example. The cell may define a coverage area or a service area of the corresponding access node. The network nodes 110 and 112 may also be referred to herein as network entities.

[0034] The network node 110 may provide a UE 120 (one or more UEs) with wireless access to the communication network. The wireless access may include downlink (DL) communication from the network node to the UE 120 and uplink (UL) communication from the UE 120 to the network node. Examples of uplink channels include physical uplink control channel (PUCCH) for transmitting control information and physical uplink shared channel (PUSCH) for transmitting data towards the network. Examples of downlink channels include physical downlink control channel (PDCCH) for transmitting control information and physical downlink shared channel (PDSCH) for transmitting data towards the user equipment.

[0035] There may be a plurality of UEs 120, 122 in the system. Each of them may be served by the same or by different network nodes 110, 112. UE may be configured with dual connectivity (DC), wherein the UE, e.g., UE 120, may be connected to multiple network nodes 110, 112. The UEs 120, 122 may communicate with each other, in case device-to-device (D2D) communication interface is established between them via a so-called sidelink (SL). Such D2D communications may be referred to as machine-to-machine, peer-to-peer (P2P) communications, or vehicle-to-vehicle (V2V), for example.

[0036] In the case of multiple network nodes in the communication network, the network nodes may be connected to each other via an interface. LTE specifications call such aninterface as X2 interface. An interface between an LTE node and a 5G node, or between two 5G nodes may be called Xn interface.

[0037] The network nodes 110 and 112 may be further connected via another interface to a core network 116 (also referred to herein as the core 116) of the communication network. The LTE specifications specify the core network as an evolved packet core (EPC), and the core network may include, for example, a mobility management entity (MME) and a gateway node. The MME may handle mobility of terminal devices in a tracking area encompassing a plurality of cells and handle signaling connections between the terminal devices and the core network. The gateway node may handle data routing in the core network and to / from the terminal devices. The 5G specifications specify the core network as a 5G core (5GC). The 5G core may include, for example, an access and mobility management function (AMF) and a user plane function / gateway (UPF) and other functions. The AMF may handle termination of non-access stratum (NAS) signaling, NAS ciphering & integrity protection, registration management, connection management, mobility management, access authentication and authorization, security context management. The UPF node may support packet routing and forwarding, packet inspection and quality of service (QoS) handling, for example.

[0038] In 5G New Radio, different kinds of data transfer services are offered by the medium access control (MAC) layer. To accommodate different kinds of data transfer services, multiple types of logical channels are defined. A MAC protocol data unit (MAC PDU) may consist of one or more MAC control elements (MAC CEs) corresponding to one or more features requiring the MAC CEs. According to the third generation partnership project (3GPP) technical specification (TS) 38.321, the MAC PDU includes a subheader with a logical channel identification (LCID) value or an extended LCID (eLCID) value. In some examples, the UEs 120, 122 may be configured to transmit information pertaining to a beam management procedure to the network nodes 110, 112 via one or more MAC CEs.

[0039] A MAC PDU is a bit string that is byte aligned (e.g., multiple of 8 bits) in length. The bit strings are represented by tables in which the most significant bit is the leftmost bit of the first line of the table, the least significant bit is the rightmost bit on the last line of the table, and more generally the bit string is to be read from left to right and then in the reading order of the lines. The bit order of each parameter field within a MAC PDU is represented with the first and most significant bit in the leftmost bit and the last and least significant bit in the rightmost bit.

[0040] A MAC SDU is a bit string that is byte aligned (e.g., multiple of 8 bits) in length. A MAC SDU is included into a MAC PDU from the first bit onward. A MAC CE is a bitstring that is byte aligned (e.g., multiple of 8 bits) in length. A MAC subheader is a bit string that is byte aligned (e.g., multiple of 8 bits) in length. Each MAC subheader is placed immediately in front of the corresponding MAC SDU, MAC CE, or padding. The MAC entity shall ignore the value of the Reserved bits in downlink MAC PDUs. The MAC SDUs may have variable sizes. The MAC PDU may include one or more MAC subPDUs. Each MAC subPDU includes one of the following: a MAC subheader only (including padding); a MAC subheader and a MAC SDU; a MAC subheader and a MAC CE; or a MAC subheader and padding. The MAC CEs may be placed together. DL MAC subPDU(s) with MAC CE(s) is placed before any MAC subPDU with MAC SDU and MAC subPDU with padding.Uplink MAC subPDU(s) with MAC CE(s) is placed after all the MAC subPDU(s) with MAC SDU and before the MAC subPDU with padding in the MAC PDU. The size of padding can be zero. A maximum of one MAC PDU can be transmitted per transport block (TB) per MAC entity.

[0041] Referring to FIG. 1 , the system may be configured to support multiple-input multiple-output (MIMO) operations, for example, at the UEs 120, 122 or the network nodes 110, 112. In some examples, the system may support UE event driven reporting for MIMO operations. For example, the system may support one or more features to facilitate UE-initiated / event-driven beam management for reducing overhead and / or latency. As used herein, UE-initiated / event-driven beam management refers to event-driven beam management that is initiated by a UE. In some examples, the term event-driven beam management refers to a beam management procedure that is triggered in response to one or more events. In some examples, UE-initiated / event-driven beam management may include the use of a unified transmission configuration indicator (TCI) and / or one or more channel state information (CSI) measurement and reporting configuration frameworks. Additionally, in some examples, UE-initiated / event-driven beam management may utilize one or more frequency ranges, such as FR2 (Frequency Range 2) or other frequency ranges that may include operational frequencies in the millimeter wave (mmWave) region (e.g., above 24 giga Hertz (GHz)). Additionally, in some examples, UE-initiated / event-driven beam management may include (or be otherwise associated with) a transmission reception point (TRP), such as a single transmission reception point (sTRP) with intra-cell beam management and / or inter-cell beam management. In some instances, uplink signaling (e.g., uplink signaling content(s) and / or uplink signaling procedure(s)) for UE-initiated / event-driven beam reporting facilitates relatively fast beam switching. Additionally, in some instances, the UE-initiated / event-drivennature of uplink transmissions, uplink signaling medium(s) / container(s) may be used for (e.g., designed for) the purpose of beam reporting.

[0042] The communication system 100 may support UEIBM. For example, the communication system 100 may employ UEIBM for cases in which a UE (e.g., the UE 120, the UE 122) may benefit from initiating beam reporting to facilitate a beam switch. In some examples, the UEIBM feature refers to cases in which a UE may be configured with at least one event, and may initiate (e.g., start) beam reporting if the at least one event occurs. For example, an event may be associated with at least one condition, and the UE may determine that the event occurred (or is occurring) if the at least one condition is satisfied. UEIBM may lead to reduced overhead within the communication system 100. For example, in accordance with UEIBM, beam reports may be sent by the UE in response to events (e.g., are only sent when needed), thereby reducing a likelihood of unnecessary beam reports, which may occur in the case of periodic reporting configured with relatively small periodicities. UEIBM may also lead to reduce latency within the communication system 100. For example, beam reports may be sent by the UE in response to one or more conditions being satisfied, thereby reducing a likelihood of unnecessary delays, which may occur in the case of periodic reporting configured with large periodicities.

[0043] In some examples, UEIBM may be used in accordance with MIMO. In some such examples, the communication system 100 may support one or more features to facilitate UEI / event-driven beam management for reducing overhead and / or latency. For example, the communication system 100 may support a unified TCI, while leveraging (e.g., as much as possible) one or more CSI measurement and reporting configuration frameworks, targeting frequency range 2 (FR2) and sTRP with intra- and inter-cell beam management. Additionally, or alternatively, the communication system 100 may support UL signaling content(s) (and procedure(s) as required) for UE-initiated / event-driven beam reporting facilitating fast beam switching. Additionally, or alternatively, the communication system 100 may support UL signaling medium / container considering the UE-initiated / event-driven nature of the UL transmission, designed primarily for the purpose of beam reporting.

[0044] In some examples of the communication system 100, a UE (e.g., the UE 120, the UE 122) may be configured to support a UEIBM framework in which the UE is configured to send a single UEI beam report irrespective of whether one or multiple UEI beam reports are triggered (e.g., in response to various conditions being satisfied). In some such examples, resources used at the UE to perform measurements for multiple UEI beam reports are used unnecessarily (e.g., wasted), which is inefficient and reduces the performance of the UE.

[0045] In some other examples of the communication system 100, the UE may be configured to support one or more techniques for UEIBM with a single bit uplink channel and multiple report configurations, as described herein. In some such examples, the UE may receive downlink control signaling that indicates multiple configurations for event triggered CSI reporting. The UE may determine that one or more triggering conditions associated with one or more configurations of the multiple configurations are satisfied. In response to determining that the that one or more triggering conditions are satisfied, the UE may transmit, in a first uplink channel (e.g., PUCCH) associated with the multiple configurations, a single bit that indicates a number of configurations of the one or more configurations. In other words, the UE may transmit an uplink channel carrying a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied (e.g., that have been triggered). By providing the network with the number of configurations that have been triggered, the UE may improve resource utilization, reduce latency, and increase a performance of UEIBM at the UE.

[0046] The network may dynamically adjust the size of a second uplink channel (e.g., PUSCH) for UEI beam reporting based on the number of configurations that have been triggered. For example, the UE may be configured to support one or more techniques for UEIBM with a variable size uplink channel, as described herein. In such an example, the UE may determine that one or more triggering conditions associated with one or more configurations of multiple configurations for event triggered CSI reporting are satisfied. In response to determining that the one or more triggering conditions are satisfied, the UE may transmit, in a first uplink channel (e.g., PUCCH) associated with the multiple configurations, a single bit that indicates a number of configurations of the one or more configurations. That is, the UE may transmit an uplink channel carrying a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied (e.g., that have been triggered). In some examples, in response to the first uplink channel, the UE may receive an indication of a grant for a second uplink channel (e.g., PUSCH) for the event triggered CSI reporting. In such examples, the second uplink channel has a size that is based on the number of configurations. By dynamically adjusting the size of the second uplink channel, the network may improve resource utilization, reduce latency, and increase a performance of UEIBM at the UE.

[0047] In some examples, the UE and the network may also support one or more techniques for UEIBM with flexible uplink scheduling. For example, the UE may determine that one or more triggering conditions associated with one or more configurations of multipleconfigurations for event triggered CSI reporting are satisfied. In response to determining that the one or more triggering conditions are satisfied, the UE may transmit, in a first uplink channel (e.g., PUCCH) associated with the multiple configurations, a single bit that indicates a number of configurations of the one or more configurations. That is, the UE may transmit an uplink channel carrying a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied (e.g., that are triggered). In some examples, after transmission of the first uplink channel, the UE may transmit at least one event triggered CSI report via at least one second uplink channel in accordance with at least one type of uplink grant that is based on the number of configurations.

[0048] In some such examples, the UE may transmit the at least one event triggered CSI report in accordance with a single type of uplink grant. For example, the UE may transmit the at least one event triggered CSI report via a second uplink channel in accordance with a first type of uplink grant based on the number of configurations including one configuration or up to a pre-determined number of configurations. Alternatively, the UE may transmit the at least one event triggered CSI report via a second uplink channel in accordance with a second type of uplink grant based on the number of configurations including more than one configuration or more than a pre-determined number of configurations.

[0049] In some other examples, the UE may transmit event triggered CSI reports in accordance with multiple types of grants (e.g., both the first type of grant and the second type of grant). For example, the UE may transmit, via one second uplink channel in accordance with the first type of uplink grant, at least a first event triggered CSI report associated with at least a first configuration of the at least two configurations. Additionally, the UE may transmit, via another second uplink channel in accordance with the second type of uplink grant, at least one other event triggered CSI report associated with at least one other configuration of the at least two configurations. By enabling the UE to use one or more types of grants for transmission of the event triggered CSI reports (e.g., by dynamically scheduling the second type of grant based on the number of triggered configurations), the network may reduce latency and improve resource utilization within the communication system 100.

[0050] FIG. 2 illustrates example timing diagrams 200 to which one or more examples disclosed herein may be applied. The timing diagrams 200 (e.g., timing diagram 200-a, timing diagram 200-b, timing diagram 200-c) may be implemented within a communication system, such as within the system of FIG. 1 , by a UE and / or a network node in accordance with one or more aspects of the present disclosure. As illustrated in the example of FIG. 2, various events may trigger a UEI beam report.

[0051] For example, an event referred to herein as Event-2 may trigger a UE to transmit a UEI beam report. Event-2 may include a scenario in which the quality of at least one new beam is sufficiently better than the quality of the current beam. The term “current beam,” as used herein, refers to a beam which a UE is actively using, or is configured to use, to transmit data to and / or receive data from a network node. The term “new beam,” as used herein, refers to a beam that a UE is not actively using, or is not configured to use, to transmit data to and / or receive data from a network node. In some examples, new beams are referred to as “candidate beams” or “candidate new beams.”

[0052] Event-2 may include a scenario in which a quality, such as the LI reference signal received power (Ll-RSRP), of at least one new beam becomes a threshold value better than the current beam. In other words, in accordance with Event-2, the UE may determine that at least one new beam is sufficiently better than the current beam based on the Ll-RSRP (or another quality metric) of the at least one new beam becoming better than that of the current beam by a threshold value. In such an example, the UE may be triggered to transmit a beam report in response to determining that the Ll-RSRP (or another quality metric) of the at least one new beam becomes better than that of the current beam by the threshold value. For example, the network may configure the UE with a threshold, such as pre-determined number of decibels (dB). In such an example, when the UE measures a new beam to have an Ll-RSRP value that is the predetermined number of dB better than the Ll-RSRP of the current beam, a UEI beam report is triggered. As an illustrative example, the network may configure the UE with a threshold of 3 dB. In such an example, when the UE measures a new beam to have an Ll-RSRP value that is 3 dB better than the Ll-RSRP of the current beam, a UEI beam report is triggered.

[0053] Another event referred to as Event- 1 may additionally, or alternatively, trigger a UE to transmit a UEI beam report. Event- 1 may include scenarios in which the quality of the current beam becomes worse than a threshold. For example, the network may configure the UE with a threshold, such as pre-determined number of dBm (decibel-milliwatts). In such an example, when the UE measures the current beam to have an Ll-RSRP value that is less than the pre-determined number of dBm, a UEI beam report is triggered. In some examples, the UE may use Event- 1 to reduce a likelihood of the UE performing beam failure recovery (BFR), or other costly beam management procedures (e.g., in terms of resources and power consumption). Another event referred to as Event-7 may additionally, or alternatively, trigger a UE to transmit a UEI beam report. Event-7 may include scenarios in which the quality of at least one new beam is sufficiently better than the quality of a reference signal, such as areference signal derived from an activated TCI with the Q-th best quality. In some examples, Event-7 may include a scenario in which the quality, such as Ll-RSRP, of at least one new beam becomes a threshold value better than the reference signal derived from the activated TCI state with the Q-th best quality. The UE may use Event-7 to update the active TCI state list.

[0054] A UE may be configured with multiple options for determining whether Event-2 is triggered. In other words, in the context of triggering event determinations for Event-2, the UE may have multiple options. In some examples, the UE may determine that Event-2 is triggered, and thus a UEI beam report may be sent, once the Ll-RSRP of the new beam becomes a threshold value better than the current beam. Additionally, or alternatively, the UE may determine that Event-2 is triggered, and thus a UEI beam report may be sent, if, within a time window (which may be configurable), a predetermined number of Event-2 instance(s) for at least one same new beam is greater than or equal to a predetermined number M (which may also be configurable). In other words, the UE may determine to send a UEI beam report for Event-2 in response to one or a predetermined number (e.g., M) occurrences of Event-2.

[0055] A UE may, additionally, or alternatively, be configured with multiple options for sending a UEI beam report in response to an event being triggered. In other words, in the context of how UEI beam reports are to be sent by the UE to the network, the UE may be configured with multiple options (e.g., procedures). In some examples, the UE may be configured to send UEI beam report(s) in accordance with Mode A, in which a second UL channel for transmission of the UEI beam report is a PUSCH dynamically scheduled by the network (e.g., a gNB). In accordance with Mode A, the UE may send, in a first UL channel (e.g., a PUCCH) a single-bit UL indication to request that the gNB allocate resources in the PUSCH to carry the UEI beam report. In response to the request, the gNB indicates to the UE, via downlink control information (DCI), an allocation of a PUSCH resource to carry the UEI beam report. In response to receiving the indication of the PUSCH resource, the UE sends the UEI beam report on the allocated (e.g., scheduled) PUSCH resource.

[0056] In some other examples, the UE may be configured to send UEI beam report(s) in accordance with Mode B, in which a second UL channel for transmission of the UEI beam report is a PUSCH (e.g., a CG-PUSCH) pre-configured by the gNB. In accordance with Mode B, the UE may send, in a first UL channel (e.g., a first PUCCH), a single-bit UL indication to notify the gNB that a UEI beam report is to be transmitted in a pre-configured CG-PUSCH resource. After transmission of the first UL channel, the UE may send the UEI beam report in the first CG-PUSCH resource X symbols after the first PUCCH. The value ofX may be configured by the network. In some examples, Mode A may be a baseline procedure supported by UEs capable of UEIBM. In some such examples, Mode B may be optional and supported by some UEs.

[0057] In some examples, the UL signal content of a UEI beam report for Event-2 with Ll-RSRP as the quality metric, may include information for N beams. For example, a UE may be configured to report beam information for the top N beams, in which the top N beams is the N beam(s) with the highest value(s) of the quality metric among measured beams). In such an example, the beam information may include, for the N beams (e.g., for each of the N beam), the beam index (e.g., channel state information reference signal resource indicator (CRI) or synchronization signal block resource indicator (SSBRI)), the Ll-RSRP value, and / or an indication of whether the beam triggered Event-2. In some examples, such as examples in which the network configures N>1 via RRC, at least one of the N beams included in the UEI beam report may satisfy Event-2. In some examples, in addition to beam information for the N beams, the network may configure, via RRC, the UE to also report beam information for the current beam.

[0058] In some examples, a UE may be configured to monitor (e.g., measure) one or more types of reference signals for Event-2. In other words, in the context of which reference signals may be monitored / measured for the current beam and one or more new beams by the UE for Event-2, the UE may monitor one or more types of reference signals for the current beam and a pre-determined number of new beams. For example, the reference signal(s) for the new beam(s) may be explicitly configured by the network via RRC and may be either a set of synchronization signal blocks (SSBs) or a set of CSI-RSs. In some examples, the reference signal for the current beam is related to an indicated TCI state, with an implicit method, such that the current beam is either the actual reference signal (e.g., the beam used to actually receive the reference signal) in the indicated TCI state or the SSB which is quasi colocated (QCLed) with the actual reference signal in the indicated TCI state, depending on the configured set of new beams, to increase a likelihood that the reference signals of the current beam and new beams are of the same type (e.g., are either all SSBs or all CSI-RSs).

[0059] In some examples, UEIBM may support beam reporting for Event-2, Event- 1, and Event-7. In other words, on UE-initiated / event-driven beam reporting, regarding trigger events, Event-2, Event- 1, and Event-7 may be supported. In some such examples, Event- 1 corresponds to scenarios in which the quality of the current beam is worse than a predetermined threshold, and Event-7 corresponds to scenarios in which the quality, such as Ll-RSRP, of at least one new beam becomes a threshold value better than the reference signal(RS) derived from the activated TCI state with the Q-th best quality. The value of Q may be RRC configured (e.g., subject to UE capability signalling). In some examples, Event-1 and / or Event-7 may use the same design as Event-2.

[0060] In some examples of UEIBM, a UE may be configured with multiple (different) CSI report configurations. For example, a UE may be configured with two (different) CSI report configurations for Event-2. In the example of FIG. 2, the UE may be configured with Configuration-A and Configuration-B for Event-2. In some examples, different CSI report configurations, such as Configuration-A and Configuration-B, may differ in terms of one or more parameters. For example, Configuration-A and Configuration-B may differ in terms of threshold, set of new beams, number N of reported beams, and / or one or more other types if parameters. In some examples, different CSI report configurations, such as Configuration-A and Configuration-B, may differ as to whether the UE is to include the current beam in the beam report. That is, different CSI report configurations, such as Configuration-A and Configuration-B, may differ as to whether the UE is to include beam information for the current beam in the beam report (e.g., in addition to beam information for N new beams).

[0061] In some examples, a UE may be configured with a single PUCCH resource for multiple configurations. In other words, on beam report transmission procedure for UE-initiated / event-driven beam reporting, a single first PUCCH resource may be associated with one or multiple CSI report configurations (e.g., regarding the same or different events). In the example of FIG. 2, the UE may be configured with a single PUCCH for Configuration-A and Configuration-B (e.g., regarding Event-2).

[0062] In some examples in which a UE is configured with a single PUCCH resource for multiple configurations, the UE may transmit a single UEI beam report via a single PUSCH. That is, in some examples, only a single UEI beam report may be carried in a single PUSCH. In the example of FIG. 2, a single UEI beam report may be carried in a single PUSCH. In some such examples, an additional indication of one CSI report configuration may be provided in the report format of the single PUSCH. For example, the single PUSCH may include an additional indication of Configuration-A or Configuration-B. The CSI report configurations associated with the same PUCCH resource may be ordered. For example, the CSI report configurations associated with the same PUCCH resource may be ordered in ascending order of corresponding configuration identifier (e.g., CSI-ReportConfigld). In such an example, the number of bits of the additional indication field may be ceil(log2(N_CSIconfig)), in which the N_CSIconfig denotes the number of CSI report configurations associated with the same PUCCH resource. Alternatively, as illustrated in theexample of FIG. 2, the CSI report configurations associated with the same PUCCH resource may be ordered in ascending order of triggering time. In some examples, the payload size of the single UEI beam report may be determined according to the maximum payload size among the associated CSI report configurations. As illustrated in the example of FIG. 2, zero padding may be appended to a UEI beam report if the payload size of the UEI beam report is less than the payload capacity of the PUSCH 210 (e.g., less than the maximum report payload). In some examples, zero padding includes adding zeros to the end of a time-domain signal, for example, to increase the time-domain length of the signal without adding data (e.g., information) to the signal.

[0063] A reported (e.g., transmitted) UEI beam report may satisfy one or more triggering condition associated with the UEI beam report. That is, a UEI beam report transmitted by a UE may satisfy a set of one or more conditions specified by a CSI report configuration associated with the UEI beam report (e.g., a CSI report configuration for which the UEI beam report is transmitted). In some such examples, if multiple sets of conditions (for multiple CSI report configurations) are satisfied, the UE may down-select from the multiple CSI report configurations. For example, the UE may down-select from the multiple CSI report configurations according to UE implementation (e.g., it is up to UE implementation to select one of the multiple CSI report configurations). That is, in some examples, the down-selection may be according to UE implementation. Additionally, or alternatively, the down-selection may be according to priority. For example, a UEI beam report with the highest priority among UEI beam reports is reported. In some other examples, the down-selection may be according to triggering time. For example, a UEI beam report triggered in the latest (e.g., most recent) measurement is reported. The term “triggering time,” and the like, as used herein, refers to a time at which a UEI beam report is triggered. In one non-limiting example, the triggering time includes a time instance at which (or a time window over which) a UE performs one or more measurements that result in an event being triggered. In another nonlimiting example, the triggering time includes a time instance at which (or a time window over which) the UE determines an event is triggered (e.g., based on the performed measurements). In some examples, multiple CSI report configurations associated with a single first PUCCH resource (the same first PUCCH resource) may be configured in the same component carrier (CC). For Mode A, the multiple CSI report configurations associated with the same first PUCCH resource may be associated with the same CSI-AperiodicTriggerState. For Mode B, the multiple CSI report configurations associated with the same first PUCCHresource may be associated with the same second PUSCH resource (e.g., pre-configured / scheduled for transmission of the UEI beam report).

[0064] In some examples in which a UE is configured with multiple CSI report configurations that are associated to the same first PUCCH and for Event-2, once the conditions of at least one of the configured CSI report configurations associated to Event-2 are satisfied, the UE may send a single-bit first PUCCH to the gNB. In such examples, because the first PUCCH is single-bit and common to multiple configured CSI report configurations, the gNB does not know which conditions associated to which CSI report configurations were satisfied. That is, the gNB lacks information for determining the at least one configured CSI report configuration for which the conditions were satisfied.

[0065] In some such examples, after sending the first PUCCH, the UE sends a single UEI beam report on a second PUSCH resource for one of the at least one configured CSI report configurations that were satisfied. Because the gNB lacks information for determining the at least one configured CSI report configuration for which the conditions were satisfied, the UE may also send, in addition to the UEI beam report, an indication of a CSI report configuration whose conditions were met. In some such examples, the size of the second PUSCH used for carrying the beam report (either scheduled by the gNB in Mode A or pre-configured in Mode B) may be determined based on the maximum payload size among the configured CSI report configurations. In some examples, if the payload size of the sent UEI beam report is less than the maximum payload size among the configured CSI report configurations, zero padding is used.

[0066] As illustrated in the example of FIG. 2, in accordance with some UEIBM frameworks, if the conditions of multiple CSI report configurations are met, only one UEI beam report is sent. For example, the UE may send, at maximum, one UEI beam report in cases in which multiple CSI report configurations are configured. In the example of FIG. 2, the UE is configured with two CSI report Configurations, denoted as Configuration A and Configuration B, both of which are associated with Event-2. As illustrated in the example of FIG. 2, Configuration-B has a larger pay load than Configuration- A. That is, Configuration-B has the largest payload among the configured CSI reports. Configuration-B may have a larger payload than Configuration-A based on Configuration-B specifying for more beams to be reported than Configuration-A.

[0067] As illustrated in the example of FIG. 2, Configuration A and Configuration B are associated with the same first PUCCH (e.g., PUCCH 208-a, PUCCH 208-b, PUCCH 208-c). Accordingly, Configuration A and Configuration B are also associated with the same secondPUSCH (e.g., PUSCH 210-a, PUSCH 210-b, PUSCH 210-c), in which the size of the second PUSCH is based on the size of Configuration B (e.g., based on Configuration-B having the largest payload among the configured CSI report configurations).

[0068] In some examples, a single UEI beam report is triggered. For example, in the timing diagram 200-a of FIG. 2, UEI beam report 204-a (associated with Configuration- A) is triggered at time 206-a. That is, time 206-a corresponds to the triggering time for UEI beam report 204-a. In response to UEI beam report 204-a being triggered, the UE sends PUCCH 208-a (the first PUCCH associated with UEI beam report 204-a and UEI beam report 204-b) to the network to notify the network that the UE intends to transmit a UEI beam report, or to request a PUSCH allocation for transmission of a UEI beam report. After transmission of the PUCCH 208-a, the UE sends the PUSCH 210-a carrying the UEI beam report 204-a. As illustrated in the timing diagram 200-a, the UE appends zero padding to the UEI beam report 204-a based on the payload size of UEI beam report 204-a being less than the payload size of UEI beam report 204-b. In the timing diagram 200-b of FIG. 2, UEI beam report 204-b (associated with Configuration-B) is triggered at time 206-b. That is, time 206-b corresponds to the triggering time for UEI beam report 204-b. In response to UEI beam report 204-b being triggered, the UE sends a PUCCH 208-b (e.g., the first PUCCH associated with UEI beam report 204-a and UEI beam report 204-b) to the network to notify the network that the UE intends to transmit a UEI beam report, or to request a PUSCH allocation for transmission of a UEI beam report. After transmission of the PUCCH 208-b, the UE sends the PUSCH 210-b (e.g., the second PUSCH) carrying the UEI beam report 204-b. As illustrated in the timing diagram 200-b, no zero padding is appended to the UEI beam report 204-b.

[0069] In some examples, if the conditions of multiple CSI report configurations are met, the UE is not allowed to report back more than one UEI beam report. For example, in the timing diagram 200-c of FIG. 2, UEI beam report 204-a is triggered at time 206-a and UEI beam report 204-b is triggered after UEI beam report 204-a at time 206-b. In response to UEI beam report 204-a and UEI beam report 204-b being triggered, the UE sends PUCCH 208-c to the network to notify the network that the UE will transmit a UEI beam report, or to request a PUSCH allocation for transmission of a UEI beam report. After transmission of the PUCCH 208-a, the UE sends the PUSCH 210-c carrying the UEI beam report 204-a (e.g., only carrying UEI beam report 204-a). The UE may include the UEI beam report 204-a in the PUSCH 210-c based on the triggering time for UEI beam report 204-a occurring before the triggering time of UEI beam report 204-b. As illustrated in the timing diagram 200-c, the UEappends zero padding to the UEI beam report 204-a based on the payload size of UEI beam report 204-a being less than the payload size of UEI beam report 204-b.

[0070] The constraint of reporting a single UEI beam report may be inefficient and lead to reduced resource utilization (e.g., wasted resources). For example, for triggered UEI beam reports that are not reported, the UE has already performed the measurements for the UEI beam reports, and consumed energy to do so. As such, preventing the UE from reporting the performed measurements is inefficient. A more efficient framework for UEIBM reporting may include a mechanism by which the UE may inform the network of how many CSI report configurations have been triggered (and thus how many UEI beam reports are to be sent) and, if necessary, enable the UE to report measurements for multiple UEIBM configurations.

[0071] In some examples, for cases in which multiple events are simultaneously triggered (e.g., for different events, such as Event-2 and Event-1), a common / shared UEI beam report may be sent back by the UE. In such examples, however, a different UEI beam report format may be used for any pair, triplet or even higher order of CSI report configurations, which may lead to increased complexity and be relatively difficult to implement.

[0072] In some other examples, for cases in which multiple events are simultaneously triggered (e.g., for different events, such as Event-2 and Event-1), one UEI beam report may be sent on the first available pre-configured PUSCH (e.g., a CG-PUSCH) and another UEI beam report may be sent on a following available pre-configured PUSCH (e.g., a next available CG-PUSCH). In such examples, however, at least two pre-configured PUSCH resource are used (and thus needed) to send the two UEI beam reports instead of one, which may lead to increased latency (e.g., due to a periodicity of the CS-PUSCH resource).

[0073] In yet some other examples, for cases in which multiple events are simultaneously triggered and all UEI beam reports are reported, the UE may use a multi-bit first PUCCH to inform the gNB of which events are triggered so that the gNB may dynamically schedule PUSCHs for all UEI beam reports. Such a mechanism, however, is not suitable for cases in which a single-bit first PUCCH is used and in which the gNB does not have a mechanism for determining which events are triggered.

[0074] In still some other examples, for cases in which multiple events are simultaneously triggered in Mode A, the DCI from the gNB, scheduling a PUSCH, may indicate to the UE which UEI beam report to send via the scheduled PUSCH. In such examples, however, the UE must inform the gNB (or the gNB must otherwise determine) which events and / or CSI report configurations are triggered. In some cases, the UE may lack a mechanism for informing the gNB which events and / or CSI report configurations aretriggered via a single-bit first PUCCH. For example, the UE may use a multi-bit first PUCCH to inform the gNB which events and / or CSI report configurations are triggered.Consequently, such a mechanism is not suitable for cases in which a single-bit first PUCCH is used.

[0075] Various aspects of the present disclosure provide a mechanism for a UE configured with UEIBM, with multiple CSI report configurations (CSI-Reportconfigs) associated to a same single-bit first uplink channel, to use a single bit transmitted on the single-bit first uplink channel to provide information to the gNB that indicates how many CSI report configurations have been triggered (e.g., simultaneously or consecutively triggered). By using a single-bit first uplink channel to inform the network of how many CSI report configurations have been triggered, the UE may reduce latency within the communication system. For example, the network may use such information provided by the UE for improved scheduling of a second uplink channel for UEI beam reporting. The first uplink channel may be an example of a PUCCH and the second uplink channel may be an example of another PUCCH or a PUSCH.

[0076] For example, various aspects of the present disclosure provide a mechanism for the network to dynamically adjust the size of a second uplink channel (e.g., a second PUSCH) for UEI beam reporting based on information provided in a single-bit first uplink channel (e.g., a first PUCCH). By adjusting the size of the second uplink channel based on the single-bit first uplink channel, the network may improve resource utilization and reduce latency within the communication system. For example, the single-bit first uplink channel may indicate how many CSI report configurations have been triggered. In such an example, the network may schedule a smaller second uplink channel for a smaller number of triggered CSI report configurations (thereby improving resource utilization by reducing a likelihood of wasted resources) and may schedule a larger second uplink channel for a larger number of triggered CSI report configurations (thereby reducing latency by enabling the UE to include more UEI beam reports in the second uplink channel).

[0077] Additionally, various aspects of the present disclosure provide a mechanism for a UE to send UEI beam reports via uplink channels configured using one or multiple types of uplink grants. For example, one or more aspects of the present disclosure provide a mechanism for the UE to use an uplink channel pre-configured at the UE in accordance with a first type of grant and / or an uplink channel dynamically scheduled for the UE in accordance with a second type of grant. In such an example, the network may dynamically schedule a second uplink channel (in accordance with the second type of grant) for UEI beam reportingbased on a number of triggered CSI report configurations indicated via a single-bit first uplink channel. That is, the single-bit first uplink channel (e.g., a PUCCH) may indicate how many CSI report configurations are triggered and, based on how many CSI report configurations are triggered, the UE may use a pre-configured second uplink channel (e.g., a pre-configured CG-PUSCH resource) and / or a dedicated second uplink channel (e.g., a dedicated PUSCH resource) to transmit one or more UEI beam reports to the network.

[0078] For example, for some cases in which a pre-configured CG-PUSCH accommodates (e.g., is large enough for, has space for) beam reports for the indicated number of triggered CSI report configurations, the UE may use the pre-configured CG-PUSCH to send the beam reports (e.g., without additional scheduling). In some other examples, for some cases in which a pre-configured CG-PUSCH fails to accommodate (e.g., is not large enough for, does not have space for) one or more beam reports for the number of CSI report configurations that are triggered, the network may dynamically schedule a dedicated PUSCH for transmission of the beam reports. In such examples, the UE may use the dedicated PUSCH to send the beam reports, or the UE may use the pre-configured CG-PUSCH and the dedicated PUSCH to send the beam reports. By using a pre-configured CG-PUSCH and / or a dedicated PUSCH (rather than multiple pre-configured CG-PUSCHs) to transmit UEI beam reports, the UE may reduce latency within the communication system.

[0079] FIG. 3 illustrates an example of a signaling diagram 300 to which one or more examples disclosed herein may be applied. The signalling diagram of FIG. 3 illustrates operations performed, such as within the system of FIG. 1 , by a UE 320 and a network node 310 in accordance with one or more aspects of the present disclosure. The UE 320 and the network node 310 may be examples of the corresponding devices illustrated by and described with reference to FIGs. 1 and 2. One or more operations performed at the UE 320 and the network node 310 (e.g., a gNB) may be performed in a different order than the example order shown. Additionally, or alternatively, one or more operations performed at the UE 320 and the network node 310 may be omitted and / or one or more other operations may be added. The signaling diagram 300 supports one or more techniques for UEIBM with a single bit uplink channel and multiple report configurations, as described herein.

[0080] For example, the signaling diagram 300 supports a mechanism for a UE configured with UEIBM, and with multiple CSI report configurations (CSI-Reportconfigs) associated to a same single-bit first uplink channel (e.g., a PUCCH), to use the single bit transmitted on the first uplink channel to provide information to the network that indicates how many CSI report configurations have been triggered (e.g., simultaneously and / orconsecutively triggered). As illustrated in the example of FIG. 3, a UE operating in Mode A may use the single-bit first uplink channel to inform the network, with the single bit set to a first value (e.g., “0”), that a single CSI-Reportconfig is triggered. Additionally, the UE operating in Mode A may use the single-bit first uplink channel to inform the network, with the single bit set to a second value (e.g., “1”), that multiple CSI-Reportconfigs are triggered. In other words, in accordance with various aspects of the present disclosure, one bit value (e.g., “0”) may be used to inform the gNB that a single CSI-Reportconfig has been triggered, and the other bit value (e.g., “1”) may be used to inform the gNB that multiple CSI-Reportconfigs have been triggered. For example, the UE may set the value of the single bit carried on the first uplink channel to “0” to indicate that a single CSI-Reportconfig has been triggered and may set the value of the single bit to “1” to indicate that multiple CSI-Reportconfigs have been triggered.

[0081] The network may then schedule the UE with a second uplink channel (e.g., a dedicated PUSCH) based on the value of the single bit included in the single-bit first uplink channel (e.g., a PUCCH). In some examples, the network schedules the second uplink channel based on the largest (e.g., maximum) payload size among CSI report configurations configured at the UE. In some other examples, the network schedules the second uplink channel (e.g., a dedicated PUSCH) based on the summation of a pre-determined number of payload sizes associated with the CSI report configurations configured at the UE. The predetermined number may include some or all payload sizes associated with the CSI report configurations.

[0082] As illustrated in the example of FIG. 3, the signaling diagram 300 provides a mechanism for the network to dynamically adjust the size of a second uplink channel for UEI beam reporting based on a single-bit first uplink channel. That is, for a UE configured with Mode A, the network may adapt, based on the single bit transmitted in the single-bit first uplink channel, the size of the second uplink channel for the UEI beam reporting. For example, after transmission of a single-bit first uplink channel, the UE may receive, in DCI, a grant for UL resources for a second uplink channel for UEI beam reporting, in which the grant is scheduled according to the range of triggered CSI Report configurations (e.g., as indicated by the UE in the single-bit first uplink channel with the value of the single bit set to “0” or “1”).

[0083] In some examples, such as is illustrated in FIG. 3, the single-bit first uplink channel informs the network, with the single bit set to “0”, that a single CSI report configuration is triggered and informs the network, with the single bit set to “1”, that multipleCSI report configurations are triggered. In some such examples, the network may schedule a second uplink channel (e.g., dedicated PUSCH) based on one or multiple payload sizes among the configured CSI report configurations (e.g., configured CSI-Reportconfigs). For example, for cases in which the first uplink channel carries a single bit with the value set to “0”, the network may schedule a second uplink channel based on the largest payload size among the multiple configured CSI-Reportconfigs. In other words, the network may schedule a second uplink channel with the maximum payload size among the configured CSI-Reportconfigs, which may allow the UE to send a single UEI beam report (e.g., any single UEI beam report that has been triggered). For cases in which the first uplink channel carries a single bit with the value set to “1”, the network may schedule a second uplink channel based on the summation of multiple payload sizes among the multiple configured CSI-Reportconfigs. In other words, the network may schedule a second uplink channel based on the summation of all pay load sizes or a predetermined number of largest pay load sizes, such as the two largest payload sizes, among the configured CSI-Reportconfigs, which may allow the UE to send multiple UEI beam reports (e.g., any combination of UEI beam reports that have been triggered).

[0084] In the example of FIG. 3, at 322, the network node 310 may configure the UE 320 with multiple CSI report configurations (A, B, C, and D) associated with Event-2. For example, the UE 320 may receive downlink control signaling that indicates the multiple CSI report configurations associated with Event-2 for event triggered CSI reporting. In some examples, the network node 310 may configure the UE 320 with UEIBM, to operate in accordance with Mode A, and with multiple CSI report configurations for Event-2. Although the example of FIG. 3 illustrates multiple CSI report configurations being associated with the same event (e.g., Event-2), the examples provided herein may also apply to scenarios in which multiple CSI report configurations are associated with different events. That is, multiple configured CSI-Reportconfigs may all be associated to a same event (e.g., all associated to Event-2 or all associated to Event- 1), or multiple configured CSI-Reportconfigs may be associated to different events. In some examples in which multiple configured CSI-Reportconfigs are associated to different events, the UE may be configured with more than one CSI-Reportconfig for an event (e.g., two associated to Event-2 and three to Event-1).

[0085] In some examples, at 324, the network node 310 may transmit downlink reference signals to the UE 320. The UE 320 may receive and measure the downlink reference signals via one or more beams in accordance with the multiple CSI report configurations. For example, the UE 320 may measure the received power (e.g., the LI reference signal receivedpower (Ll-RSRP) or another suitable received power metric) of the downlink reference signals received via the one or more beams in accordance with the multiple CSI report configurations.

[0086] At 326, the UE 320 may determine that configuration A is triggered. For example, the UE 320 may determine that one or more triggering conditions associated with configuration A are satisfied (e.g., based on the downlink reference signal measurements). In other words, the UE 320 may determine that one or more triggering conditions associated with one configuration of the multiple CSI report configurations are satisfied. In some examples, the UE may transmit, in a first uplink channel associated with the multiple CSI configurations, a single bit that indicates the number of triggered CSI report configurations (e.g., one).

[0087] At 328, in response to the determination at 326, the UE 320 may transmit a first uplink channel (e.g., a single-bit first PUCCH) with a single bit set to “0”. That is, the UE 320 may set the single bit of the single-bit first PUCCH to a first value (“0”) that indicates that one or more triggering conditions associated with one configuration (e.g., configuration A) of the multiple CSI report configurations are satisfied.

[0088] In some examples, at 330, in response to the first uplink channel, the UE 320 may receive DCI scheduling a second uplink channel (e.g., a dedicated PUSCH) with a size that is based on a maximum payload size among the multiple CSI report configurations. For example, the UE 320 may receive, in response to the first uplink channel, an indication of a grant for a second uplink channel for event triggered CSI reporting, in which the second uplink channel has a size that is based on the number of triggered configurations. Based on the first uplink channel sent at 328 indicating that the number of triggered configurations is one (e.g., based on the value of the single bit being set to “0”), the size of the second uplink channel may be based on the maximum payload size among the multiple CSI report configurations. The maximum pay load size may correspond to the largest pay load size among multiple payload sizes associated with the multiple CSI report configurations.

[0089] In some such examples, at 332, the UE 320 may transmit the second uplink channel with a beam report for configuration A. That is, the UE 320 may transmit, via the second uplink channel, a number of event triggered CSI reports corresponding to the number of configurations. In other words, the UE 320 may transmit, via the second uplink channel, one event triggered CSI report corresponding to the one triggered CSI report configuration.

[0090] At 334, the UE 320 may determine that configurations A and B are triggered. For example, the UE 320 may determine that one or more triggering conditions associated withconfigurations A and B are satisfied (e.g., based on the downlink reference signal measurements). In other words, the UE 320 may determine that one or more triggering conditions associated with more than one configuration of the multiple CSI report configurations are satisfied. In some examples, the UE may transmit, in a first uplink channel associated with the multiple CSI configurations, a single bit that indicates the number of triggered CSI report configurations (e.g., two).

[0091] At 336, in response to the determination at 326, the UE 320 may transmit a first uplink channel (e.g., a single-bit first PUCCH) with a single bit set to “1”. That is, the UE 320 may set the single bit to a second value that indicates that one or more triggering conditions associated with more than one configuration (e.g., configurations A and B) of the multiple CSI report configurations are satisfied.

[0092] In some examples, at 338, in response to the first uplink channel, the UE 320 may receive DCI scheduling a second uplink channel (e.g., a dedicated PUSCH) with a size that is based on the summation of all payload sizes associated with the multiple CSI report configurations. For example, the UE 320 may receive, in response to the first uplink channel, an indication of a grant for a second uplink channel for the event triggered CSI reporting, in which the second uplink channel has a size that is based on the number of triggered configurations. Based on the first uplink channel sent at 336 indicating that the number of triggered CSI report configurations is more than one (e.g., based on the value of the single bit being set to “1”), the size of the second uplink channel scheduled at 338 may be larger than the size of the second uplink channel scheduled at 330 (e.g., in response to a first uplink channel with a single bit set to “0”). For example, the size of the second uplink channel scheduled at 338 may be based on the summation of a pre-determined number of payload size among the multiple CSI report configurations. While the example of FIG. 3 illustrates the pre-determined number of payload sizes including all payload sizes associated with the multiple CSI report configurations, the examples provided herein may also apply to scenarios in which the pre-determined number of payload sizes includes some (but not all) of the payload sizes associated with the multiple CSI report configurations.

[0093] In some such examples, at 340, the UE 320 may transmit the second uplink channel with beam reports for configurations A and B (e.g., with a beam report for configuration A and another beam report for configuration B). That is, the UE 320 may transmit, via the second uplink channel, a number of event triggered CSI reports corresponding to the number of configurations. In other words, the UE 320 may transmit, viathe second uplink channel, two event triggered CSI reports corresponding to two configurations.

[0094] FIG. 4 illustrates an example of a signaling diagram 400 to which one or more examples disclosed herein may be applied. The signalling diagram of FIG. 4 illustrates operations performed, such as within the system of FIG. 1 , by a UE 420 and a network node 410 in accordance with one or more aspects of the present disclosure. The UE 420 and the network node 410 may be examples of the corresponding devices illustrated by and described with reference to FIGs. 1 through 3. One or more operations performed at the UE 420 and the network node 410 may be performed in a different order than the example order shown. Additionally, or alternatively, one or more operations performed at the UE 420 and the network node 410 may be omitted and / or one or more other operations may be added. The signaling diagram 400 supports one or more techniques for UEIBM with a single bit uplink channel and multiple report configurations, as described herein.

[0095] For example, the signaling diagram 400 supports a mechanism for a UE configured with UEIBM, and with multiple CSI report configurations (CSI-Reportconfigs) associated to a same single-bit first uplink channel (e.g., PUCCH), to use the single bit transmitted on the first uplink channel to provide information to the network that indicates how many CSI report configurations have been triggered (e.g., simultaneously and / or consecutively triggered). In other words, a UE configured with multiple CSI-Reportconfigs may use a single-bit first uplink channel to provide, to the network, information pertaining to how many CSI-Reportconfigs are triggered. In some examples, the network may use the information to determine a suitable size of a second uplink channel for UEI beam reporting by the UE. That is, the network may use the information to determine a suitable size of a second uplink channel to be allocated to enable the UE to transmit multiple UEI beam reports (e.g., when multiple UEI beam reports are triggered). As illustrated in the example of FIG. 4, a UE operating in Mode A may use the single-bit first uplink channel to inform the network, with the single bit included in the first uplink channel set to a first value (e.g., “0”), that up to L CSI-Reportconfigs are triggered. Additionally, the UE operating in Mode A may use the single-bit first uplink channel to inform the network, with the single bit included in the first uplink channel set to a second value (e.g., “1”), that more than L CSI-Reportconfigs are triggered. In other words, in accordance with various aspects of the present disclosure, one bit value (e.g., “0”) may be used to inform the gNB that up to L CSI-Reportconfigs have been triggered, and the other bit value (e.g., “1”) may be used to inform the gNB that more than L CSI-Reportconfigs have been triggered. That is, the UE may set the value of the single bitcarried on the first uplink channel to “0” to indicate that up to L CSI-Reportconfigs have been triggered and may set the value of the single bit to “1” to indicate that more than L CSI-Reportconfigs have been triggered. In some such examples, the value of L may be predefined (e.g., in a standard and hardcoded at the UE). Additionally, or alternatively, the value of L may be configured (e.g., initially configured or updated) at the UE by the network. In some examples, the network (or the UE) may select a value for L from among a pre-defined set of values. In some network implementations, the network may determine to set L to a relatively low value to reduce a likelihood of the UE sending beam information for a relatively large number of triggered CSI-Reportconfigs simultaneously (e.g., the network may not need or desire to be informed of a large number of triggered CSI-Reportconfigs at the same time).

[0096] The network may schedule the UE with a second uplink channel based on the single-bit first uplink channel. In some examples, the network schedules the second uplink channel (e.g., a dedicated PUSCH) based on the maximum payload size for the CSI report configurations. The maximum pay load size may correspond to the largest pay load size among multiple payload sizes associated with the CSI report configurations. In some other examples, the network schedules the second uplink channel (e.g., a dedicated PUSCH) based on the summation of a pre-determined number of pay load sizes. The pre-determined number of payload sizes may include some or all payload sizes associated with the CSI report configurations.

[0097] As illustrated in the example of FIG. 4, the signaling diagram 400 provides a mechanism for the network to dynamically adjust the size of a second uplink channel (e.g., PUSCH) for UEI beam reporting based on a single-bit first uplink channel (e.g., a PUCCH). That is, for a UE configured with Mode A, the network may adapt, based on the value of the single bit transmitted in the first uplink channel, the size of the second uplink channel for the UEI beam reporting. For example, after transmission of a first uplink channel, the UE may receive, in DCI, a grant for UL resources for a second uplink channel for CSI reporting, in which the grant is scheduled according to the range of triggered CSI report configurations (e.g., as indicated by the UE in the single-bit first uplink channel with the value of the single bit set to “0” or “1”).

[0098] In some examples, such as is illustrated in FIG. 4, the single-bit first uplink channel informs the network, with the value of the single bit set to “0”, that up to L CSI- Reportconfigs is triggered and informs the network, with the value of the single bit set to “1”, that more than L CSI-Reportconfigs are triggered. In some such examples, the network mayschedule a second uplink channel based on L or more than L payload sizes among the configured CSI-Reportconfigs. For example, the value of L may be set to 2 (e.g., L=2) and, as such, the single-bit first uplink channel informs the network, with the single bit set to “0”, that up to L=2 CSI-Reportconfigs are triggered and informs the network, with the single bit set to “1”, that more than L=2 CSI-Reportconfigs are triggered. In such an example, for cases in which the first uplink channel carries a bit with the value set to “0”, the network may schedule a second uplink channel based on the summation of the two largest payload sizes among multiple payload sizes associated with the configured CSI-Reportconfigs, which allows the UE to send a pair (e.g., any pair) of UEI beam reports that have been triggered. In other words, the network may schedule a second uplink channel based on the summation of L largest payload sizes among the configured CSI-Reportconfigs. Additionally, for cases in which the first uplink channel carries a bit with the value set to “1”, the network may schedule a second uplink channel based on the summation of more than two payload sizes, which allows the UE to send a combination of UEI beam reports (e.g., any combination of UEI beam reports that have been triggered). In other words, the network may schedule a second uplink channel based on the summation of more than L payload sizes associated with the CSI-Reportconfigs. For example, the network may schedule a second uplink channel based on the summation of all payload sizes among the configured CSI-Reportconfigs.

[0099] In the example of FIG. 4, at 422, the network node 410 may configure the UE 420 with multiple CSI report configurations (A, B, C, and D) associated with Event-2. For example, the UE may receive downlink control signaling that indicates the multiple CSI report configurations for event triggered CSI reporting. In some examples, the network node 410 may configure the UE 420 with UEIBM, to operate in accordance with Mode A, and with multiple CSI report configurations for Event-2. Although the example of FIG. 4 illustrates multiple CSI report configurations being associated with the same event (e.g., Event-2), the examples provided herein may also apply to scenarios in which multiple CSI-Reportconfigs are associated with different events.

[0100] In some such examples, at 424, the UE 420 may receive downlink signaling that indicates the value of L (a pre-determined number of configurations). The network may schedule a second uplink channel (e.g., a dedicated PUSCH) based on the summation of the L payload sizes among the multiple CSI report configurations (e.g., the L largest payload sizes among the multiple CSI report configurations), or the network may schedule the second uplink channel based on the summation of more than L payload sizes associated with the multiple CSI report configurations (e.g., the summation of all payload sizes associated withthe multiple CSI report configurations). In the example of FIG. 4, the UE 420 may receive downlink signaling that indicates a value of 2 for L. That is, the network may set L=2. In such an example, the network may schedule a second uplink channel based on the summation of the two largest payload sizes among the multiple CSI report configurations, or the network may schedule a second uplink channel based on the summation of more than two (e.g., all) payload sizes associated with the multiple CSI report configurations.

[0101] In some examples, at 426, the network node 410 may transmit downlink reference signals to the UE 420. The UE 420 may receive and measure the downlink reference signals via one or more beams in accordance with the multiple CSI report configurations. For example, the UE 420 may measure the received power (e.g., Ll-RSRP or another suitable received power metric) of the downlink reference signals received via the one or more beams in accordance with the multiple CSI report configurations.

[0102] At 428, the UE 420 may determine that configurations A and D are triggered. For example, the UE 420 may determine that one or more triggering conditions associated with configurations A and D are satisfied (e.g., based on the downlink reference signal measurements). In other words, the UE 420 may determine that one or more triggering conditions associated with up to L configurations of the multiple CSI report configurations are satisfied. In some examples, the UE may transmit, in a first uplink channel associated with the multiple CSI configurations, a single bit that indicates the number of triggered CSI report configurations (e.g., up to L).

[0103] At 430, in response to the determination at 428, the UE 420 may transmit a first uplink channel (e.g., a single-bit first PUCCH) with a single bit set to “0”. That is, the UE 320 may set the single bit to a first value that indicates that one or more triggering conditions associated with up to L configurations (e.g., configurations A and D) of the multiple CSI report configurations are satisfied.

[0104] In some examples, at 432, in response to the first uplink channel, the UE 420 may receive DCI scheduling a second uplink channel (e.g., a dedicated PUSCH) with a size that is based on the summation of the two largest payload sizes among the multiple CSI report configurations. For example, the UE 420 may receive, in response to the first uplink channel, an indication of a grant for a second uplink channel for the event triggered CSI reporting, in which the second uplink channel has a size that is based on the number of triggered configurations. Based on the first uplink channel sent at 430 indicating that the number of triggered configurations is up to L (e.g., based on the value of the single bit being set to “0”),and based on L being set to 2, the size of the second uplink channel may be based on the two largest payload sizes among the multiple CSI report configurations.

[0105] In some such examples, at 434, the UE 420 may transmit the second uplink channel with beam reports for configurations A and D (e.g., with a beam report for configuration A and another beam report for configuration D). That is, the UE 420 may transmit, via the second uplink channel, a number of event triggered CSI reports corresponding to the number of configurations. In other words, the UE 420 may transmit, via the second uplink channel, up to two event triggered CSI reports corresponding to the up to two configurations.

[0106] At 436, the UE 420 may determine that configurations A, C and D are triggered. For example, the UE 420 may determine that one or more triggering conditions associated with configurations A, C and D are satisfied (e.g., based on the downlink reference signal measurements). In other words, the UE 420 may determine that one or more triggering conditions associated with more than L configurations of the multiple CSI report configurations are satisfied. In some examples, the UE may transmit, in a first uplink channel associated with the multiple CSI configurations, a single bit that indicates the number of triggered CSI report configurations (e.g., more than L).

[0107] At 438, in response to the determination at 436, the UE 420 may transmit a first uplink channel (e.g., a single-bit first PUCCH) with a single bit set to “1”. That is, the UE 420 may set the single bit to a second value that indicates that one or more triggering conditions associated with more than L configurations (e.g., configurations A, C, and D) of the multiple CSI report configurations are satisfied.

[0108] In some examples, at 440, in response to the first uplink channel, the UE 420 may receive DCI scheduling a second uplink channel (e.g., a dedicated PUSCH) with a size that is based on a summation of all payload size associated with the multiple CSI report configurations. For example, the UE 420 may receive, in response to the first uplink channel, an indication of a grant for a second uplink channel for the event triggered CSI reporting, in which the second uplink channel has a size that is based on the number of triggered configurations. Based on the first uplink channel sent at 438 indicating that the number of triggered configurations is more than L (e.g., based on the value of the single bit being set to “1”), the size of the second uplink channel scheduled at 440 may be larger than the size of the second uplink channel scheduled at 432 (e.g., in response to a first uplink channel with a single bit set to “0”). For example, the size of the second uplink channel scheduled at 440 may be based on the summation of a pre-determined number of payload size among themultiple CSI report configurations. While the example of FIG. 4 illustrates the predetermined number of payload sizes including all payload sizes associated with the multiple CSI report configurations, the examples provided herein may also apply to scenarios in which the pre-determined number of payload sizes includes some (but not all) of the payload sizes associated with the multiple CSI report configurations. For example, the pre-determined number may be greater than L, but less than the total number of payload sizes associated with the multiple CSI report configurations.

[0109] In some examples, at 442 the UE 420 may transmit the second uplink channel with beam reports for configurations A, C, and D (e.g., with a beam report for configuration A, another beam report for configuration C, and yet another beam report for configuration D). That is, the UE 420 may transmit, via the second uplink channel, a number of event triggered CSI reports corresponding to the number of configurations. In other words, the UE 420 may transmit, via the second uplink channel, more than two event triggered CSI reports corresponding to the more than two configurations.

[0110] FIG. 5 illustrates an example of a signaling diagram 500 to which one or more examples disclosed herein may be applied. The signalling diagram of FIG. 5 illustrates operations performed, such as within the system of FIG. 1 , by the UE 520 and the network node 510 in accordance with one or more aspects of the present disclosure. The UE 520 and the network node 510 may be examples of the corresponding devices illustrated by and described with reference to FIG. 1. One or more operations performed at the UE 520 and the network node 510 may be performed in a different order than the example order shown. Additionally, or alternatively, one or more operations performed at the UE 520 and the network node 510 may be omitted and / or one or more other operations may be added. The signaling diagram 500 supports one or more techniques for UEIBM with a single bit uplink channel and multiple report configurations, as described herein.

[0111] For example, the signaling diagram 500 supports a mechanism for the network to dynamically schedule a second uplink channel (e.g., PUSCH) for UEI beam reporting based on a single-bit first uplink channel (e.g., a PUCCH). That is, for a UE configured with Mode B, the transmitted bit in the single-bit first PUCCH may trigger the network (e.g., a gNB) to schedule a second uplink channel for carrying one or more beam reports. For example, for cases in which a first uplink channel carries a bit with the value set to “0” (indicating that 1 or up to L configurations are triggered), the UE may send the triggered beam report(s) on a preconfigured second uplink channel. The pre-configured second uplink channel may be an example of a pre-configured CG-PUSCH. For cases in which a first uplink channel carries abit with the value set to “1” (indicating that more than 1 or more than L configurations are triggered), the UE may refrain from sending the triggered beam reports on the pre-configured second uplink channel. For example, instead of the UE sending the triggered beam reports on the pre-configured second uplink channel, the network, in the same or a similar manner as is done for Mode A, replies to the first uplink channel by indicating, to the UE via DCI, a dedicated second uplink channel (e.g., a dedicated PUSCH resource). The dedicated second uplink channel may be larger than the pre-configured second uplink channel, so that the dedicated second uplink channel may carry the indicated number of triggered UEI beam reports.

[0112] For example, for Mode B, uplink channels used for UEI beam reporting include pre-configured CG-PUSCH resources, which cannot be dynamically updated by the network. In accordance with various aspects of the present disclosure, if the triggered beam report(s) fit the pre-configured CG-PUSCH, the UE may use the pre-configured CG-PUSCH to transmit the triggered beam report(s). Otherwise, the UE may request, via a single-bit first PUCCH with the single bit set to “1”, a dedicated PUSCH (that is larger than the CG-PUSCH) to carry the triggered UEI beam report(s). In some examples, the CG-PUSCH may be based on the largest (e.g., maximum) payload size among the configured CSI-Report configs, whereas the dedicated PUSCH may be based on the summation of multiple payload sizes (e.g., all or a predetermined number of largest payload sizes among the configured CSI-Reportconfigs).

[0113] In the example of FIG. 5, at 522, the network node 510 may configure the UE 520 with multiple CSI report configurations (A, B, C, and D). The multiple CSI report configurations may be associated with the same event (e.g., Event-2 or another suitable event) or with multiple different events. The UE may be configured with the multiple CSI report configurations by receiving downlink control signaling that indicates the multiple CSI configurations for event triggered CSI reporting. For example, the network node 510 may use control signaling to configure the UE 520 with UEIBM, to operate in accordance with Mode A and / or Mode B, and with multiple CSI report configurations for one or more events.

[0114] In some examples, at 524, the network node 510 may transmit downlink reference signals to the UE 520. The UE 520 may receive and measure the downlink reference signals via one or more beams in accordance with the multiple CSI report configurations. For example, the UE 520 may measure the received power (e.g., the Ll-RSRP or another suitable received power metric) of the downlink reference signals received via the one or more beams in accordance with the multiple CSI report configurations.

[0115] At 526, the UE 520 may determine that configuration A is triggered. For example, the UE 520 may determine that one or more triggering conditions associated with configuration A are satisfied (e.g., based on the downlink reference signal measurements). In other words, the UE 520 may determine that one or more triggering conditions associated with one configuration of the multiple CSI report configurations are satisfied. In some examples, the UE may transmit, in a first uplink channel associated with the multiple CSI configurations, a single bit that indicates the number of triggered CSI report configurations (e.g., 1 or up to L, for L=l).

[0116] At 528, in response to the determination at 526, the UE 520 may transmit a first uplink channel (e.g., a single-bit first PUCCH) with a single bit set to “0”. That is, in some examples, the UE 520 may set the single bit to a first value that indicates that one or more triggering conditions associated with one configuration (e.g., configuration A) of the multiple CSI report configurations are satisfied. In some other examples, for any L, the UE 520 may set the single bit to a first value that indicates that one or more triggering conditions associated with up to L configurations are triggered.

[0117] In some such examples, at 530, the UE 520 may transmit a second uplink channel with a beam report for configuration A according to a first type of uplink grant (e.g., via a pre-configured CG-PUSCH). That is, the UE 520 may transmit, via a second uplink channel, the at least one event triggered CSI report in accordance with a first type of uplink grant based on the number of configurations including one configuration or up to a pre-determined number of configurations. The first type of uplink grant may be a Type 1 configured grant indicating UL resource(s) for a CG-PUSCH.

[0118] In some examples, the UE may use both a CG-PUSCH and a dedicated PUSCH to send UEI beam reports. For example, for a UE configured with Mode B, the UE may send a single-bit first PUCCH with the single bit set to “1” (indicating that more than 1 or more than L configurations are triggered). In some examples, the UE may receive a dedicated PUSCH to send beam reports for all triggered CSI report configurations (e.g., in place of a preconfigured CG-PUSCH). In some other examples, rather than receiving a dedicated PUSCH to report all triggered CSI-Reportconfigs (e.g., as a replacement of a pre-configured CG-PUSCH), the UE may use both the pre-configured CG-PUSCH and a dedicated PUSCH.

[0119] For example, the UE may use the pre-configured CG-PUSCH for at least one of the triggered CSI-Reportconfigs and may receive a grant from the network for a dedicated PUSCH (e.g., an additional PUSCH resource) to report one or more additional CSI- Reportconfigs not reported in the CG-PUSCH. Thus , in accordance with various aspects ofthe present disclosure, the UE may operate with Mode A and Mode B (e.g., Mode A+B), such that pre-scheduled CG-PUSCH resources (Mode B) may be used independently of the number of triggered CSI-Reportconfigs, and additionally scheduled dedicated PUSCH resources (Mode A) may be used for one or more additional CSI-Reportconfigs triggered and not reported in the CG-PUSCH.

[0120] As an illustrative example, for L=l, a single-bit first PUCCH with the single bit set to “0” indicates a single triggered CSI-Reportconfig and a single-bit first PUCCH with the single bit set to “1” indicates more than one CSI-Reportconfig is triggered. In such an example, in accordance with Mode B, a CG-PUSCH resource may be pre-configured at the UE with a size that is based on the largest (e.g., maximum) payload size among the configured CSI-Reportconfigs. In some examples, the UE may transmit a single-bit first PUCCH with the single bit set to “1” indicating that multiple CSI-Reportconfigs are triggered. In some such examples, the UE may transmit, in the pre-configured CG-PUSCH resource, a UEI beam report for one of the triggered CSI-Reportconfigs. The one of the triggered CSI-Reportconfigs may be selected by the UE according to a configured rule. For example, the UE may be configured with one or more rules for determining which one or more of the triggered CSI-Reportconfigs the UE is to send a UEI beam report for in the CG-PUSCH.

[0121] In some examples, the one or more rules specify for the UE to select CSI report configurations in ascending or descending order of triggering time. For example, the one or more rules specify for the UE to select the first or last (e.g., most recently) triggered CSI-Reportconfigs among the multiple triggered CSI-Reportconfigs. In some examples, the one or more rules specify for the UE to select CSI report configurations in ascending or descending order of configuration ID. For example, the one or more rules specify for the UE to select the triggered CSI-Reportconfig with the highest or lowest configuration ID among the multiple triggered CSI-Reportconfigs, or the triggered CSI-Reportconfig with the highest or lowest priority among the multiple triggered CSI-Reportconfigs. In some other examples, the one or more rules specify for the UE to select CSI report configurations in descending order of payload size. For example, the one or more rules specify for the UE to select the triggered CSI-Reportconfig associated with the largest payload size among the multiple triggered CSI-Reportconfigs. In yet some other examples, the one or more rules specify for the UE to select the triggered CSI-Reportconfig for which the associated UEI beam report includes information pertaining to the beam with the highest received power metric (e.g., Ll-RSRP) among beams measured in accordance with the multiple triggered CSI-Reportconfigs. Inother words, the one or more rules specify for the UE to select a CSI-Reportconfig based on: the CSI-Reportconfig being the first or last (e.g., most recent) triggered CSI-Reportconfig; the CSI-Reportconfig having the lowest or highest configuration ID; the CSI-Reportconfig having the lowest or highest priority (which may be configured by the network); the CSI-Reportconfig being associated to the UEI beam report with largest payload size; or the UEI beam report associated to the CSI-Reportconfig including the beam with highest Ll-RSRP.

[0122] In some examples, based on the first PUCCH including the single bit set to “1”, the gNB schedules an additional dedicated PUSCH resource (e.g., as in Mode A). The additional dedicated PUSCH resource may occur at the same time (e.g., in the same slot or frame) as the CG-PUSCH or at a different time (e.g., in a different slot or frame) than the CG-PUSCH. In some examples, the additional dedicated PUSCH resource(s) may be scheduled with a size according to the difference between the summation of all payload sizes among the configured CSI-Reportconfigs and the highest (e.g., maximum) payload size among the configured CSI-Reportconfigs. That is, the additional dedicated PUSCH resource(s) may be scheduled with a size according to “sum of all payload sizes among the configured CSI-Reportconfigs” minus “maximum payload size among the configured CSI-Reportconfigs”. In some examples, the additional dedicated PUSCH resource(s) may be used to transmit one or more triggered CSI-Reportconfigs not reported in the CG-PUSCH. In other words, the additional dedicated PUSCH resource(s) may be used to transmit one or more beam reports for one or more remaining triggered CSI-Reportconfigs.

[0123] In the example of FIG. 5, at 532, the UE 520 may determine that configurations A and B are triggered. For example, the UE 520 may determine that one or more triggering conditions associated with configurations A and B are satisfied (e.g., based on the downlink reference signal measurements). In other words, the UE 520 may determine that one or more triggering conditions associated with more than one configuration of the multiple CSI report configurations are satisfied. In some examples, the UE may transmit, in a first uplink channel associated with the multiple CSI configurations, a single bit that indicates the number of triggered CSI report configurations (e.g., more than 1 or more than L, for L=l).

[0124] At 534, in response to the determination at 532, the UE 520 may transmit a first uplink channel (e.g., a single-bit first PUCCH) with a single bit set to “1”. That is, in some examples, the UE 520 may set the single bit to a second value that indicates that one or more triggering conditions associated with more than one configuration (e.g., configurations A and B) of the multiple CSI report configurations are satisfied. In some other examples, for any L,the UE 520 may set the single bit to a second value that indicates that one or more triggering conditions associated with more than L configurations are triggered.

[0125] In some examples, the UE 520 may transmit a second uplink channel with beam reports for configurations A and B according to a second type of uplink grant (e.g., via a dedicated PUSCH). For example, instead of using a first type of uplink grant (e.g., a CG-PUSCH) to send the beam reports, the UE may request, via a single-bit first PUCCH with the single bit set to “1”, a second type of grant (e.g., a dedicated PUSCH that is larger than the CG-PUSCH) to carry the triggered UEI beam reports. In some other examples, as illustrated in FIG. 5, the UE 520 may transmit a second uplink channel with beam reports for configurations A and B according to the first type of grant and the second type of grant.

[0126] For example, at 536, the UE 520 may transmit, via a second uplink channel in accordance with a first type of uplink grant, a first event triggered CSI report associated with a first configuration of the at least two configurations. In other words, the UE 520 may transmit, via a second uplink channel in accordance with the first type of uplink grant (e.g., via a CG-PUSCH), a beam report for configuration A. Although the example of FIG. 5 illustrates a single beam report being transmitted via the second uplink channel at 536, the examples provided herein may also apply to scenarios in which multiple beam reports are transmitted via a second uplink channel in accordance with the first type of grant (e.g., via a CG-PUSCH).

[0127] Additionally, at 538, the UE 520 may transmit, via another second uplink channel in accordance with a second type of uplink grant, at least one other event triggered CSI report associated with at least one other configuration of the at least two configurations. In other words, the UE 520 may transmit, via another second uplink channel in accordance with the second type of uplink grant (e.g., via a dedicated PUSCH), a beam report for configuration B.

[0128] FIG. 6 illustrates an example block diagram of an apparatus 10 to which one or more examples disclosed herein may be applied. The apparatus 10 includes, for example, at least one processor 12 and at least one memory 14 storing instructions 15 that, when executed by the at least one processor, cause the apparatus 10 at least to perform the method or methods as disclosed herein, and one or more embodiments thereof. In an example, the at least one memory and the instructions (e.g., a computer program code, software), are configured, with the at least one processor, to cause the apparatus 10 to perform the method or methods as disclosed herein, and one or more embodiments thereof.

[0129] A processor 12 may include circuitry, or be constituted as circuitry or circuitries, the circuitry or circuitries being configured to perform phases of methods in accordance withone or more example embodiments described herein. As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations, such as implementations in only analog and / or digital circuitry, and (b) combinations of hardware circuits and software, such as, as applicable: (i) a combination of analog and / or digital hardware circuit(s) with software / firmware and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a user equipment, to perform various functions) and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation. This definition of circuitry applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term circuitry also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0130] The memory 14 may be implemented using any suitable data storage technology. The memory may include a database for storing data. The memory 14 may be at least in part external to apparatus 10 but accessible to apparatus 10.

[0131] The instructions 15 may be included in a computer readable medium or a non-transitory computer readable medium. A term non-transitory, as used herein, is a limitation of the medium itself (e.g., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., random access memory, RAM, vs. read only memory, ROM).

[0132] For example, the apparatus 10 may be a terminal device, such as the UE of FIGs.1-5. As another example, the apparatus may be included in such a terminal device, e.g., as a chipset configured to control the terminal device. The apparatus 10 may be caused or configured to perform one or more operations of the UE illustrated in the signaling diagrams of FIGs. 3-5 and / or one or more embodiments described herein.

[0133] As another example, the apparatus 10 is a network node (e.g., a RAN node) of FIGs. 1-5. In another embodiment, the apparatus is included in such a network node, e.g., as a chipset configured to control the network node. The apparatus 10 may be caused or configured to perform one or more operations of the network node illustrated in the signaling diagrams of FIGs. 3-5 and / or one or more embodiments described herein.

[0134] The apparatus may include one or more entities of any of protocol layers, such as a MAC entity, an RRC entity, an RLC entity, a PDCP entity or a PHY entity. In at least one embodiment, the entity is configured to perform at least operation illustrated in the signaling diagrams of FIGs. 3-5 and / or one or more embodiments described herein.

[0135] In some examples, the apparatus 10 may include a radio interface 16. The radio interface 16 may provide the apparatus 10 with communication capabilities. The radio interface 16 may include a receiver configured to receive information in accordance with at least one cellular or non-cellular standard. The radio interface 16 may include a transmitter configured to transmit information in accordance with at least one cellular or non-cellular standard. The receiver may include more than one receiver. The transmitter may include more than one transmitter. The radio interface 16 may include a transceiver configured to receive and transmit information in accordance with at least one cellular or non-cellular standard.

[0136] The term “transmit,” and the like, as used herein, refers to outputting of a signal via an interface providing a wired or wireless connection between two or more devices (or two or more components of a single device). In some examples, the signal is a radio frequency signal output, for example, via the radio interface 16. In some other examples, the signal is an electrical signal (or optical signal) output, for example, via the processor 12.

[0137] In some examples, the apparatus 10 may include a user interface 18 including, for example, at least one of a keypad, a microphone, a touch display, a display, a speaker, etc. The user interface 18 may be used to control the apparatus by the user. The user interface 18 may be external to the apparatus 10. For example, the apparatus 10 may be connected to another device, such as a computer, either via wireless or wired connection, and the apparatus 10 is controlled by the user via the computer.

[0138] In at least one embodiment, at least some of the processes described herein may be carried out by an apparatus including means for carrying out at least some of the described processes. Means for performing methods as disclosed herein may include software and / or hardware components of the apparatus 10. For example, the at least one processor 12, the memory 14, and the computer program code form means for carrying out the method or methods as disclosed herein, and one or more embodiments thereof. The term “means” as used in the description and in the claims may refer to one or more individual elements configured to perform the corresponding recited functionality or functionalities, or it may refer to several elements that perform such functionality or functionalities. Furthermore, several functionalities recited in the claims may be performed by the same individual meansor the same combination of means. For example, performing such functionality or functionalities may be caused in an apparatus by a processor that executes instructions stored in a memory of the apparatus.

[0139] FIG. 7 illustrates an example flowchart 700 of a method to which one or more examples disclosed herein may be applied. The method may be computer-implemented. The method may be performed by a UE, such as a UE illustrated by and described with reference to FIGs. 1-5. In some examples, the UE may be an example of an apparatus 10 illustrated by and described with reference to FIG. 6.

[0140] As shown in FIG. 7, the UE at block 710 receives downlink control signaling that indicates a plurality of configurations for event triggered CSI reporting. For example, the UE may include the means (e.g., a processor 12, a memory 14, a radio interface 16) for receiving downlink control signaling that indicates a plurality of configurations for event triggered CSI reporting.

[0141] As shown in FIG. 7, the UE at block 712 determines that one or more triggering conditions associated with one or more configurations of the plurality of configurations are satisfied. For example, the UE may include the means (e.g., a processor 12, a memory 14) for determining that one or more triggering conditions associated with one or more configurations of the plurality of configurations are satisfied.

[0142] As shown in FIG. 7, the UE at block 714 transmits, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations of the one or more configurations. For example, the UE may include the means (e.g., a processor 12, a memory 14, a radio interface 16) for transmitting, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations of the one or more configurations.

[0143] FIG. 8 illustrates an example flowchart 800 of a method to which one or more examples disclosed herein may be applied. The method may be computer-implemented. The method may be performed by a network node, such as a network node illustrated by and described with reference to FIGs. 1-5. In some examples, the network node may be an example of an apparatus 10 illustrated by and described with reference to FIG. 6.

[0144] As shown in FIG. 8, the network node at block 810 transmits downlink control signaling that indicates a plurality of configurations for event triggered CSI reporting. For example, the network node may include the means (e.g., a processor 12, a memory 14, a radio interface 16) for transmitting downlink control signaling that indicates a plurality of configurations for event triggered CSI reporting.

[0145] As shown in FIG. 8, the network node at block 812 receives, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied. For example, the network node may include the means (e.g., a processor 12, a memory 14, a radio interface 16) for receiving, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied.

[0146] Even though the present disclosure has been described above with reference to an example according to the accompanying drawings, it is clear that the present disclosure is not restricted thereto but can be modified in several ways within the scope of the appended claims. Therefore, all words and expressions should be interpreted broadly, and they are intended to illustrate, not to restrict, the embodiment. It will be obvious to a person skilled in the art that, as technology advances, the inventive concept can be implemented in various ways. Further, it is clear to a person skilled in the art that the described embodiments may, but are not required to, be combined with other embodiments in various ways.

Claims

What is claimed is:

1. An apparatus, comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:receive downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting;determine that one or more triggering conditions associated with one or more configurations of the plurality of configurations are satisfied; andtransmit, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations of the one or more configurations.

2. The apparatus of claim 1, wherein:the single bit has a first value that indicates the number of configurations by indicating that one or more triggering conditions associated with one configuration of the plurality of configurations are satisfied, orthe single bit has a second value that indicates the number of configurations by indicating that one or more triggering conditions associated with more than one configuration of the plurality of configurations are satisfied.

3. The apparatus of claim 1, wherein:the single bit has a first value that indicates the number of configurations by indicating that one or more triggering conditions associated with up to a pre-determined number of configurations are satisfied, orthe single bit has a second value that indicates the number of configurations by indicating that one or more triggering conditions associated with more than the predetermined number of configurations are satisfied.

4. The apparatus of claim 3, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to:receive second control signaling that indicates the pre-determined number of configurations.

5. The apparatus of claim 3 or 4, wherein the pre-determined number of configurations is one of a set of numbers configured for the event triggered CSI reporting.

6. The apparatus of any one of claims 1 through 5, wherein the plurality of configurations is associated with one or more types of events.

7. The apparatus of any one of claims 1 through 6, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to:transmit, via a second uplink channel associated with the first uplink channel, a number of event triggered CSI reports corresponding to the number of configurations.

8. The apparatus of claim 7, wherein the first uplink channel comprises a first physical uplink control channel (PUCCH), and wherein the second uplink channel comprises a second PUCCH or a physical uplink shared channel (PUSCH).

9. An apparatus, comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the apparatus at least to:transmit downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting; andreceive, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied.

10. The apparatus of claim 9, wherein:the single bit has a first value that indicates the number of configurations by indicating that one or more triggering conditions associated with one configuration of the plurality of configurations are satisfied, orthe single bit has a second value that indicates the number of configurations by indicating that one or more triggering conditions associated with more than one configuration of the plurality of configurations are satisfied.

11. The apparatus of claim 9, wherein:the single bit has a first value that indicates the number of configurations by indicating that one or more triggering conditions associated with up to a pre-determined number of configurations are satisfied, orthe single bit has a second value that indicates the number of configurations by indicating that one or more triggering conditions associated with more than the predetermined number of configurations are satisfied.

12. The apparatus of claim 11, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to:transmit second control signaling that indicates the pre-determined number of configurations.

13. The apparatus of claim 11 or 12, wherein the pre-determined number of configurations is one of a set of numbers configured for the event triggered CSI reporting.

14. The apparatus of any one of claims 9 through 13, wherein the plurality of configurations is associated with one or more types of events.

15. The apparatus of any one of claims 9 through 14, wherein the instructions, when executed by the at least one processor, cause the apparatus at least to:receive, via a second uplink channel associated with the first uplink channel, a number of event triggered CSI reports corresponding to the number of configurations.

16. The apparatus of claim 15, wherein the first uplink channel comprises a first physical uplink control channel (PUCCH), and wherein the second uplink channel comprises a second PUCCH or a physical uplink shared channel (PUSCH).

17. A method, comprising:receiving downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting;determining that one or more triggering conditions associated with one or more configurations of the plurality of configurations are satisfied; andtransmitting, in a first uplink channel associated with the plurality of configurations, asingle bit that indicates a number of configurations of the one or more configurations.

18. A method, comprising:transmitting downlink control signaling that indicates a plurality of configurations for event triggered channel state information (CSI) reporting; andreceiving, in a first uplink channel associated with the plurality of configurations, a single bit that indicates a number of configurations that one or more triggering conditions associated therewith are satisfied.

Images