Patent Description:
These systems may employ technologies such as code division multiple access (CDMA), time division multiple access (TDMA), frequency division multiple access (FDMA), orthogonal frequency division multiple access (OFDMA), or discrete Fourier transform-spread-OFDM (DFT-S-OFDM).

<CIT> relates to configuring channel state information reference signal (CSI-RS) reporting configurations to reduce CSI re-computations.

In some wireless communications systems, a UE may be configured to support multiple types of communications with different priority levels (e.g., ultra-reliable low latency communications (URLLC), enhanced mobile broadband (eMBB) communications, shortened transmission time interval (sTTI) communications). Accordingly, a base station may request channel state information (CSI) reports from the UE for one or more carriers of the different priority level types of communications, where the UE may update CSI processes corresponding to the requested CSI reports before responding with updated CSI reports for one or more carriers of the types of communications. In order to prevent an overload at the UE due to updating a large number of CSI processes in succession, the UE may employ limits to the number of CSI updates performed.

A method of wireless communications is described. The method may include identifying that a UE supports communications of a first service priority type and a second service priority type, reporting a CSI update capability associated with both the first and second service priority types, prioritizing one or more CSI processes of the first service priority type, the second service priority type, or both based on a set of priority rules and the CSI update capability, updating CSI for the one or more CSI processes based on the prioritization of the one or more CSI processes, and reporting the updated CSI.

An apparatus for wireless communications is described. The apparatus may include means for identifying that a UE supports communications of a first service priority type and a second service priority type, means for reporting a CSI update capability associated with both the first and second service priority types, means for prioritizing one or more CSI processes of the first service priority type, the second service priority type, or both based on a set of priority rules and the CSI update capability, means for updating CSI for the one or more CSI processes based on the prioritization of the one or more CSI processes, and means for reporting the updated CSI.

Another apparatus for wireless communications is described. The apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be operable to cause the processor to identify that a UE supports communications of a first service priority type and a second service priority type, report a CSI update capability associated with both the first and second service priority types, prioritize one or more CSI processes of the first service priority type, the second service priority type, or both based on a set of priority rules and the CSI update capability, update CSI for the one or more CSI processes based on the prioritization of the one or more CSI processes, and report the updated CSI.

A non-transitory computer-readable medium for wireless communications is described. The non-transitory computer-readable medium may include instructions operable to cause a processor to identify that a UE supports communications of a first service priority type and a second service priority type, report a CSI update capability associated with both the first and second service priority types, prioritize one or more CSI processes of the first service priority type, the second service priority type, or both based on a set of priority rules and the CSI update capability, update CSI for the one or more CSI processes based on the prioritization of the one or more CSI processes, and report the updated CSI.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, reporting the updated CSI includes reporting the updated CSI and a previously determined CSI of at least one of the one or more CSI processes based at least in part on a service priority type of the at least one of the one or more CSI processes.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, reporting the updated CSI includes refraining from reporting a previously determined CSI of at least one of the one or more CSI processes based at least in part on a service priority type of the at least one of the one or more CSI processes.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a URLLC priority service type over a CSI process associated with an sTTI priority service type in accordance with the set of priority rules.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a later received CSI request and a higher priority service type over a CSI process associated with an earlier received CSI request and a lower priority service type.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a URLLC priority service type over a CSI process associated with an eMBB priority service type in accordance with the set of priority rules.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with an aperiodic CSI request over a CSI process associated with a periodic CSI request in accordance with the set of priority rules.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a lower cell index over a CSI process associated with a higher cell index in accordance with the set of priority rules.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a lower CSI process index over a CSI process associated with a higher CSI process index in accordance with the set of priority rules.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a first downlink control information (DCI) format different from the first DCI format over a CSI process associated with a second DCI format in accordance with the set of priority rules.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a first block error rate (BLER) target value over a CSI process associated with a second BLER target value different from the first BLER target value in accordance with the set of priority rules.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, updating CSI for the one or more CSI processes includes: updating fewer than all of the one or more CSI processes based on the prioritization of the one or more CSI processes and the CSI update capability.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, reporting the CSI update capability includes reporting a pair of CSI update capabilities, each corresponding to a respective one of the first service priority type and the second service priority type.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, reporting the updated CSI includes: reporting a previously determined CSI of at least one of the one or more CSI processes based on the CSI update capability.

Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for receiving a first CSI request associated with the first service priority type, where a first CSI process of the one or more CSI processes may be updated in response to the first CSI request.

Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for receiving a second CSI request associated with the second service priority type, where a second CSI process of the one or more CSI processes may be updated in response to the second CSI request.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, updating CSI for the one or more CSI processes includes: performing a CSI update for the first CSI process before performing a CSI update for the second CSI process based on the set of priority rules.

Some examples of the method, apparatus, and non-transitory computer-readable medium described above may further include processes, features, means, or instructions for receiving a third CSI request associated with the first service priority type, where updating the CSI for the one or more CSI processes includes canceling a CSI update for the second CSI process and performing a CSI update for a third CSI process based on the set of priority rules and the CSI update capability.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, reporting the updated CSI includes: transmitting a CSI feedback message via a physical uplink shared channel (PUSCH) or a physical uplink control channel (PUCCH).

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, reporting the updated CSI includes: reporting respective CSI feedback messages for each of a plurality of CCs.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, the updated CSI may be reported based on respective transmission modes associated with the one or more CSI processes.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, the first service priority type includes a URLLC priority service, an sTTI priority service, or an eMBB priority service and the second service priority type may be different than the first service priority type.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, the CSI update capability indicates a number of CSI update processes supported by the UE per serving cell.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, the CSI update capability indicates a number of CSI processes across multiple CCs capable of being updated by the UE.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, the one or more CSI processes correspond to respective CCs of a primary cell or a secondary cell.

In some examples of the method, apparatus, and non-transitory computer-readable medium described above, the CSI update capability includes a joint CSI update capability.

In some wireless communications systems, a base station may aperiodically request a user equipment (UE) to transmit one or more channel state information (CSI) reports for corresponding component carriers (CCs). The UE may update a subset of CSI processes corresponding to the requested CSI reports before transmitting the CSI reports back to the base station. For example, the UE may update a number of CSI processes for a new aperiodic request according to a number of unreported CSI processes (Nu) associated with previously received CSI report requests for a single serving cell (e.g., a CC) and a maximum number of CSI processes supported by the UE and serving cell (Nx). Additionally or alternatively, the UE may update a number of CSI processes according to a maximum number of CSI processes (Ny), the UE may update when the UE is configured for communication via multiple cells (e.g., multiple CCs) and receives multiple aperiodic CSI report requests in a subframe. In some cases, the UE may be configured for regular transmission time intervals (TTIs) and for shortened TTIs (sTTIs). Accordingly, the UE may define separate Nx and Ny for both TTI and sTTI operations. Additionally, the UE may update CSI processes associated with sTTI CSI report requests according to Ny and Nu, where Nu may be defined as unreported CSI processes before an sTTI where signaling carrying the corresponding CSI process is transmitted. In some aspects, the number of unreported CSI processes before the sTTI carrying the corresponding CSI process (e.g., the sTTI carrying a physical uplink shared channel (PUSCH)) may include pending requests for TTI or sTTI operations (e.g., requests triggered by TTI (or legacy) DCI, sTTI DCI, or any combination thereof).

In some cases, a UE may be configured to support multiple types of communications with different priority levels (e.g., ultra-reliable low latency communications (URLLC), enhanced mobile broadband (eMBB) communications, sTTI communications, etc.). As such, the UE may choose to provide updated CSI processes separately for each of the different priority level types of communications because each type may have a separately configured transmission mode. For example, a first transmission mode (e.g., transmission mode <NUM> (TM9)) may be configured for a first priority level type of communication (e.g., sTTI communications), and a second transmission mode (e.g., transmission mode <NUM> (TM2)) may be configured for a second priority level type of communication (e.g., URLLC). The UE may be able to separately (e.g., separate CSI update capability) or jointly (e.g., joint CSI update capability) report its capability to update CSI processes for the different priority level types of communications. For example, the UE may define Nx and Ny for each type of communication (e.g., Nx_sTTI, Nx_URLLC, Ny_STTI, Ny_URLLC), where the CSI process updates may be run separately for each type of communication. Alternatively, the UE may utilize a jointly defined Nx and Ny for the types of communications (e.g., Nx and Ny include both sTTI and URLLC CSI processes).

Whether the UE reports its CSI update capability jointly or separately, the UE may employ a set of priority rules for determining which CSI processes are updated for the different types of communications. For example, the UE may update CSI processes in time according to the type of communication associated with the CSI report request (e.g., URLLC CSI processes are updated before sTTI or eMBB CSI processes), when the CSI report request is received (e.g., earlier CSI report requests are updated before later CSI report requests), whether the CSI report request is aperiodic or periodic (e.g., aperiodic CSI report requests are updated before periodic CSI report requests), a cell index and/or CSI process index (e.g., lower indices are updated before larger indices), UE implementation, or a combination thereof. Additionally, the UE may employ a set of priority rules for updating CSI processes over the frequency-domain. For example, the UE may update CSI processes in frequency according to UE implementation, a block error rate (BLER) associated with the CSI process, a format or a value of the downlink control information (DCI) that contains the CSI report request, the type of communication associated with the CSI report request, a cell index and/or CSI process index, or a combination thereof.

Aspects of the disclosure are initially described in the context of wireless communications systems. Additionally, examples of CSI process timelines are provided to describe aspects of the disclosure. Aspects of the disclosure are further illustrated by and described with reference to a process flow, apparatus diagrams, system diagrams, and flowcharts that relate to channel reporting for communication service priority types.

<FIG> illustrates an example of a wireless communications system <NUM> in accordance with various 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.

The wireless communications system <NUM> may include, for example, a heterogeneous LTE/LTE-A or NR network in which different types of base stations <NUM> provide coverage for various geographic coverage areas <NUM>.

The term "cell" refers 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 (PCI), 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), NB-IoT, eMBB, or others) that may provide access for different types of devices.

A UE <NUM> may be a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer.

In one example, a base station <NUM> may use multiple antennas or antenna arrays to conduct beamforming operations for directional communications with a UE <NUM>. For instance, some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by a base station <NUM> multiple times in different directions, which may include a signal being transmitted according to different beamforming weight sets associated with different directions of transmission. Transmissions in different beam directions may be used to identify (e.g., by the base station <NUM> or a receiving device, such as a UE <NUM>) a beam direction for subsequent transmission and/or reception by the base station <NUM>. Some signals, such as data signals associated with a particular receiving device, may be transmitted by a base station <NUM> in a single beam direction (e.g., a direction associated with the receiving device, such as a UE <NUM>). In some examples, the beam direction associated with transmissions along a single beam direction may be determined based at least in in part on a signal that was transmitted in different beam directions. For example, a UE <NUM> may receive one or more of the signals transmitted by the base station <NUM> in different directions, and the UE <NUM> may report to the base station <NUM> an indication of the signal it received with a highest signal quality, or an otherwise acceptable signal quality. Although these techniques are described with reference to signals transmitted in one or more directions by a base station <NUM>, a UE <NUM> may employ similar techniques for transmitting signals multiple times in different directions (e.g., for identifying a beam direction for subsequent transmission or reception by the UE <NUM>), or transmitting a signal in a single direction (e.g., for transmitting data to a receiving device).

For example, a receiving device may try multiple receive directions by receiving via different antenna subarrays, by processing received signals according to different antenna subarrays, by receiving according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, or by processing received signals according to different receive beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receive beams or receive directions. The single receive beam may be aligned in a beam direction determined based on listening according to different receive beam directions (e.g., a beam direction determined to have a highest signal strength, highest signal-to-noise ratio, or otherwise acceptable signal quality based on listening according to multiple beam directions).

Time intervals of a communications resource may be organized according to radio frames each having a duration of <NUM> milliseconds (ms), where the frame period may be expressed as Tf= <NUM>,<NUM> Ts. In some cases a subframe may be the smallest scheduling unit of the wireless communications system <NUM>, and may be referred to as a TTI. In other cases, a smallest scheduling unit of the wireless communications system <NUM> may be shorter than a subframe or may be dynamically selected (e.g., in bursts of sTTIs or in selected CCs using sTTIs).

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 DFT-s-OFDM).

The organizational structure of the carriers may be different for different radio access technologies (e.g., LTE, LTE-A, NR, etc.).

Devices of the wireless communications system <NUM> (e.g., base stations <NUM> or UEs <NUM>) may have a hardware configuration that supports communications over a particular carrier bandwidth, or may be configurable to support communications over one of a set of carrier bandwidths. In some examples, the wireless communications system <NUM> may include base stations <NUM> and/or UEs that can support simultaneous communications via carriers associated with more than one different carrier bandwidth.

Carrier aggregation may be used with both FDD and TDD CCs.

In some cases, wireless communications system <NUM> may utilize enhanced CCs (eCCs).

Wireless communications systems such as an NR system may utilize any combination of licensed, shared, and unlicensed spectrum bands, among others. The flexibility of eCC symbol duration and subcarrier spacing may allow for the use of eCC across multiple spectrums. In some examples, NR shared spectrum may increase spectrum utilization and spectral efficiency, specifically through dynamic vertical (e.g., across frequency) and horizontal (e.g., across time) sharing of resources.

In some cases, a base station <NUM> may aperiodically request a UE <NUM> to transmit multiple CSI reports for corresponding CCs. CSI may include information describing characteristics of the radio channel, typically indicating the complex transfer function matrix between one or more transmit antennas and one or more receive antennas. The base station <NUM> may gather channel condition information from the UE <NUM> in order to efficiently configure and schedule the channel. This information may be sent from the UE <NUM> in the form of a channel state report. The base station <NUM> may configure the UE <NUM> to send periodic reports at regular intervals and may also request additional reports as needed. Aperiodic reports may include wideband reports indicating the channel quality across an entire cell bandwidth, UE-selected reports indicating a subset of the best subbands, or configured reports in which the subbands reported are selected by the base station <NUM>.

The UE <NUM> may update CSI processes corresponding to the requested CSI reports before transmitting the CSI reports to the base station <NUM>. Alternatively, in order to prevent an overload at the UE <NUM> due to updating a large number of CSI processes in succession, the UE <NUM> may employ limits to the number of CSI updates performed in either or both of the time and frequency domain. For example, if the UE <NUM> is configured with more than one CSI process for a serving cell (e.g., a CC used for communication with base station <NUM>), the UE <NUM>, on reception of an aperiodic CSI report request triggering a CSI report (e.g., if the CSI report is triggered according to a table), may not be expected to update CSI processes corresponding to the CSI reference for all CSI processes. Rather, the UE may update the max(<NUM>,Nx-Nu) lowest-indexed CSI processes for the serving cell associated with the request. In such a case, Nu may represent the number of unreported CSI processes of the UE <NUM> that are associated with other aperiodic CSI requests for the serving cell. A CSI process associated with a CSI request may be only counted as unreported in a subframe prior to one where a physical uplink shared channel (PUSCH) carrying the corresponding CSI report is transmitted. Nx may represent the maximum number of CSI processes supported by the UE <NUM> for the serving cell.

In one example, a UE <NUM> may support four (<NUM>) CSI processes for a serving cell (i.e., Nx = <NUM>). In a first subframe, the UE <NUM> may receive a first trigger to report CSI for three (<NUM>) CSI processes for the serving cell. In the next subframe, the UE <NUM> may receive a second trigger to report three (<NUM>) CSI processes for the same serving cell. Upon receiving the second trigger, the first three (<NUM>) CSI processes associated with the first trigger may have not been reported (i.e., Nu = <NUM>). As such, the difference between the maximum number of supported CSI processes and the unreported CSI processes may be one (<NUM>) (i.e., max(<NUM>,Nx- Nu) = <NUM>). Therefore, the UE <NUM> may update one (<NUM>) CSI process with the lowest-indexed CSI process out of the three (<NUM>) CSI processes associated with the second trigger and transmit CSI that was initially or previously determined for the remaining CSI processes. As such, although CSI reports may be transmitted for all (<NUM>) CSI processes, only (<NUM>) of those CSI processes may be updated. This approach may set a limit on the number of CSI processes that can be updated in the time domain in one serving cell and for a UE <NUM> that is configured with more than one CSI process. However, it may not be applicable to all transmission modes.

Additionally or alternatively, if a UE <NUM> is configured with a physical uplink control channel secondary channel (PUCCH-SCell), and if the UE <NUM> receives multiple aperiodic CSI report requests in a subframe triggering more than one CSI report for both the primary PUCCH group and the secondary PUCCH group, then the UE <NUM> may not be required to update CSI for more than five (<NUM>) CSI processes from the CSI processes corresponding to all the triggered CSI reports. This updating process may be done under the assumption that the total number of serving cells in the primary and secondary PUCCH group is no more than five (<NUM>). If a UE <NUM> is configured with more than five (<NUM>) serving cells, and if the UE <NUM> receives aperiodic CSI report requests in a subframe triggering more than Ny CSI reports, the UE <NUM> may not be required to update CSI for more than Ny CSI processes from the CSI processes corresponding to all the triggered CSI reports. In some cases, the value of Ny may be given by maxNumberUpdatedCSI-Proc-r13. This approach may set a limit on the number of CSI processes that can be updated in the frequency domain and across all CCs.

In some cases, the UE <NUM> may be configured for regular TTIs and for sTTIs. In such cases, the sTTI CSIs and regular CSIs may be associated with separate DCI formats (e.g., the DCI which triggers the reporting for the sTTI CSI processes may be different than the DCI which triggers the reporting for regular CSI processes). Accordingly, the UE <NUM> may define separate Nx and Ny for both TTI and sTTI operations (e.g., according to DCI format). Additionally, the UE <NUM> may update CSI processes associated with sTTI CSI report requests according to Ny and Nu, where Nu may be defined as a number of unreported CSI processes (e.g., the number of unreported CSI processes before an sTTI in which signaling carrying the CSI reports corresponding to the CSI processes is transmitted). In some cases, Ny may be a UE capability of the UE <NUM> and may be declared for CSI reporting under the sTTI operation.

In some cases, the UE <NUM> may be configured to support multiple types of communications with different priority levels (e.g., URLLC, eMBB communications, sTTI communications, etc.). As such, the UE <NUM> may need to provide updated CSI processes for each of the different priority level types of communications separately because each type may have a separately configured transmission mode. The UE <NUM> may be able to separately (e.g., separate CSI update capability) or jointly (e.g., joint CSI update capability) update CSI processes for the different priority level types of communications. For example, the UE <NUM> may define Nx and Ny for each type of communication (e.g., Nx_sTTI, Nx_URLLC, Ny_STTI, Ny_URLLC), where the CSI process updates may be run separately for each type of communication. Such examples may include a separate Nu for each type of CSI process (e.g., an Nu_STT, and an Nu_URLLC). Alternatively, the UE <NUM> may utilize a jointly defined Nx and Ny for the types of communications (e.g., Nx and Ny include both sTTI and URLLC CSI processes). Such examples may include a single Nu for all CSI process types. In either case, the UE <NUM> may use the methods described herein. For example, the calculations performed for one set of variables, (Ny, Ny, Nu), could also be extended to multiple sets of variables, such as (Nx_sTTI, Ny_STTI, Nu_STTI) and (Nx_URLLC, Ny_URLLC, Nu_URLLC). Further, the UE <NUM> may determine a number of CSI processes to update for each set of variables, where each set of variables may correspond to a different type of CSI process.

Wireless communications system <NUM> may employ a set of priority rules for a UE <NUM> for determining which CSI processes are updated for the different types of communications when the UE <NUM> utilizes a joint CSI update capability. For example, the UE <NUM> may update CSI processes in time according to the type of communication associated with the CSI report request (e.g., URLLC CSI processes are updated before sTTI or eMBB CSI processes), when the CSI report request is received (e.g., earlier CSI report requests are updated before later CSI report requests), whether the CSI report request is aperiodic or periodic (e.g., aperiodic CSI report requests are updated before periodic CSI report requests), a cell index and/or CSI process index (e.g., lower indices are updated before larger indices), UE implementation, or a combination thereof. Additionally, the UE <NUM> may employ a set of priority rules for updating CSI processes over the frequency-domain. For example, the UE <NUM> may update CSI processes in frequency according to UE implementation, the type of communication associated with the CSI report request, a cell index and/or CSI process index, or a combination thereof.

<FIG> illustrates an example of a wireless communications system <NUM> that supports channel reporting for communication service priority types in accordance with various aspects of the present disclosure. In some examples, wireless communications system <NUM> may implement aspects of wireless communications system <NUM>. Wireless communications system <NUM> may include a base station <NUM>-a and a UE <NUM>-a, which may be examples of corresponding base stations <NUM> and UEs <NUM> as described with reference to <FIG>. Base station <NUM>-a and UE <NUM>-a may communicate on resources of a CC <NUM>-a and a CC <NUM>-b.

In some cases, UE <NUM>-a may support multiple types of communications with different priority levels (URLLC, eMBB communications, sTTI communications, etc.) and a joint CSI update capability as described herein. For example, base station <NUM>-a and UE <NUM>-a may communicate on resources of CC <NUM>-a utilizing a first priority level type of communication (e.g., URLLC) and on resources of CC <NUM>-b utilizing a second priority level type of communication (e.g., sTTI communications or eMBB communications). Although not shown, it is to be understood that UE <NUM>-a may communicate with multiple base stations on resources of one or more carriers (e.g., CCs <NUM>). For example, UE <NUM>-a may communicate with base station <NUM>-a on resources of CC <NUM>-a and with a neighboring base station <NUM> on resources of CC <NUM>-b.

Each CC <NUM> may include multiple subcarriers. Base station <NUM>-a may request CSI reports for one or more CCs <NUM>. The request from base station <NUM>-a may trigger CSI processes at UE <NUM>-a, where UE <NUM>-a may update corresponding CSI for CCs indicated by the requested CSI reports. To reduce the number of updates performed on CSI processes, UE <NUM>-a may employ a set of priority rules to determine which CSI processes are updated. For example, UE <NUM>-a may update CSI processes in time according to the type of communication associated with the CSI report request (e.g., URLLC CSI processes are updated before sTTI or eMBB CSI processes), then according to when the CSI report request is received (e.g., earlier CSI report requests are updated before later CSI report requests), then according to whether the CSI report request is aperiodic or periodic (e.g., aperiodic CSI report requests are updated before periodic CSI report requests), then according to a cell index and/or CSI process index (e.g., lower indices are updated before larger indices), and then according to UE implementation. Under these priority rules, the processing or updating of earlier triggered CSI processes may be stopped in favor of later triggered CSI processes. In cases of separate CSI update capability, UE <NUM>-a may prioritize CSI processes of different service types separately, meaning that UE <NUM>-a may prioritize the CSI processes under the latter three rules and/or other rules (e.g., the other rules disclosed herein). In some cases, higher priority may be given to URLLC CSI processes over sTII or eMBB CSI processes and then UE <NUM>-a may prioritize CSI updating according to UE implementation. As an example, if a sTTI CSI process is received at an earlier time than a URLCC CSI process, the URLCC CSI may be prioritized because a CSI process being received earlier is less important under the priority rules than a CSI process being a URLCC CSI process. In general, prioritization may mean that CSI processes that are associated with a higher priority (e.g., by priority rules or elsewise) may be updated in favor of CSI processes that are associated with a lower priority. Even if a CSI process has a higher priority according to a few of the priority rules (e.g., an sTTI CSI process received at an earlier time than a URLLC process), some of the priority rules (e.g., the type of CSI process) may supersede the others (e.g., the time the CSI process was received).

Additionally, as described herein, UE <NUM>-a may update Ny CSI processes across all CCs <NUM> within a subframe. UE <NUM>-a may similarly employ a set of priority rules for updating CSI processes over the frequency-domain. For example, UE <NUM>-a may update CSI processes in frequency according to a priority level associated with URLLC CSI processes, eMBB CSI processes, sTTI CSI processes, or the like; then according to when the CSI report request is received; then according to whether the CSI report request is aperiodic or periodic; and then a cell index and/or CSI process index. In another example, higher priority may be given to URLLC CSI processes over sTII or eMBB CSI processes. In some cases, Ny CSI processes may be prioritized according to UE implementation. Various combinations of priority levels for communication service priority type, time at which a CSI request was received, cell index, etc. may be considered without departing from the scope of the disclosure.

In some cases, UE <NUM>-a may update CSI processes in time and/or frequency according to the format of the downlink control information (DCI) associated with each CSI report request. For example, the DCI format associated with a first set of CSI processes to be reported may be determined to be at a priority higher than a DCI format associated with a second set of CSI processes. As such, the first set of CSI processes may be prioritized over the second set of CSI processes. In some cases, updating the CSI processes based on the format of the DCI may be included in the set of priority rules and may be used in place of or in conjunction with the type of communication associated with the CSI report request or any of the other priority rules.

In some cases, UE <NUM>-a may update CSI processes in time and/or frequency according to a trigger associated with a DCI associated with a set of CSI processes, such as a CSI request field. If the trigger has a value determined to have a priority higher than another trigger's value, the CSI processes associated with the DCI containing the higher priority trigger may be prioritized over CSI processes associated with the DCI containing the lower priority trigger value. In some cases, updating the CSI processes based on the trigger value may be included in the set of priority rules and may be used in place of or in conjunction with the type of communication associated with the CSI report request or any other priority rules.

In some cases, UE <NUM>-a may update CSI processes in time and/or frequency according to the BLER target of requested CSI processes. For example, a first CSI process may have a BLER target of <NUM>-<NUM> and a second CSI process may have a BLER target of <NUM>-<NUM>. In some cases, the CSI process with a BLER target of <NUM>-<NUM> may be prioritized over the CSI process with the BLER target of <NUM>-<NUM> (i.e., CSI processes with higher BLER target values may be targeted over those with lower BLER target values). In other cases, CSI processes with lower BLER target values may be prioritized over CSI processes with higher BLER target values. In some cases, updating the CSI processes based on the BLER target value may be included in the set of priority rules and may be used in place of or in conjunction with the type of communication associated with the CSI report request and/or any other priority rules.

In some cases, the capabilities may be separately indicated for each type of communication, but in pairs. For example, UE <NUM>-a may indicate the following list of capabilities: (the number of CSI processes to update for sTTI, the number of CSI processes to update for URLLC) = (<NUM>,<NUM>) and (<NUM>,<NUM>). In some cases, the URLLC CSI computation may be less computationally intensive or otherwise easier than sTTI. For example, if sTTI CSI processes is reduced by one, UE <NUM>-a may handle two (<NUM>) more URLLC CSI processes (e.g., decreasing the number of sTTI processes from three (<NUM>) to two (<NUM>) results in an increase in the number of URLLC CSI processes from five (<NUM>) to seven (<NUM>)). Each pair (X,Y) may signify that UE <NUM>-a may not go beyond Y number of CSI processes for URLLC while UE <NUM>-a processes X number of CSIs for sTTI. This scenario may be different from the case where the capability is a single value, and that single value could all be for sTTI or URLLC. Additionally, it may be different from the separate indication for each type of communication.

As an example, a first request may trigger CSI for five (<NUM>) sTTI CSI processes. UE <NUM>-a, with the pairs above, may support three (<NUM>) of triggered five (<NUM>) sTTI CSI processes and drop the other two (<NUM>) sTTI CSI processes. A subsequent request may trigger ten (<NUM>) URLLC CSI processes. UE <NUM>-a may keep the three (<NUM>) sTTI CSI processes and update up to five (<NUM>) URLLC CSI processes. Alternatively, UE <NUM>-a may drop one (<NUM>) sTTI CSI process from initially supported three (<NUM>) sTTI CSI processes and then support up to seven (<NUM>) URLLC CSI processes (i.e., (<NUM>,<NUM>)). According to the priority rules defined above, UE <NUM>-a may utilize the second approach (e.g., prioritize the URLLC CSI processes over the sTTI processes or prioritize the URLCC CSI processes over CSI processes associated with a lower priority DCI format, trigger, or BLER target value).

<FIG> illustrates an example of a CSI process timeline <NUM> that supports channel reporting for communication service priority types in accordance with various aspects of the present disclosure. In some examples, CSI process timeline <NUM> may implement aspects of wireless communications systems <NUM> and <NUM>. A base station <NUM> may request CSI reports associated with different types of communications at sTTI n and sTTI n + <NUM> from a UE <NUM>. As described herein, the UE <NUM> may employ a set of priority rules to determine which CSI processes to update before transmitting the CSI reports back to the base station <NUM> at sTTI n + <NUM> and sTTI n + <NUM>. While sTTI CSI processes and URLCC processes follow the same timeline in the present example, it should be noted that the timelines may be different in some implementations.

In the example of CSI process timeline <NUM>, the base station <NUM> may request three (<NUM>) sTTI CSI processes at sTTI n and five (<NUM>) URLLC CSI processes at sTTI n + <NUM>. The maximum number of CSI processes that the UE <NUM> may update across all CCs may be four (<NUM>) (i.e., Ny = <NUM>) and may be set jointly for both sTTI and URLLC operations (e.g., the UE <NUM> has a joint CSI update capability). The number of unreported CSI requests (Nu) may be defined as described herein (i.e., all unreported CSI processes associated with other requests up until an sTTI before the sTTI where the CSI is reported on a shortened PUSCH (sPUSCH)). For example, the second set of CSI processes requested at sTTI n + <NUM> should have corresponding CSI processes transmitted back to the base station <NUM> at sTTI n + <NUM>. Therefore, the number of unreported CSI requests may be counted until n + <NUM>. Since the unreported CSI processes are associated with other requests, the number of unreported CSI requests may be three (<NUM>) (i.e., Nu = <NUM>). Based on the priority rules described herein with reference to <FIG>, the UE <NUM> may give a higher priority to the URLLC CSI process requests. Out of the five (<NUM>) URLLC CSI processes requested at n + <NUM>, the UE <NUM> may update four (<NUM>) of them (i.e., Ny = <NUM>). The UE <NUM> may update the four (<NUM>) URLCC CSI processes associated with the lowest indexed CSI processes/cell index.

As such, the sTTI CSI processes and the remaining URLLC CSI process may not be updated and may be transmitted based on information initially or previously received for the CC associated with each CSI process. Additionally, if the processing of the sTTI CSI processes had started, the UE <NUM> may stop or drop the processing in favor of the URLLC CSI processes. Accordingly, the UE <NUM> may transmit the three (<NUM>) sTTI CSI processes at sTTI n + <NUM>, where the UE <NUM> may have not updated the CSI processes. At sTTI n + <NUM>, the UE <NUM> may transmit the four (<NUM>) updated URLLC CSI processes and the one (<NUM>) URLLC CSI process that was not updated.

<FIG> illustrates an example of a CSI process timeline <NUM> that supports channel reporting for communication service priority types in accordance with various aspects of the present disclosure. In some examples, CSI process timeline <NUM> may implement aspects of wireless communications systems <NUM> and <NUM>. A base station <NUM> may request CSI reports associated with different types of communications at sTTI n and sTTI n + <NUM> from a UE <NUM>. As described herein, the UE <NUM> may employ a set of priority rules to determine which CSI processes to update before transmitting the CSI reports back to the base station <NUM> at sTTI n + <NUM> and sTTI n + <NUM>.

In the example of CSI process timeline <NUM>, the base station <NUM> may request three (<NUM>) URLLC CSI processes at sTTI n and may further request two (<NUM>) eMBB CSI processes and three (<NUM>) URLLC CSI processes at sTTI n + <NUM>. The maximum number of CSI processes that the UE <NUM> may update across all CCs may be four (<NUM>) (i.e., Ny = <NUM>) and may be set jointly for both sTTI and URLLC operations (e.g., the UE <NUM> has a joint CSI update capability). The second set of CSI processes requested at sTTI n + <NUM> should have corresponding CSI processes transmitted back to the base station <NUM> at sTTI n + <NUM>. Therefore, the number of unreported CSI requests may be counted until n + <NUM>. Since the unreported CSI processes are associated with other requests, the number of unreported CSI requests may be three (<NUM>) (i.e., Nu = <NUM>). Based on the priority rules described herein with reference to <FIG>, the UE <NUM> may give a higher priority to the URLLC CSI process requests. Since there are six (<NUM>) total URLLC CSI processes to be updated and the maximum number of CSI processes that the UE <NUM> may update is four (<NUM>), the UE <NUM> may update four (<NUM>) of the six (<NUM>) URLLC CSI processes. Based on the priority rule described herein with reference to <FIG>, for the same type of CSI process, the CSI processes triggered or requested earlier will take precedence. Therefore, the first three (<NUM>) URLLC processes requested at sTTI n may be updated, and out of the three (<NUM>) URLLC processes requested at sTTI n + <NUM>, the URLLC CSI process with the lowest-indexed CSI process may be updated.

A such, the eMBB CSI processes and the remaining URLLC CSI process that was not updated may be transmitted based on information initially or previously received for the CC associated with each CSI process. Accordingly, the UE <NUM> may transmit the three (<NUM>) updated URLLC CSI processes at sTTI n + <NUM>. At sTTI n + <NUM>, the UE <NUM> may transmit the one (<NUM>) updated URLLC CSI process, the remaining two (<NUM>) URLLC CSI processes that were not updated, and the two (<NUM>) eMBB CSI processes that were not updated.

<FIG> illustrates an example of a process flow <NUM> that supports channel reporting for communication service priority types in accordance with various aspects of the present disclosure. In some examples, process flow <NUM> may implement aspects of wireless communications systems <NUM> and <NUM>. Process flow <NUM> illustrates aspects of techniques performed by a base station <NUM>-b and a UE <NUM>-b, which may be examples of a base station <NUM> and a UE <NUM> as described with reference to <FIG>. In some cases, UE <NUM>-b may support communications of a first service priority type (e.g., a first priority type of communications) and a second service priority type (e.g., a second priority type of communication). In some cases, the first service priority type may include an URLLC priority service, a sTTI priority service, or an eMBB priority service, and the second service priority type is different than the first service priority type.

In the following description of the process flow <NUM>, the operations between UE <NUM>-b and base station <NUM>-b may be performed in different orders or at different times. Certain operations may also be left out of the process flow <NUM>, or other operations may be added to the process flow <NUM>. It is to be understood that while a UE <NUM> is shown performing a number of the operations of process flow <NUM>, any transmitting device may perform the operations shown.

At <NUM>, UE <NUM>-b may report a joint CSI update capability associated with both the first and second service priority types. In some examples, a CSI update capability for UE <NUM>-b may be separately reported for each type of communication in pairs, as described herein. For instance, UE <NUM>-b may indicate the following list of capabilities: (the number of CSI processes to update for sTTI, the number of CSI processes to update for URLLC) = (<NUM>,<NUM>) and (<NUM>,<NUM>). In some cases, the URLLC CSI computation may be less computationally intensive or otherwise easier than sTTI. For example, if sTTI CSI processes is reduced by one, UE <NUM>-b may handle up to two (<NUM>) more URLLC CSI processes (e.g., decreasing the number of sTTI processes from three (<NUM>) to two (<NUM>) results in an increase in the number of URLLC CSI processes from five (<NUM>) to seven (<NUM>)). In some cases, the joint CSI update capability may indicate a number of CSI update processes supported by UE <NUM>-b per serving cell. Additionally or alternatively, the joint CSI update capability may indicate a number of CSI processes across multiple CCs capable of being updated by UE <NUM>-b.

At <NUM>, UE <NUM>- b may receive multiple CSI process requests from base station <NUM>-b. For example, UE <NUM>-b may receive a first CSI request associated with the first service priority type, where a first CSI process of the one or more CSI processes is updated in response to the first CSI request; a second CSI request associated with the second service priority type, where a second CSI process of the one or more CSI processes is updated in response to the second CSI request; and a third CSI request associated with the first service priority type, where updating the CSI for the one or more CSI processes includes canceling a CSI update for the second CSI process and performing a CSI update for a third CSI process based on a set of priority rules and the joint CSI update capability.

At <NUM>, UE <NUM>-b may prioritize one or more CSI processes of the first service priority type or the second service priority type based on a set of priority rules and the joint CSI update capability. In some cases, UE <NUM>-b may prioritize a CSI process associated with an URLLC priority service type over a CSI process associated with a sTTI priority service type in accordance with the set of priority rules. Additionally or alternatively, UE <NUM>-b may prioritize a CSI process associated with an URLLC priority service type over a CSI process associated with an eMBB priority service type in accordance with the set of priority rules. In some cases, UE <NUM>-b may further prioritize a CSI process associated with an earlier received CSI request over a CSI process associated with a later received CSI request in accordance with the set of priority rules. Additionally, UE <NUM>-b may prioritize a CSI process associated with an aperiodic CSI request over a CSI process associated with a periodic CSI request in accordance with the set of priority rules. UE <NUM>-b may further prioritize a CSI process associated with a lower cell index over a CSI process associated with a higher cell index in accordance with the set of priority rules. Additionally or alternatively, UE <NUM>-b may prioritize a CSI process associated with a lower CSI process index over a CSI process associated with a higher CSI process index in accordance with the set of priority rules. Additionally or alternatively, UE <NUM>-b may prioritize a CSI process associated with a first DCI format over a CSI process associated with a second DCI format different from the first DCI format in accordance with the set of priority rules. Additionally or alternatively, UE <NUM>-b may prioritize a CSI process associated with a first BLER target value over a CSI process associated with a second BLER target value different from the first BLER target value in accordance with the set of priority rules,.

At <NUM>, UE <NUM>-b may update CSI for the one or more CSI processes based on the prioritization of the one or more CSI processes. In some cases, UE <NUM>-b may update fewer than all of the one or more CSI processes based on the prioritization of the one or more CSI processes and the joint CSI update capability. Additionally, UE <NUM>-b may perform a CSI update for the first CSI process before performing a CSI update for the second CSI process based on the set of priority rules. In some examples, the one or more CSI processes may correspond to respective CCs of a primary cell or a secondary cell.

At <NUM>, UE <NUM>-b may report the updated CSI. In some cases, reporting the updating CSI may include transmitting a CSI feedback message via a PUSCH or a PUCCH. Additionally, reporting the updating CSI may include reporting respective CSI feedback messages for each of a plurality of CCs. In some cases, the updated CSI may be reported based on respective transmission modes associated with the one or more CSI processes. The reported CSI may include CSI that has been updated at <NUM>, as well as CSI that has not been updated as a result of the prioritization decisions made at <NUM>.

<FIG> shows a block diagram <NUM> of a wireless device <NUM> that supports channel reporting for communication service priority types in accordance with aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a UE <NUM> as described herein. Wireless device <NUM> may include receiver <NUM>, communications manager <NUM>, and transmitter <NUM>. Wireless 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).

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 channel reporting for communication service priority types, etc.). Information may be passed on to other components of the device. 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.

Communications manager <NUM> may be an example of aspects of the communications manager <NUM> described with reference to <FIG>. Communications manager <NUM> and/or at least some of its various sub-components may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions of the communications manager <NUM> and/or at least some of its various sub-components may be executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), an 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 in the present disclosure.

The communications manager <NUM> and/or at least some of its various sub-components may be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations by one or more physical devices. In some examples, communications manager <NUM> and/or at least some of its various sub-components may be a separate and distinct component in accordance with various aspects of the present disclosure. In other examples, communications manager <NUM> and/or at least some of its various sub-components may be combined with one or more other hardware components, including but not limited to an I/O component, a transceiver, a network server, another computing device, one or more other components described in the present disclosure, or a combination thereof in accordance with various aspects of the present disclosure.

Communications manager <NUM> may identify that a UE <NUM> supports communications of a first service priority type and a second service priority type and may report a CSI update capability associated with both the first and second service priority types. Communications manager <NUM> may prioritize one or more CSI processes of the first service priority type, the second service priority type, or both based on a set of priority rules and the CSI update capability. Communications manager <NUM> may update CSI for the one or more CSI processes based on the prioritization of the one or more CSI processes and may report the updated CSI.

<FIG> shows a block diagram <NUM> of a wireless device <NUM> that supports channel reporting for communication service priority types in accordance with aspects of the present disclosure. Wireless device <NUM> may be an example of aspects of a wireless device <NUM> or a UE <NUM> as described with reference to <FIG>. Wireless device <NUM> may include receiver <NUM>, communications manager <NUM>, and transmitter <NUM>. Wireless 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).

Communications manager <NUM> may be an example of aspects of the communications manager <NUM> described with reference to <FIG>. Communications manager <NUM> may also include service identifier <NUM>, capability component <NUM>, prioritization component <NUM>, CSI update component <NUM>, and reporting component <NUM>.

Service identifier <NUM> may identify that a UE <NUM> supports communications of a first service priority type and a second service priority type. In some cases, the first service priority type includes a URLLC priority service, an sTTI priority service, or an eMBB priority service and the second service priority type is different than the first service priority type.

Capability component <NUM> may report a CSI update capability associated with both the first and second service priority types. In some examples, reporting the CSI update capability includes reporting a pair of CSI update capabilities, each corresponding to a respective one of the first service priority type and the second service priority type. In some aspects, the CSI update capability indicates a number of CSI update processes supported by the UE <NUM> per serving cell. In some cases, the CSI update capability indicates a number of CSI processes across multiple CCs capable of being updated by the UE <NUM>. In some examples of the method, apparatus, and non-transitory computer-readable medium described herein, the CSI update capability may be a joint CSI update capability.

Prioritization component <NUM> may prioritize one or more CSI processes of the first service priority type, the second service priority type, or both based on a set of priority rules and the CSI update capability. In some examples, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a URLLC priority service type over a CSI process associated with an sTTI priority service type in accordance with the set of priority rules. In some aspects, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a URLLC priority service type over a CSI process associated with an eMBB priority service type in accordance with the set of priority rules. In some instances, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with an earlier received CSI request over a CSI process associated with a later received CSI request in accordance with the set of priority rules.

In some cases, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with an aperiodic CSI request over a CSI process associated with a periodic CSI request in accordance with the set of priority rules. In some examples, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a lower cell index over a CSI process associated with a higher cell index in accordance with the set of priority rules. In some instances, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a lower CSI process index over a CSI process associated with a higher CSI process index in accordance with the set of priority rules. In some aspects, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a first DCI format over a CSI process associated with a second DCI format different from the first DCI format in accordance with the set of priority rules. In some cases, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a first BLER target value over a CSI process associated with a second BLER target value different from the first BLER target value in accordance with the set of priority rules.

CSI update component <NUM> may update CSI for the one or more CSI processes based on the prioritization of the one or more CSI processes. In some examples, updating CSI for the one or more CSI processes includes: updating fewer than all of the one or more CSI processes based on the prioritization of the one or more CSI processes and the CSI update capability. In some aspects, updating CSI for the one or more CSI processes includes: performing a CSI update for the first CSI process before performing a CSI update for the second CSI process based on the set of priority rules. In some cases, the updated CSI is reported based on respective transmission modes associated with the one or more CSI processes. In some instances, the one or more CSI processes correspond to respective CCs of a primary cell or a secondary cell.

Reporting component <NUM> may report the updated CSI. In some cases, reporting the updated CSI includes: reporting a previously determined CSI of at least one of the one or more CSI processes based on the CSI update capability. In some cases, reporting the updated CSI includes: transmitting a CSI feedback message via a PUSCH or a PUCCH. In some cases, reporting the updated CSI includes: reporting respective CSI feedback messages for each of a set of CCs.

<FIG> shows a block diagram <NUM> of a communications manager <NUM> that supports channel reporting for communication service priority types 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 with reference to <FIG>, <FIG>, and <FIG>. The communications manager <NUM> may include service identifier <NUM>, capability component <NUM>, prioritization component <NUM>, CSI update component <NUM>, reporting component <NUM>, and request component <NUM>. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

Capability component <NUM> may report a CSI update capability associated with both the first and second service priority types. In some cases, reporting the CSI update capability includes reporting a pair of CSI update capabilities, each corresponding to a respective one of the first service priority type and the second service priority type. In some examples, the CSI update capability indicates a number of CSI update processes supported by the UE <NUM> per serving cell. In some instances, the CSI update capability indicates a number of CSI processes across multiple CCs capable of being updated by the UE <NUM>.

Prioritization component <NUM> may prioritize one or more CSI processes of the first service priority type, the second service priority type, or both based on a set of priority rules and the CSI update capability. In some cases, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a URLLC priority service type over a CSI process associated with an sTTI priority service type in accordance with the set of priority rules. In some examples, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a URLLC priority service type over a CSI process associated with an eMBB priority service type in accordance with the set of priority rules. In some aspects, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with an earlier received CSI request over a CSI process associated with a later received CSI request in accordance with the set of priority rules. In some instances, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with an aperiodic CSI request over a CSI process associated with a periodic CSI request in accordance with the set of priority rules.

In some cases, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a lower cell index over a CSI process associated with a higher cell index in accordance with the set of priority rules. In some examples, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a lower CSI process index over a CSI process associated with a higher CSI process index in accordance with the set of priority rules. In some aspects, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a first DCI format over a CSI process associated with a second DCI format different from the first DCI format in accordance with the set of priority rules. In some instances, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a first BLER target value over a CSI process associated with a second BLER target value different from the first BLER target value in accordance with the set of priority rules,. In some cases, prioritizing the one or more CSI processes includes: prioritizing a CSI process associated with a later received CSI request and a higher priority service type over a CSI process associated with an earlier received CSI request and a lower priority service type.

CSI update component <NUM> may update CSI for the one or more CSI processes based on the prioritization of the one or more CSI processes. In some cases, updating CSI for the one or more CSI processes includes: updating fewer than all of the one or more CSI processes based on the prioritization of the one or more CSI processes and the CSI update capability. In some examples, updating CSI for the one or more CSI processes includes: performing a CSI update for the first CSI process before performing a CSI update for the second CSI process based on the set of priority rules. In some aspects, the updated CSI is reported based on respective transmission modes associated with the one or more CSI processes. In some instances, the one or more CSI processes correspond to respective CCs of a primary cell or a secondary cell.

Reporting component <NUM> may report the updated CSI. In some cases, reporting the updated CSI includes: reporting a previously determined CSI of at least one of the one or more CSI processes based on the CSI update capability. In some examples, reporting the updated CSI includes: transmitting a CSI feedback message via a PUSCH or a PUCCH. In some instances, reporting the updated CSI includes: reporting respective CSI feedback messages for each of a set of CCs.

Request component <NUM> may receive a first CSI request associated with the first service priority type, where a first CSI process of the one or more CSI processes is updated in response to the first CSI request and receive a second CSI request associated with the second service priority type, where a second CSI process of the one or more CSI processes is updated in response to the second CSI request. Request component <NUM> may receive a third CSI request associated with the first service priority type, where updating the CSI for the one or more CSI processes includes canceling a CSI update for the second CSI process and performing a CSI update for a third CSI process based on the set of priority rules and the CSI update capability.

<FIG> shows a diagram of a system <NUM> including a device <NUM> that supports channel reporting for communication service priority types in accordance with aspects of the present disclosure. Device <NUM> may be an example of or include the components of wireless device <NUM>, wireless device <NUM>, or a UE <NUM> as described above, e.g., with reference to <FIG> and <FIG>. Device <NUM> may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including communications manager <NUM>, processor <NUM>, memory <NUM>, software <NUM>, transceiver <NUM>, antenna <NUM>, and I/O controller <NUM>. These components may be in electronic communication via one or more buses (e.g., bus <NUM>). Device <NUM> may communicate wirelessly with one or more base stations <NUM>.

Processor <NUM> may include an intelligent hardware device, (e.g., a general-purpose processor, a DSP, a central processing unit (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, processor <NUM> may be configured to operate a memory array using a memory controller. In other cases, a memory controller may be integrated into processor <NUM>. Processor <NUM> may be configured to execute computer-readable instructions stored in a memory to perform various functions (e.g., functions or tasks supporting channel reporting for communication service priority types).

Software <NUM> may include code to implement aspects of the present disclosure, including code to support channel reporting for communication service priority types. Software <NUM> may be stored in a non-transitory computer-readable medium such as system memory or other memory. In some cases, the software <NUM> may not be directly executable by the processor but may cause a computer (e.g., when compiled and executed) to perform functions described herein.

The wireless device may include a single antenna <NUM>.

<FIG> shows a flowchart illustrating a method <NUM> for channel reporting for communication service priority types 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 <NUM> may execute a set of codes to control the functional elements of the device to perform the functions described below. Additionally or alternatively, the UE <NUM> may perform aspects of the functions described below using special-purpose hardware.

At <NUM> the UE <NUM> may identify that a UE <NUM> supports communications of a first service priority type and a second service priority type. The operations of <NUM> may be performed according to the methods described herein. In certain examples, aspects of the operations of <NUM> may be performed by a service identifier as described with reference to <FIG>.

At <NUM> the UE <NUM> may report a CSI update capability associated with both the first and second service priority types. The operations of <NUM> may be performed according to the methods described herein. In certain examples, aspects of the operations of <NUM> may be performed by a capability component as described with reference to <FIG>.

At <NUM> the UE <NUM> may prioritize one or more CSI processes of the first service priority type, the second service priority type, or both based at least in part on a set of priority rules and the CSI update capability. The operations of <NUM> may be performed according to the methods described herein. In certain examples, aspects of the operations of <NUM> may be performed by a prioritization component as described with reference to <FIG>.

At <NUM> the UE <NUM> may update CSI for the one or more CSI processes based at least in part on the prioritization of the one or more CSI processes. The operations of <NUM> may be performed according to the methods described herein. In certain examples, aspects of the operations of <NUM> may be performed by a CSI update component as described with reference to <FIG>.

At <NUM>, the UE <NUM> may report the updated CSI. The operations of <NUM> may be performed according to the methods described herein. In certain examples, aspects of the operations of <NUM> may be performed by a reporting component as described with reference to <FIG>.

An eNB may support one or multiple (e.g., two, three, four, and the like) cells, and may also support communications using one or multiple CCs.

The wireless communications systems <NUM> or <NUM>, or systems described herein may support synchronous or asynchronous operation.

By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable read only memory (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.

Claim 1:
A method (<NUM>) at a user equipment for wireless communications, the method (<NUM>) comprising:
identifying (<NUM>) that a user equipment, UE, supports communications of a first service priority type and a second service priority type, wherein the first service priority type is different to the second priority type;
reporting (<NUM>) a joint channel state information, CSI, update capability comprising a maximum number of CSI processes capable of being performed by the UE for both the first and second service priority types combined;
receiving a first CSI request associated with the first service priority type and a second CSI request associated with the second service priority type;
prioritizing (<NUM>), when a number of CSI processes comprising a first CSI process associated with the first CSI request and a second CSI process associated with the second CSI request to update exceeds the maximum number of CSI processes capable of being performed by the UE, the first CSI process of the first service priority type over the second CSI process of the second service priority type in accordance with a set of priority rules associated with the first and second service priority types and the joint CSI update capability;
updating (<NUM>) CSI for at least the first CSI process associated with the first service priority type in accordance with the prioritization of the first CSI process associated with the first service priority type over the second CSI process associated with the second service priority type; and
reporting (<NUM>) the updated CSI.