WO2021147149A1

WO2021147149A1 - Collision resolution between channel state information reports

Info

Publication number: WO2021147149A1
Application number: PCT/CN2020/078531
Authority: WO
Inventors: Yi Huang; Wei Yang; Seyedkianoush HOSSEINI; Yu Zhang; Wanshi Chen; Peter Gaal; Krishna Kiran Mukkavilli
Original assignee: Qualcomm Inc
Current assignee: Qualcomm Inc
Priority date: 2020-01-23
Filing date: 2020-03-10
Publication date: 2021-07-29
Anticipated expiration: 2022-07-23
Also published as: WO2021147058A1

Abstract

Disclosed are techniques for resolving collisions between multiple channel state information (CSI) reports triggered at the user equipment.

Description

COLLISION RESOLUTION BETWEEN CHANNEL STATE INFORMATION REPORTS

CROSS-REFERENCE TO RELATED APPLICATION

The present Application for Patent claims the benefit of PCT Application No. PCT/CN2020/073941 entitled “COLLISION RESOLUTION BETWEEN CHANNEL STATE INFORMATION REPORTS, ” filed January 23, 2020, assigned to the assignee hereof, and expressly incorporated herein by reference in its entirety.

TECHNICAL FIELD

Various aspects described herein generally relate to wireless communication systems, and more particularly to collision resolution between channel state information reports.

BACKGROUND

Wireless communication systems have developed through various generations, including a first-generation analog wireless phone service (1G) , a second-generation (2G) digital wireless phone service (including interim 2.5G and 2.75G networks) , a third-generation (3G) high speed data, Internet-capable wireless service and a fourth-generation (4G) service (e.g., Long Term Evolution (LTE) or WiMax) . There are presently many different types of wireless communication systems in use, including Cellular and Personal Communications Service (PCS) systems. Examples of known cellular systems include the cellular Analog Advanced Mobile Phone System (AMPS) , and digital cellular systems based on Code Division Multiple Access (CDMA) , Frequency Division Multiple Access (FDMA) , Time Division Multiple Access (TDMA) , the Global System for Mobile access (GSM) variation of TDMA, etc.

A fifth generation (5G) mobile standard calls for higher data transfer speeds, greater numbers of connections, and better coverage, among other improvements. The 5G standard, according to the Next Generation Mobile Networks Alliance, is designed to provide data rates of several tens of megabits per second to each of tens of thousands of users, with 1 gigabit per second to tens of workers on an office floor. Several hundreds of thousands of simultaneous connections should be supported in order to support large sensor deployments. Consequently, the spectral efficiency of 5G mobile communications should be significantly enhanced compared to the current 4G standard. Furthermore, signaling efficiencies should be enhanced and latency should be substantially reduced compared to current standards.

Some wireless communication networks, such as 5G, support operation at very high and even extremely-high frequency (EHF) bands, such as millimeter wave (mmW) frequency bands (generally, wavelengths of 1mm to 10mm, or 30 to 300GHz) . These extremely high frequencies may support very high throughput such as up to six gigabits per second (Gbps) .

SUMMARY

This summary identifies features of some example aspects, and is not an exclusive or exhaustive description of the disclosed subject matter. Whether features or aspects are included in, or omitted from this summary is not intended as indicative of relative importance of such features. Additional features and aspects are described, and will become apparent to persons skilled in the art upon reading the following detailed description and viewing the drawings that form a part thereof.

An exemplary method performed by a user equipment (UE) is disclosed. The method may comprise receiving, from a network node, or more first scheduling information triggering the UE to provide corresponding one or more first channel state information (CSI) reports to the network node on corresponding one or more first CSI report resource sets. Each first CSI report resource set may comprise one or more resources of an uplink (UL) control channel. The one or more first scheduling information may comprise a downlink (DL) grant scheduling information notifying the UE of scheduling of resources of a DL data channel. The first CSI report corresponding to the DL grant scheduling information may be a DL grant triggered aperiodic CSI (A-CSI) report, and the first CSI report resource set corresponding to the DL grant scheduling information may be a DL grant A-CSI report resource set. The method may also comprise receiving, from the network node, one or more second scheduling information triggering the UE to provide corresponding one or more second CSI reports to the network node on corresponding one or more second CSI report resource sets. Each second CSI report resource set may comprise one or more resources of a UL data channel. The one or more second scheduling information may comprise a UL grant scheduling information notifying the UE of scheduling of resources of a UL data channel. The second CSI report corresponding to the UL grant scheduling information may be a UL grant triggered A-CSI report, and the second CSI report resource set corresponding to the UL grant scheduling information may be a UL grant A-CSI report resource set. The method may further comprise resolving one or more collisions among the one or more first CSI reports and the one or more second CSI reports so as to select one of the DL grant A-CSI report resource set and the second A-CSI report resource set as a selected CSI report resource set. Two CSI reports may collide when a time occupancy of CSI report resource sets corresponding to the two CSI reports overlap in at least one symbol. The method may yet further comprise providing a report set to the network node on the selected CSI report resource set. The report set may comprise one or both of the DL grant triggered A-CSI report and the UL grant triggered A-CSI report.

An exemplary user equipment (UE) is disclosed. The UE may comprise a transceiver circuitry, a memory circuitry, and a processor circuitry. The transceiver circuitry, the memory circuitry, and the processor circuitry may be configured to receive, from a network node, or more first scheduling information triggering the UE to provide corresponding one or more first channel state information (CSI) reports to the network node on corresponding one or more first CSI report resource sets. Each first CSI report resource set may comprise one or more resources of an uplink (UL) control channel. The one or more first scheduling information may comprise a downlink (DL) grant scheduling information notifying the UE of scheduling of resources of a DL data channel. The first CSI report corresponding to the DL grant scheduling information may be a DL grant triggered aperiodic CSI (A-CSI) report, and the first CSI report resource set corresponding to the DL grant scheduling information may be a DL grant A-CSI report resource set. The transceiver circuitry, the memory circuitry, and the processor circuitry may also be configured to receive, from the network node, one or more second scheduling information triggering the UE to provide corresponding one or more second CSI reports to the network node on corresponding one or more second CSI report resource sets. Each second CSI report resource set may comprise one or more resources of a UL data channel. The one or more second scheduling information may comprise a UL grant scheduling information notifying the UE of scheduling of resources of a UL data channel. The second CSI report corresponding to the UL grant scheduling information may be a UL grant triggered A-CSI report, and the second CSI report resource set corresponding to the UL grant scheduling information may be a UL grant A-CSI report resource set. The transceiver circuitry, the memory circuitry, and the processor circuitry may further be configured to resolve one or more collisions among the one or more first CSI reports and the one or more second CSI reports so as to select one of the DL grant A-CSI report resource set and the second A-CSI report resource set as a selected CSI report resource set. Two CSI reports may collide when a time occupancy of CSI report resource sets corresponding to the two CSI reports overlap in at least one symbol. The transceiver circuitry, the memory circuitry, and the processor circuitry may yet further be configured to provide a report set to the network node on the selected CSI report resource set. The report set may comprise one or both of the DL grant triggered A-CSI report and the UL grant triggered A-CSI report.

Another exemplary user equipment (UE) is disclosed. The UE may comprise means for receiving, from a network node, or more first scheduling information triggering the UE to provide corresponding one or more first channel state information (CSI) reports to the network node on corresponding one or more first CSI report resource sets. Each first CSI report resource set may comprise one or more resources of an uplink (UL) control channel. The one or more first scheduling information may comprise a downlink (DL) grant scheduling information notifying the UE of scheduling of resources of a DL data channel. The first CSI report corresponding to the DL grant scheduling information may be a DL grant triggered aperiodic CSI (A-CSI) report, and the first CSI report resource set corresponding to the DL grant scheduling information may be a DL grant A-CSI report resource set. The UE may also comprise means for receiving, from the network node, one or more second scheduling information triggering the UE to provide corresponding one or more second CSI reports to the network node on corresponding one or more second CSI report resource sets. Each second CSI report resource set may comprise one or more resources of a UL data channel. The one or more second scheduling information may comprise a UL grant scheduling information notifying the UE of scheduling of resources of a UL data channel. The second CSI report corresponding to the UL grant scheduling information may be a UL grant triggered A-CSI report, and the second CSI report resource set corresponding to the UL grant scheduling information may be a UL grant A-CSI report resource set. The UE may further comprise means for resolving one or more collisions among the one or more first CSI reports and the one or more second CSI reports so as to select one of the DL grant A-CSI report resource set and the second A-CSI report resource set as a selected CSI report resource set. Two CSI reports may collide when a time occupancy of CSI report resource sets corresponding to the two CSI reports overlap in at least one symbol. The UE may yet further comprise means for providing a report set to the network node on the selected CSI report resource set. The report set may comprise one or both of the DL grant triggered A-CSI report and the UL grant triggered A-CSI report.

An exemplary non-transitory computer-readable medium storing computer-executable instructions for a user equipment (UE) is disclosed. The computer-executable instructions may comprise one or more instructions causing the UE to receive, from a network node, or more first scheduling information triggering the UE to provide corresponding one or more first channel state information (CSI) reports to the network node on corresponding one or more first CSI report resource sets. Each first CSI report resource set may comprise one or more resources of an uplink (UL) control channel. The one or more first scheduling information may comprise a downlink (DL) grant scheduling information notifying the UE of scheduling of resources of a DL data channel. The first CSI report corresponding to the DL grant scheduling information may be a DL grant triggered aperiodic CSI (A-CSI) report, and the first CSI report resource set corresponding to the DL grant scheduling information may be a DL grant A-CSI report resource set. The computer-executable instructions may also comprise one or more instructions causing the UE to receive, from the network node, one or more second scheduling information triggering the UE to provide corresponding one or more second CSI reports to the network node on corresponding one or more second CSI report resource sets. Each second CSI report resource set may comprise one or more resources of a UL data channel. The one or more second scheduling information may comprise a UL grant scheduling information notifying the UE of scheduling of resources of a UL data channel. The second CSI report corresponding to the UL grant scheduling information may be a UL grant triggered A-CSI report, and the second CSI report resource set corresponding to the UL grant scheduling information may be a UL grant A-CSI report resource set. The computer-executable instructions may further comprise one or more instructions causing the UE to resolve one or more collisions among the one or more first CSI reports and the one or more second CSI reports so as to select one of the DL grant A-CSI report resource set and the second A-CSI report resource set as a selected CSI report resource set. Two CSI reports may collide when a time occupancy of CSI report resource sets corresponding to the two CSI reports overlap in at least one symbol. The computer-executable instructions may yet further comprise one or more instructions causing the UE to provide a report set to the network node on the selected CSI report resource set. The report set may comprise one or both of the DL grant triggered A-CSI report and the UL grant triggered A-CSI report.

Other objects and advantages associated with the aspects disclosed herein will be apparent to those skilled in the art based on the accompanying drawings and detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are presented to aid in the description of examples of one or more aspects of the disclosed subject matter and are provided solely for illustration of the examples and not limitation thereof:

FIG. 1 illustrates the signals exchanged between nodes for the initial access procedure;

FIG. 2 illustrates an exemplary network node and an exemplary user equipment, according to various aspects;

FIGs. 3A-15B illustrates flow charts of exemplary methods performed by a user equipment, according to various aspects;

FIG. 16 illustrates a simplified block diagram of an example user equipment apparatus configured to perform random access with a network node, according to various aspects.

DETAILED DESCRIPTION

Aspects of the subject matter are provided in the following description and related drawings directed to specific examples of the disclosed subject matter. Alternates may be devised without departing from the scope of the disclosed subject matter. Additionally, well-known elements will not be described in detail or will be omitted so as not to obscure the relevant details.

The word “exemplary” is used herein to mean “serving as an example, instance, or illustration. ” Any aspect described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects. Likewise, the term “aspects” does not require that all aspects include the discussed feature, advantage, or mode of operation.

The terminology used herein describes particular aspects only and should not be construed to limit any aspects disclosed 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. Those skilled in the art will further understand that the terms “comprises, ” “comprising, ” “includes, ” and/or “including, ” as 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.

Further, various aspects may be described in terms of sequences of actions to be performed by, for example, elements of a computing device. Those skilled in the art will recognize that various actions described herein can be performed by specific circuits (e.g., an application specific integrated circuit (ASIC) ) , by program instructions being executed by one or more processors, or by a combination of both. Additionally, these sequences of actions described herein can be considered to be embodied entirely within any form of non-transitory computer-readable medium having stored thereon a corresponding set of computer instructions that upon execution would cause an associated processor to perform the functionality described herein. Thus, the various aspects described herein may be embodied in a number of different forms, all of which have been contemplated to be within the scope of the claimed subject matter. In addition, for each of the aspects described herein, the corresponding form of any such aspects may be described herein as, for example, “logic configured to” and/or other structural components configured to perform the described action.

As used herein, the terms “user equipment” (UE) and “base station” are not intended to be specific or otherwise limited to any particular Radio Access Technology (RAT) , unless otherwise noted. In general, such UEs may be any wireless communication device (e.g., a mobile phone, router, tablet computer, laptop computer, tracking device, Internet of Things (IoT) device, etc. ) used by a user to communicate over a wireless communications network. A UE may be mobile or may (e.g., at certain times) be stationary, and may communicate with a Radio Access Network (RAN) . As used herein, the term “UE” may be referred to interchangeably as an “access terminal” or “AT, ” a “client device, ” a “wireless device, ” a “subscriber device, ” a “subscriber terminal, ” a “subscriber station, ” a “user terminal” or UT, a “mobile terminal, ” a “mobile station, ” or variations thereof. Generally, UEs can communicate with a core network via a RAN, and through the core network the UEs can be connected with external networks such as the Internet and with other UEs. Of course, other mechanisms of connecting to the core network and/or the Internet are also possible for the UEs, such as over wired access networks, WiFi networks (e.g., based on Institute of Electrical and Electronics Engineers (IEEE) 802.11, etc. ) and so on.

A base station may operate according to one of several RATs in communication with UEs depending on the network in which it is deployed, and may be alternatively referred to as an Access Point (AP) , a Network Node, a NodeB, an evolved NodeB (eNB) , a general Node B (gNodeB, gNB) , etc. In addition, in some systems a base station may provide purely edge node signaling functions while in other systems it may provide additional control and/or network management functions.

UEs can be embodied by any of a number of types of devices including but not limited to printed circuit (PC) cards, compact flash devices, external or internal modems, wireless or wireline phones, smartphones, tablets, tracking devices, asset tags, and so on. A communication link through which UEs can send signals to a RAN is called an uplink channel (e.g., a reverse traffic channel, a reverse control channel, an access channel, etc. ) . A communication link through which the RAN can send signals to UEs is called a downlink or forward link channel (e.g., a paging channel, a control channel, a broadcast channel, a forward traffic channel, etc. ) . As used herein the term traffic channel (TCH) can refer to either an uplink /reverse or downlink /forward traffic channel.

As mentioned above, one way to achieve high data rates is to operate in very high frequencies such as in millimeter waves (mmW) . One disadvantage of radio waves with such high frequencies is high path loss, which in turn means that the operation range is relatively short. Beamforming can compensate by directing the transmission energy as much as possible towards the intended receiver. Therefore, beamforming is a form of directional communication. Such directional links can involve an accurate alignment of a beam link pair (BLP) , i.e., or transmitted and received beams. Beam management operations are included in 5G NR to enable such an alignment.

Transmit “beamforming” is a technique for focusing a radio frequency (RF) signal in a specific direction. Traditionally, when a network node (e.g., a gNodeB or gNB) broadcasts an RF signal, it broadcasts the signal in all directions (omni-directionally) . With transmit beamforming, the network node determines where a given target device (e.g., UE) is located (relative to the transmitting network node) and projects a stronger downlink RF signal in that specific direction, thereby providing a faster (in terms of data rate) and stronger RF signal for the receiving device (s) . To change the directionality of the RF signal when transmitting, a network node can control the phase and relative amplitude of the RF signal at each of the one or more transmitters that are broadcasting the RF signal. For example, a network node may use an array of antennas (referred to as a “phased array” or an “antenna array” ) that creates a beam of RF waves that can be “steered” to point in different directions, without actually moving the antennas. Specifically, the RF current from the transmitter is fed to the individual antennas with the correct phase relationship so that the radio waves from the separate antennas add together to increase the radiation in a desired direction, while cancelling to suppress radiation in undesired directions.

In receive beamforming, the receiver uses a receive beam to amplify RF signals detected on a given channel. For example, the receiver can increase the gain setting and/or adjust the phase setting of an array of antennas in a particular direction to amplify (e.g., to increase the gain level of) the RF signals received from that direction. Thus, when a receiver is said to beamform in a certain direction, it means the beam gain in that direction is high relative to the beam gain along other directions, or the beam gain in that direction is the highest compared to the beam gain in that direction of all other receive beams available to the receiver. This results in a stronger received signal strength (e.g., reference signal received power (RSRP) , SINR, etc. ) of the RF signals received from that direction.

Transmit beams may be quasi-collocated (QCLed) , meaning that they appear to the receiver as having the same parameters, regardless of whether or not the transmitting antennas themselves are physically collocated. In other words, the receiver may derive certain parameters about a second reference signal on a second beam from information about a source reference signal on a source beam. These parameters include any one or more of Doppler spread, Doppler shift, average gain, average delay, delay spread, and, when applicable, spatial Rx parameters.

FIG. 1 illustrates the signals exchanged between the gNB 110 (more generally, network node) and the UE 150 for the initial access procedure. To enable initial access, the gNB 110 may periodically broadcast some minimum system information (e.g., system information block (SIB) , master information block (MIB) ) in synchronization signal blocks (SSBs) . Each SSB carries the primary synchronization signal (PSS) , secondary synchronization signal (SSS) , and physical broadcast channel (PBCH) .

The gNB 110 may perform beam sweeping to transmit the SSBs. Beam sweeping is a way of covering a spatial area with a set of beams according to predefined intervals and directions. The gNB 110 may transmit the SSBs in synchronization signal (SS) bursts that periodically repeat. The gNB 110 may also periodically transmit remaining minimum system information (RMSI) and other system information (OSI) carried on the physical data shared channel (PDSCH) . The RMSIs inform the UE 150 to the resources that can be used to perform the random access.

Regarding the SSBs, the gNB 110 may transmit multiple SSBs within one SS burst. An SSB burst set defines a window (e.g., 5 ms) within which a number of SSBs are transmitted. Each SSB within one SS burst can be uniquely identified by an SSB index. Also, each SSB within one SS burst may be transmitted in a specific downlink (DL) beam radiated in a particular direction. That is, there may be a correspondence between the SSB index and the DL beam used to transmit the SSB. The SS burst may repeat in SSB periodicity (5/10/20/40/80/160 ms) .

The UE 150 can receive one or more of the DL beams transmitted from the gNB 110 and select the best one. For example, the DL beam with the highest received power may be selected. Typically, this is the DL beam that is transmitted in the direction of the UE 150 from the gNB 110. Since, in one implementation, the SSBs uniquely correspond to the DL beams, in such an implementation, selecting a DL beam effectively selects the SSB. After the DL beam selection, the UE 150 may transmit in an uplink (UL) beam a physical random access channel (PRACH) preamble to the gNB 110. The PRACH preamble, also referred to as Msg1, is based on the SSB so that the gNB 110 is informed of the DL beam selected by the UE 150.

In response to receiving the PRACH preamble, the gNB 110 may respond with a random access response (RAR) message, also referred to as Msg2. Upon receiving the RAR and successful decoding thereof, the UE 150 may send a radio resource control (RRC) connection request, also referred to as Msg3, to the gNB 110. The gNB 110 may respond with an RRC connection setup, also referred to as Msg4.

Thereafter, to facilitate communication between the gNB 110 and the UE 150, the gNB 110 may transmit downlink control information (DCI) on physical downlink control channel (PDCCH) to the UE 150. The DCIs may notify the UE 150 of grant or schedule of resources of PDSCH for use by the UE 150 to receive DL data from the gNB 110 (e.g., Format 0_1) , or of resources of physical uplink shared channel (PUSCH) for use by the UE 150 to send UL data to the gNB 110 (e.g., Format 1_1) .

From time to time, the gNB 110 may request or trigger a channel state information (CSI) report from the UE 150 in DCIs, and the UE 150 may respond by measuring and sending the CSI report based on the measurement. The CSI report may be sent on physical uplink control channel (PUCCH) or on PUSCH, depending on the type of CSI report that is triggered.

In NR Release 15 and 16 (Rel-15/16) of Third Generation Partnership Project (3GPP ^TM) , there are four types of CSI reports that the UE may be configured to send (see e.g., Technical Specification “3GPP TS 38.214 V15.7.0 (2019-09) ” , section 5.2.5) :

● A-CSI on PUSCH –aperiodic CSI report carried on PUSCH;

● SP-CSI on PUSCH –semi-persistent CSI (SP-CSI) report carried on PUSCH;

● SP-CSI on PUCCH –semi-persistent CSI report carried on PUCCH; and

● P-CSI on PUCCH –periodic CSI (P-CSI) report carried on PUCCH.

It can be that when multiple CSI reports are triggered, two or more of them may collide. According to 3GPP, two CSI reports collide “if the time occupancy of the physical channels scheduled to carry the CSI reports overlap in at least one OFDM symbol and are transmitted on the same carrier. ” Technical Specification “3GPP TS 38.214 V15.7.0 (2019-09) ” , section 5.2.5.3GPP also provides rules to resolve conflicts between colliding CSI reports.

The four CSI reports types identified above are triggered only through uplink grants, e.g., in DCIs conforming to DCI Format 0_1. But in one or more aspects, it is proposed to expand the types of CSI reports. For example, the following new type of CSI report may be defined:

● A-CSI on PUCCH –aperiodic CSI report carried on PUCCH.

In an aspect, the new CSI report type may be triggered a downlink grant, e.g., in DCIs conforming to DCI Format 1_1 or even DCI Format 1_0. That is, even though the downlink grant triggers the new CSI report type, the corresponding CSI report is provided on the PUCCH. It is also proposed to provide techniques to resolve collisions between the new CSI report type and existing CSI reports.

Before proceeding further, the following should be noted. It is contemplated that in an alternative, the new CSI report type may be triggered on an uplink grant (e.g., in DCIs conforming to DCI Format 0_1) . But in this disclosure, techniques to resolve collisions will be described in detail assuming that the new CSI report type is triggered through a downlink grant. However, some or all of the described techniques can be readily applied in a relatively straightforward manner if the new CSI report type is triggered through an uplink grant.

According to various aspects, FIG. 2 illustrates an exemplary network node 210 in communication with an exemplary user equipment (UE) 250. A base station such as the gNB 110 may be an example of the network node 210, and the UE 150 may be an example of the UE 250. At the network node 210, Internet Protocol (IP) packets may be provided to a controller/processor 275. The controller/processor 275 may implement functionality for a radio resource control (RRC) layer, a packet data convergence protocol (PDCP) layer, a radio link control (RLC) layer, and a medium access control (MAC) layer. The controller/processor 275 may provide RRC layer functionality associated with broadcasting of system information (e.g., MIB, SIBs) , RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release) , inter-RAT mobility, and measurement configuration for CSI measurement reporting; PDCP layer functionality associated with header compression/decompression, security (ciphering, deciphering, integrity protection, integrity verification) , and handover support functions; RLC layer functionality associated with the transfer of upper layer packet data units (PDUs) , error correction through ARQ, concatenation, segmentation, and reassembly of RLC service data units (SDUs) , re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, scheduling information reporting, error correction, priority handling, and logical channel prioritization.

The transmit (TX) processor 216 and the receive (RX) processor 270 may implement Layer-1 functionality associated with various signal processing functions. Layer-1, which includes a physical (PHY) layer, may include error detection on the transport channels, forward error correction (FEC) coding/decoding of the transport channels, interleaving, rate matching, mapping onto physical channels, modulation/demodulation of physical channels, and multiple-input and multiple-output (MIMO) antenna processing. The TX processor 216 may handle mapping to signal constellations based on various modulation schemes (e.g., binary phase-shift keying (BPSK) , quadrature phase-shift keying (QPSK) , M-phase-shift keying (M-PSK) , M-quadrature amplitude modulation (M-QAM) ) . The coded and modulated symbols may then be split into parallel streams. Each stream may then be mapped to an orthogonal frequency division multiplexing (OFDM) subcarrier, multiplexed with a reference signal (e.g., pilot) in the time and/or frequency domain, and then combined together using an Inverse Fast Fourier Transform (IFFT) to produce a physical channel carrying a time domain OFDM symbol stream. The OFDM stream is spatially precoded to produce multiple spatial streams. Channel estimates from a channel estimator 274 may be used to determine the coding and modulation scheme, as well as for spatial processing. The channel estimate may be derived from a reference signal and/or channel condition feedback transmitted by the UE 250. Each spatial stream may then be provided to one or more different antennas 220 via a separate transmitter 218a. Each transmitter 218a may modulate an RF carrier with a respective spatial stream for transmission.

At the UE 250, each receiver 254a may receive a signal through its respective antenna 252. Each receiver 254a may recover information modulated onto an RF carrier and may provide the information to the RX processor 256. The TX processor 268 and the RX processor 256 may implement Layer-1 functionality associated with various signal processing functions. The RX processor 256 may perform spatial processing on the information to recover any spatial streams destined for the UE 250. If multiple spatial streams are destined for the UE 250, they may be combined by the RX processor 256 into a single OFDM symbol stream. The RX processor 256 may then convert the OFDM symbol stream from the time-domain to the frequency domain using a Fast Fourier Transform (FFT) . The frequency domain signal may comprise a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, and the reference signal, may be recovered and demodulated by determining the most likely signal constellation points transmitted by the network node 210. These soft decisions may be based on channel estimates computed by the channel estimator 258. The soft decisions may then decoded and de-interleaved to recover the data and control signals that were originally transmitted by the network node 210 on the physical channel. The data and control signals may then be provided to the controller/processor 259, which implements Layer-3 and Layer-2 functionality.

The controller/processor 259 can be associated with a memory 260 that stores program codes and data. The memory 260 may be referred to as a computer-readable medium. In the UL, the controller/processor 259 may provide demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, and control signal processing to recover IP packets from the core network. The controller/processor 259 may also be responsible for error detection.

Similar to the functionality described in connection with the transmission by the network node 210, the controller/processor 259 may provide RRC layer functionality associated with system information (e.g., MIB, SIBs) acquisition, RRC connections, and measurement reporting; PDCP layer functionality associated with header compression/decompression, and security (ciphering, deciphering, integrity protection, integrity verification) ; RLC layer functionality associated with the transfer of upper layer PDUs, error correction through ARQ, concatenation, segmentation, and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; and MAC layer functionality associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.

Channel estimates derived by the channel estimator 258 from a reference signal or feedback transmitted by the network node 210 may be used by the TX processor 268 to select the appropriate coding and modulation schemes, and to facilitate spatial processing. The channel estimates may be used as a basis of the CSI report provided to the network node 210. The spatial streams generated by the TX processor 268 may be provided to different antenna 252 via separate transmitters 254b. Each transmitter 254b may modulate an RF carrier with a respective spatial stream for transmission.

The UL transmission may be processed at the network node 210 in a manner similar to that described in connection with the receiver function at the UE 250. Each receiver 218b may receive a signal through its respective antenna 220. Each receiver 218b may recover information modulated onto an RF carrier and may provide the information to a RX processor 270.

The controller/processor 275 can be associated with a memory 276 that stores program codes and data. The memory 276 may be referred to as a computer-readable medium. In the UL, the controller/processor 275 may provide demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover IP packets from the UE 250. IP packets from the controller/processor 275 may be provided to the core network. The controller/processor 275 may also be responsible for error detection.

In the UE 250, the transmitter 254b and the receiver 254a may together form a transceiver 254. In the network node 210, the transmitter 218a and the receiver 218b may together form a transceiver 218.

The network node 210 may be configured to trigger CSI reports though DCIs granting DL and UL resources to the UE 250, and the UE 250 may be configured to resolve collisions between CSI reports triggered by the network node 210. In an aspect, the types of CSI reports may be generalized as follows:

● A-CSI on uplink control channel (e.g., PUCCH) ;

● A-CSI on uplink shared channel (e.g., PUSCH) ;

● SP-CSI on uplink shared channel;

● SP-CSI on uplink control channel;

● P-CSI on uplink control channel.

FIGs. 3A-3D illustrate an exemplary method 300 performed by a user equipment (e.g., UE 150, 250) configured to resolve CSI report collisions. At block 310, the UE may receive a first scheduling information from a network node, such as base station, NodeB, gNodeB, gNB, etc. The first scheduling information may notify the UE of scheduling of resources of a DL data channel such as PDSCH. For example, the first scheduling information may be a DCI informing the UE of resources of the DL data channel for the UE to receive DL data from the network node. In this instance, the first scheduling information may also be referred to as a DL grant.

The first scheduling information may also trigger the UE to provide a first CSI report to the network node to be carried on one or more resources of a UL control channel such as PUCCH. For example, the first CSI report may be an A-CSI report. For ease of reference, the one or more resources of the UL control channel configured to carry the first CSI report (e.g., A-CSI report) to the network node may be referred to as the first CSI report resource set.

At block 320, the UE may receive a second scheduling information from the network node. The second scheduling information may trigger the UE to provide a second CSI report to the network node to be carried on one or more resources of a UL channel. The UL channel may be UL control channel (e.g., PUCCH) and/or UL data channel (e.g., PUSCH) . The second CSI report may be any of A-CSI (on UL shared channel) , SP-CSI (on UL shared or control channel) , or P-CSI (on UL control channel) .

For ease of reference, the one or more resources of the UL channel configured to carry the second CSI report to the network node may be referred to as the second CSI report resource set. That is, the second CSI report resource set may comprise resources of the UL control channel (e.g., PUCCH) and/or resources of the UL data channel (e.g., PUSCH) .

If the second CSI report resource set comprises resources of the UL control channel (e.g., PUCCH) , then it may be said that the first CSI resource set comprises one or more first resources of the UL control channel and the second CSI resource set comprises one or more second resources of the UL control channel. Note that some, none, or all of the first resources may be the same as the second resources of the UL control channel.

The second scheduling information may be different depending on the type of the second CSI report. In one aspect, the second scheduling information may notify the UE of scheduling of resources of a UL data channel such as PUSCH. For example, the second scheduling information may be a DCI informing the UE of resources of the UL data channel for the UE to send UL data to the network node. In this instance, the second scheduling information may also be referred to as a UL grant. Such UL grant may be used to trigger A-CSI report or SP-CSI report on UL shared channel.

In another aspect, the second scheduling information may be a control element (e.g., MAC-CE) that activates/deactivates CSI reporting. For example, SP-CSI report on UL control channel may be activated or otherwise triggered through the UE receiving the control element. In yet another aspect, the second scheduling information may be a higher layer configuration. For example, the UE may be configured, e.g., through higher layer signaling, with P-CSI report on UL control channel.

At block 325, the UE may determine whether first CSI report collides with the second CSI report. Two CSI reports may be deemed to collide when a time occupancy of CSI report resource sets corresponding to the two CSI reports overlap in at least one symbol. It may be assumed that the two CSI reports scheduled to be carried on the same carrier.

It should be noted that in an aspect, symbol overlap may be sufficient to determine that the two CSI reports collide. That is, if at least one resource of the first CSI report resource set (scheduled to carry the first CSI report) overlaps in time with at least one resource of the second CSI report resource set (scheduled to carry the second CSI report) , then the first and second CSI reports may be deemed to collide, e.g., when the first and second CSI reports are scheduled to be transmitted on the same carrier.

In another aspect, the definition of collision may also include condition of overlap in frequency in addition to overlap in time. However, unless stated otherwise, the broader definition of collision (overlap in time) will be assumed in this disclosure. Nonetheless, it will be readily apparent that some or all of the described techniques to resolve collision will be applicable regardless of the definition of collision.

If the first and second CSI reports do collide ( “Y” branch from 325) , then at block 330, the UE may resolve the collision so as to select one of the first and second CSI report resource sets as a selected CSI report resource set. Then at block 340, the UE may provide the first and/or the second CSI report to the network node on the selected CSI report resource set. For ease of reference, a report set will be used to indicate the CSI report or reports provided to the network, i.e., the report set may comprise at least one of the first CSI report and the second CSI report.

Note that blocks 330 and 340 represent two components –selecting a CSI report resource set (block 330) , and determining the CSI report or reports that will be sent on the selected CSI report resource set (block 340) . The two components may be independent, at least somewhat, from each other. That is, it may be possible to provide the first CSI report on the first CSI report resource set or on the second CSI report resource set. Similarly, it may be possible to provide the second CSI report on the first CSI report resource set or on the second CSI report resource set. Further, it may be possible to provide the both the first and second CSI reports on the first CSI report resource set or on the second CSI report resource set.

When the first and second CSI reports do collide, whether only one or both of the first and second CSI reports are provided to the network and on which CSI report resource set may depend on the type of the second CSI report. FIG. 4 illustrates an exemplary process performed by the UE to implement block 340. In FIG. 4, it is assumed that the second CSI report is a report other than A-CSI report on UL shared channel (e.g., the second CSI report may be SP-CSI report on UL shared channel, SP-CSI report on UL control channel, or P-CSI on UL control channel) . At block 410, the UE may provide at least the first CSI report (e.g., the A-CSI report) on the selected CSI report resource set. For example, the second CSI report may be dropped. In another example, the first and second CSI reports may be multiplexed on the selected CSI report resource set (assuming sufficient payload) .

FIG. 5 illustrates an exemplary process performed by the UE to implement

blocks

330 and 340. In FIG. 5, like in FIG. 4, it is assumed that the second CSI report is a report other than A-CSI report on UL shared channel (e.g., the second CSI report may be SP-CSI report or P-CSI report) . FIG. 5 reflects an aspect in which the first CSI report wins outright when the second CSI report is not another A-CSI report. At block 510, the UE may implement block 330 by selecting the first CSI report resource set as the selected CSI report resource set. At block 520, the UE may implement block 340 by providing only the first CSI report to the network node on the selected CSI report resource set, i.e., on the first CSI report resource set. In other words, the second CSI report may be dropped.

FIG. 6 illustrates another exemplary process performed by the UE to implement

blocks

330 and 340. In FIG. 6, it is assumed that the second CSI report is a report other than A-CSI report and that the second CSI report resource set are also resources of the UL control channel (e.g., PUCCH) . For example, the second CSI report may be SP-CSI report on UL control channel or a P-CSI on UL control channel. For ease of reference, in this instance, the first CSI report resource set may be said to comprise one or more first resources of the UL control channel, and the second CSI report resource set may be said to comprise one or more second resources of the UL control channel.

FIG. 6 reflects an aspect in which the first CSI report is prioritized. But nonetheless, an attempt is made to provide both CSI reports to the network node. At block 610, the UE may implement block 330 by selecting the first or the second CSI report resource set, based on one or more selection rules, as the selected CSI report resource set. Following are some (not necessarily exhaustive) example selection rules:

● Select CSI report resource set with larger payload;

● Select CSI report resource set with earlier starting OFDM symbol;

● Select CSI report resource set with later starting OFDM symbol;

● Always select first CSI report resource set;

● Always select second CSI report resource set.

The UE may implement block 340 through

blocks

620, 630, and 640. At block 620, the UE may determine whether the payload of the selected CSI report resource set is sufficient to carry both the first CSI report and the CSI report. If it is determined that the selected CSI report resource set is sufficient ( “Y” branch from block 620) , then at block 630, the UE may multiplex the first CSI report and the second CSI report to the network node on the selected CSI report resource set. Otherwise ( “N” branch from block 620) , at block 640, the UE may provide only the first CSI report to the network node on the selected CSI report resource set.

FIG. 7 illustrates a further exemplary process performed by the UE to implement

blocks

330 and 340. In FIG. 7, it is assumed that the second CSI report is a report other than A-CSI report and that the second CSI report resource set are also resources of the UL data channel (e.g., PUSCH, slightly different from assumption of FIG. 6) . For example, the second CSI report may be SP-CSI report on UL data channel.

FIG. 7 reflects an aspect in which the first CSI report is strictly prioritized, but takes advantage of the uplink data channel resources, which was originally allocated for the second CSI report, to provide the first CSI report. At block 710, the UE may implement block 330 by selecting the second CSI report resource set (e.g., PUSCH resources) as the selected CSI report resource set. Then at block 720, the UE may implement block 340 by providing only the first CSI report to the network node on the selected CSI report resource set, i.e., on the second CSI report resource set. In other words, the second CSI report may be dropped even though the second CSI report resource set is used.

FIG. 8 illustrates a yet further exemplary process performed by the UE to implement

blocks

330 and 340. In FIG. 8, like in FIG. 7, it is assumed that the second CSI report is a report other than A-CSI report and that the second CSI report resource set are also resources of the UL data channel. For example, the second CSI report may be SP-CSI report on UL data channel.

FIG. 8 is different from FIG. 7 in that FIG. 8 reflects an aspect in which both CSI reports are provided on the uplink data channel resources originally allocated for the second CSI report. At block 810, the UE may implement block 330 by selecting the second CSI report resource set as the selected CSI report resource set. Then at block 820, the UE may implement block 340 by multiplexing the first CSI report and the second CSI report to the network node on the selected CSI report resource set, i.e., on the second CSI report resource set. While not shown in FIG. 8, processes similar to

blocks

620, 630, 640 of FIG. 6 may be performed to multiplex when there is sufficient payload. Otherwise, only the first CSI report may be provided.

FIGs. 4-8 reflect situations in which the second CSI report is something other than an A-CSI report. In these situations, the first CSI report may be prioritized such that the first CSI report (A-CSI report) is always provided. However, if the second CSI report is another A-CSI report, then either the first or the second CSI report may be prioritized. In FIGs. 9A-11D, it may be assumed that the second CSI report is another A-CSI report on UL data channel. That is, in these figures, the following may be assumed:

● first CSI report

A-CSI report;

● first CSI report resource set

UL control channel resources;

● second CSI report

another A-CSI report;

● second CSI report resource set

UL data channel resources.

As indicated above, the second scheduling information that triggers the UE to provide the second CSI report may be another DCI that notifies the UE of scheduling of resources of a UL data channel. For example, the second scheduling information may be a DCI informing the UE of resources of the UL data channel for the UE to send UL data to the network node, i.e., the second scheduling information may be a UL grant.

FIGs. 9A-9C illustrate exemplary processes performed by the UE to implement

blocks

330 and 340. In these figures, order in which the first and second scheduling are received at the UE is taken into account. At block 905, the UE may determine whether the first scheduling information (triggering the first CSI report) is received before the second scheduling information (triggering the second CSI report) . For example, the first scheduling information may be a downlink (DL) grant scheduling information that triggers an aperiodic CSI (A-CSI) report, and the second scheduling information may be an uplink (UL) scheduling information that triggers another A-CSI report.

If the first scheduling information is received earlier ( “Y” branch from block 905) , then at block 910, the UE may implement block 330 by selecting the second CSI report resource set as the selected CSI report resource set. At block 920, the UE may implement block 340 by multiplexing the first CSI report and the second CSI report to the network node on the selected CSI report resource set, i.e., on the resources of the UL data channel resources. One rationale is that it is more likely that the UL grant can provide resources for multiplexing.

On the other hand, if the first scheduling information is received later ( “N” branch from block 905) , then the CSI report priorities of the CSI reports may be considered. That is, the first and second CSI reports may respectively be associated with first and second CSI report priorities. In an aspect, indicators used to indicate the priorities of HARQ-ACK and/or PUSCH (e.g., in Rel 16) may be used as the CSI report priorities. In another aspect, the CSI report priorities may be added to the fields of DCIs. Generally, it may be said that the first and second scheduling information respectively include or otherwise indicate the first and second CSI priorities.

In an aspect, if the first scheduling information is received later ( “N” branch from block 905) , then at block 925 of FIG. 9B, the UE may determine whether the first CSI report priority (e.g., DL grant A-CSI report priority) is greater than or a same priority with the second CSI report priority (e.g., UL grant A-CSI report priority) . Note that greater (lesser) “priority” should NOT be confused with higher (lower) “priority value” , e.g., if priority is indicated by a numerical value. In some implementations, a higher priority may be indicated by a lower numerical priority value such that a CSI report with lower CSI report priority numerical value may be given priority over a CSI report with higher CSI report priority numerical value. In this implementation, the CSI report with the lower CSI report priority numerical value would be deemed to have a greater priority over a higher CSI report priority numerical value.

If the first CSI report priority is greater than or the same as the second CSI report priority ( “Y” branch from block 925) (i.e., when the first CSI report priority indicates a greater priority than the second CSI report priority or same priority as the second CSI report priority) , then at block 930, the UE may implement block 330 by selecting the first CSI report resource set as the selected CSI report resource set. At block 940, the UE may implement block 340 by providing only the first CSI report to the network node on the selected CSI report resource set, i.e., on the first CSI report resource set.

If the first CSI report priority is lesser than the second CSI report priority ( “N” branch from block 925) (i.e., when the first CSI report priority indicates a lesser priority than the second CSI report priority) , then at block 950 of FIG. 9C, the UE may implement block 330 by selecting the second CSI report resource set as the selected CSI report resource set. At block 960, the UE may implement block 340 by providing only the second CSI report to the network node on the selected CSI report resource set, i.e., on the second CSI report resource set.

FIGs. 10A-10D illustrate exemplary processes performed by the UE to implement

blocks

330 and 340. In these figures, like in FIGs. 9A-9C, the order in which the first and second scheduling are received at the UE as well as the associated CSI report priorities are considered. At block 1002, the UE may determine whether the first scheduling information (triggering the first CSI report) is received before the second scheduling information (triggering the second CSI report) .

If the first scheduling information is received earlier ( “Y” branch from block 1002) , then at block 1005, the UE may determine whether the first CSI report priority is greater than the second CSI report priority. If so ( “Y” branch from block 1005) , then at block 1010 of FIG. 10B, the UE may implement block 330 by selecting the first CSI report resource set as the selected CSI report resource set. At block 1020, the UE may implement block 340 by providing only the first CSI report to the network node on the selected CSI report resource set, i.e., on the first CSI report resource set.

Referring back to FIG. 10A, if the first CSI report priority is not greater than the second CSI report priority ( “N” branch from block 1005) , then at block 1025, the UE may determine whether the first CSI report priority is less than the second CSI report priority (i.e., determine whether the first CSI report priority indicates a lesser priority than the second CSI report priority) . If so ( “Y” branch from block 1025) , then at block 1030 of FIG. 10C, the UE may implement block 330 by selecting the second CSI report resource set as the selected CSI report resource set. At block 1040, the UE may implement block 340 by providing only the second CSI report to the network node on the selected CSI report resource set, i.e., on the second CSI report resource set.

Referring back to FIG. 10A, if the first CSI report priority is not less than the second CSI report priority ( “N” branch from block 1025) , then the UE may proceed to block 1050 of FIG. 10D. Note that the UE proceeds to block 1050 when the first and second CSI report priorities are the same. At block 1050, the UE may implement block 330 by selecting the second CSI report resource set as the selected CSI report resource set. At block 1060, the UE may implement block 340 by multiplexing the first CSI report and the second CSI report to the network node on the selected CSI report resource set, i.e., on second CSI report resource set.

FIGs. 11A-11E illustrate exemplary processes performed by the UE to implement

blocks

330 and 340. In these figures, the CSI report priorities may be a more significant consideration than the order of receiving the scheduling information. At block 1105, the UE may determine whether the first CSI report priority (e.g., DL grant A-CSI report priority) is greater than the second CSI report priority (e.g., UL grant A-CSI report priority) (i.e., determine whether the first CSI report priority indicates a greater priority than the second CSI report priority) . If so ( “Y” branch from block 1105) , then at block 1110 of FIG. 11B, the UE may implement block 330 by selecting the first CSI report resource set as the selected CSI report resource set. At block 1120, the UE may implement block 340 by providing only the first CSI report to the network node on the selected CSI report resource set, i.e., on the first CSI report resource set.

Referring back to FIG. 11A, if the first CSI report priority is not greater than the second CSI report priority ( “N” branch from block 1105) , then at block 1125, the UE may determine whether the first CSI report priority is less than the second CSI report priority. If so ( “Y” branch from block 1125) , then at block 1130 of FIG. 11C, the UE may implement block 330 by selecting the second CSI report resource set as the selected CSI report resource set. At block 1140, the UE may implement block 340 by providing only the second CSI report to the network node on the selected CSI report resource set, i.e., on the second CSI report resource set.

Referring back to FIG. 11A, if the first CSI report priority is not less than the second CSI report priority ( “N” branch from block 1125) , this means that the first and second CSI report priorities are the same. In one aspect, when the first and second CSI report priorities are the same ( “N” branch from block 1125) , then at block 1150 of FIG. 11D, the UE may implement block 330 by selecting the second CSI report resource set as the selected CSI report resource set. At block 1160, the UE may implement block 340 by multiplexing the first CSI report and the second CSI report to the network node on the selected CSI report resource set, i.e., on second CSI report resource set.

In another aspect, when the first and second CSI report priorities are the same ( “N” branch from block 1125) , the order of the received scheduling may then be taken into account, and prioritize the later received scheduling information. In this regard, at block 1165 of FIG. 11E, the UE may determine whether the first scheduling information is received before the second scheduling information. If so ( “Y” branch from block 1165) , the UE may proceed to perform

blocks

1130 and 1140. If not, ( “N” branch from block 1165) , the UE may proceed to perform

blocks

1110 and 1120.

Referring back to FIG. 3A, it can be that after resolving the collision between the first and second CSI reports, that is, after selecting one of the first or the second CSI report resource set at block 330, the selected CSI report resource set may collide with a resource set of another CSI report. Note that the UE may observe more than three colliding CSI reports. It should be noted that the CSI reports need not mutually collide. For example, CSI report 1 may collide with CSI report 2 and CSI report 2 may collide with CSI report 3. However, CSI report 1 may not necessarily collide with CSI report 3.

It may be that the UE observes three (or more) CSI reports that may collide. Also, it may be that two of those colliding CSI reports are of types that correspond to first and second CSI reports (one is an A-CSI report triggered by a DL grant and another is an A-CSI report triggered by a UL grant) . In an aspect, when the UE makes such an observation, the UE may first resolve the collision between the two triggered A-CSI reports. Thereafter, the UE may resolve the collision (if any) between the winning A-CSI report and the third CSI report. In other words, there can be an ordering by which the UE resolves collisions involving three or more CSI reports.

In this aspect, after block 330 (e.g., after performing any of the

blocks

510, 610, 710, 810, 910, 930, 950, 1010, 1030, 1050, 1110, 1130, 1150) , the UE may proceed to block 350 of FIG. 3B in which the UE may receive a third scheduling information from the network node triggering the UE to provide a third CSI report to the network node to be carried on one or more resources of the UL channel (control and/or data) , which may be referred to as a third CSI report resource set.

At block 355, the UE may determine whether a selected CSI report corresponding to the selected CSI report resource set and the third CSI report collide. That is, if the first CSI report resource set is selected at block 330, then at block 355, the UE may determine whether the first and third CSI report resource sets overlap. On the other hand, if the second CSI report resource set is selected at block 330, then at block 355, the UE may determine whether the second and third CSI report resource sets overlap.

If the selected and third CSI reports do collide ( “Y” branch from 355) , then at block 360, the UE may resolve the collision so as to select one of the selected and third CSI report resource sets as an updated selected CSI report resource set. Then at block 370, the UE may provide an updated report set to the network node on the updated selected CSI report resource set. The updated report set may comprise the selected CSI report and/or the third CSI report.

FIG. 12 illustrates an exemplary processes performed by the UE to implement

blocks

360 and 370. In FIG. 12, it is assumed that the second CSI report resource set (UL data channel resources) is the selected CSI report. In this instance, the third CSI report may be dropped. For example, at block 1210, the UE may implement block 360 by selecting the selected CSI report resource set as the updated selected CSI report resource set. At block 1220, the UE may implement block 370 by providing only the selected CSI report to the network node on the updated selected CSI report resource set.

Referring back to FIG. 3B, if the selected and third CSI reports do not collide ( “N” branch from 355) , then the UE may proceed block 390 of FIG. 3D. At block 390, the UE may provide the selected CSI report to the network node on the selected CSI report resource set. At block 395, the UE may provide the third CSI report to the network node on the third CSI report resource set.

Referring back to FIG. 3A, if the first and second CSI reports do not collide ( “N” branch from 325) , then the UE may proceed block 380 of FIG. 3C. At block 380, the UE may provide the first CSI report to the network node on the first CSI report resource set. At block 385, the UE may provide the second CSI report to the network node on the second CSI report resource set.

FIG. 13 illustrates an exemplary method 1300 performed by a user equipment (e.g., UE 150, 250) configured to resolve CSI report collisions. In particular, FIG. 13 may be viewed as a more detailed example of FIGs. 3B and 12 in which the UE resolves collisions among multiple CSI reports.

At block 1310, the UE may receive one or more first scheduling information. Each first scheduling information may trigger the UE to provide corresponding first CSI report to the network node on corresponding first CSI report resource sets. Each first CSI report resource set may comprise one or more resources of UL control channel. The one or more first scheduling information may comprise a DL grant scheduling information notifying the UE of scheduling of resources of a DL data channel. The first CSI report corresponding to the DL grant scheduling information may be an A-CSI report. Since this corresponding A-CSI report is triggered by the DL grant scheduling information, the corresponding report may also be referred to as DL grant triggered A-CSI report. Further, the first CSI report resource set corresponding to the DL grant scheduling information, which comprise one or more UL control channel (e.g., PUCCH) , may be referred to as DL grant A-CSI report resource set.

At block 1320, the UE may receive one or more second scheduling information. Each second scheduling information may trigger the UE to provide corresponding second CSI report to the network node on corresponding second CSI report resource sets. Each second CSI report resource set may also comprise one or more resources of UL data channel. The one or more second scheduling information may comprise a UL grant scheduling information notifying the UE of scheduling of resources of a UL data channel. The second CSI report corresponding to the DL grant scheduling information may be an A-CSI report. Since this corresponding A-CSI report is triggered by the UL grant scheduling information, the corresponding report may also be referred to as UL grant triggered A-CSI report. Further, the second CSI report resource set corresponding to the UL grant scheduling information, which comprise one or more UL data channel (e.g., PUSCH) , may be referred to as DL grant A-CSI report resource set.

From block 1320, the method 1300 may proceed to block 1330 in which the UE may resolve collisions among the first CSI reports and the second CSI reports. That is, block 1330 assumes that there are collisions among the one or more first CSI reports, among the one or more second CSI reports, and/or between the one or more first CSI reports and the one or more second CSI reports.

Of course, it is possible that there are no collisions among the first CSI reports, among the second CSI reports, and between the first and second CSI reports. In this instance, the UE may provide each first CSI report on corresponding first CSI report resource set and may provide each second CSI report on corresponding second CSI report resource set (not shown) .

At block 1330, UE may resolve collisions among the one or more first CSI reports and the one or more second CSI reports so as to select one of the DL grant A-CSI report resource set and the second A-CSI report resource set as a selected CSI report resource set. That is, the DL grant A-CSI report resource set and/or the second A-CSI report resource set may be prioritized over non A-CSI report resource sets (e.g., prioritized over SP-CSI on uplink shared channel, over SP-CSI on uplink control channel, and over P-CSI on uplink control channel) .

FIG. 14A illustrates an exemplary scenario of implementing block 1330 by the UE. Specifically, it may be assumed that five CSI reports are triggered –three on uplink control channel (s) (e.g., PUCCH) and two on uplink shared channel (s) (e.g., PUSCH) . The uplink and downlink channels may be on a same carrier component (CC) . One of the triggered CSI reports on the uplink control channel may be a DL grant triggered A-CSI report, and one of the triggered CSI reports on the downlink control channel may be a UL grant triggered A-CSI report. The A-CSI reports may be of greater priority than non-A-CSI reports (e.g., greater priority than P or SP-CSI reports) .

FIG. 14A may be generalized as implementing block 1330 through, in order: (1) resolving collisions (if any) among CSI reports on uplink control channel (s) ; (2) resolving collision (if any) between DL and UL triggered A-CSI reports; and (3) resolving collisions (if any) among winning A-CSI report with other CSI reports on uplink data channel (s) .

When implementing (1) , it is seen that in the scenario of FIG. 14A, three CSI reports are triggered on the uplink control channel –DL grant triggered A-CSI, P-CSI, and SP-CSI reports all on PUCCH. To the extent that the A-CSI reports are prioritized, the DL grant triggered A-CSI report resource set will be selected at (1) in this example. Thus, after (1) , the remaining CSI reports for which collision (s) are to be resolved include the DL grant A-CSI report on PUCCH and the triggered CSI reports on the uplink shared channel –the UL grant triggered A-CSI and SP-CSI reports on PUSCH.

In FIG. 14A, when implementing (2) , collision between the DL grant triggered A-CSI report on PUCCH and the UL grant triggered A-CSI on PUSCH is resolved. The selected CSI report may be the report with a higher (greater) priority. In FIG. 14A, it is assumed that the DL grant triggered A-CSI report is prioritized over the UL grant triggered A-CSI report (e.g., DL grant A-CSI report priority is greater than the UL grant A-CSI report priority) . That is, the DL grant triggered A-CSI report may be selected at (2) .

When implementing (3) , collision (s) among the CSI report selected at (2) and triggered CSI reports on the uplink shared channel other than the UL grant triggered A-CSI report may be resolved. In the scenario of FIG. 14A, this implies that collision between the DL grant triggered A-CSI report on PUCCH and the SP-CSI report on PUSCH may be resolved. Assuming that the A-CSI reports are prioritized over non-A-CSI reports, the DL grant triggered A-CSI report may be selected at (3) .

FIG. 14B illustrates an exemplary process performed by the UE to implement block 1330 that generalizes the implementation scenario of FIG. 14A. At block 1410, the UE may resolve one or more collisions among the one or more first CSI reports by selecting the DL grant A-CSI report resource set among the one or more first CSI report resource sets. In short, the DL grant triggered A-CSI report may be prioritized over other first CSI reports that are not A-CSI reports. Since the first CSI reports are over UL control channel, other first CSI reports may comprise one or more P-CSI reports, one or more SP-CSI reports, or a combination thereof.

After block 1410, the UE at block 1420 may resolve a collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report by selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set. There are multitudes of ways to implement block 1420. For example, block 1420 may be implemented through any of the processes illustrated in FIGs. 9A –11E.

After block 1420, the UE at block 1430 may resolve one or more collisions among a selected CSI report and one or more other second CSI reports by selecting the selected CSI report resource set. That is, the selected CSI report may be prioritized over other second CSI reports that are not A-CSI reports. Since the second CSI reports are over UL data channel, other second CSI reports may comprise one or more SP-CSI reports. When the DL grant A-CSI report resource set is selected as the selected CSI report resource set, the DL grant triggered A-CSI report may be the selected CSI report. Conversely, when the UL grant A-CSI report resource set is selected, the UL grant triggered A-CSI report may be the selected CSI report.

FIG. 15A illustrates another exemplary scenario of implementing block 1330 by the UE. The initial scenario is the same as that of FIG. 14A. However, the order is different. FIG. 15A may be generalized as implementing block 1330 through, in order: (1) resolving collision (if any) between DL and UL triggered A-CSI reports; (2) resolving collisions (if any) among winning A-CSI report with other CSI reports on uplink control channel (s) ; and (3) resolving collisions among winning A-CSI report with other CSI reports on uplink data channel (s) .

When implementing (1) , collision between the DL grant triggered A-CSI report on PUCCH and the UL grant triggered A-CSI on PUSCH is resolved. The selected CSI report may be the report with a higher priority. In FIG. 15A, it is again assumed that the DL grant triggered A-CSI report is prioritized over the UL grant triggered A-CSI report. That is, the DL grant triggered A-CSI report may be selected at (1) . Thus, after (1) , the remaining CSI reports for which collision (s) are to be resolved include the DL grant A-CSI report on PUCCH, other CSI report (s) triggered on the uplink control channel (e.g., P-CSI and SP-CSI on PUCCH) and other CSI report (s) on the uplink shared channel (e.g., SP-CSI on PUSCH) .

When implementing (2) , collision (s) among the CSI report selected at (1) and other CSI report (s) triggered on the uplink control channel. That is, in the scenario of FIG. 15A, collisions among the DL grant triggered A-CSI report, the P-CSI report, and the SP-CSI report on PUCCH may be resolved. To the extent that the A-CSI reports are prioritized, the DL grant A-CSI report on PUCCH may be selected at (2) .

When implementing (3) , collision (s) among the CSI report selected at (2) and other triggered CSI reports on the uplink shared channel may be resolved. In the scenario of FIG. 15A, this implies that collision between the DL grant triggered A-CSI report on PUCCH and the SP-CSI report on PUSCH may be resolved. Assuming that the A-CSI reports are prioritized over non-A-CSI reports, the DL grant triggered A-CSI report may be selected at (3) .

FIG. 15B illustrates another exemplary process performed by the UE to implement block 1330 that generalizes the implementation scenario of FIG. 15A. At block 1510, the UE may resolve a collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report by selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set. Again, there are multitudes of ways to implement block 1510. For example, block 1510 may be implemented through any of the processes illustrated in FIGs. 9A –11E.

After block 1510, the UE at block 1520 may resolve one or more collisions among a selected CSI report and one or more other first CSI reports by selecting the selected CSI report resource set. That is, the selected CSI report (the DL grant triggered A-CSI report or the UL grant triggered A-CSI report) may be prioritized over other first CSI reports that are not A-CSI reports.

After block 1520, the UE at block 1530 may resolve one or more collisions among the selected CSI report and one or more other second CSI reports by selecting the selected CSI report resource set. That is, the selected CSI report may be prioritized over other second CSI reports that are not A-CSI reports.

Referring back to FIG. 13, at block 1340, the UE may provide the DL grant triggered A-CSI report and/or the UL grant triggered A-CSI report to the network node on the selected CSI report resource set. Again, for ease of reference, a report set will be used to indicate the CSI report or reports provided to the network, i.e., the report set may comprise one or both of the DL grant triggered A-CSI report and the UL grant triggered A-CSI report. There are multitudes of ways to implement block 1340. For example, block 1340 may be implemented through any of the processes illustrated in FIGs. 9A –11E.

While not shown, block 1330 may also be implemented: (1a) resolving collisions (if any) among CSI reports on uplink control channel (s) and (1b) resolving collisions (if any) among CSI reports on uplink data channel (s) (1a and 1b being performed in either order) ; and (2) resolving collision between DL and UL triggered A-CSI reports.

FIG. 16 illustrates an example user equipment apparatus 1600 represented as a series of interrelated functional modules connected by a common bus. A module for receiving scheduling information 1610 may correspond at least to transceiver 254, RX processor 256, and controller/processor 259 of FIG. 2, as discussed herein. A module for determining CSI report collisions 1620 may correspond at least to controller/processor 259 of FIG. 2, as discussed herein. A module for resolving CSI report collisions 1630 may correspond at least to controller/processor 259 of FIG. 2, as discussed herein. A module for providing CSI reports 1640 may correspond at least to transceiver 254, TX processor 268, and controller/processor 259 of FIG. 2, as discussed herein. In all of memory 260 may comprise data and/or software containing instructions for instructing these various hardware components to perform the functions described herein.

The functionality of the modules of FIG. 16 may be implemented in various ways consistent with the teachings herein. In some designs, the functionality of these modules may be implemented as one or more electrical components. In some designs, the functionality of these blocks may be implemented as a processing system including one or more processor components. In some designs, the functionality of these modules may be implemented using, for example, at least a portion of one or more integrated circuits (e.g., an ASIC) . As discussed herein, an integrated circuit may include a processor, software, other related components, or some combination thereof. Thus, the functionality of different modules may be implemented, for example, as different subsets of an integrated circuit, as different subsets of a set of software modules, or a combination thereof. Also, it will be appreciated that a given subset (e.g., of an integrated circuit and/or of a set of software modules) may provide at least a portion of the functionality for more than one module.

In addition, the components and functions represented by FIG. 16, as well as other components and functions described herein, may be implemented using any suitable means. Such means also may be implemented, at least in part, using corresponding structure as taught herein. For example, the components described above in conjunction with the “module for” components of FIG. 16 also may correspond to similarly designated “means for” functionality. Thus, in some aspects one or more of such means may be implemented using one or more of processor components, integrated circuits, or other suitable structure as taught herein.

Those skilled in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Further, those skilled in the art will appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted to depart from the scope of the various aspects described herein.

The various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented or performed with a general purpose processor, a digital signal processor (DSP) , an application specific integrated circuit (ASIC) , a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or other such configurations) .

The methods, sequences, and/or algorithms described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM) , flash memory, Read-Only Memory (ROM) , Erasable Programmable ROM (EPROM) , Electrically Erasable Programmable ROM (EEPROM) , registers, hard disk, a removable disk, a CD-ROM, or any other form of non-transitory computer-readable medium known in the art. An exemplary non-transitory computer-readable medium may be coupled to the processor such that the processor can read information from, and write information to, the non-transitory computer-readable medium. In the alternative, the non-transitory computer-readable medium may be integral to the processor. The processor and the non-transitory computer-readable medium may reside in an ASIC. The ASIC may reside in a user device (e.g., a UE) or a base station. In the alternative, the processor and the non-transitory computer-readable medium may be discrete components in a user device or base station.

In one or more exemplary aspects, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a non-transitory computer-readable medium. Computer-readable media may include storage media and/or communication media including any non-transitory medium that may facilitate transferring a computer program from one place to another. A storage media may be any available media that can be accessed by a computer. By way of example, and not limitation, such computer-readable media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of a medium. The term disk and disc, which may be used interchangeably herein, includes a Compact Disk (CD) , laser disc, optical disk, Digital Video Disk (DVD) , floppy disk, and Blu-ray discs, which usually reproduce data magnetically and/or optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

While the foregoing disclosure shows illustrative aspects, those skilled in the art will appreciate that various changes and modifications could be made herein without departing from the scope of the disclosure as defined by the appended claims. Furthermore, in accordance with the various illustrative aspects described herein, those skilled in the art will appreciate that the functions, steps, and/or actions in any methods described above and/or recited in any method claims appended hereto need not be performed in any particular order. Further still, to the extent that any elements are described above or recited in the appended claims in a singular form, those skilled in the art will appreciate that singular form (s) contemplate the plural as well unless limitation to the singular form (s) is explicitly stated.

Claims

A method performed by user equipment (UE) , the method comprising:

receiving, from a network node, one or more first scheduling information triggering the UE to provide corresponding one or more first channel state information (CSI) reports to the network node on corresponding one or more first CSI report resource sets, each first CSI report resource set comprising one or more resources of an uplink (UL) control channel, the one or more first scheduling information comprising a downlink (DL) grant scheduling information notifying the UE of scheduling of resources of a DL data channel, the first CSI report corresponding to the DL grant scheduling information being a DL grant triggered aperiodic CSI (A-CSI) report, and the first CSI report resource set corresponding to the DL grant scheduling information being a DL grant A-CSI report resource set;

receiving, from the network node, one or more second scheduling information triggering the UE to provide corresponding one or more second CSI reports to the network node on corresponding one or more second CSI report resource sets, each second CSI report resource set comprising one or more resources of a UL data channel, the one or more second scheduling information comprising a UL grant scheduling information notifying the UE of scheduling of resources of a UL data channel, the second CSI report corresponding to the UL grant scheduling information being a UL grant triggered A-CSI report, and the second CSI report resource set corresponding to the UL grant scheduling information being a UL grant A-CSI report resource set;

resolving one or more collisions among the one or more first CSI reports and the one or more second CSI reports so as to select one of the DL grant A-CSI report resource set and the second A-CSI report resource set as a selected CSI report resource set, wherein two CSI reports collide when a time occupancy of CSI report resource sets corresponding to the two CSI reports overlap in at least one symbol; and

providing a report set to the network node on the selected CSI report resource set, the report set comprising one or both of the DL grant triggered A-CSI report and the UL grant triggered A-CSI report.
The method of claim 1,

wherein the DL grant A-CSI report resource set comprises one or more resources of a physical uplink control channel (PUCCH) , and/or

wherein the UL grant A-CSI report resource set comprises one or more resources of a physical uplink shared channel (PUSCH) .
The method of claim 1,

wherein the one or more first CSI report comprises one or more periodic CSI (P-CSI) reports and/or one or more semi-persistent CSI (SP-CSI) reports, and/or

wherein the one or more second CSI report comprises one or more semi-persistent CSI (SP-CSI) reports.
The method of claim 1, wherein resolving the one or more collisions among the one or more first CSI reports and the one or more second CSI reports comprises:

resolving one or more collisions among the one or more first CSI reports by selecting the DL grant A-CSI report resource set among the one or more first CSI report resource sets;

subsequent to resolving the one or more collisions among the one or more first CSI reports, resolving a collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report by selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set; and

subsequent to resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report, resolving one or more collisions among a selected CSI report and one or more other second CSI reports by selecting the selected CSI report resource set,

wherein the DL grant triggered A-CSI report is the selected CSI report when the DL grant A-CSI report resource set is selected as the selected CSI report resource set, and the UL grant triggered A-CSI report is the selected CSI report when the UL grant A-CSI report resource set is selected as the selected CSI report resource set, and

wherein the one or more other second CSI reports comprise the one or more second CSI reports other than the UL grant triggered A-CSI report.
The method of claim 4, wherein resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set based on an order of receiving the DL grant scheduling information and the UL grant scheduling information.
The method of claim 5, wherein when the DL grant scheduling information is received earlier than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 6, wherein providing the report set to the network node comprises multiplexing the DL grant triggered A-CSI report and the UL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 5,

wherein the DL grant scheduling information includes a DL grant A-CSI report priority and the UL grant scheduling information includes a UL grant A-CSI report priority,

wherein when the DL grant scheduling information is received later than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set also based on the DL grant A-CSI report priority and the UL grant A-CSI report priority.
The method of claim 8, wherein when the DL grant A-CSI report priority indicates a greater priority than or a same priority with the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the DL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 9, wherein providing the report set to the network node comprises providing only the DL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 8, wherein when the DL grant A-CSI report priority indicates a lesser priority than the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 11, wherein providing the report set to the network node comprises providing only the UL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 5, wherein when the DL grant scheduling information is received later than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 13, wherein providing the report set to the network node comprises providing only the UL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 5,

wherein the DL grant scheduling information includes a DL grant A-CSI report priority and the UL grant scheduling information includes a UL grant A-CSI report priority, and

wherein when the DL grant scheduling information is received earlier than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set also based on the DL grant A-CSI report priority and the UL grant A-CSI report priority.
The method of claim 15,

wherein when the DL grant A-CSI report priority indicates a greater priority than the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set,

wherein when the DL grant A-CSI report priority indicates a lesser priority than or a same priority with the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 16,

wherein when the DL grant A-CSI report priority indicates the greater priority than the UL grant A-CSI report priority, providing the report set to the network node comprises providing only the DL grant triggered A-CSI report the network node on the selected CSI report resource set,

wherein when the DL grant A-CSI report priority indicates the lesser priority than the UL grant A-CSI report priority, providing the report set to the network node comprises providing only the UL grant triggered A-CSI report the network node on the selected CSI report resource set, and

wherein when the DL grant A-CSI report priority indicates the same priority with the UL grant A-CSI report priority, providing the report set to the network node comprises multiplexing the DL grant triggered A-CSI report and the UL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 4,

wherein the DL grant scheduling information includes a DL grant A-CSI report priority and the UL grant scheduling information includes a UL grant A-CSI report priority, and

wherein resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set based on the DL grant A-CSI report priority and the UL grant A-CSI report priority.
The method of claim 18,

wherein when the DL grant A-CSI report priority indicates a greater priority than the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set,

wherein when the DL grant A-CSI report priority indicates a lesser priority than or a same priority with the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 19,

wherein when the DL grant A-CSI report priority indicates the greater priority than the UL grant A-CSI report priority, providing the report set to the network node comprises providing only the DL grant triggered A-CSI report the network node on the selected CSI report resource set,

wherein when the DL grant A-CSI report priority indicates the lesser priority than the UL grant A-CSI report priority, providing the report set to the network node comprises providing only the UL grant triggered A-CSI report the network node on the selected CSI report resource set, and

wherein when the DL grant A-CSI report priority indicates the same priority with the UL grant A-CSI report priority, providing the report set to the network node comprises multiplexing the DL grant triggered A-CSI report and the UL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 19, wherein when the DL grant A-CSI report priority indicates the same priority with the UL grant A-CSI report priority

wherein resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set also based on an order of receiving the DL grant scheduling information and the UL grant scheduling information.
The method of claim 21,

wherein when the DL grant scheduling information is received earlier than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set, and

wherein when the DL grant scheduling information is received later than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the DL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 22,

wherein when the DL grant scheduling information is received earlier than the UL grant scheduling information, providing the report set to the network node comprises providing only the UL grant triggered A-CSI report to the network node on the selected CSI report resource set, and

wherein when the DL grant scheduling information is received later than the UL grant scheduling information, providing the report set to the network node comprises providing only the DL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 1, wherein resolving the one or more collisions among the one or more first CSI reports and the one or more second CSI reports comprises:

resolving a collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report by selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set;

subsequent to resolving the collision between DL grant triggered A-CSI report and the UL grant triggered A-CSI report, resolving one or more collisions among a selected CSI report and one or more other first CSI reports by selecting the selected CSI report resource set; and

subsequent to resolving the one or more collisions among the selected CSI report and the one or more other first CSI reports, resolving one or more collisions among the selected CSI report and one or more other second CSI reports by selecting the selected CSI report resource set,

wherein the DL grant triggered A-CSI report is the selected CSI report when the DL grant A-CSI report resource set is selected as the selected CSI report resource set, and the UL grant triggered A-CSI report is the selected CSI report when the UL grant A-CSI report resource set is selected as the selected CSI report resource set, and

wherein the one or more other first CSI reports comprise the one or more first CSI reports other than the DL grant triggered A-CSI report, and the one or more other second CSI reports comprise the one or more second CSI reports other than the UL grant triggered A-CSI report.
The method of claim 24, wherein resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set based on an order of receiving the DL grant scheduling information and the UL grant scheduling information.
The method of claim 25, wherein when the DL grant scheduling information is received earlier than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 26, wherein providing the report set to the network node comprises multiplexing the DL grant triggered A-CSI report and the UL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 25,

wherein the DL grant scheduling information includes a DL grant A-CSI report priority and the UL grant scheduling information includes a UL grant A-CSI report priority,

wherein when the DL grant scheduling information is received later than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set also based on the DL grant A-CSI report priority and the UL grant A-CSI report priority.
The method of claim 28, wherein when the DL grant A-CSI report priority indicates a greater priority than or a same priority with the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the DL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 29, wherein providing the report set to the network node comprises providing only the DL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 28, wherein when the DL grant A-CSI report priority indicates a lesser priority than the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 31, wherein providing the report set to the network node comprises providing only the UL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 25, wherein when the DL grant scheduling information is received later than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 33, wherein providing the report set to the network node comprises providing only the UL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 25,

wherein the DL grant scheduling information includes a DL grant A-CSI report priority and the UL grant scheduling information includes a UL grant A-CSI report priority, and

wherein when the DL grant scheduling information is received earlier than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set also based on the DL grant A-CSI report priority and the UL grant A-CSI report priority.
The method of claim 35,

wherein when the DL grant A-CSI report priority indicates a greater priority than the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set,

wherein when the DL grant A-CSI report priority indicates a lesser priority than or a same priority with the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 36,

wherein when the DL grant A-CSI report priority indicates the greater priority than the UL grant A-CSI report priority, providing the report set to the network node comprises providing only the DL grant triggered A-CSI report the network node on the selected CSI report resource set,

wherein when the DL grant A-CSI report priority indicates the lesser priority than the UL grant A-CSI report priority, providing the report set to the network node comprises providing only the UL grant triggered A-CSI report the network node on the selected CSI report resource set, and

wherein when the DL grant A-CSI report priority indicates the same priority with the UL grant A-CSI report priority, providing the report set to the network node comprises multiplexing the DL grant triggered A-CSI report and the UL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 24,

wherein the DL grant scheduling information includes a DL grant A-CSI report priority and the UL grant scheduling information includes a UL grant A-CSI report priority, and

wherein resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set based on the DL grant A-CSI report priority and the UL grant A-CSI report priority.
The method of claim 38,

wherein when the DL grant A-CSI report priority indicates a greater priority than the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set,

wherein when the DL grant A-CSI report priority indicates a lesser priority than or a same priority with the UL grant A-CSI report priority, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 39,

wherein when the DL grant A-CSI report priority indicates the greater priority than the UL grant A-CSI report priority, providing the report set to the network node comprises providing only the DL grant triggered A-CSI report the network node on the selected CSI report resource set,

wherein when the DL grant A-CSI report priority indicates the lesser priority than the UL grant A-CSI report priority, providing the report set to the network node comprises providing only the UL grant triggered A-CSI report the network node on the selected CSI report resource set, and

wherein when the DL grant A-CSI report priority indicates the same priority with the UL grant A-CSI report priority, providing the report set to the network node comprises multiplexing the DL grant triggered A-CSI report and the UL grant triggered A-CSI report to the network node on the selected CSI report resource set.
The method of claim 39, wherein when the DL grant A-CSI report priority indicates the same priority with the UL grant A-CSI report priority

wherein resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting one of the DL grant A-CSI report resource set and the UL grant A-CSI report resource set as the selected CSI report resource set also based on an order of receiving the DL grant scheduling information and the UL grant scheduling information.
The method of claim 41,

wherein when the DL grant scheduling information is received earlier than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the UL grant A-CSI report resource set as the selected CSI report resource set, and

wherein when the DL grant scheduling information is received later than the UL grant scheduling information, resolving the collision between the DL grant triggered A-CSI report and the UL grant triggered A-CSI report comprises selecting the DL grant A-CSI report resource set as the selected CSI report resource set.
The method of claim 42,

wherein when the DL grant scheduling information is received earlier than the UL grant scheduling information, providing the report set to the network node comprises providing only the UL grant triggered A-CSI report to the network node on the selected CSI report resource set, and

wherein when the DL grant scheduling information is received later than the UL grant scheduling information, providing the report set to the network node comprises providing only the DL grant triggered A-CSI report to the network node on the selected CSI report resource set.
A user equipment (UE) , comprising:

a transceiver circuitry;

a memory circuitry; and

a processor circuitry,

wherein the transceiver circuitry, the memory circuitry, and the processor circuitry are configured to:

receive, from a network node, one or more first scheduling information triggering the UE to provide corresponding one or more first channel state information (CSI) reports to the network node on corresponding one or more first CSI report resource sets, each first CSI report resource set comprising one or more resources of an uplink (UL) control channel, the one or more first scheduling information comprising a downlink (DL) grant scheduling information notifying the UE of scheduling of resources of a DL data channel, the first CSI report corresponding to the DL grant scheduling information being a DL grant triggered aperiodic CSI (A-CSI) report, and the first CSI report resource set corresponding to the DL grant scheduling information being a DL grant A-CSI report resource set;

receive, from the network node, one or more second scheduling information triggering the UE to provide corresponding one or more second CSI reports to the network node on corresponding one or more second CSI report resource sets, each second CSI report resource set comprising one or more resources of a UL data channel, the one or more second scheduling information comprising a UL grant scheduling information notifying the UE of scheduling of resources of a UL data channel, the second CSI report corresponding to the UL grant scheduling information being a UL grant triggered A-CSI report, and the second CSI report resource set corresponding to the UL grant scheduling information being a UL grant A-CSI report resource set;

resolve one or more collisions among the one or more first CSI reports and the one or more second CSI reports so as to select one of the DL grant A-CSI report resource set and the second A-CSI report resource set as a selected CSI report resource set, wherein two CSI reports collide when a time occupancy of CSI report resource sets corresponding to the two CSI reports overlap in at least one symbol; and

provide a report set to the network node on the selected CSI report resource set, the report set comprising one or both of the DL grant triggered A-CSI report and the UL grant triggered A-CSI report.
A user equipment (UE) , comprising:

means for receiving, from a network node, one or more first scheduling information triggering the UE to provide corresponding one or more first channel state information (CSI) reports to the network node on corresponding one or more first CSI report resource sets, each first CSI report resource set comprising one or more resources of an uplink (UL) control channel, the one or more first scheduling information comprising a downlink (DL) grant scheduling information notifying the UE of scheduling of resources of a DL data channel, the first CSI report corresponding to the DL grant scheduling information being a DL grant triggered aperiodic CSI (A-CSI) report, and the first CSI report resource set corresponding to the DL grant scheduling information being a DL grant A-CSI report resource set;

means for receiving, from the network node, one or more second scheduling information triggering the UE to provide corresponding one or more second CSI reports to the network node on corresponding one or more second CSI report resource sets, each second CSI report resource set comprising one or more resources of a UL data channel, the one or more second scheduling information comprising a UL grant scheduling information notifying the UE of scheduling of resources of a UL data channel, the second CSI report corresponding to the UL grant scheduling information being a UL grant triggered A-CSI report, and the second CSI report resource set corresponding to the UL grant scheduling information being a UL grant A-CSI report resource set;

means for resolving one or more collisions among the one or more first CSI reports and the one or more second CSI reports so as to select one of the DL grant A-CSI report resource set and the second A-CSI report resource set as a selected CSI report resource set, wherein two CSI reports collide when a time occupancy of CSI report resource sets corresponding to the two CSI reports overlap in at least one symbol; and

means for providing a report set to the network node on the selected CSI report resource set, the report set comprising one or both of the DL grant triggered A-CSI report and the UL grant triggered A-CSI report.
A non-transitory computer-readable medium storing computer-executable instructions for a user equipment (UE) , the computer-executable instructions comprising:

one or more instructions causing the UE to receive, from a network node, one or more first scheduling information triggering the UE to provide corresponding one or more first channel state information (CSI) reports to the network node on corresponding one or more first CSI report resource sets, each first CSI report resource set comprising one or more resources of an uplink (UL) control channel, the one or more first scheduling information comprising a downlink (DL) grant scheduling information notifying the UE of scheduling of resources of a DL data channel, the first CSI report corresponding to the DL grant scheduling information being a DL grant triggered aperiodic CSI (A-CSI) report, and the first CSI report resource set corresponding to the DL grant scheduling information being a DL grant A-CSI report resource set;

one or more instructions causing the UE to receive, from the network node, one or more second scheduling information triggering the UE to provide corresponding one or more second CSI reports to the network node on corresponding one or more second CSI report resource sets, each second CSI report resource set comprising one or more resources of a UL data channel, the one or more second scheduling information comprising a UL grant scheduling information notifying the UE of scheduling of resources of a UL data channel, the second CSI report corresponding to the UL grant scheduling information being a UL grant triggered A-CSI report, and the second CSI report resource set corresponding to the UL grant scheduling information being a UL grant A-CSI report resource set;

one or more instructions causing the UE to resolve one or more collisions among the one or more first CSI reports and the one or more second CSI reports so as to select one of the DL grant A-CSI report resource set and the second A-CSI report resource set as a selected CSI report resource set, wherein two CSI reports collide when a time occupancy of CSI report resource sets corresponding to the two CSI reports overlap in at least one symbol; and

one or more instructions causing the UE to provide a report set to the network node on the selected CSI report resource set, the report set comprising one or both of the DL grant triggered A-CSI report and the UL grant triggered A-CSI report.