Patent Description:
Examples of such multiple-access systems include fourth generation (<NUM>) systems such as Long-Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth generation (<NUM>) systems which may be referred to as New Radio (NR) systems.

In some wireless communications systems, a UE may be configured to report CSI to a base station to indicate downlink channel conditions, and the base station may use the CSI to improve the quality of downlink transmissions to the UE. For example, the CSI may include a channel quality indicator (CQI), and the base station may use the CQI to identify appropriate parameters (e.g., a modulation and coding scheme (MCS)) for transmitting downlink data to the UE. Current techniques for reporting CSI from a UE to a base station may be inefficient for certain types of traffic (e.g., for uplink dominant traffic).

<CIT> discloses systems, apparatuses, and method for wireless communications. A base station may transmit, and a wireless device may receive, one or more messages that may comprise configuration parameters of semi persistent (SP) channel state information (CSI) reporting and an SP CSI skip indicator indicating that skipping SP CSI report transmission is allowed. The wireless device may skip transmitting an SP CSI report based on the CSI skip indicator.

Preferred embodiments are provided in the dependent claims. The described techniques relate to improved channel state information (CSI) triggering for uplink dominant traffic. Generally, the described techniques at a UE provide for efficiently reporting CSI to a base station with limited overhead. In one aspect, if a UE is configured to transmit data and CSI to a base station periodically in a configured grant physical uplink shared channel (CG-PUSCH), the UE may transmit the CSI when the UE has data to transmit to the base station in the CG-PUSCH. In particular, the UE may transmit data and a CSI report during a transmission opportunity of a CG-PUSCH if the UE has data to transmit in the transmission opportunity of the CG-PUSCH. Otherwise, the UE may suppress transmission of the CSI report. In another aspect, a UE may be configured to transmit CSI to a base station when downlink channel conditions change. In particular, when the UE identifies a change in channel conditions, the UE may request to report CSI to the base station, and the base station may trigger the UE to report the CSI after receiving the request.

Aspects of present invention are provided in the independent claims. Further implementation details are provided in the dependent claims. The scope of the present invention is defined by the scope of the appended claims.

In some wireless communications systems, a user equipment (UE) may be configured to perform channel measurements on downlink signals received from a base station and report the channel measurements to the base station. In such systems, the UE may transmit the results of the channel measurements in channel state information (CSI) feedback to the base station. Using the CSI feedback, the base station may identify suitable parameters for downlink transmissions to the UE to improve the likelihood that the downlink transmissions are received by the UE. In some cases, communications between the UE and the base station may be uplink dominant, and conventional techniques for facilitating CSI reporting may be deficient. In one example, if a UE is configured to periodically report CSI to a base station, the CSI reported by the UE may not be used by the base station when there is no downlink traffic (e.g., resulting in wasted resources). In another example, if a base station is configured to trigger CSI reporting from multiple UEs, the overhead associated with transmitting a trigger command to each of the multiple UEs may be high.

As described herein, a UE may support efficient techniques for reporting CSI to a base station with limited overhead for uplink dominant traffic. In one aspect, if a UE is configured to transmit data and CSI to a base station periodically in a configured grant physical uplink shared channel (CG-PUSCH), the UE may transmit the CSI in the CG-PUSCH when the UE has data to transmit to the base station in the CG-PUSCH. In particular, the UE may transmit data and a CSI report during a transmission opportunity of a CG-PUSCH if the UE has data to transmit in the transmission opportunity of the CG-PUSCH. Otherwise, the UE may suppress transmission of the CSI report. In another aspect, a UE may be configured to transmit CSI to a base station when downlink channel conditions change. In particular, when the UE identifies a change in channel conditions, the UE may request to report CSI to the base station, and the base station may trigger the UE to report the CSI after receiving the request.

Aspects of the disclosure introduced above are described below in the context of a wireless communications system. Examples of processes and signaling exchanges that support CSI triggering for uplink dominant traffic are then described. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to CSI triggering for uplink dominant traffic.

<FIG> illustrates an example of a wireless communications system <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The wireless communications system <NUM> includes base stations <NUM>, UEs <NUM>, and a core network <NUM>. In some examples, the wireless communications system <NUM> may be a Long-Term Evolution (LTE) network, an LTE-Advanced (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some cases, wireless communications system <NUM> may support enhanced broadband communications, ultra-reliable (e.g., mission critical) communications, low latency communications, or communications with low-cost and low-complexity devices.

Communication links <NUM> shown in wireless communications system <NUM> may include uplink transmissions from a UE <NUM> to a base station <NUM> (e.g., in a physical uplink control channel (PUCCH) or a physical uplink shared channel (PUSCH)), or downlink transmissions from a base station <NUM> to a UE <NUM> (e.g., in a physical downlink control channel (PDCCH) or a physical downlink shared channel (PDSCH)).

The term "cell" may refer to a logical communication entity used for communication with a base station <NUM> (e.g., over a carrier), and may be associated with an identifier for distinguishing neighboring cells (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID)) operating via the same or a different carrier. In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., machine-type communication (MTC), narrowband Internet-of Things (NB-IoT), enhanced mobile broadband (eMBB), or others) that may provide access for different types of devices.

The term "carrier" may refer to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communications over a communication link <NUM>. A carrier may be associated with a pre-defined frequency channel (e.g., an evolved universal mobile telecommunication system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)), and may be positioned according to a channel raster for discovery by UEs <NUM>. In some examples, signal waveforms transmitted over a carrier may be made up of multiple sub-carriers (e.g., using multi-carrier modulation (MCM) techniques such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)).

In some cases, wireless communications system <NUM> may be a packet-based network that operates according to a layered protocol stack.

A UE <NUM> in wireless communications system <NUM> may be configured to report CSI feedback to a base station <NUM> which the base station <NUM> may use to identify suitable parameters for downlink transmissions to the UE <NUM>. CSI feedback may be periodic, aperiodic, or semi-persistent, and the mechanism used to trigger CSI feedback from a UE <NUM> may be higher or lower layer signaling. For periodic CSI reporting, a UE <NUM> may report CSI in a PUCCH based on a configured reporting periodicity and offset, or the UE <NUM> may transmit the CSI with data in a PUSCH (e.g., piggyback on a PUSCH) when the UE <NUM> is scheduled to transmit data in the PUSCH at the same time (e.g., in a same slot). For semi-persistent CSI reporting, a UE <NUM> may report CSI in a PUCCH or PUSCH after receiving activation signaling from a base station <NUM> (e.g., based on the activation or deactivation by a MAC control element (MAC-CE)). Once the UE <NUM> is activated to report CSI, the UE <NUM> may report the CSI based on a higher layer configured periodicity. For aperiodic CSI reporting, a UE <NUM> may receive DCI that may dynamically indicate one of a number of higher layer CSI reporting settings, and, based on the indication in the DCI, the UE <NUM> may report CSI in a PUSCH in accordance with the indicated CSI reporting setting. Thus, in each of the above examples, a base station <NUM> may trigger a UE <NUM> to report CSI either periodically, semi-persistently, or aperiodically (e.g., a network-based triggering mechanism).

In some cases, communications between the UE <NUM> and the base station <NUM> may be downlink dominant or balanced between downlink and uplink. In such cases, the techniques described above for facilitating or triggering CSI reporting may be suitable (e.g., since the CSI may be used frequently by the base station <NUM> to improve the quality of downlink transmissions). In other cases, however, communications between the UE <NUM> and the base station <NUM> may be uplink dominant. One example of uplink dominant traffic may be for video surveillance (e.g., or other sensor applications, where a UE <NUM> may be primarily transmitting data to a base station <NUM>). In this example, downlink data transmissions may be used to acknowledge uplink data transmissions (e.g., in application layer feedback or an RRC response message). In such cases, conventional techniques for facilitating or triggering CSI reporting may be deficient. In particular, the network-based CSI triggering mechanism described may consider (e.g., only consider) CSI reporting for downlink dominant traffic and may not be optimal for uplink dominant traffic.

In one example, if a UE <NUM> is configured to periodically report CSI to a base station <NUM>, the CSI reported by the UE <NUM> may not be used by the base station <NUM> when there is no downlink traffic (e.g., resulting in resources being wasted). In another example, if a base station <NUM> is configured to trigger CSI reporting from multiple UEs, the overhead associated with transmitting a trigger command to each of the multiple UEs may be high. For instance, although a UE <NUM> may be triggered to report CSI when there is downlink traffic, the trigger command may be sent on a PDCCH to each UE <NUM>, and, when the number of UEs <NUM> is high, the base station <NUM> may not be able to trigger aperiodic CSI reporting for each UE <NUM> with an individual PDCCH. Further, since for uplink dominant traffic (e.g., for a fixed surveillance camera), the downlink channel may be slow-varying, the CSI may not change very often, and the aperiodic reporting of unchanged CSI may cause an unnecessary waste of both downlink and uplink resources. In wireless communications system <NUM>, a UE <NUM> may support efficient techniques for reporting CSI to a base station <NUM> with limited overhead for uplink dominant traffic.

<FIG> illustrates an example of a wireless communications system <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The wireless communications system <NUM> includes a UE <NUM>-a, which may be an example of a UE <NUM> described with reference to <FIG>. The wireless communications system <NUM> also includes a base station <NUM>-a, which may be an example of a base station <NUM> described with reference to <FIG>. The base station <NUM>-a may provide communication coverage for a coverage area <NUM>-a. UE <NUM>-a in coverage area <NUM>-a may transmit uplink signals to base station <NUM>-a on resources of a carrier <NUM>. The wireless communications system <NUM> may implement aspects of wireless communications system <NUM>. For example, the UE <NUM>-a in wireless communications system <NUM> may support efficient techniques for reporting CSI to the base station <NUM>-a with limited overhead for uplink dominant traffic.

In the example of <FIG>, the UE <NUM>-a may be configured for periodic CSI reporting in a CG-PUSCH (e.g., instead of a PUCCH). The base station <NUM>-a may configure the UE <NUM>-a with a first set of periodic resources <NUM> for transmitting data and a second set of periodic resources <NUM> for reporting CSI. The periodic resources <NUM> for transmitting data may be referred to as a CG-PUSCH and may correspond to periodically scheduled frequency resources (e.g., one or more resource blocks (RBs)) in a PUSCH allocated for periodic transmissions from the UE <NUM>-a. The CG-PUSCH configured for UE <NUM>-a may be used for transmission when data (e.g., mobile originated (MO) data) is present in buffers of the UE <NUM>-a for transmission to the base station <NUM>-a, and may be unused by UE <NUM>-a when it does not have MO data. For example, a CG-PUSCH may include periodic uplink resources, and the UE <NUM>-a may use a subset of the resources for transmission. In some cases, multiple UEs <NUM> may be scheduled on the same resources, and concurrent transmissions may be differentiated by the base station <NUM>-a based on cover codes or other coding applied to the transmissions. Thus, each set of time/frequency resources of the CG-PUSCH may or may not carry data transmitted by the UE <NUM>-a without DCI. Further, the periodic resources <NUM> for reporting CSI may be a portion or all of the CG-PUSCH resources (e.g., a portion or all of the periodic resources <NUM> for transmitting data). In one example, the UE <NUM>-a may be configured to report CSI with a same periodicity configured for transmitting data, where all CG-PUSCH resources may be configured for reporting CSI. In another example, the UE <NUM>-a may be configured to report CSI with a different periodicity from the periodicity configured for transmitting data (e.g., a larger periodicity that is an integer multiple of the periodicity configured for transmitting data), where a subset of the CG-PUSCH resources may be configured for reporting CSI.

Thus, the first set of periodic resources <NUM> may be time and frequency resources allocated for CG-PUSCH, and the second set of periodic resources <NUM> may be a subset of the time and frequency resources allocated for the CG-PUSCH. In some cases, the base station <NUM>-a may configure the first set of periodic resources <NUM> and the second set of periodic resources <NUM> together (e.g., in a single configuration or control message). In such cases, the base station <NUM>-a may transmit a configuration to the UE <NUM>-a including a CSI reporting configuration and a CG-PUSCH configuration, and the configuration may indicate a first offset and periodicity for transmitting data using the CG-PUSCH and a second offset and periodicity for reporting CSI via the CG-PUSCH (e.g., where the second offset may be zero or an integer multiple of the first periodicity configured for transmitting data in the CG-PUSCH). In other cases, the base station <NUM>-a may configure the first set of periodic resources <NUM> separately from the second set of periodic resources <NUM> (e.g., in different control messages). The periodicity for reporting CSI via the CG-PUSCH may be linked to the periodicity of the CG-PUSCH. For example, the base station <NUM>-a may transmit a CSI reporting configuration to the UE <NUM>-a including a link to a CG-PUSCH configuration index, and the CSI reporting configuration may indicate a first offset and periodicity for reporting CSI in the CG-PUSCH corresponding to the indicated CG-PUSCH configuration index.

Once the UE <NUM>-a identifies the periodic resources <NUM> for transmitting data and the periodic resources <NUM> for reporting CSI, the UE <NUM>-a may then transmit data and CSI reports to the base station <NUM>-a in one or more opportunities <NUM>. The one or more opportunities may correspond to either time and frequency resources scheduled for transmitting data or time and frequency resources scheduled for transmitting data and a CSI report in accordance with the periodic resources <NUM> for transmitting data and the periodic resources <NUM> for reporting CSI. As described herein, the UE <NUM>-a may transmit a CSI report in an opportunity <NUM> in the CG-PUSCH only when data is transmitted in the CG-PUSCH (e.g., CG-PUSCH is transmitted in the opportunity) and not when no data is transmitted in the CG-PUSCH (e.g., CG-PUSCH is not transmitted in the opportunity). That is, the UE <NUM>-a may transmit a CSI report in an opportunity <NUM> of the CG-PUSCH corresponding to periodic resources <NUM> for reporting CSI if the UE <NUM>-a has data to transmit in the opportunity <NUM> of the CG-PUSCH. Otherwise, the UE <NUM>-a may suppress transmission of the CSI report in the opportunity <NUM> of the CG-PUSCH if the UE <NUM>-a does not have data to transmit in the opportunity <NUM> in the CG-PUSCH. For example, the UE <NUM>-a may not transmit using the opportunity <NUM> of the CG-PUSCH if the UE <NUM>-a does not have data to transmit in the opportunity <NUM>. As such, the UE <NUM>-a may report CSI only when there is uplink traffic (e.g., since the UE may not transmit on the CG-PUSCH when there is no uplink data), and the CSI may then be used by the base station <NUM>-a for scheduling the associated downlink acknowledgment message (e.g., application layer feedback).

As an example, the UE <NUM>-a may identify a first opportunity <NUM>-a for transmitting data and a CSI report on a CG-PUSCH to the base station <NUM>-a. If the UE <NUM>-a determines that the UE <NUM>-a has data to transmit during the first opportunity <NUM>-a on the CG-PUSCH, the UE <NUM>-a may transmit the data and the CSI report during the first opportunity <NUM>-a on the CG-PUSCH. Alternatively, if the UE <NUM>-a determines that the UE <NUM>-a does not have data to transmit during the first opportunity <NUM>-a on the CG-PUSCH, the UE <NUM>-a may suppress transmission of the CSI report during the first opportunity <NUM>-a on the CG-PUSCH. In some cases, the UE <NUM>-a may drop reporting of the CSI report scheduled for the first opportunity <NUM>-a. Alternatively, the UE <NUM>-a may defer reporting of the CSI report scheduled for the first opportunity <NUM>-a to the next opportunity. For example, where the UE <NUM>-a suppresses transmission of the CSI report during the first opportunity <NUM>-a, the UE <NUM>-a may determine that the UE <NUM>-a has data to transmit in a second opportunity <NUM>-b, and, although the second opportunity <NUM>-b may not be scheduled for reporting CSI, the UE <NUM>-a may transmit the data and the CSI report in the second opportunity <NUM>-b on the CG-PUSCH. Deferred reporting may also be used, for example, in the case where the periodicity of reporting CSI is not an integer of the periodicity for CG-PUSCH. Thus, the UE <NUM>-a may not report CSI on the opportunities configured for CSI (unless they happen to overlap in time with a CG-PUSCH opportunity), but instead may report CSI on the next CG-PUSCH opportunity subsequent to the CSI reporting opportunity where the UE <NUM>-a has MO data to transmit.

In some cases, when the UE <NUM>-a determines to transmit data and a CSI report in an opportunity <NUM> on the CG-PUSCH, the UE <NUM>-a may transmit the CSI report in layer one (L1) signaling, or the UE <NUM>-a may transmit the CSI report in a MAC-CE of the CG-PUSCH. If the UE <NUM>-a is configured to transmit the CSI report in L1 signaling, the UE <NUM>-a may encode the data and the CSI report using different encoding schemes (e.g., using separate channel coding), and the UE <NUM>-a may map the data and the CSI report to different resource elements (e.g., using separate resource element mapping). The UE <NUM>-a may then multiplex the data and the CSI report on the CG-PUSCH.

Alternatively, if the UE <NUM>-a is configured to transmit the CSI report in a MAC-CE of the CG-PUSCH, the number of bits for the CSI report may be fixed (e.g., irrespective of the number of CSI reference signal (CSI-RS) ports for which measurements were performed and included in the CSI report). In some aspects, the UE <NUM>-a may also avoid reporting a precoder matrix indicator (PMI) in the CSI report (e.g., since the number of bits for the CSI report may be limited). In such aspects, the channel quality indicator (CQI) included in the CSI report for a CSI-RS may be based on the PMI from the latest reported aperiodic CSI associated with the same CSI-RS or precoder cycling over a set of preconfigured precoders in a codebook subset (e.g., a PMI associated with a precoder cycling). Further, the UE <NUM>-a may include an indication of the PMI (e.g., one-bit PMI) to indicate whether the precoder for CQI calculation is based on the PMI in the latest reported aperiodic CSI or based on precoder cycling.

<FIG> illustrates an example of a process flow <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The process flow <NUM> illustrates aspects of techniques performed by a UE <NUM>-b, which may be an example of a UE <NUM> described with reference to <FIG> and <FIG>. The process flow <NUM> also illustrates aspects of techniques performed by a base station <NUM>-b, which may be an example of a base station <NUM> described with reference to <FIG> and <FIG>. As described herein, UE <NUM>-b in process flow <NUM> may support efficient techniques for reporting CSI to the base station <NUM>-b with limited overhead for uplink dominant traffic.

At <NUM>, the base station <NUM>-b is configured to transmit a periodic CSI report configuration to the UE <NUM>-b which may include a CG-PUSCH configuration or a link to a CG-PUSCH configuration index. The periodic CSI report configuration may allocate periodic resources for the UE <NUM>-b to transmit CSI reports to the base station <NUM>-b, and the CG-PUSCH configuration may allocate periodic resources for the UE <NUM>-b to transmit data to the base station <NUM>-b. For instance, the UE <NUM>-b may receive, from the base station <NUM>-b, a configuration of a first periodicity for transmitting CSI reports to the base station <NUM>-b and a second periodicity for transmitting data to the base station <NUM>-b. Alternatively, the UE <NUM>-b may receive, from the base station <NUM>-b, a configuration of a first periodicity for transmitting CSI reports to the base station <NUM>-b, where the configuration indicates an index of the CG-PUSCH linked to the CSI reports that is associated with a second periodicity. In any case, the first periodicity may be an integer multiple (e.g., one or more) of the second periodicity.

Based on the configuration received at <NUM>, the UE <NUM>-b is configured to identify that the UE <NUM>-b is configured for transmitting a CSI report to the base station <NUM>-b on a CG-PUSCH. At <NUM>, UE <NUM>-b is configured to identify a first opportunity for transmitting data and the CSI report on the CG-PUSCH. At <NUM>, the UE <NUM>-b is configured to determine whether the UE <NUM>-b has data to transmit during the first opportunity on the CG-PUSCH. Then, if the UE <NUM>-b has data to transmit during the first opportunity, at <NUM>, the UE <NUM>-b is configured to transmit the data and the CSI report on the CG-PUSCH during the first opportunity. Alternatively, if the UE <NUM>-b does not have data to transmit during the first opportunity, the UE <NUM>-b is configured to suppress transmission of the CSI report on the CG-PUSCH during the first opportunity, wherein suppressing transmission of the CSI report includes suppressing transmitting the CSI report on any physical channel during the first opportunity.

Thus, using the techniques described herein, for each P-CSI reporting instance in a CG-PUSCH, if data is transmitted in the CG-PUSCH due to uplink traffic, the UE <NUM>-b may measure and report periodic CSI on the CG-PUSCH. Otherwise, the UE <NUM>-b may not transmit data on the CG-PUSCH and may not report periodic CSI. In particular, when the UE <NUM>-b identifies a transmit time for periodic CSI, and the UE <NUM>-b determines that the UE <NUM>-b has data to transmit at the transmit time for the periodic CSI on a CG-PUSCH, the UE <NUM>-b may transmit the periodic CSI and the data on the CG-PUSCH at the transmit time. Alternatively, when the UE <NUM>-b identifies a transmit time for periodic CSI, and the UE <NUM>-b determines that the UE <NUM>-b does not have data to transmit at the transmit time for the periodic CSI on a CG-PUSCH, the UE <NUM>-b may not transmit the periodic CSI on the CG-PUSCH at the transmit time (e.g., no periodic CSI report for not transmitting the CG-PUSCH).

<FIG> illustrates an example of a wireless communications system <NUM> that supports CSI triggering for uplink dominant traffic in accordance with an aspect not falling within the scope of the appended claims. The wireless communications system <NUM> includes a UE <NUM>-c, which may be an example of a UE <NUM> described with reference to <FIG>. The wireless communications system <NUM> also includes a base station <NUM>-c, which may be an example of a base station <NUM> described with reference to <FIG>. The base station <NUM>-a may provide communication coverage for a coverage area <NUM>-b. UE <NUM>-c in coverage area <NUM>-b may transmit uplink signals to base station <NUM>-c on resources of a carrier <NUM>, and base station <NUM>-c may transmit downlink signals to UE <NUM>-c on resources of a carrier <NUM> (e.g., where carriers <NUM> and <NUM> may be the same or different carriers). The wireless communications system <NUM> may implement aspects of wireless communications system <NUM>. For example, the UE <NUM>-c in wireless communications system <NUM> may support efficient techniques for reporting CSI to the base station <NUM>-c with limited overhead for uplink dominant traffic.

In the example of <FIG>, UE <NUM>-c may be configured to aperiodically report CSI to the base station <NUM>-c. As described herein, to limit the overhead associated with triggering UEs <NUM> to report CSI, the UE <NUM>-c may be configured to request to report CSI when the UE <NUM>-c determines that channel conditions have changed. Thus, when the UE <NUM>-c identifies a change in downlink channel conditions, the UE <NUM>-c may transmit a request <NUM> for the UE <NUM>-c to report CSI to the base station <NUM>-c. The request <NUM> for the UE <NUM>-c to report the CSI to the base station <NUM>-c may be a one-bit CSI update request which may be sent on a CG-PUSCH using a MAC-CE or by a dedicated PUCCH resource. Base station <NUM>-c may then determine that CSI previously reported by the UE <NUM>-c is invalid (e.g., outdated), and base station <NUM>-c may transmit an aperiodic request <NUM> (e.g., via DCI) for CSI from the UE <NUM>-c. That is, after receiving the request <NUM> for the CSI update, the base station <NUM>-c may assume that the previously reported CSI is outdated, and the base station <NUM>-c may request (e.g., via DCI) for the UE <NUM>-c to update the CSI (e.g., reusing the aperiodic CSI request or trigger field in the uplink grant of a PDCCH). The UE <NUM>-c may then transmit a CSI report to the base station <NUM>-c after receiving the request <NUM> for CSI from the base station <NUM>-c.

<FIG> illustrates an example of a process flow <NUM> that supports CSI triggering for uplink dominant traffic in accordance with an aspect not falling within the scope of the appended claims. The process flow <NUM> illustrates aspects of techniques performed by a UE <NUM>-d, which may be an example of a UE <NUM> described with reference to <FIG>. The process flow <NUM> also illustrates aspects of techniques performed by a base station <NUM>-d, which may be an example of a base station <NUM> described with reference to <FIG>. As described herein, UE <NUM>-d in process flow <NUM> may support efficient techniques for reporting CSI to the base station <NUM>-d with limited overhead for uplink dominant traffic.

At <NUM>, the UE <NUM>-d may identify a change of downlink channel conditions based on one or more downlink transmissions received from the base station <NUM>-d. For instance, the UE <NUM>-d may determine that a CQI or PMI associated with the downlink channel conditions is different from a previously reported CQI or PMI. At <NUM>, UE <NUM>-d may then transmit, and the base station <NUM>-d may receive, a request for the UE <NUM>-d to report CSI to the base station <NUM>-d (e.g., a one-bit CSI update request) based on identifying the change of downlink channel conditions. In some cases, the UE <NUM>-d may transmit the request in a MAC-CE of a CG-PUSCH or in a dedicated control channel. The base station <NUM>-d may determine that previous CSI received from the UE <NUM>-d is invalid based on receiving the request for the UE <NUM>-d to report the CSI to the base station <NUM>-d. At <NUM>, the base station <NUM>-d may transmit, and the UE <NUM>-d may receive, an indication that the UE <NUM>-d is to report the CSI to the base station <NUM>-b based on the request at <NUM>. At <NUM>, UE <NUM>-d may then report the CSI to the base station <NUM>-d.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a UE <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The receiver <NUM> may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to CSI triggering for uplink dominant traffic, etc.). Information may be passed on to other components of the device <NUM>. The receiver <NUM> may be an example of aspects of the transceiver <NUM> described with reference to <FIG>. The receiver <NUM> may utilize a single antenna or a set of antennas.

The communications manager <NUM> may identify that the UE is configured for transmitting a channel state information report to a base station on a configured grant uplink data channel. The communications manager <NUM> may identify a first opportunity for transmitting data and the channel state information report on the configured grant uplink data channel. The communications manager <NUM> may determine whether the UE has data to transmit during the first opportunity on the configured grant uplink data channel. The communications manager <NUM> may transmit data and the channel state information report on the configured grant uplink data channel during the first opportunity if the UE has data to transmit during the first opportunity, and the communications manager <NUM> may suppress transmission of the channel state information report on the configured grant uplink data channel during the first opportunity if the UE does not have data to transmit during the first opportunity.

The communications manager <NUM> may also identify a change of downlink channel conditions based on one or more downlink transmissions received from a base station. The communications manager <NUM> may transmit a request for the UE to report channel state information to the base station based on the identifying. The communications manager <NUM> may receive an indication that the UE is to report the channel state information to the base station based on transmitting the request. The communications manager <NUM> may report the channel state information to the base station. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM>, or a UE <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The communications manager <NUM> may be an example of aspects of the communications manager <NUM> as described herein. The communications manager <NUM> may include a CSI reporter <NUM>, a periodic resource manager <NUM>, a data manager <NUM>, a CG-PUSCH manager <NUM>, a downlink channel manager <NUM>, a CSI request manager <NUM>, and a CSI triggering manager <NUM>. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The CSI reporter <NUM> may identify that the UE is configured for transmitting a channel state information report to a base station on a configured grant uplink data channel. The periodic resource manager <NUM> may identify a first opportunity for transmitting data and the channel state information report on the configured grant uplink data channel. The data manager <NUM> may determine whether the UE has data to transmit during the first opportunity on the configured grant uplink data channel. The CG-PUSCH manager <NUM> may transmit data and the channel state information report on the configured grant uplink data channel during the first opportunity if the UE has data to transmit during the first opportunity and suppress transmission of the channel state information report on the configured grant uplink data channel during the first opportunity if the UE does not have data to transmit during the first opportunity.

The downlink channel manager <NUM> may identify a change of downlink channel conditions based on one or more downlink transmissions received from a base station. The CSI request manager <NUM> may transmit a request for the UE to report channel state information to the base station based on the identifying. The CSI triggering manager <NUM> may receive an indication that the UE is to report the channel state information to the base station based on transmitting the request. The CSI reporter <NUM> may report the channel state information to the base station.

<FIG> shows a block diagram <NUM> of a communications manager <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The communications manager <NUM> may be an example of aspects of a communications manager <NUM>, a communications manager <NUM>, or a communications manager <NUM> described herein. The communications manager <NUM> may include a CSI reporter <NUM>, a periodic resource manager <NUM>, a data manager <NUM>, a CG-PUSCH manager <NUM>, an encoder <NUM>, a resource mapper <NUM>, a multiplexer <NUM>, a downlink channel manager <NUM>, a CSI request manager <NUM>, and a CSI triggering manager <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The CSI reporter <NUM> may identify that the UE is configured for transmitting a channel state information report to a base station on a configured grant uplink data channel. The periodic resource manager <NUM> may identify a first opportunity for transmitting data and the channel state information report on the configured grant uplink data channel. The data manager <NUM> may determine whether the UE has data to transmit during the first opportunity on the configured grant uplink data channel. The CG-PUSCH manager <NUM> may transmit data and the channel state information report on the configured grant uplink data channel during the first opportunity if the UE has data to transmit during the first opportunity. In some examples, the CG-PUSCH manager <NUM> may suppress transmission of the channel state information report on the configured grant uplink data channel during the first opportunity if the UE does not have data to transmit during the first opportunity.

In some examples, the CG-PUSCH manager <NUM> may suppress transmitting the channel state information report on any physical channel during the first opportunity. In some examples, the data manager <NUM> may determine, subsequent to suppressing transmission of the channel state information report during the first opportunity on the configured grant uplink data channel, that the UE has data to transmit during a second opportunity on the configured grant uplink data channel. In some examples, the CG-PUSCH manager <NUM> may transmit the data and the channel state information report in the second opportunity on the configured grant uplink data channel based on determining that the UE has data to transmit during the second opportunity.

In some examples, the periodic resource manager <NUM> may receive a configuration of a first periodicity for transmitting channel state information reports to the base station and a second periodicity for transmitting data to the base station, where the first periodicity is an integer multiple of the second periodicity. In some examples, the periodic resource manager <NUM> may receive a configuration of a first periodicity for transmitting channel state information reports to the base station, where the configuration indicates an index of the configured grant uplink data channel linked to the channel state information reports and associated with a second periodicity for transmitting data to the base station, where the first periodicity is an integer multiple of the second periodicity.

The encoder <NUM> may encode the data and the channel state information report using different encoding schemes. The resource mapper <NUM> may map the data and the channel state information report to different resource elements. The multiplexer <NUM> may multiplex the data and the channel state information report in the first opportunity on the configured grant uplink data channel. In some examples, the CSI reporter <NUM> may transmit the channel state information report in a MAC-CE during the first opportunity on the configured grant uplink data channel. In some examples, the CSI reporter <NUM> may determine a channel quality indicator to include in the channel state information report based on a previous precoding matrix indicator reported in aperiodic channel state information feedback or a precoder matrix cycling over a codebook subset. In some examples, the CSI reporter <NUM> may transmit, in the MAC-CE, an indication of whether the channel quality indicator is based on the previous precoding matrix indicator reported in the aperiodic channel state information feedback or the precoder matrix cycling over the codebook subset.

The downlink channel manager <NUM> may identify a change of downlink channel conditions based on one or more downlink transmissions received from a base station. The CSI request manager <NUM> may transmit a request for the UE to report channel state information to the base station based on the identifying. The CSI triggering manager <NUM> may receive an indication that the UE is to report the channel state information to the base station based on transmitting the request. In some examples, the CSI reporter <NUM> may report the channel state information to the base station. In some examples, the downlink channel manager <NUM> may determine that a channel quality indicator or precoding matrix indicator associated with the downlink channel conditions is different from a previously reported channel quality indicator or precoding matrix indicator. In some examples, the CSI reporter <NUM> may transmit the request in a MAC-CE of a configured grant uplink data channel or in a dedicated control channel. In some cases, the request for the UE to report the channel state information includes a one-bit channel state information update request.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, or a UE <NUM> as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager <NUM>, an I/O controller <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, and a processor <NUM>. These components may be in electronic communication via one or more buses (e.g., bus <NUM>).

The communications manager <NUM> may also identify a change of downlink channel conditions based on one or more downlink transmissions received from a base station. The communications manager <NUM> may transmit a request for the UE to report channel state information to the base station based on the identifying. The communications manager <NUM> may receive an indication that the UE is to report the channel state information to the base station based on transmitting the request. The communications manager <NUM> may report the channel state information to the base station.

The memory <NUM> may include RAM and ROM.

The processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into the processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory (e.g., the memory <NUM>) to cause the device <NUM> to perform various functions (e.g., functions or tasks supporting CSI triggering for uplink dominant traffic).

<FIG> shows a block diagram <NUM> of a device <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a base station <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The communications manager <NUM> may receive, from a UE, a request for the UE to report channel state information to the base station. The communications manager <NUM> may transmit an indication that the UE is to report the channel state information to the base station based on receiving the request. The communications manager <NUM> may receive the channel state information from the UE based on transmitting the indication. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

<FIG> shows a block diagram <NUM> of a device <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The device <NUM> may be an example of aspects of a device <NUM>, or a base station <NUM> as described herein. The device <NUM> may include a receiver <NUM>, a communications manager <NUM>, and a transmitter <NUM>. The device <NUM> may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

The communications manager <NUM> may be an example of aspects of the communications manager <NUM> as described herein. The communications manager <NUM> may include a CSI request manager <NUM>, a CSI triggering manager <NUM>, and a CSI manager <NUM>. The communications manager <NUM> may be an example of aspects of the communications manager <NUM> described herein.

The CSI request manager <NUM> may receive, from a UE, a request for the UE to report channel state information to the base station. The CSI triggering manager <NUM> may transmit an indication that the UE is to report the channel state information to the base station based on receiving the request. The CSI manager <NUM> may receive the channel state information from the UE based on transmitting the indication.

<FIG> shows a block diagram <NUM> of a communications manager <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The communications manager <NUM> may be an example of aspects of a communications manager <NUM>, a communications manager <NUM>, or a communications manager <NUM> described herein. The communications manager <NUM> may include a CSI request manager <NUM>, a CSI triggering manager <NUM>, a CSI manager <NUM>, and a CSI validator <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The CSI request manager <NUM> may receive, from a UE, a request for the UE to report channel state information to the base station. The CSI triggering manager <NUM> may transmit an indication that the UE is to report the channel state information to the base station based on receiving the request. The CSI manager <NUM> may receive the channel state information from the UE based on transmitting the indication. The CSI validator <NUM> may determine that previous channel state information received from the UE is invalid based on receiving the request for the UE to report the channel state information to the base station. In some examples, the CSI request manager <NUM> may receive the request in a MAC-CE of a configured grant uplink data channel or in a dedicated control channel. In some cases, the request for the UE to report the channel state information includes a one-bit channel state information update request.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The device <NUM> may be an example of or include the components of device <NUM>, device <NUM>, or a base station <NUM> as described herein. The device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager <NUM>, a network communications manager <NUM>, a transceiver <NUM>, an antenna <NUM>, memory <NUM>, a processor <NUM>, and an inter-station communications manager <NUM>. These components may be in electronic communication via one or more buses (e.g., bus <NUM>).

The communications manager <NUM> may receive, from a UE, a request for the UE to report channel state information to the base station. The communications manager <NUM> may transmit an indication that the UE is to report the channel state information to the base station based on receiving the request. The communications manager <NUM> may receive the channel state information from the UE based on transmitting the indication.

The processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some cases, the processor <NUM> may be configured to operate a memory array using a memory controller. In some cases, a memory controller may be integrated into processor <NUM>. The processor <NUM> may be configured to execute computer-readable instructions stored in a memory (e.g., the memory <NUM>) to cause the device <NUM> to perform various functions (e.g., functions or tasks supporting CSI triggering for uplink dominant traffic).

The inter-station communications manager <NUM> may manage communications with other base station <NUM> and may include a controller or scheduler for controlling communications with UEs <NUM> in cooperation with other base stations <NUM>.

<FIG> shows a flowchart illustrating a method <NUM> that supports CSI triggering for uplink dominant traffic in accordance with aspects of the present disclosure. The operations of method <NUM> may be implemented by a UE <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally, or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.

At <NUM>, the UE is configured to identify that the UE is configured for transmitting a channel state information report to a base station on a configured grant uplink data channel. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a CSI reporter as described with reference to <FIG>.

At <NUM>, the UE is configured to identify a first opportunity for transmitting data and the channel state information report on the configured grant uplink data channel. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a periodic resource manager as described with reference to <FIG>.

At <NUM>, the UE is configured to determine whether the UE has data to transmit during the first opportunity on the configured grant uplink data channel. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a data manager as described with reference to <FIG>.

At <NUM>, the UE is configured to transmit data and the channel state information report on the configured grant uplink data channel during the first opportunity if the UE has data to transmit during the first opportunity. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a CG-PUSCH manager as described with reference to <FIG>.

At <NUM>, the UE is configured to suppress transmission of the channel state information report on the configured grant uplink data channel during the first opportunity if the UE does not have data to transmit during the first opportunity. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a CG-PUSCH manager as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> that supports CSI triggering for uplink dominant traffic in accordance with an aspect not falling within the scope of the appended claims. The operations of method <NUM> may be implemented by a UE <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. In some examples, a UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally, or alternatively, a UE may perform aspects of the functions described below using special-purpose hardware.

At <NUM>, the UE may identify a change of downlink channel conditions based on one or more downlink transmissions received from a base station. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a downlink channel manager as described with reference to <FIG>.

At <NUM>, the UE may transmit a request for the UE to report channel state information to the base station based on the identifying. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a CSI request manager as described with reference to <FIG>.

At <NUM>, the UE may receive an indication that the UE is to report the channel state information to the base station based on transmitting the request. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a CSI triggering manager as described with reference to <FIG>.

At <NUM>, the UE may report the channel state information to the base station. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a CSI reporter as described with reference to <FIG>.

<FIG> shows a flowchart illustrating a method <NUM> that supports CSI triggering for uplink dominant traffic in accordance with an aspect not falling within the scope of the appended claims. The operations of method <NUM> may be implemented by a base station <NUM> or its components as described herein. For example, the operations of method <NUM> may be performed by a communications manager as described with reference to <FIG>. In some examples, a base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally, or alternatively, a base station may perform aspects of the functions described below using special-purpose hardware.

At <NUM>, the base station may receive, from a UE, a request for the UE to report channel state information to the base station. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a CSI request manager as described with reference to <FIG>.

At <NUM>, the base station may transmit an indication that the UE is to report the channel state information to the base station based on receiving the request. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a CSI triggering manager as described with reference to <FIG>.

At <NUM>, the base station may receive the channel state information from the UE based on transmitting the indication. The operations of <NUM> may be performed according to the methods described herein. In some examples, aspects of the operations of <NUM> may be performed by a CSI manager as described with reference to <FIG>.

By way of example, and not limitation, non-transitory computer-readable media may include random-access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.

As used herein, including in the claims, "or" as used in a list of items (e.g., a list of items prefaced by a phrase such as "at least one of" or "one or more of') indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

Claim 1:
A method (<NUM>) for wireless communication at a user equipment, UE, the method being performed by the UE and comprising:
identifying (<NUM>) that the UE is configured for transmitting a channel state information report to a base station on a configured grant uplink data channel;
identifying (<NUM>) a first opportunity for transmitting data and the channel state information report on the configured grant uplink data channel; the method being characterized by:
determining (<NUM>) whether the UE has data to transmit during the first opportunity;
transmitting (<NUM>) data and the channel state information report on the configured grant uplink data channel during the first opportunity if the UE has data to transmit during the first opportunity; and
suppressing (<NUM>) transmission of the channel state information report during the first opportunity on the configured grant uplink data channel if the UE does not have data to transmit during the first opportunity.