Configuring uplink resources for user equipment initiated beam reporting

Abstract

A method, network node and user equipment (UE) for configuring uplink resources for user equipment (UE) initiated beam reporting are provided. According to one aspect, a method in a UE includes receiving from the network node a first channel state information (CSI) report configuration including information of a first trigger condition and information of a first uplink channel. The method includes receiving from the network node a second CSI report configuration including information of a second trigger condition and information of the first uplink channel. The method includes transmitting a UE-initiated beam report in a second uplink channel when at least one of the first and the second trigger conditions is fulfilled, the UE-initiated beam report corresponding to one of the first and second CSI report configurations.

Description

[0001] CONFIGURING UPLINK RESOURCES FOR USER EQUIPMENT INITIATED BEAM

[0002] REPORTING

[0003] FIELD

[0004] The present disclosure relates to wireless communications, and in particular, to configuring uplink resources for user equipment (UE) initiated beam reporting.

[0005] BACKGROUND

[0006] The Third Generation Partnership Project (3 GPP) has developed and is developing standards for Fourth Generation (4G) (also referred to as Long Term Evolution (LTE)) and Fifth Generation (5G) (also referred to as New Radio (NR)) wireless communication systems. Such systems provide, among other features, broadband communication between network nodes, such as base stations, and mobile user equipments (UE), as well as communication between network nodes (NNs) and between UEs. The 3GPP is also developing standards for Sixth Generation (6G) wireless communication networks.

[0007] NR Frame Structure and Resource Grid

[0008] NR uses Cyclic Prefix Orthogonal Frequency Division Multiplexing (CP-OFDM) in both downlink (e.g., from a network node (gNB or base station) to a UE) and uplink (e.g., from the UE to the network node). Discrete Fourier Transform (DFT) spread OFDM is also supported in the uplink. In the time domain, NR downlink and uplink are organized into equally sized subframes of 1ms each. A subframe is further divided into multiple slots of equal duration. Each slot consists of 14 OFDM symbols. The number of slots in a subframe depends on subcarrier spacing. The supported subcarrier spacing values are given by A = (15 X 2^kHz, where [i G 0,1, 2, 3, 4, 5,6. The number of slots per subframe equals 2^. For subcarrier spacing of A = 15kHz, i.e., f = 0, there is only one slot per subframe.

[0009] In the frequency domain, a bandwidth part (BWP) is divided into resource blocks (RBs), each corresponding to 12 contiguous subcarriers. The RBs are numbered starting with 0 from one end of the BWP. One OFDM subcarrier during one OFDM symbol interval forms one resource element (RE).

[0010] Downlink (DL) and uplink (UL) transmissions may be either dynamically scheduled or semi-persistently scheduled. In the case of dynamic scheduling, the network node transmits scheduling information (or downlink control information (DCI)) via Physical Downlink Control Channel (PDCCH) on a slot-by-slot basis. Actual UE data transmissions are carried on Physical Downlink Shared Channel (PDSCH) in the downlink (DL) and on Physical Uplink Shared Channel (PUSCH) in the uplink (UL). Various DCI formats are defined in NR for DL and UL scheduling, e.g., DCI format l_0, DCI format 1_1, and DCI format 1_2 for DL scheduling, and DCI format 0-0, DCI format 0_l, and DCI format 0_2 for UL scheduling.

[0011] In cases of semi-persistent scheduling, scheduling information is pre-configured and may be referred to as configured grant (CG) in the uplink. Two types of CG PUSCHs are supported, i.e., type 1 configured grant (CG)-PUSCH and type 2 CG-PUSCH. In type 1 CG-PUSCH, periodic uplink PUSCH resources are configured. In type 2 CG-PUSCH, periodic uplink PUSCH resources may be dynamically activated and de-activated via DCI. Beam management with unified Transmission Configuration Indication (TCI) framework

[0012] In NR, a spatial beam (or simply beam) is defined by a reference signal (RS) transmitted via the beam. The RS may be a Channel State Information Reference Signal (CSLRS) or a Synchronization Singal Block (SSB). Beam management may be about determining proper beams for DL transmission from the network node to a UE and UL transmission from the UE to the network node. In the DL, the UE may need to know the network node transmission beam in order to use a proper receive beam to receive DL data. With beam correspondence, the UE may determine a UL transmit beam based on a DL receive beam for UL data transmission. Therefore, a UL transmit beam may be linked to a DL RS. Information about a DL beam used for data transmission to the UE is indicated via a transmission configuration indicator (TCI) state. For beam indication, a TCI state includes information of a RS for type-D Quasi Co-location (QCL) . For example, if a TCI state with a RS for QCL typeD is indicated to UE for a PDSCH, it is assumed that a receive beam (or spatial filter) previously determined for receiving the RS may be used by the UE to receive the PDSCH.

[0013] For beam management purposes, a list of TCI states may be configured for a UE in a higher layer parameter PDSCH-Config via Radio Resource Control (RRC) signaling (e.g., as described in 3GPP Technical Specification (TS) 38.331 section 6.3.2). Up to 8 TCI states from the list may be activated with a Medium Access Control (MAC) Control Element (CE).

[0014] In 3GPP NR Technical Release 17 (3GPP Rel-17), a unified beam indication framework was introduced to simplify beam management, in which a common beam applicable to multiple channels and signals may be indicated to a UE via a “unified” TCI state. Either “Joint DL / UL TCI” or “Separate DL / UL TCI” may be configured. For “Joint DL / UL TCI”, one TCI state is used to indicate a common beam for both DL and UL (uplink) signals / channels. For “Separate DL / UL TCI”, one DL-only TCI state is used for DL channels / signals and one UL-only TCI state is used for UL signals / channels. A TCI state under the framework is also referred to as a unified TCI state.

[0015] A unified TCI state for DL or joint DL and UL includes identifiers of two QCL source RSs, where the first RS is a QCL source RS for one of {typeA, typeB, typeC} QCL types, while the second RS is a QCL source RS for QCL typeD. The second RS is used to indicate a spatial beam or filter associated with the unified TCI state.

[0016] A unified TCI state may be updated with one of two alternatives:

[0017] • Two-stage: RRC signaling is used to configure a list of unified TCI states in higher layer parameter PDSCH-config, and a MAC-CE is used to activate one unified TCI state in the list of unified TCI states; and

[0018] • Three-stage: RRC signaling is used to configure a list of unified TCI states in PDSCH-config, a MAC-CE is used to activate up to 8 unified TCI states in the list, and a 3-bit TCI state bitfield in DCI (Downlink Control Information) formats 1_1 or 1_2 is used to indicate one of the activate unified TCI states.

[0019] The one activated ( in two-stage) or indicated (in three-stage) unified TCI state is used in subsequent DL transmissions until a new unified TCI state is activated or indicated.

[0020] Beam reporting

[0021] The signal quality of a DL beam may be measured and reported by a UE based on a corresponding downlink RS, i.e., an SSB or a CSLRS, associated with the DL beam. The signal quality may be one of Ll-RSRP (layer one (LI) reference signal received power), Ll-SINR (signal to interference and noise ratio), or Ll-RSRQ (RS received quality). Such reports on Ll-RSRP or Ll-SINR are referred to as beam reports. Beam reports are configured via CSI report configuration in NR.

[0022] In NR, a UE may be configured by the network node with one or more CSI report configurations. Each CSI report configuration is used to configure a CSI report. A CSI report may be either periodic, semi-persistent, or aperiodic. CSI reports from the UE may be used to assist the network node to perform beam management operations, such as determining a proper beam for transmitting data and / or control channels to the UE. In this case, a CSI report is also referred to as a beam report. A CSI report configuration is signaled in an information element (IE) CSI- ReportConfig in a RRC message. The IE CSI-ReportConfig is defined in 3GPP TS 38.331, V18.0.0, clause 6.3. It includes a CSI report identifier (ID), a CSI resource configuration ID for channel measurement, a serving cell index (also known as carrier index) for a serving cell over which the CSI resources are to be measured, a CSI report type, i.e., whether it is periodic, semi-persistent, or aperiodic, a report quantity indicating what to be reported, and others. For beam management purposes, the report quantity may be Ll- RSRP, Ll-SINR, CRI (CSI-RS resource indicator), and SSBRI (SSB Resource Indicator) (e.g., as described in 3GPP TS 38.214, vl8.1.0, clause 5.2).

[0023] A CSI resource configuration includes a list of RS resource sets to be measured, such as NZP (Non-Zero Power) CSI-RS resource sets and / or SSB resource sets for a given serving cell. The UE may measure CSI resources of a first serving cell and report in another serving cell.

[0024] Periodic or semi-persistent beam reports may be carried on Physical Uplink Control Channel (PUCCH), and aperiodic beam reports are carried on PUSCH as part of Uplink Control Information (UCI). Semi-persistent beam report on PUSCH is also supported. In cases of aperiodic CSI report, the network node sends a CSI request in DCI, where a CSI request field in the DCI pointing to an aperiodic CSI trigger state which in turn pointing to one or more CSI report configurations.

[0025] UE-initiated / event-driven beam management

[0026] Up to 3GPP NR Technical Release 19 (3GPP Rel-19), the CSFbeam reporting is always network-initiated, i.e., the network node explicitly configures or requests a certain CSI reports for the UE to report.

[0027] In 3GPP NR Rel-19, UE initiated beam reporting will be supported in which a UE keeps monitoring the quality of a set of DL beams (or RS) and sends a beam report only when certain triggering conditions are met, or certain event(s) occur.

[0028] On triggering conditions or events, a few events have been discussed in 3GPP but only Event-2 below is agreed to so far. Event-2 is as follows:

[0029] • Event-2: Quality of at least one new beam becomes a threshold value better than the current beam, where the quality is at least Ll-RSRP. where the current beam refers to a current serving beam indicated by the indicated TCI state and the new beam is a beam that is different than the current serving beam.

[0030] With respect to a beam report transmission procedure for UE-initiated / event-driven beam reporting, it has been agreed that the following two modes will be supported: • Mode A (dynamically scheduling UCI by gNB):

[0031] • Step 1: UE transmits a first PUCCH (one-bit / multi-bit) to request a resource for a second UL channel to carry beam report;

[0032] • Step 2: UE detects the DCI format to indicate a resource for a second UL channel to carry beam report; and

[0033] • Step 3: Beam report is transmitted in second UL channel.

[0034] • Mode B (UCI in pre-configured resource(s) for second UL channel):

[0035] • Step 1: UE transmits a first PUCCH (one-bit / multi-bit) notifying a second UL channel to carry beam report;

[0036] • Step 2: UE transmits the beam report in the second UL channel; and

[0037] • The notification in Stepl is in a separate reporting instance from the beam report in Step 2.

[0038] It has been further assumed that the first physical uplink control channel (PUCCH) has one-bit and the cross component carrier (CC) beam reporting in case carrier aggregation (CA) is supported for both modes.

[0039] As for the second UL channel in Mode B, a few high-level proposals below have been discussed in 3GPP in terms of whether physical uplink shared channel (PUSCH) and / or PUCCH should be used for the second channel, details are to be further agreed.

[0040] Proposal 3.3 (PUSCH+PUCCH):

[0041] With respect to a beam report transmission procedure for UE-initiated / event-driven beam reporting, for Mode-B, the pre-configured resource(s) for the second channel in Step-2 may be either PUSCH or PUCCH.

[0042] FFS: Signaling design for PUSCH and PUCCH configuration;

[0043] Note: For a given UE, only one of the two types of resources may be preconfigured for UEIBM report; and

[0044] Introduce UE capability signaling to indicate support of PUSCH, PUCCH, or both.

[0045] Proposal 3.3 (At least PUCCH):

[0046] On beam report transmission procedure for UE-initiated / event-driven beam reporting, for regarding Mode-B, the pre-configured resource(s) for the second channel in Step-2 is at least PUCCH.

[0047] For further study (FFS): PUSCH as the second channel.

[0048] Proposal 3.3 (At least PUSCH): On beam report transmission procedure for UE-initiated / ev ent-driven beam reporting, for regarding Mode-B, the pre-configured resource(s) for the second channel in Step-2 is at least PUSCH.

[0049] FFS: PUCCH as the second channel.

[0050] For UE initiated beam reporting, an open problem is how to design the second UE channel in Mode B for carrying beam report. When multiple CSI report configurations, each associated with a serving cell or a component carrier (CC) for carrier aggregation (CA) and / or an event, are configured, more than one event may occur on the same CC or different CCs at the same time. In this case, how to design the second channel and transmit beam report in the second channel is another problem.

[0051] SUMMARY

[0052] Some embodiments advantageously provide methods, systems, and apparatuses for configuring uplink resources for user equipment initiated beam reporting.

[0053] According to one aspect, a method of UE initiated beam reporting at a UE when multiple events and / or multiple CCs are configured for UE initiated beam reporting is described. The method includes one or more of:

[0054] • Configuring the UE with the same first PUCCH (or first channel) and a same second UL channel for the multiple events or CCs;

[0055] • Sending an indication in the first PUCCH when one or more events occur in one or more of the CCs at the same time;

[0056] • Determining by the UE a beam report associated with one or more events that occur in one or more of the CCs;

[0057] • Sending the beam report in the second uplink channel, wherein the beam report contains an indication indicating a number of remaining beam reports to be sent;

[0058] • After receiving the beam report, sending to the UE a CSI request and an uplink grant in DCI; and / or

[0059] • Sending by the UE one or more of the remaining beam reports in an uplink resource indicated in the uplink grant.

[0060] According to another aspect, a method performed at a UE is described. The method includes one or more of: • Receiving from a network node multiple CSI report configurations each associated with an event and a CC, and receiving from the network node a configuration of a first and a second UL channels;

[0061] • Sending to the network node an indication on the first UL channel when one or more events corresponding to the multiple CSI report configurations occur;

[0062] • Determining by the UE a first beam report to send in the second uplink channel when more than one event occurs in one or more CCs at the same time, wherein the first beam report corresponds to one CSI report configuration among the multiple CSI report configurations: o The determining is based on a priority rule, where a priority is associated with each of the multiple CSI report configurations;

[0063] • Including in the first beam report an indication indicating a number of events that occurred in one or more CCs or additional beam reports to be sent; and / or

[0064] • Sending to the network node the first beam report in the second UL channel.

[0065] Further, the UE may receive from the network node a CSI request and an uplink grant in DCI for sending one or more of the additional beam reports if indicated in the first beam report.

[0066] One or more advantages of the present embodiments may include saving of resource overhead for the second UL channel.

[0067] According to one aspect, a method in a network node include transmitting to the UE a first channel state information, CSI, report configuration including information of a first trigger condition and information of a first uplink channel. The method includes transmitting to the UE a second CSI report configuration including information of a second trigger condition and information of the first uplink channel. The process includes transmitting a UE-initiated beam report in a second uplink channel when at least one of at least one of the first and second trigger conditions is fulfilled, the UE-initiated beam report corresponding to one of the first and second CSI report configurations.

[0068] According to this aspect, in some embodiments, the first trigger condition is associated to a first event and the second trigger condition is associated to a second event. In some embodiments, the first event is the same as the second event. In some embodiments, the first event is different than the second event. In some embodiments, a resource for the second uplink channel is configured to carry a single UE-initiated beam report. In some embodiments, the first uplink channel is a physical uplink control channel, PUCCH with a first periodicity, and wherein the first uplink channel is for carrying a UE- initiated beam report indicator. In some embodiments, the second uplink channel is one of a physical uplink shared channel, PUSCH, dynamically scheduled, and a PUSCH semi- statically scheduled with a second periodicity, and wherein the second uplink channel is for carrying the UE-initiated beam report. In some embodiments, the second uplink channel is a configured grant physical uplink shared channel, PUSCH, and wherein for each occasion of the first uplink channel, there is a corresponding occasion of the second uplink channel separated from the first uplink channel by a time offset. In some embodiments, the second uplink channel is a configured grant PUSCH and wherein the first periodicity and the second periodicity are the same. In some embodiments, when beam reporting is triggered for both the first and second CSI report configurations, only a single UE-initiated beam report associated to one of the first and second CSI report configurations is transmitted on the second uplink channel. In some embodiments, the single UE-initiated beam report corresponds to one of the first and second CSI report configurations with a high priority. In some embodiments, each of the first and the second CSI report configurations further includes a same carrier index. In some embodiments, the method includes indicating to the UE a set of dedicated physical uplink shared channel, PUSCH, resources for transmitting the UE-initiated beam report.

[0069] According to another aspect, a network node includes processing circuitry configured to transmit to the UE a first channel state information, CSI, report configuration including information of a first trigger condition and information of a first uplink channel. The processing circuitry is configure to transmit to the UE a second CSI report configuration including information of a second trigger condition and information of the first uplink channel. The processing circuitry is configure to transmit a UE-initiated beam report in a second uplink channel when at least one of at least one of the first and second trigger conditions is fulfilled, the UE-initiated beam report corresponding to one of the first and second CSI report configurations.

[0070] According to this aspect, in some embodiments, the first trigger condition is associated to a first event and the second trigger condition is associated to a second event. In some embodiments, the first event is the same as the second event. In some embodiments, the first event is different than the second event. In some embodiments, a resource for the second uplink channel is configured to carry a single UE-initiated beam report. In some embodiments, the first uplink channel is a physical uplink control channel, PUCCH with a first periodicity, and wherein the first uplink channel is for carrying a UE- initiated beam report indicator. In some embodiments, the second uplink channel is one of a physical uplink shared channel, PUSCH, dynamically scheduled, and a PUSCH semi- statically scheduled with a second periodicity, and wherein the second uplink channel is for carrying the UE-initiated beam report. In some embodiments, the second uplink channel is a configured grant physical uplink shared channel, PUSCH, and wherein for each occasion of the first uplink channel, there is a corresponding occasion of the second uplink channel separated from the first uplink channel by a time offset. In some embodiments, the second uplink channel is a configured grant PUSCH and wherein the first periodicity and the second periodicity are the same. In some embodiments, when beam reporting is triggered for both the first and second CSI report configurations, only a single UE-initiated beam report associated to one of the first and second CSI report configurations is transmitted on the second uplink channel. In some embodiments, the single UE-initiated beam report corresponds to one of the first and second CSI report configurations with a high priority. In some embodiments, each of the first and the second CSI report configurations further includes a same carrier index. In some embodiments, the processing circuitry is configured to the UE a set of dedicated physical uplink shared channel, PUSCH, resources for transmitting the UE-initiated beam report.

[0071] According to another aspect, a method in a user equipment includes receiving from the network node a first channel state information, CSI, report configuration including information of a first trigger condition and information of a first uplink channel. The process includes receiving from the network node a second CSI report configuration including information of a second trigger condition and information of the first uplink channel. The process also includes transmitting a UE-initiated beam report in a second uplink channel when at least one of the first and the second trigger conditions is fulfilled, the UE-initiated beam report corresponding to one of the first and second CSI report configurations.

[0072] In some embodiments, the first trigger condition is associated to a first event and the second trigger condition is associated to a second event. In some embodiments, the first event is the same as the second event. In some embodiments, the first event is different than the second event. In some embodiments, a resource for the second uplink channel is configured to carry a single UE-initiated beam report. In some embodiments, the first uplink channel is a physical uplink control channel, PUCCH with a first periodicity, and wherein the first uplink channel is for carrying a UE-initiated beam report indicator. In some embodiments, the second uplink channel is one of a physical uplink shared channel, PUSCH, dynamically scheduled, and a PUSCH semi-statically scheduled with a second periodicity, and wherein the second uplink channel is for carrying the UE- initiated beam report. In some embodiments, the second uplink channel is a configured grant physical uplink shared channel, PUSCH, and wherein for each occasion of the first uplink channel, there is a corresponding occasion of the second uplink channel separated from the first uplink channel by a time offset. In some embodiments, the second uplink channel is a configured grant PUSCH and wherein the first periodicity and the second periodicity are the same. In some embodiments, when beam reporting is triggered for both the first and second CSI report configurations, only a single UE-initiated beam report associated to one of the first and second CSI report configurations is transmitted on the second uplink channel. In some embodiments, the single UE-initiated beam report corresponds to one of the first and second CSI report configurations with a high priority. In some embodiments, each of the first and the second CSI report configurations further includes a same carrier index. In some embodiments, UE-initiated beam reports are prioritized according to an order of the first trigger condition and the second trigger condition. In some embodiments, each of the first and the second CSI report configurations includes a configuration index and wherein UE-initiated beam reports are prioritized according to the configuration index, wherein a lower or smaller index value is associated to a higher priority. In some embodiments, the process includes, when a UE- initiated beam report on the second uplink channel collides with resources of a hybrid automatic repeat request acknowledgment, HARQ-ACK, multiplexing the UE-initiated beam report with the HARQ-ACK on the second uplink channel. In some embodiments, when a UE-initiated beam report on the second uplink channel collides with resources for a scheduling request, SR, dropping the UE-initiated beam report when the second uplink channel is a physical uplink shared channel, PUSCH, or a configured grant PUSCH. In some embodiments, when a UE-initiated beam report on the second uplink channel collides with periodic or semi-persistent CSI in a slot, dropping the periodic or semi- persistent CSI. In some embodiments, the method includes, when a UE-initiated beam report on the second uplink channel collides with an aperiodic CSI on a physical uplink shared channel, multiplexing the UE-initiated beam report with the aperiodic CSI or dropping the aperiodic CSI.

[0073] According to another aspect, a user equipment includes processing circuitry configured to receive from the network node a first channel state information, CSI, report configuration including information of a first trigger condition and information of a first uplink channel. The processing circuitry configured to receive from the network node a second CSI report configuration including information of a second trigger condition and information of the first uplink channel. The processing circuitry configured to transmit a UE-initiated beam report in a second uplink channel when at least one of the first and the second trigger conditions is fulfilled, the UE-initiated beam report corresponding to one of the first and second CSI report configurations.

[0074] According to this aspect, in some embodiments, the first trigger condition is associated to a first event and the second trigger condition is associated to a second event. In some embodiments, the first event is the same as the second event. In some embodiments, the first event is different than the second event. In some embodiments, a resource for the second uplink channel is configured to carry a single UE-initiated beam report. In some embodiments, the first uplink channel is a physical uplink control channel, PUCCH with a first periodicity, and wherein the first uplink channel is for carrying a UE- initiated beam report indicator. In some embodiments, the second uplink channel is one of a physical uplink shared channel, PUSCH, dynamically scheduled, and a PUSCH semi- statically scheduled with a second periodicity, and wherein the second uplink channel is for carrying the UE-initiated beam report. In some embodiments, the second uplink channel is a configured grant physical uplink shared channel, PUSCH, and wherein for each occasion of the first uplink channel, there is a corresponding occasion of the second uplink channel separated from the first uplink channel by a time offset. In some embodiments, the second uplink channel is a configured grant PUSCH and wherein the first periodicity and the second periodicity are the same. In some embodiments, when beam reporting is triggered for both the first and second CSI report configurations, only a single UE-initiated beam report associated to one of the first and second CSI report configurations is transmitted on the second uplink channel. In some embodiments, the single UE-initiated beam report corresponds to one of the first and second CSI report configurations with a high priority. In some embodiments, each of the first and the second CSI report configurations further includes a same carrier index. In some embodiments, UE-initiated beam reports are prioritized according to an order of the first trigger condition and the second trigger condition. In some embodiments, each of the first and the second CSI report configurations includes a configuration index and wherein UE-initiated beam reports are prioritized according to the configuration index, wherein a lower or smaller index value is associated to a higher priority. In some embodiments, when a UE-initiated beam report on the second uplink channel collides with resources of a hybrid automatic repeat request acknowledgment, HARQ-ACK, the processing circuitry is configured to multiplex the UE-initiated beam report with the HARQ-ACK on the second uplink channel. In some embodiments, when a UE-initiated beam report on the second uplink channel collides with resources for a scheduling request, SR, the processing circuitry configured to drop the UE-initiated beam report when the second uplink channel is a physical uplink shared channel, PUSCH, or a configured grant PUSCH. In some embodiments, when a UE-initiated beam report on the second uplink channel collides with periodic or semi-persistent CSI in a slot, the processing circuitry configured to drop the periodic or semi-persistent CSI. In some embodiments, the method includes, when a UE- initiated beam report on the second uplink channel collides with an aperiodic CSI on a physical uplink shared channel, multiplexing the UE-initiated beam report with the aperiodic CSI or dropping the aperiodic CSI.

[0075] BRIEF DESCRIPTION OF THE DRAWINGS

[0076] A more complete understanding of the present embodiments, and the attendant advantages and features thereof, will be more readily understood by reference to the following detailed description when considered in conjunction with the accompanying drawings wherein:

[0077] FIG. 1 is a schematic diagram of an example network architecture illustrating a communication system according to principles disclosed herein;

[0078] FIG. 2 is a block diagram of a network node in communication with a user equipment over a wireless connection according to some embodiments of the present disclosure;

[0079] FIG. 3 is a flowchart of an example process in a user equipment according to some embodiments of the present disclosure;

[0080] FIG. 4 is a flowchart of an example process in a network node according to some embodiments of the present disclosure;

[0081] FIG. 5 is a flowchart of another example process in a network node according to some embodiments of the present disclosure;

[0082] FIG. 6 is a flowchart of another example process in a user equipment according to some embodiments of the present disclosure;

[0083] FIG. 7 shows an example PUCCH as a second UL channel according to some embodiments of the present disclosure;

[0084] FIG. 8 shows an example PUSCH as a second UE channel according to some embodiments of the present disclosure; FIG. 9 shows an example CG-PUSCH as a second UL channel according to some embodiments of the present disclosure;

[0085] FIG. 10 shows an example repetition of the second UL channel according to some embodiments of the present disclosure;

[0086] FIG. 11 shows an example UE initiated beam reporting when events configured in multiple CSI report configurations occur at the same time according to some embodiments of the present disclosure; and

[0087] FIG. 12 shows an example UE initiated beam reporting when events configured in multiple CSI report configurations are prioritized according to the time in which they occur according to some embodiments of the present disclosure.

[0088] DETAILED DESCRIPTION

[0089] Before describing in detail exemplary embodiments, it is noted that the embodiments reside primarily in combinations of apparatus components and processing steps related to configuring uplink resources for user equipment initiated beam reporting. Accordingly, components have been represented where appropriate by conventional symbols in the drawings, showing only those specific details that are pertinent to understanding the embodiments so as not to obscure the disclosure with details that will be readily apparent to those of ordinary skill in the art having the benefit of the description herein. Features which are described in the context of separate aspects and embodiments of the invention may be used together and / or be interchangeable. Similarly, features described in the context of a single embodiment may also be provided separately or in any suitable subcombination.

[0090] As used herein, relational terms, such as “first” and “second,” “top” and “bottom,” and the like, may be used solely to distinguish one entity or element from another entity or element without necessarily requiring or implying any physical or logical relationship or order between such entities or elements. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0091] In embodiments described herein, the joining term, “in communication with” and the like, may be used to indicate electrical or data communication, which may be accomplished by physical contact, induction, electromagnetic radiation, radio signaling, infrared signaling or optical signaling, for example. One having ordinary skill in the art will appreciate that multiple components may interoperate, and modifications and variations are possible of achieving the electrical and data communication.

[0092] In some embodiments described herein, the term “coupled,” “connected,” and the like, may be used herein to indicate a connection, although not necessarily directly, and may include wired and / or wireless connections.

[0093] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the concepts described herein. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises,” “comprising,” “includes” and / or “including” when used herein, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0094] The term “network node” used herein may be any kind of network node included in a radio network which may further include any of base station (BS), radio base station, base transceiver station (BTS), base station controller (BSC), radio network controller (RNC), g Node B (gNB), evolved Node B (eNB or eNodeB), Node B, multi-standard radio (MSR) radio node such as MSR BS, multi-cell / multicast coordination entity (MCE), relay node, donor node controlling relay, radio access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU) Remote Radio Head (RRH), a core network node (e.g., mobile management entity (MME), self-organizing network (SON) node, a coordinating node, positioning node, MDT node, etc.), an external node (e.g., 3rd party node, a node external to the current network), nodes in distributed antenna system (DAS), a spectrum access system (SAS) node, an element management system (EMS), a distributed unit (DU), a centralized unit (CU), etc. The network node may also include test equipment. The term “radio node” used herein may be used to also denote a user equipment (UE) such as a wireless device (WD) or a radio network node. In some embodiments, the non-limiting terms wireless device (WD) or a user equipment (UE) are used interchangeably. The UE herein may be any type of user equipment capable of communicating with a network node or another UE over radio signals, such as a wireless device (WD). The UE may also be a radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), low-cost and / or low-complexity UE, a sensor equipped with UE, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), an Internet of Things (loT) device, or a Narrowband loT (NB-IOT) device etc.

[0095] Also, in some embodiments the generic term “radio network node” is used. It may be any kind of a radio network node which may include any of base station, radio base station, base transceiver station, base station controller, network controller, RNC, evolved Node B (eNB), Node B, gNB, Multi-cell / multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH).

[0096] Note that although terminology from one particular wireless system, such as, for example, 3GPP LTE and / or New Radio (NR), may be used in this disclosure, this should not be seen as limiting the scope of the disclosure to only the aforementioned system. Other wireless systems, including without limitation Wide Band Code Division Multiple Access (WCDMA), Worldwide Interoperability for Microwave Access (WiMax), Ultra Mobile Broadband (UMB) and Global System for Mobile Communications (GSM), may also benefit from exploiting the ideas covered within this disclosure.

[0097] Note further, that functions described herein as being performed by a user equipment or a network node may be distributed over a plurality of user equipments and / or network nodes. In other words, it is contemplated that the functions of the network node and user equipment described herein are not limited to performance by a single physical device and, in fact, may be distributed among several physical devices.

[0098] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. It will be further understood that terms used herein should be interpreted as having a meaning that is consistent with their meaning in the context of this specification and the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein. Referring to the drawing figures, in which like elements are referred to by like reference numerals, there is shown in FIG.1 a schematic diagram of an example communication system 10, according to an embodiment, such as a 3GPP-type cellular network that may support standards such as LTE and / or NR (5G), which includes an access network 12, such as a radio access network, and a core network 14. The access network 12 includes a plurality of network nodes 16a, 16b, 16c (referred to collectively as network nodes 16), such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 18a, 18b, 18c (referred to collectively as coverage areas 18). In some embodiments, coverage area 18 corresponds to a cell, which may serve or be used for communication with other devices of system 10. In some embodiments, a cell may be referred to as cell 18 (which may provide one or more coverage areas as described herein). Further, a cell may be of one or more types, such as a serving cell, target cell, neighbor cell, etc. Each network node 16a, 16b, 16c is connectable to the core network 14 over a wired or wireless connection 20. A first user equipment (UE) 22a located in coverage area 18a is configured to wirelessly connect to, or be paged by, the corresponding network node 16a. A second UE 22b in coverage area 18b is wirelessly connectable to the corresponding network node 16b. While a plurality of UEs 22a, 22b (collectively referred to as user equipments 22) are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding network node 16. Note that although only two UEs 22 and three network nodes 16 are shown for convenience, the communication system may include many more UEs 22 and network nodes 16.

[0099] Also, it is contemplated that a UE 22 may be in simultaneous communication and / or configured to separately communicate with more than one network node 16 and more than one type of network node 16. For example, a UE 22 may have dual connectivity with a network node 16 that supports LTE and the same or a different network node 16 that supports NR. As an example, UE 22 may be in communication with an eNB for LTE / E-UTRAN and a gNB for NR / NG-RAN.

[0100] A network node 16 (eNB or gNB) is configured to include a node management unit 24 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., network node functions. A user equipment 22 is configured to include a UE management unit 26 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., UE functions.

[0101] Example implementations, in accordance with an embodiment, of the UE 22 and network node 16 discussed in the preceding paragraphs will now be described with reference to FIG. 2.

[0102] The communication system 10 includes a network node 16 provided in a communication system 10 and includes hardware 28 enabling it to communicate with the UE 22. The hardware 28 may include a radio interface 30 for setting up and maintaining at least a wireless connection 32 with a UE 22 located in a coverage area 18 served by the network node 16. The radio interface 30 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 30 includes an array of antennas 34 to radiate and receive signal(s) carrying electromagnetic waves. Hardware 28 may also include communication interface 31 configured for setting up and maintaining communication with other network nodes 16, via wired / wireless connection(s).

[0103] In the embodiment shown, the hardware 28 of the network node 16 further includes processing circuitry 36. The processing circuitry 36 may include a processor 38 and a memory 40. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 36 may include integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 38 may be configured to access (e.g., write to and / or read from) the memory 40, which may include any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0104] Thus, the network node 16 further has software 42 stored internally in, for example, memory 40, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the network node 16 via an external connection. The software 42 may be executable by the processing circuitry 36. The processing circuitry 36 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by network node 16. Processor 38 corresponds to one or more processors 38 for performing network node 16 functions described herein. The memory 40 is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 42 may include instructions that, when executed by the processor 38 and / or processing circuitry 36, causes the processor 38 and / or processing circuitry 36 to perform the processes described herein with respect to network node 16. For example, processing circuitry 36 of the network node 16 may include a node management unit 24 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., network node functions.

[0105] The communication system 10 further includes the UE 22 already referred to. The UE 22 may have hardware 44 that may include a radio interface 46 configured to set up and maintain a wireless connection 32 with a network node 16 serving a coverage area 18 in which the UE 22 is currently located. The radio interface 46 may be formed as or may include, for example, one or more RF transmitters, one or more RF receivers, and / or one or more RF transceivers. The radio interface 46 includes an array of antennas 48 to radiate and receive signal(s) carrying electromagnetic waves.

[0106] The hardware 44 of the UE 22 further includes processing circuitry 50. The processing circuitry 50 may include a processor 52 and memory 54. In particular, in addition to or instead of a processor, such as a central processing unit, and memory, the processing circuitry 50 may include integrated circuitry for processing and / or control, e.g., one or more processors and / or processor cores and / or FPGAs (Field Programmable Gate Array) and / or ASICs (Application Specific Integrated Circuitry) adapted to execute instructions. The processor 52 may be configured to access (e.g., write to and / or read from) memory 54, which may include any kind of volatile and / or nonvolatile memory, e.g., cache and / or buffer memory and / or RAM (Random Access Memory) and / or ROM (Read-Only Memory) and / or optical memory and / or EPROM (Erasable Programmable Read-Only Memory).

[0107] Thus, the UE 22 may further include software 56, which is stored in, for example, memory 54 at the UE 22, or stored in external memory (e.g., database, storage array, network storage device, etc.) accessible by the UE 22. The software 56 may be executable by the processing circuitry 50. The software 56 may include a client application 58. The client application 58 may be operable to provide a service to a human or non-human user via the UE 22.

[0108] The processing circuitry 50 may be configured to control any of the methods and / or processes described herein and / or to cause such methods, and / or processes to be performed, e.g., by UE 22. The processor 52 corresponds to one or more processors 52 for performing UE 22 functions described herein. The UE 22 includes memory 54 that is configured to store data, programmatic software code and / or other information described herein. In some embodiments, the software 56 and / or the client application 58 may include instructions that, when executed by the processor 52 and / or processing circuitry 50, causes the processor 52 and / or processing circuitry 50 to perform the processes described herein with respect to UE 22. For example, the processing circuitry 50 of the user equipment 22 may include a UE management unit 26 which is configured to perform any step and / or task and / or process and / or method and / or feature described in the present disclosure, e.g., UE functions.

[0109] In some embodiments, the inner workings of the network node 16 and UE 22 may be as shown in FIG. 2 and independently, the surrounding network topology may be that of FIG. 1.

[0110] The wireless connection 32 between the UE 22 and the network node 16 is in accordance with the teachings of the embodiments described throughout this disclosure. More precisely, the teachings of some of these embodiments may improve the data rate, latency, and / or power consumption and thereby provide benefits such as reduced user waiting time, relaxed restriction on file size, better responsiveness, extended battery lifetime, etc. In some embodiments, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.

[0111] Although FIGS. 1 and 2 show various “units” such as node management unit 24 and UE management unit 26 as being within a respective processor, it is contemplated that these units may be implemented such that a portion of the unit is stored in a corresponding memory within the processing circuitry. In other words, the units may be implemented in hardware or in a combination of hardware and software within the processing circuitry.

[0112] FIG. 3 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the UE management unit 26), processor 52, and / or radio interface 46. User equipment 22 such as via processing circuitry 50 and / or processor 52 and / or radio interface 46 is configured to one or more of: (A) receive (Block S100), from the network node 16, a plurality of channel state information (CSI) report configurations, each CSI report configuration being associated with an event and a component carrier (CC); (B) receive (Block S102), from the network node 16, a configuration of a first uplink (UL) channel and a second UL channel; (C) transmit (Block S104) a first indication on the first UL channel when one or more events occur in one or more of the CCs; (D) determine (Block S 106) a beam report associated with the one or more events that occur in the one or more of the CCs; (E) transmit (Block S 108) the beam report in the second UL channel, the beam report including a second indication indicating a number of remaining beam reports to be transmitted; and (F) transmit (Block S 110) one or more of the remaining beam reports in a UL resource indicated in a UL grant in downlink control information (DCI) if the indicated number of remaining beam reports is non-zero. The dashed lines in FIG. 3 indicate optional steps.

[0113] In some embodiments, the UE initiated beam reporting occurs when the one or more events and / or the one or more CCs are configured for the UE initiated beam reporting. In some embodiments, the first indication is transmitted when the one or more events occur in one or more of the CCs at the same time. In some embodiments, one or both of the beam report corresponds to one CSI report configuration of the plurality of CSI report configurations and the beam report is determined based on a priority rule having a priority associated with each of the plurality of CSI report configurations. In some embodiments, the second indication further indicates a number of events that occurred in the one or more CCs.

[0114] In some embodiments, the method further includes receiving, from the network node 16, a CSI request and the UL grant in DCI for transmitting one or more additional beam reports if indicated in the beam report.

[0115] FIG. 4 is a flowchart of an example process in a network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, and / or radio interface 30. Network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 is configured to one or more of: (A) transmit (Block S 112), to the UE 22, a plurality of channel state information (CSI) report configurations, each CSI report configuration being associated with an event and a component carrier (CC); (B) transmit (Block SI 14), to the UE 22, a configuration of a first uplink (UL) channel and a second UL channel; (C) receive (Block SI 16), from the UE 22, a first indication on the first UL channel when one or more events occur in one or more of the CCs; (D) receive (Block S 118), from the UE 22, a beam report in the second UL channel, the beam report including a second indication indicating a number of remaining beam reports to be transmitted, the beam report being associated with the one or more events that occur in the one or more of the CCs; and (E) receive (Block S120), from the UE 22, one or more of the remaining beam reports in a UL resource indicated in a UL grant in downlink control information (DCI) if the indicated number of remaining beam reports is non-zero. The dashed lines in FIG. 4 indicate optional steps.

[0116] In some embodiments, the UE initiated beam reporting occurs when the one or more events and / or the one or more CCs are configured for the UE initiated beam reporting. In some embodiments, the first indication is received when the one or more events occur in one or more of the CCs at the same time.

[0117] In some embodiments, one or both of the beam report corresponds to one CSI report configuration of the plurality of CSI report configurations and the beam report is based on a priority rule having a priority associated with each of the plurality of CSI report configurations. In some embodiments, the second indication further indicates a number of events that occurred in the one or more CCs. In some embodiments, the method further includes transmitting, to the UE, a CSI request and the UL grant in DCI for transmitting by the UE 22 one or more additional beam reports if indicated in the beam report.

[0118] FIG. 5 is a flowchart of an example process in a network node 16. One or more blocks described herein may be performed by one or more elements of network node 16 such as by one or more of processing circuitry 36 (including the node management unit 24), processor 38, and / or radio interface 30. Network node 16 such as via processing circuitry 36 and / or processor 38 and / or radio interface 30 is configured to transmit to the UE 22 a first channel state information, CSI, report configuration including information of a first trigger condition and information of a first uplink channel (Block S122). The process includes transmitting to the UE 22 a second CSI report configuration including information of a second trigger condition and information of the first uplink channel (Block S 124). The process includes transmitting a UE-initiated beam report in a second uplink channel when at least one of at least one of the first and second trigger conditions is fulfilled, the UE-initiated beam report corresponding to one of the first and second CSI report configurations (Block S 126).

[0119] In some embodiments, the first trigger condition is associated to a first event and the second trigger condition is associated to a second event. In some embodiments, the first trigger condition is the same as the second trigger condition. In some embodiments, the first trigger condition is different than the second trigger condition. In some embodiments, a resource for the second uplink channel is configured to carry a single UE- initiated beam report. In some embodiments, the first uplink channel is a physical uplink control channel, PUCCH with a first periodicity, and wherein the first uplink channel is for carrying a UE-initiated beam report indicator. In some embodiments, the second uplink channel is one of a physical uplink shared channel, PUSCH, dynamically scheduled, and a PUSCH semi- statically scheduled with a second periodicity, and wherein the second uplink channel is for carrying the UE-initiated beam report. In some embodiments, the second uplink channel is a configured grant physical uplink shared channel, PUSCH, and wherein for each occasion of the first uplink channel, there is a corresponding occasion of the second uplink channel separated from the first uplink channel by a time offset. In some embodiments, the second uplink channel is a configured grant PUSCH and wherein the first periodicity and the second periodicity are the same. In some embodiments, when beam reporting is triggered for both the first and second CSI report configurations, only a single UE-initiated beam report associated to one of the first and second CSI report configurations is transmitted on the second uplink channel. In some embodiments, the single UE-initiated beam report corresponds to one of the first and second CSI report configurations with a high priority. In some embodiments, each of the first and the second CSI report configurations further includes a same carrier index. In some embodiments, the method includes indicating to the UE 22 a set of dedicated physical uplink shared channel, PUSCH, resources for transmitting the UE-initiated beam report.

[0120] FIG. 6 is a flowchart of an example process in a user equipment 22 according to some embodiments of the present disclosure. One or more blocks described herein may be performed by one or more elements of user equipment 22 such as by one or more of processing circuitry 50 (including the UE management unit 26), processor 52, and / or radio interface 46. User equipment 22 such as via processing circuitry 50 and / or processor 52 and / or radio interface 46 is configured to receive from the network node 16 a first channel state information, CSI, report configuration including information of a first trigger condition and information of a first uplink channel (Block S128). The process includes receiving from the network node 16 a second CSI report configuration including information of a second trigger condition and information of the first uplink channel (Block S 130). The process also includes transmitting a UE-initiated beam report in a second uplink channel when at least one of the first and the second trigger conditions is fulfilled, the UE-initiated beam report corresponding to one of the first and second CSI report configurations (Block S 132).

[0121] In some embodiments, the first trigger condition is associated to a first event and the second trigger condition is associated to a second event. In some embodiments, the first trigger condition is the same as the second trigger condition. In some embodiments, the first trigger condition is different than the second trigger condition. In some embodiments, a resource for the second uplink channel is configured to carry a single UE- initiated beam report. In some embodiments, the first uplink channel is a physical uplink control channel, PUCCH with a first periodicity, and wherein the first uplink channel is for carrying a UE-initiated beam report indicator. In some embodiments, the second uplink channel is one of a physical uplink shared channel, PUSCH, dynamically scheduled, and a PUSCH semi- statically scheduled with a second periodicity, and wherein the second uplink channel is for carrying the UE-initiated beam report. In some embodiments, the second uplink channel is a configured grant physical uplink shared channel, PUSCH, and wherein for each occasion of the first uplink channel, there is a corresponding occasion of the second uplink channel separated from the first uplink channel by a time offset. In some embodiments, the second uplink channel is a configured grant PUSCH and wherein the first periodicity and the second periodicity are the same. In some embodiments, when beam reporting is triggered for both the first and second CSI report configurations, only a single UE-initiated beam report associated to one of the first and second CSI report configurations is transmitted on the second uplink channel. In some embodiments, the single UE-initiated beam report corresponds to one of the first and second CSI report configurations with a high priority. In some embodiments, each of the first and the second CSI report configurations further includes a same carrier index. In some embodiments, UE-initiated beam reports are prioritized according to an order of the first trigger condition and the second trigger condition. In some embodiments, each of the first and the second CSI report configurations includes a configuration index and wherein UE-initiated beam reports are prioritized according to the configuration index, wherein a lower or smaller index value is associated to a higher priority. In some embodiments, the process includes, when a UE-initiated beam report on the second uplink channel collides with resources of a hybrid automatic repeat request acknowledgment, HARQ-ACK, multiplexing the UE- initiated beam report with the HARQ-ACK on the second uplink channel. In some embodiments, when a UE-initiated beam report on the second uplink channel collides with resources for a scheduling request, SR, dropping the UE-initiated beam report when the second uplink channel is a physical uplink shared channel, PUSCH, or a configured grant PUSCH. In some embodiments, when a UE-initiated beam report on the second uplink channel collides with periodic or semi-persistent CSI in a slot, dropping the periodic or semi-persistent CSI, i.e., the UE-initiated beam report has a higher priority than periodic or semi-persistent CSI. In some embodiments, the method includes, when a UE-initiated beam report on the second uplink channel collides with an aperiodic CSI on a physical uplink shared channel, multiplexing the UE-initiated beam report with the aperiodic CSI or dropping the aperiodic CSI.

[0122] Having described the general process flow of arrangements of the disclosure and having provided examples of hardware and software arrangements for implementing the processes and functions of the disclosure, the sections below provide details and examples of arrangements configuring uplink resources for user equipment initiated beam reporting.

[0123] An example method may include one or more of the following steps performed at a UE 22:

[0124] • Step 1, receiving from a network node 16 a first CSI report configuration including information of a first event and information of a first uplink channel, and a second CSI report configuration including information of a second event and information of the first uplink channel;

[0125] • Step 2, transmitting an indication in the first uplink channel when conditions for at least one of the first and second events are fulfilled; and / or

[0126] • Step 3, transmitting a UE-initiated beam report in a second UL channel, where the report corresponds to one of the first and second CSI report configurations.

[0127] The first uplink channel is PUCCH (also referred to as the first PUCCH) and may be a scheduling request (SR) identified by an SR index or ID. The SR is configured with a first periodicity, a first slot offset, and a PUCCH resource index indicating a PUCCH resource for the SR. The information of the first uplink channel in the first and second CSI report configuration includes an SR index.

[0128] The first and the second events may be the same or different. The first or the second event may be event-2, for example.

[0129] In cases of Mode -A, the second uplink channel is a PUSCH resource scheduled by DCI (e.g., DCI format 0_l, DCI format 0_2). In the case of Mode-B, each of the first and second CSI report configurations further includes information of the second uplink channel. In this case, the second UL channel may be one of PUCCH, PUSCH, and CG- PUSCH, which are further discussed below.

[0130] PUCCH as the second UL channel

[0131] In cases that PUCCH is configured for the second UL channel, for each occasion of the first UL channel, there is a corresponding occasion of the second UL channel separated by a time offset (T) as shown in FIG. 7, where the time offset may be a number of slots between the slot of the first UL channel and the slot of the second UL channel

[0132] PUCCH.

[0133] The time offset may be prespecified or preconfigured as part of the second UL channel configuration. The second UL channel configuration may include one or both of:

[0134] • A PUCCH resource index; and / or

[0135] • A second periodicity and a second slot offset. where the second periodicity may be the same as the first periodicity, and the second slot offset may equal to the first slot offset plus the time offset T. The PUCCH resource may be with one of PUCCH formats 2, 3, 4 as defined in NR.

[0136] PUS CH as the second UL channel

[0137] When PUSCH is configured for the second UL channel, in some embodiments, a new pre-configured PUSCH resource, e.g., UE-Initiated Beam Management (UIBM)- PUSCH, is introduced. The PUSCH transmission occasions are linked to the first PUCCH as illustrated in FIG. 8.

[0138] The configuration of UIBM-PUSCH for the second UL channel may include one or more of: o Time domain resource allocation (TDRA); o Frequency domain resource allocation (FDRA); o MCS (modulation and coding scheme); and / or o Slot offset (T) with respect to the first UL channel.

[0139] In addition, the configuration may further include one or more of: o A third periodicity; o Beta offset; o Number of repetitions; o DMRS configuration; o Number of layer and precoding information; o A new RNTI is to be associated with the second UL Channel; o A CS-RNTI; o An index indicates which UIBM event the report is associated with; o An index indicates which UIBM report the UL channel is associated with; and / or o An index indicates which CG-PUSCH configuration to be used for sending report. The third periodicity may be the same as the first periodicity, where the “beta offset” configures a power offset for transmitting the UE-initiated beam report with respect to normal PUSCH transmission. The beta offset may be different from that configured for normal UCI on PUSCH, i.e., configured in PUSCH-config in NR; “number of repetitions” may configure the number of PUSCH repetitions if more reliable beam reporting is needed. The “DMRS configuration” may configure a different DMRS port for different UEs 22 to facilitate spatial multi-user multiplexing or MU-MIMO. The “Number of layer and precoding information” configures the number of layers and precoders used.

[0140] In some embodiments, the PUSCH resources configured for the second UL channel are limited to UIBM for reporting, and the PUSCH UL-SCH (UL Shared Channel) data cannot be transmitted using the pre-configured PUSCH resources.

[0141] CG-PUSCH as the second UL channel

[0142] In some embodiments, when a type-1 CG-PUSCH in NR is configured for the second UL channel, the CG-PUSCH may have the same or different (e.g., smaller) periodicity as the first UL channel. When triggered, the beam report may be sent on a CG- PUSCH transmit occasion right after the first PUCCH resource as illustrated in the example of FIG. 9, where the CG-PUSCH has the same periodicity as the first UL channel but different slot offsets. The time offset T is the slot offset between the first UL channel and the CG-PUSCH. If there is no beam report indication sent on the first PUCCH, the subsequent CG-PUSCH resource may be used following existing CG-PUSCH rules in NR.

[0143] In some embodiments, the CG-PUSCH is a Type2 CG PUSCH. The activation DCI for the Type 2 CG-PUSCH is used to activate / deactivate both the first UL channel and the second UL channel for UIBM (UE-initiated beam) report. UE 22 transmits on the first and the second UL Channel only after receiving an activation DCI.

[0144] The second UL channel may be repeated in time (either in the same slot or different slots) for increased reliability of the beam report as illustrated in the example of FIG. 10.

[0145] The first and second CSI report configurations in Step 1 may further include a first and a second carrier (or serving cell) index, respectively. The first and the second carrier indices may be the same or different.

[0146] When the network node 16 receives an indication in the first UL channel, the network node 16 may not know or be able to determine whether the first event, the second event, or both the first and second events corresponding respectively to the first and second CSI report configurations have occurred. To minimize resource overhead, in some embodiments the resource for the second UL channel is designed for carrying a single UE- initiated beam report, i.e., a beam report associated to a single CSI report configuration. If UE-initiated beam reporting is triggered for both the first and second CSI report configurations, only the beam report with the highest priority among the beam reports may be transmitted on the second UL channel.

[0147] An indication may be included in the beam report sent in the second UL channel indicating the number of additional beam report(s) to be sent. After receiving the beam report and the indication on the second UL channel, the network node 16 may schedule additional UL resources for the UE 22 to send the remaining beam report(s). In this way, large overhead for the second UL channel may be avoided at the cost of extra beam report delay for the remaining beam report(s) with lower priorities.

[0148] For requesting the UE 22 to send the remaining beam report(s), a CSI trigger state may be configured for the purpose such that when a DCI (e.g., DCI format 0-1, DCI format 0-2) is received with a CSI request field in the DCI indicating the trigger state, the UE 22 sends the remaining beam report(s) in the resource scheduled by the DCI. This is illustrated in the example of FIG. 11.

[0149] In cases where the first and the second carrier indices are different, the priority of a beam report may be determined based on the carrier index value configured in the corresponding CSI report configuration. A beam report associated with a lower carrier index value has a higher priority than a beam report associated with a higher carrier index value. In case the first and the second carrier indices are the same but the first and the second events are different, a beam report associated with a CSI report configuration with a lower report configuration index value has a higher priority.

[0150] In some embodiments, when multiple events corresponding to multiple CSI reporting configurations occur, the beam reports are prioritized according to the order in which the events occurred. An example is shown in FIG. 12 where the event corresponding to the 2ndCSI reporting configuration occurs at an earlier time than the event corresponding to the 1stCSI reporting configuration. Then, the beam report corresponding to the 2ndCSI reporting configuration has higher priority than the beam report corresponding to the 1stCSI reporting configuration. In the example of FIG. 12, after the events occur, the UE 22 sends a beam report indication in the 1stUL channel. As shown in the figure, a beam report corresponding to the 2ndCSI reporting configuration plus an indication of additional beam report(s) to be sent is then transmitted in 2ndUL channel. The additional beam report here is the beam report corresponding to the 1stCSI reporting configuration. Following transmission of beam report corresponding to the 2ndCSI reporting configuration plus additional beam report indication in the 2ndUL channel, the UE 22 receives a DCI with a CSI request where the DCI provides an UL grant. The UE then transmits the beam report corresponding to the 1stCSI reporting configuration in the resources provided by the UL grant.

[0151] Handling collisions with other UCIs

[0152] Colliding may refer to the second UL channel carrying a beam report overlapping with other UCI resources in at least one OFDM symbol. In cases where a beam report on the second UL channel collides with resources for HARQ-ACK (Hybrid Automatic Repeat reQuest ACKnowledgment), the beam report may be multiplexed with the HARQ- ACK on the second UL channel. In cases where a beam report on the second UL channel collides with resources for SR, the beam report may be multiplexed with the SR on the second UL channel if the second UL channel is a PUCCH, and the beam report is dropped if the second UL channel is a PUSCH or a CG-PUSCH. Alternatively, the SR may be dropped.

[0153] In cases where a beam report on the second UL channel collides with periodic or semi-persistent CSI in a slot, the periodic or semi-persistent CSI may be dropped.

[0154] In cases where a beam report on the second UL channel collides with an aperiodic CSI on PUSCH, the beam report may be multiplexed with the aperiodic CSI on PUSCH. Alternatively, the aperiodic CSI may be dropped.

[0155] Multiplexing with UL-SCH data

[0156] In some embodiments, whether or not UL-SCH data may be multiplexed on the CG-PUSCH for UIBM is predetermined in specification. In some embodiments, dedicated PUSCH resources are indicated to UE to transmit the UIBM report. In some embodiments, network node 16 determines whether or not UL-SCH data may be multiplexed with UIBM on the PUSCH resources used for UIBM report and indicates that to the UE via RRC configuration and / or DCI signaling:

[0157] • For type 1 CG PUSCH, a flag may be added in higher level signaling, e.g. RRC configuration, that enables multiplexing of UL-SCH data with UIBM on the PUSCH resources; and / or

[0158] • For type 2 CG-PUSCH, a PDCCH signaling with DCI field “UL-SCH” set to ‘0’ or ‘1’ in the activation DCI for type 2 CG-PUSCH indicates whether UL-SCH data may be multiplexed. A flag may also be added in higher layer signaling for type 2 CG- PUSCH to indicate whether the UE may multiplex UL-SCH on the CG-PUSCH resources for UIBM report. If the flag indicates no multiplexing with PUSCH data, UE 22 ignores the “UL-SCH” field in the activation DCI, or the “UL-SCH” field may be used for validation of activation and deactivation of DCI for CG-PUSCH for UIBM.

[0159] In some embodiments, if UL-SCH data is not allowed to multiplex with UIBM, HARQ process ID is not allocated and used for the UIBM report. There is no retransmission allowed for CG-PUSCH for UIBM.

[0160] In some embodiments, if UL-SCH data is not allowed to multiplex with CG- PUSCH-UIBM, timer for CG-PUSCH is not needed.

[0161] In some embodiments, the CG-PUSCH resources configured for transmitting PUSCH data may be configured to also be used for transmitting UIBM report. UE 22 transmits both UL-SCH data and the UIBM report on the CG-PUSCH resources.

[0162] Some embodiments may include one or more of the following:

[0163] Embodiment AL A method in a user equipment (UE) for communicating with a network node, the method being for a UE initiated beam reporting at the UE, the method comprising one or more of: receiving, from the network node, a plurality of channel state information (CSI) report configurations, each CSI report configuration being associated with an event and a component carrier (CC); receiving, from the network node, a configuration of a first uplink (UL) channel and a second UL channel; transmitting a first indication on the first UL channel when one or more events occur in one or more of the CCs; determining a beam report associated with the one or more events that occur in the one or more of the CCs; transmitting the beam report in the second UL channel, the beam report including a second indication indicating a number of remaining beam reports to be transmitted; and transmitting one or more of the remaining beam reports in a UL resource indicated in a UL grant in downlink control information (DCI) if the indicated number of remaining beam reports is non-zero.

[0164] Embodiment A2. The method of Embodiment Al, wherein the UE initiated beam reporting occurs when the one or more events and / or the one or more CCs are configured for the UE initiated beam reporting. Embodiment A3. The method of Embodiments Al and A2, wherein the first indication is transmitted when the one or more events occur in one or more of the CCs at the same time.

[0165] Embodiment A4. The method of Embodiments Al -A3, wherein one or both of: the beam report corresponds to one CSI report configuration of the plurality of CSI report configurations; and the beam report is determined based on a priority rule having a priority associated with each of the plurality of CSI report configurations.

[0166] Embodiment A5. The method of Embodiments A1-A4, wherein the second indication further indicates a number of events that occurred in the one or more CCs.

[0167] Embodiment A6. The method of Embodiments A1-A5, wherein the method further includes: receiving, from the network node, a CSI request and the UL grant in DCI for transmitting one or more additional beam reports if indicated in the beam report.

[0168] Embodiment Bl. A user equipment (UE) for communicating with a network node, the UE being configured for a UE initiated beam reporting, the UE being configured to, and / or comprising a radio interface and / or processing circuitry configured to perform any one of Embodiments A1-A6.

[0169] Embodiment Cl. A method in a network node for communicating with a user equipment (UE), the method being for a user equipment (UE) initiated beam reporting, the method comprising one or more of: transmitting, to the UE, a plurality of channel state information (CSI) report configurations, each CSI report configuration being associated with an event and a component carrier (CC); transmitting, to the UE, a configuration of a first uplink (UL) channel and a second UL channel; receiving, from the UE, a first indication on the first UL channel when one or more events occur in one or more of the CCs; receiving, from the UE, a beam report in the second UL channel, the beam report including a second indication indicating a number of remaining beam reports to be transmitted, the beam report being associated with the one or more events that occur in the one or more of the CCs; and receiving, from the UE, one or more of the remaining beam reports in a UL resource indicated in a UL grant in downlink control information (DCI) if the indicated number of remaining beam reports is non-zero.

[0170] Embodiment C2. The method of Embodiment C 1 , wherein the UE initiated beam reporting occurs when the one or more events and / or the one or more CCs are configured for the UE initiated beam reporting.

[0171] Embodiment C3. The method of Embodiments Cl and C2, wherein the first indication is received when the one or more events occur in one or more of the CCs at the same time.

[0172] Embodiment C4. The method of Embodiments C1-C3, wherein one or both of: the beam report corresponds to one CSI report configuration of the plurality of CSI report configurations; and the beam report is based on a priority rule having a priority associated with each of the plurality of CSI report configurations.

[0173] Embodiment C5. The method of Embodiments C1-C4, wherein the second indication further indicates a number of events that occurred in the one or more CCs.

[0174] Embodiment C6. The method of Embodiments C 1-C5, wherein the method further includes: transmitting, to the UE, a CSI request and the UL grant in DCI for transmitting by the UE one or more additional beam reports if indicated in the beam report.

[0175] Embodiment DI. A network node for communicating with a user equipment (UE) for communicating with a network node, the UE being configured for a user equipment (UE) initiated beam reporting, the network node being configured to, and / or comprising a radio interface and / or processing circuitry configured to perform any one of Embodiments C1-C6.

[0176] As will be appreciated by one of skill in the art, the concepts described herein may be embodied as a method, data processing system, computer program product and / or computer storage media storing an executable computer program. Accordingly, the concepts described herein may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects all generally referred to herein as a “circuit” or “module.” Any process, step, action and / or functionality described herein may be performed by, and / or associated to, a corresponding module, which may be implemented in software and / or firmware and / or hardware. Furthermore, the disclosure may take the form of a computer program product on a tangible computer usable storage medium having computer program code embodied in the medium that may be executed by a computer. Any suitable tangible computer readable medium may be utilized including hard disks, CD-ROMs, electronic storage devices, optical storage devices, or magnetic storage devices.

[0177] Some embodiments are described herein with reference to flowchart illustrations and / or block diagrams of methods, systems and computer program products. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer (to thereby create a special purpose computer), special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0178] These computer program instructions may also be stored in a computer readable memory or storage medium that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture including instruction means which implement the function / act specified in the flowchart and / or block diagram block or blocks.

[0179] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0180] It is to be understood that the functions / acts noted in the blocks may occur out of the order noted in the operational illustrations. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality / acts involved. Although some of the diagrams include arrows on communication paths to show a primary direction of communication, it is to be understood that communication may occur in the opposite direction to the depicted arrows.

[0181] Computer program code for carrying out operations of the concepts described herein may be written in an object oriented programming language such as Python, Java® or C++. However, the computer program code for carrying out operations of the disclosure may also be written in conventional procedural programming languages, such as the "C" programming language. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0182] Many different embodiments have been disclosed herein, in connection with the above description and the drawings. It will be understood that it would be unduly repetitious and obfuscating to literally describe and illustrate every combination and subcombination of these embodiments. Accordingly, all embodiments may be combined in any way and / or combination, and the present specification, including the drawings, shall be construed to constitute a complete written description of all combinations and subcombinations of the embodiments described herein, and of the manner and process of making and using them, and shall support claims to any such combination or subcombination.

[0183] It will be appreciated by persons skilled in the art that the embodiments described herein are not limited to what has been particularly shown and described herein above. In addition, unless mention was made above to the contrary, it should be noted that all of the accompanying drawings are not to scale. A variety of modifications and variations are possible in light of the above teachings without departing from the scope of the following claims.

Claims

What is Claimed is:

1. A method in a user equipment, UE (22), configured to communicate with a network node (16), the method comprising: receiving (S128) from the network node (16) a first channel state information, CSI, report configuration including information of a first trigger condition and information of a first uplink channel; receiving (S130) from the network node (16) a second CSI report configuration including information of a second trigger condition and information of the first uplink channel; and transmitting (S132) a UE-initiated beam report in a second uplink channel when at least one of the first and the second trigger conditions is fulfilled, the UE-initiated beam report corresponding to one of the first and second CSI report configurations.

2. The method of Claim 1, wherein the first trigger condition is associated to a first event and the second trigger condition is associated to a second event.

3. The method of Claim 2, wherein the first event is the same as the second event.

4. The method of Claim 2, wherein the first event is different than the second event.

5. The method of Claim 1, wherein a resource for the second uplink channel is configured to carry a single UE-initiated beam report.

6. The method of any of Claims 1-5, wherein the first uplink channel is a physical uplink control channel, PUCCH with a first periodicity, and wherein the first uplink channel is for carrying a UE initiated beam report indicator.

7. The method of any of Claims 1-6, wherein the second uplink channel is one of a physical uplink shared channel, PUSCH, dynamically scheduled, and a PUSCH semi- statically scheduled with a second periodicity, and wherein the second uplink channel is for carrying the UE initiated beam report.

8. The method of any of Claims 1-7, wherein the second uplink channel is a configured grant physical uplink shared channel, PUSCH, and wherein for each occasion of the first uplink channel, there is a corresponding occasion of the second uplink channel separated from the first uplink channel by a time offset.

9. The method of any of Claims 1-7, wherein the second uplink channel is a configured grant PUSCH and wherein the first periodicity and the second periodicity are the same.

10. The method of any of Claims 1-9, wherein, when beam reporting is triggered for both the first and second CSI report configurations, only a single UE-initiated beam report associated to one of the first and second CSI report configurations is transmitted on the second uplink channel.

11. The method of Claim 10, wherein the single UE initiated beam report corresponds to one of the first and second CSI report configurations with a high priority.

12. The method of any of Claims 1-11, wherein each of the first and the second CSI report configurations further comprises a same carrier index.

13. The method of any of Claims 1-12, wherein UE-initiated beam reports are prioritized according to an order of the first trigger condition and the second trigger condition.

14. The method of any of Claims 1-13, wherein each of the first and the second CSI report configurations comprises a configuration index and wherein UE-initiated beam reports are prioritized according to the configuration index, wherein a lower or smaller index value is associated to a higher priority.

15. The method of any of Claims 1-14, further comprising, when a UE-initiated beam report on the second uplink channel collides with resources of a hybrid automatic repeat request acknowledgment, HARQ-ACK, multiplexing the UE-initiated beam report with the HARQ-ACK on the second uplink channel.

16. The method of any of Claims 1-14, further comprising, when a UE-initiated beam report on the second uplink channel collides with resources for a scheduling request, SR, dropping the UE-initiated beam report when the second uplink channel is a physical uplink shared channel, PUSCH, or a configured grant PUSCH.

17. The method of any of Claims 1-14, further comprising, when a UE-initiated beam report on the second uplink channel collides with periodic or semi-persistent CSI in a slot, dropping the periodic or semi-persistent CSI.

18. The method of any of Claims 1-17, further comprising, when a UE-initiated beam report on the second uplink channel collides with an aperiodic CSI on a physical uplink shared channel, multiplexing the UE-initiated beam report with the aperiodic CSI or dropping the aperiodic CSI.

19. A user equipment, UE (22), configured to communicate with a network node (16), the UE (22) comprising processing circuitry configured to: receive from the network node (16) a first channel state information, CSI, report configuration including information of a first trigger condition and information of a first uplink channel; receive from the network node (16) a second CSI report configuration including information of a second trigger condition and information of the first uplink channel; and transmit a UE-initiated beam report in a second uplink channel when at least one of the first and the second trigger conditions is fulfilled, the UE-initiated beam report corresponding to one of the first and second CSI report configurations.

20. The UE (22) of Claim 19, wherein the first trigger condition is associated to a first event and the second trigger condition is associated to a second event.

21. The UE (22) of Claim 20, wherein the first event is the same as the second event.

22. The UE (22) of any of Claim 20, wherein the first event is different than the second event.

23. The UE (22) of Claim 19, wherein a resource for the second uplink channel is configured to carry a single UE-initiated beam report.

24. The UE (22) of any of Claims 19-23, wherein the first uplink channel is a physical uplink control channel, PUCCH with a first periodicity, and wherein the first uplink channel is for carrying a UE initiated beam report indicator.

25. The UE (22) of any of Claims 19-24, wherein the second uplink channel is one of a physical uplink shared channel, PUSCH, dynamically scheduled, and a PUSCH semi-statically scheduled with a second periodicity, and wherein the second uplink channel is for carrying the UE initiated beam report.

26. The UE (22) of any of Claims 19-25, wherein the second uplink channel is a configured grant physical uplink shared channel, PUSCH, and wherein for each occasion of the first uplink channel, there is a corresponding occasion of the second uplink channel separated from the first uplink channel by a time offset.

27. The UE (22) of any of Claims 19-26, wherein the second uplink channel is a configured grant PUSCH and wherein the first periodicity and the second periodicity are the same.

28. The UE (22) of any of Claims 19-27, wherein, when beam reporting is triggered for both the first and second CSI report configurations, only a single UE-initiated beam report associated to one of the first and second CSI report configurations is transmitted on the second uplink channel.

29. The UE (22) of Claim 28, wherein the single UE initiated beam report corresponds to one of the first and second CSI report configurations with a high priority.

30. The UE (22) of any of Claims 19-29, wherein each of the first and the second CSI report configurations further comprises a same carrier index.

31. The UE (22) of any of Claims 19-30, wherein UE-initiated beam reports are prioritized according to an order of the first trigger condition and the second trigger condition.

32. The UE (22) of any of Claims 19-31, wherein each of the first and the second CSI report configurations comprises a configuration index and wherein UE- initiated beam reports are prioritized according to the configuration index, wherein a lower or smaller index value is associated to a higher priority.

33. The UE (22) of any of Claims 19-31 wherein, when a UE-initiated beam report on the second uplink channel collides with resources of a hybrid automatic repeat request acknowledgment, HARQ-ACK, the processing circuitry is configured to multiplex the UE-initiated beam report with the HARQ-ACK on the second uplink channel.

34. The UE (22) of any of Claims 19-31, wherein, when a UE-initiated beam report on the second uplink channel collides with resources for a scheduling request, SR, the processing circuitry is configured to drop the UE-initiated beam report when the second uplink channel is a physical uplink shared channel, PUSCH, or a configured grant PUSCH.

35. The UE (22) of any of Claims 19-31, further comprising, when a UE- initiated beam report on the second uplink channel collides with periodic or semi- persistent CSI in a slot, dropping the periodic or semi-persistent CSI.

36. The UE (22) of any of Claims 19-35, further comprising, when a UE- initiated beam report on the second uplink channel collides with an aperiodic CSI on a physical uplink shared channel, multiplexing the UE-initiated beam report with the aperiodic CSI or dropping the aperiodic CSI.

37. A method in a network node (16) configured to communicate with a user equipment, UE (22), the method comprising: transmitting (S122) to the UE (22) a first channel state information, CSI, report configuration including information of a first trigger condition and information of a first uplink channel; transmitting (S124) to the UE (22) a second CSI report configuration including information of a second trigger condition and information of the first uplink channel; andtransmitting (S126) a UE-initiated beam report in a second uplink channel when at least one of at least one of the first and second trigger conditions is fulfilled, the UE- initiated beam report corresponding to one of the first and second CSI report configurations.

38. The method of Claim 37, wherein the first trigger condition is associated to a first event and the second trigger condition is associated to a second event.

39. The method of Claim 38, wherein the first event is the same as the second event.

40. The method of Claim 38, wherein the first event is different than the second event.

41. The method of Claim 40, wherein a resource for the second uplink channel is configured to carry a single UE-initiated beam report.

42. The method of any of Claims 37-41, wherein the first uplink channel is a physical uplink control channel, PUCCH with a first periodicity, and wherein the first uplink channel is for carrying a UE initiated beam report indicator.

43. The method of any of Claims 37-42, wherein the second uplink channel is one of a physical uplink shared channel, PUSCH, dynamically scheduled, and a PUSCH semi- statically scheduled with a second periodicity, and wherein the second uplink channel is for carrying the UE initiated beam report.

44. The method of any of Claims 37-43, wherein the second uplink channel is a configured grant physical uplink shared channel, PUSCH, and wherein for each occasion of the first uplink channel, there is a corresponding occasion of the second uplink channel separated from the first uplink channel by a time offset.

45. The method of any of Claims 37-44, wherein the second uplink channel is a configured grant PUSCH and wherein the first periodicity and the second periodicity are the same.

46. The method of any of Claims 37-45, wherein, when beam reporting is triggered for both the first and second CSI report configurations, only a single UE-initiated beam report associated to one of the first and second CSI report configurations is transmitted on the second uplink channel.

47. The method of Claim 46, wherein the single UE initiated beam report corresponds to one of the first and second CSI report configurations with a high priority.

48. The method of any of Claims 37-47, wherein each of the first and the second CSI report configurations further comprises a same carrier index.

49. The method of Claim 48, further comprising indicating to the UE (22) a set of dedicated physical uplink shared channel, PUSCH, resources for transmitting the UE- initiated beam report.

50. A network node (16) configured to communicate with a user equipment, UE (22), the network node (16) comprising processing circuitry configured to: transmit to the UE (22) a first channel state information, CSI, report configuration including information of a first trigger condition and information of a first uplink channel; transmit to the UE (22) a second CSI report configuration including information of a second trigger condition and information of the first uplink channel; and transmit a UE-initiated beam report in a second uplink channel when at least one of at least one of the first and second trigger conditions is fulfilled, the UE-initiated beam report corresponding to one of the first and second CSI report configurations.

51. The network node (16) of Claim 50, wherein the first trigger condition is associated to a first event and the second trigger condition is associated to a second event.

52. The network node (16) of Claim 51, wherein the first event is the same as the second event.

53. The network node (16) of Claim 51, wherein the first event is different than the second event.

54. The network node (16) of Claim 53, wherein a resource for the second uplink channel is configured to carry a single UE-initiated beam report.

55. The network node (16) of any of Claims 50-54, wherein the first uplink channel is a physical uplink control channel, PUCCH with a first periodicity, and wherein the first uplink channel is for carrying a UE initiated beam report indicator.

56. The network node (16) of any of Claims 50-55, wherein the second uplink channel is one of a physical uplink shared channel, PUSCH, dynamically scheduled, and a PUSCH semi- statically scheduled with a second periodicity, and wherein the second uplink channel is for carrying the UE initiated beam report.

57. The network node (16) of any of Claims 50-56, wherein the second uplink channel is a configured grant physical uplink shared channel, PUSCH, and wherein for each occasion of the first uplink channel, there is a corresponding occasion of the second uplink channel separated from the first uplink channel by a time offset.

58. The network node (16) of any of Claims 50-57, wherein the second uplink channel is a configured grant PUSCH and wherein the first periodicity and the second periodicity are the same.

59. The network node (16) of any of Claims 50-58, wherein, when beam reporting is triggered for both the first and second CSI report configurations, only a single UE-initiated beam report associated to one of the first and second CSI report configurations is transmitted on the second uplink channel.

60. The network node (16) of Claim 59, wherein the single UE initiated beam report corresponds to one of the first and second CSI report configurations with a high priority.

61. The network node (16) of any of Claims 50-60, wherein each of the first and the second CSI report configurations further comprises a same carrier index.

62. The network node (16) of Claim 61, wherein the processing circuitry is configured to indicate to the UE (22) a set of dedicated physical uplink shared channel, PUSCH, resources for transmitting the UE-initiated beam report.

Images