Downlink-triggered channel state information reporting for semi-persistent scheduling

Abstract

Systems, methods, and apparatus for wireless communication are described. A user equipment (UE) can determine a channel state reporting configuration for one or more semi-persistent scheduling (SPS) configurations used for communicating with a base station. For example, different channel state reporting configurations can be configured for the UE within an SPS configuration. Additionally, downlink control information (DCI) associated with the SPS configuration can be used to activate the channel state reporting configuration. In some cases, different channel state reporting configurations can be configured for an SPS configuration, and the DCI can include bit fields to indicate which channel state reporting configuration is activated for the SPS configuration. Furthermore, if the DCI indicates a release of the SPS configuration, the UE can avoid sending a channel state report along with an acknowledgment feedback confirming the release.

Description

Technical Field

[0001] In general, the following relates to wireless communication, and more specifically, to downlink-triggered Channel State Information (CSI) reporting for semi-persistent scheduling (SPS). Background Technology

[0002] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcasting. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (e.g., Long Term Evolution (LTE) systems, improved LTE (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems can 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 Spectrum Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations or one or more network access nodes, each base station or network access node simultaneously supporting communication with multiple communication devices (which may also be referred to as User Equipment (UE)).

[0003] In some wireless communication systems, communication between a base station and a UE can be transmitted according to an SPS configuration. For example, the SPS configuration may include periodic downlink messages transmitted by the base station on a downlink channel every "X" time slots (e.g., each time slot, each second time slot, each fourth time slot, etc.). Subsequently, after receiving the periodic downlink messages, the UE may send an acknowledgment feedback on an uplink channel (e.g., on time-frequency resources configured by the base station, such as in the next occurring time slot, two time slots later, etc.), where the acknowledgment feedback indicates whether the UE has successfully received and decoded the periodic downlink messages. An efficient technique is desired for transmitting acknowledgment feedback for periodic downlink messages received according to the SPS configuration. Summary of the Invention

[0004] The described technology relates to improved methods, systems, devices, and apparatuses for supporting downlink-triggered Channel State Information (CSI) reporting for Semi-Persistent Scheduling (SPS). Typically, the described technology provides a User Equipment (UE) receiving an SPS configuration from a base station to receive subsequent periodic downlink traffic. In some cases, the UE may subsequently receive Activation Downlink Control Information (DCI) to activate the SPS configuration. Subsequently, based on the SPS configuration, the Activation DCI, or both, the UE may determine a Channel State Report (e.g., Channel State Information (CSI) or Channel Quality Indication (CQI) report) configuration for the SPS configuration and may transmit a Channel State Report to the base station according to the Channel State Report configuration, wherein the Channel State Report includes information about the downlink channels received from the base station as part of the SPS configuration.

[0005] In some cases, the UE can determine the channel state report configuration based on an indication in the SPS configuration of the channel state report, so that the UE can transmit for that SPS configuration. Alternatively or additionally, the UE can determine the channel state report configuration based on an indication in the active DCI of the channel state report, so that the UE can transmit for the active SPS configuration. The channel state report configuration can include different types so that the UE can transmit a channel state report with acknowledgment feedback for the downlink channel, regardless of whether the acknowledgment feedback is positive (e.g., a positive acknowledgment (ACK) feedback message) or negative (e.g., a negative acknowledgment (NACK) feedback message), or so that the UE only transmits a channel state report when the acknowledgment feedback for the downlink channel is negative. Additionally, the UE can receive multiple SP configurations, where each SPS configuration includes a channel state report configuration specific to that SPS configuration (e.g., indicated in the corresponding SPS configuration, in the active DCI, etc.).

[0006] A method for wireless communication at a UE is described. The method may include: receiving an SPS configuration for the UE from a base station; receiving a DCI for activating the SPS configuration from the base station; determining a channel state report configuration for the SPS configuration based on the DCI, the SPS configuration, or both; and sending a channel state report to the base station and according to the channel state report configuration for a downlink shared channel received according to the SPS configuration.

[0007] An apparatus for wireless communication at a UE is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: receive an SPS configuration for the UE from a base station; receive a DCI for activating the SPS configuration from the base station; determine a channel state report configuration for the SPS configuration based on the DCI, the SPS configuration, or both; and send a channel state report to the base station and, according to the channel state report configuration, for a downlink shared channel received according to the SPS configuration.

[0008] Another apparatus for wireless communication at a UE is described. The apparatus may include: a unit for receiving an SPS configuration for the UE from a base station; a unit for receiving a DCI for activating the SPS configuration from the base station; a unit for determining a channel state report configuration for the SPS configuration based on the DCI, the SPS configuration, or both; and a unit for sending a channel state report to the base station and, according to the channel state report configuration, for a downlink shared channel received according to the SPS configuration.

[0009] A non-transitory computer-readable medium is described, storing code for wireless communication at a UE. The code may include instructions executable by a processor to: receive an SPS configuration for the UE from a base station; receive a DCI from the base station to activate the SPS configuration; determine a channel state report configuration for the SPS configuration based on the DCI, the SPS configuration, or both; and send a channel state report to the base station and, according to the channel state report configuration, for a downlink shared channel received according to the SPS configuration.

[0010] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving a downlink shared channel from a base station according to an SPS configuration, wherein the downlink shared channel is indicated by a DCI; determining an acknowledgment feedback for the downlink shared channel, the acknowledgment feedback being at least partially based on an attempt to decode the downlink shared channel; and sending the acknowledgment feedback for the downlink shared channel to the base station, wherein the acknowledgment feedback may be sent together with a channel state report.

[0011] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, determining the channel state configuration for the SPS configuration may include operations, features, elements, or instructions for: identifying the SPS configuration as including an indication of a channel state reporting configuration in a set of channel state reporting configurations; and determining, at least in part based on the reception of the DCI, that the channel state reporting configuration may be a channel state reporting configuration in a set of channel state reporting configurations.

[0012] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, channel state reports and acknowledgments for the downlink shared channel can be sent together, regardless of whether the UE successfully decodes the downlink shared channel.

[0013] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, when the UE fails to decode the downlink shared channel, a channel state report and acknowledgment feedback for the downlink shared channel can be sent together.

[0014] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, determining the channel state configuration for the SPS configuration may include operations, features, elements, or instructions for: identifying the DCI including an indication of a channel state report configuration in a set of channel state report configurations, wherein the channel state report configuration is a channel state report configuration in the set of channel state report configurations indicated by the DCI.

[0015] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, the indication in the DCI may include a bit field for activating a channel state reporting configuration included in an SPS configuration, wherein the SPS configuration includes one or more channel state reporting configurations.

[0016] In some examples of the methods, apparatus, or non-transitory computer-readable media described herein, an SPS configuration may include multiple SPS configurations, wherein the indication in the DCI includes a multi-bit field indicating the corresponding channel state report configuration for each of the multiple SPS configurations.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: receiving an additional DCI indicating that the SPS configuration will be released, the additional DCI including a bit field indicating the channel state report configuration; and avoiding future transmissions of channel state reports based at least in part on the reception of the additional DCI.

[0018] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the bit field may include a predetermined value for indicating the release of the SPS configuration.

[0019] In some examples of the methods, apparatus, or non-transitory computer-readable media described herein, SPS configuration may include a set of configuration parameters: time resources, frequency resources, modulation and coding schemes (MCS), or combinations thereof, for SPS configuration.

[0020] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, the SPS configuration may include a set of SPS configurations, and the DCI may be associated with one or more SPS configurations in the set of SPS configurations.

[0021] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, one or more SPS configurations may be single-carrier configurations for the UE.

[0022] A method for wireless communication at a base station is described. The method may include: sending an SPS configuration for communication with a UE; sending a DCI to the UE to activate the SPS configuration, wherein the DCI activates a channel state report configuration for the SPS configuration; and receiving a channel state report from the UE, and according to the channel state report configuration, for a downlink shared channel received according to the SPS configuration.

[0023] An apparatus for wireless communication at a base station is described. The apparatus may include: a processor; a memory coupled to the processor; and instructions stored in the memory. The instructions are executable by the processor to cause the apparatus to: send an SPS configuration for communication with a UE; send a DCI to the UE to activate the SPS configuration, wherein the DCI activates a channel state report configuration for the SPS configuration; and receive a channel state report from the UE, and according to the channel state report configuration, for a downlink shared channel received according to the SPS configuration.

[0024] Another apparatus for wireless communication at a base station is described. The apparatus may include: a unit for transmitting an SPS configuration for communication with a UE; a unit for transmitting a DCI to the UE for activating the SPS configuration, wherein the DCI activates a channel state report configuration for the SPS configuration; and a unit for receiving a channel state report from the UE and according to the channel state report configuration for a downlink shared channel received according to the SPS configuration.

[0025] A non-transitory computer-readable medium is described, storing code for wireless communication at a base station. The code may include instructions executable by a processor to perform the following operations: sending an SPS configuration for communication with a UE; sending a DCI to the UE to activate the SPS configuration, wherein the DCI activates a channel state report configuration for the SPS configuration; and receiving a channel state report from the UE, and according to the channel state report configuration, for a downlink shared channel received according to the SPS configuration.

[0026] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: transmitting a downlink shared channel to a UE according to an SPS configuration, wherein the downlink shared channel may be indicated by a DCI; and receiving acknowledgment feedback from the UE for the downlink shared channel, wherein the acknowledgment feedback may be received together with a channel state report.

[0027] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending an instruction to the UE using an SPS configuration for a channel state report configuration set, wherein the channel state report configuration is a channel state report configuration in the channel state report configuration set.

[0028] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, channel state reports and acknowledgments for the downlink shared channel can be received together, regardless of whether the UE successfully decodes the downlink shared channel.

[0029] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, when the UE fails to decode the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel can be received together.

[0030] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for sending an indication to the UE in the DCI to a channel state report configuration set, wherein the channel state report configuration may be a channel state report configuration indicated by the DCI in the channel state report configuration set.

[0031] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, the indication in the DCI may include a bit field for activating a channel state reporting configuration included in an SPS configuration, wherein the SPS configuration includes one or more channel state reporting configurations.

[0032] In some examples of the methods, apparatus, or non-transitory computer-readable media described herein, an SPS configuration may include multiple SPS configurations, and wherein the indication in the DCI includes a multi-bit field indicating a corresponding channel state report configuration for each of the multiple SPS configurations.

[0033] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, units, or instructions for: sending an additional DCI to the UE to indicate that the SPS configuration is to be released, the additional DCI including a bit field for indicating the channel state report configuration, wherein, based on the additional DCI, no channel state report will be received in future transmissions from the UE.

[0034] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, bit fields may include predetermined values ​​for indicating the release of SPS configuration.

[0035] In some examples of the methods, apparatus, or non-transitory computer-readable media described herein, SPS configuration may include the following set of configuration parameters: time resources, frequency resources, MCS, or combinations thereof for SPS configuration.

[0036] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, the SPS configuration may include a set of SPS configurations, and the DCI may be associated with one or more SPS configurations in the set of SPS configurations.

[0037] In some examples of the methods, apparatuses, or non-transitory computer-readable media described herein, one or more SPS configurations may be single-carrier configurations for the UE. Attached Figure Description

[0038] Figure 1 An example of a system for supporting downlink-triggered channel state information (CSI) reporting for semi-persistent scheduling (SPS) is shown, according to aspects of this disclosure.

[0039] Figure 2 An example of a confirmation feedback configuration for a downlink-triggered CSI report for SPS, based on aspects of this disclosure, is shown.

[0040] Figure 3 An example of a wireless communication system that supports downlink-triggered CSI reporting for SPS is shown, according to aspects of this disclosure.

[0041] Figure 4An example of a process flow supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown.

[0042] Figure 5 and Figure 6 A block diagram of a device supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown.

[0043] Figure 7 A block diagram of a user equipment (UE) communications manager supporting downlink-triggered CSI reporting for SPS is shown, according to aspects of this disclosure.

[0044] Figure 8 A diagram of a system including a device supporting downlink-triggered CSI reporting for SPS is shown, according to aspects of this disclosure.

[0045] Figure 9 and Figure 10 A block diagram of a device supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown.

[0046] Figure 11 A block diagram of a base station communication manager supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown.

[0047] Figure 12 A diagram of a system including a device supporting downlink-triggered CSI reporting for SPS is shown, according to aspects of this disclosure.

[0048] Figures 13 to 17 A flowchart illustrating a method for supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. Detailed Implementation

[0049] In some wireless communication systems, a base station can configure a User Equipment (UE) to receive periodic downlink traffic according to a semi-persistent scheduling (SPS) configuration and send acknowledgment feedback for that periodic downlink traffic. For example, the SPS configuration may include periodic downlink messages sent by the base station every “X” time slots (e.g., every time slot, every second time slot, every fourth time slot, etc.) on the Physical Downlink Shared Channel (PDSCH). Subsequently, the UE may send acknowledgment feedback on the Physical Uplink Control Channel (PUCCH) after receiving the periodic downlink messages (e.g., on time-frequency resources configured by the base station, such as in the next occurring time slot, after two time slots, etc.). Conventionally, for acknowledgment feedback reports, when a negative acknowledgment (NACK) is received from the UE, the base station may make one or more adjustments to the retransmission of the periodic downlink messages. However, these adjustments may be slow because the base station does not know how to adjust the retransmissions to increase the UE's chances of receiving and decoding the periodic downlink messages (e.g., utilizing the retransmission). For example, the base station may make overly conservative or overly extreme adjustments to the retransmission of periodic downlink messages, such that the UE is still unable to decode the retransmission (e.g., overly conservative) or uses unnecessary resources for retransmission (e.g., overly extreme).

[0050] To better indicate how the transmission / retransmission of periodic downlink messages should be adjusted, the UE can send Channel State Information (CSI) and / or Channel Quality Indicator (CQI) feedback for previously received periodic downlink messages, allowing the base station to identify which adjustments need to be made (e.g., increasing the modulation and coding scheme (MCS) by a certain amount, increasing the time / frequency resources used, etc.). In some cases, the UE can be configured to send CSI / CQI feedback along with acknowledgment feedback according to different reporting modes. For example, a first reporting mode (e.g., type 1) may include the UE reporting CSI / CQI feedback with each acknowledgment, regardless of whether the periodic downlink message was successfully received and decoded. Alternatively, a second reporting mode (e.g., type 2) may include the UE reporting CSI / CQI feedback when sending a NACK for a received periodic downlink message. However, when the UE is configured with an SPS configuration for communicating with the base station, the UE may not know which reporting mode to use when sending CSI / CQI information with acknowledgment feedback. Additionally, the UE can be configured with more than one SPS configuration.

[0051] The techniques described herein allow for indicating and activating CSI / CQI reporting configurations for each SPS configuration of the UE. For each SPS configuration, a first or second reporting mode (e.g., a Type 1 or Type 2 downlink CSI / CQI triggering configuration) can be configured for the UE within the SPS configuration to trigger the CSI / CQI reporting configuration. The base station can then activate the CSI / CQI reporting configuration using Activated Downlink Control Information (DCI) associated with the SPS configuration. Alternatively, for each SPS configuration, a first reporting mode, a second reporting mode, both reporting modes, or neither reporting mode can be configured to trigger the CSI / CQI reporting configuration, and activating the DCI can include a bit field indicating which CSI configuration is actually activated. The above techniques can be used for a single SPS configuration or multiple SPS configurations. Furthermore, if the DCI (e.g., a subsequent DCI that supplements or replaces the activating DCI) indicates a release of the SPS configuration, the UE can avoid sending a CSI / CQI report with a positive acknowledgment (ACK) feedback confirming the release.

[0052] First, various aspects of this disclosure are described within the context of a wireless communication system. Furthermore, aspects of this disclosure are illustrated by confirming feedback configuration, additional wireless communication systems, and process flows. Various aspects of this disclosure are further illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to downlink-triggered CSI reporting for SPS.

[0053] Figure 1 An example of a wireless communication system 100 for supporting downlink-triggered channel state information reporting for semi-persistent scheduling, according to aspects of this disclosure, is shown. The wireless communication system 100 may include one or more base stations 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an improved LTE (LTE-A) network, an LTE-A Pro network, or a New Radio (NR) network. In some examples, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication with low-cost and low-complexity devices, or any combination thereof.

[0054] Base stations 105 can be distributed throughout a geographical area to form a wireless communication system 100, and can be devices of different forms or with different capabilities. Base stations 105 and UE 115 can communicate wirelessly via one or more communication links 125. Each base station 105 can provide a coverage area 110, on which UE 115 and base station 105 can establish one or more communication links 125. Coverage area 110 can be an example of a geographical area where base station 105 and UE 115 can support signal transmission according to one or more wireless access technologies.

[0055] UE 115 can be distributed throughout the entire coverage area 110 of the wireless communication system 100, and each UE 115 can be stationary, mobile, or both at different times. UE 115 can be devices of different forms or with different capabilities. Figure 1 Some example UE 115s are shown in the document. The UE 115 described herein is capable of communicating with various types of devices, such as other UE 115s, base station 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), such as... Figure 1 As shown.

[0056] Base station 105 can communicate with core network 130, communicate with each other, or perform both operations. For example, base station 105 can interface with core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). Base station 105 can communicate directly (e.g., directly between base stations 105) on backhaul links 120 (e.g., via X2, Xn, or other interfaces), or indirectly (e.g., via core network 130), or perform both operations. In some examples, backhaul link 120 can be one or more radio links or may include one or more radio links.

[0057] One or more of the base stations 105 described herein may include, or may be referred to by those skilled in the art as, a base station transceiver, a wireless base station, an access point, a wireless transceiver, a node B, an evolved node B (eNB), a next-generation node B or a gigabit node B (any of which may be referred to as gNB), a home node B, a home evolved node B, or some other suitable term.

[0058] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or user equipment, or some other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, and other examples. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, among others, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, which, among other examples, may be implemented in various objects such as electrical appliances, vehicles, or instruments.

[0059] The UE 115 described herein is capable of communicating with various types of devices, such as other UEs 115 that can sometimes act as repeaters, as well as base station 105 and network devices, including, among other examples, macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, such as... Figure 1 As shown in the image.

[0060] UE 115 and base station 105 can communicate wirelessly with each other via one or more communication links 125 on one or more carriers. The term "carrier" refers to a set of radio frequency spectrum resources having a defined physical layer structure for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth portion (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating the operation of the carrier, user data, or other signaling. Wireless communication system 100 can support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 can be configured with multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation can be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

[0061] In some examples (e.g., in a carrier aggregation configuration), the carrier may also have acquisition or control signaling for coordinating the operation of other carriers. The carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute Radio Frequency Channel Number (EARFCN)) and may be positioned according to a channel grid for discovery by UE 115. The carrier may operate in standalone mode, where UE 115 may perform initial acquisition and connection via the carrier, or the carrier may operate in non-standalone mode, where different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0062] The communication link 125 shown in the wireless communication system 100 may include uplink transmission from UE 115 to base station 105, or downlink transmission from base station 105 to UE 115. The carrier may carry downlink or uplink communication (e.g., in FDD mode) or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0063] A carrier can be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, the carrier bandwidth can be referred to as the carrier or the "system bandwidth" of the wireless communication system 100. For example, the carrier bandwidth can be one of several defined bandwidths of a carrier for a specific wireless access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz). Devices of the wireless communication system 100 (e.g., base station 105, UE 115, or both) can have a hardware configuration that supports communication on a specific carrier bandwidth, or can be configured to support communication on one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 can include a base station 105 or UE 115 that supports simultaneous communication via carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 can be configured to operate on a portion (e.g., a subband, BWP) or all of the carrier bandwidth.

[0064] The signal waveform transmitted on a carrier can consist of multiple subcarriers (e.g., using multicarrier modulation (MCM) techniques such as Orthogonal Frequency Division Multiplexing (OFDM) or Discrete Fourier Transform Spread Spectrum OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element can consist of one symbol period (e.g., the duration of a modulation symbol) and one subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate can be for UE 115. Wireless communication resources can refer to a combination of radio frequency spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial layers can further increase the data rate or data integrity used for communication with UE 115.

[0065] One or more digital schemes can be supported for the carrier, where the digital scheme may include subcarrier spacing (Δf) and a cyclic prefix. The carrier can be divided into one or more BWPs with the same or different digital schemes. In some examples, UE 115 can be configured with multiple BWPs. In some examples, a single BWP for the carrier is active at a given time, and communication for UE 115 can be restricted to one or more active BWPs.

[0066] It can be expressed in a basic unit of time (which can be, for example, T). s =1 / (Δf) max ·N f The sampling period is ) seconds, where Δf max This can represent the maximum supported subcarrier spacing, and N f The time interval for base station 105 or UE 115 can be represented as a multiple of the maximum supported Discrete Fourier Transform (DFT) size. The time interval for communication resources can be organized based on radio frames, each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0067] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may be divided (e.g., in the time domain) into subframes, and each subframe may be further divided into multiple time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include multiple symbol periods (e.g., this depends on the length of the cyclic prefix added before each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots containing one or more symbols. Excluding the cyclic prefix, each symbol period may contain one or more (e.g., N) f (Number) sampling periods. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0068] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0069] Physical channels can be multiplexed on a carrier using various techniques. For example, one or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used to multiplex physical control channels and physical data channels on a downlink carrier. A control region (e.g., a control resource set (CORESET)) for physical control channels can be defined by multiple symbol periods and can extend over the system bandwidth or a subset of the system bandwidth of the carrier. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search for control regions for control information based on one or more search space sets, and each search space set can include one or more control channel candidates from one or more aggregation levels arranged in a cascaded manner. An aggregation level for control channel candidates can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set used to send control information to a specific UE 115.

[0070] Each base station 105 may provide communication coverage via one or more cells (e.g., macro cells, small cells, hotspots, or other types of cells, or any combination thereof). The term "cell" may refer to a logical communication entity used (e.g., on a carrier) to communicate with base station 105 and may be associated with an identifier used to distinguish neighboring cells (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID), or other identifier). In some examples, a cell may also refer to a geographic coverage area 110 or a portion of geographic coverage area 110 (e.g., a sector) on which a logical communication entity operates. Depending on various factors (such as the capabilities of base station 105), the range of such cells can range from small areas (e.g., structures, subsets of structures) to large areas. For example, a cell may be or may include buildings, subsets of buildings, or external space between or overlapping geographic coverage areas 110, and other examples.

[0071] Macro cells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 115 with a service subscription to a network provider supporting the macro cell. In contrast, small cells can be associated with a lower-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells can provide unrestricted access to UE 115 with a service subscription to a network provider, or restricted access to UE 115 associated with a small cell (e.g., UE 115 in a Closed Subscriber Group (CSG), or UE 115 associated with a user in a residence or office). Base station 105 can support one or more cells and can also support communication on one or more cells using one or more component carriers.

[0072] In some examples, a carrier can support multiple cells and can be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., MTC, Narrowband IoT (NB-IoT), Enhanced Mobile Broadband (eMBB)).

[0073] In some examples, base station 105 may be mobile, and therefore provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies may overlap, but the different geographic coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographic coverage areas 110 associated with different technologies may be supported by different base stations 105. Wireless communication system 100 may include, for example, a heterogeneous network, in which different types of base stations 105 use the same or different wireless access technologies to provide coverage for various geographic coverage areas 110.

[0074] The wireless communication system 100 can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timing, and transmissions from different base stations 105 may not be time-aligned in some examples. The techniques described herein can be used for both synchronous and asynchronous operation.

[0075] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that allow devices to communicate with each other or with base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices that integrate sensors or meters for measuring or capturing information and transmitting that information to a central server or application, which can then utilize that information or present it to people interacting with the application. Some UE 115 devices can be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, medical monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based service charging.

[0076] Wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UE 115 can be designed to support ultra-reliable, low-latency, or mission-critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private or group communication and can be supported by one or more mission-critical services, such as mission-critical push-to-talk (MCPTT), mission-critical video (MCVideo), or mission-critical data (MCData). Support for mission-critical functions can include service prioritization, and mission-critical services can be used for public safety or general commercial applications. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency are used interchangeably herein.

[0077] In some examples, UE 115 can also communicate directly with other UE 115s on a device-to-device (D2D) communication link 135 (e.g., using peer-to-peer (P2P) or D2D protocols). One or more UEs 115s utilizing D2D communication can be within the geographic coverage area 110 of base station 105. Other UEs 115s in such a group can be outside the geographic coverage area 110 of base station 105, or otherwise unable to receive transmissions from base station 105. In some examples, multiple groups of UEs 115 communicating via D2D communication can utilize a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some examples, base station 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication is performed between UEs 115 without involving base station 105.

[0078] In some systems, the D2D communication link 135 may be an example of a communication channel (e.g., a lateral link communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. Vehicles may be notified of information relating to traffic conditions, signal control, weather, safety, emergencies, or any other information relating to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (e.g., roadside units) or use vehicle-to-network (V2N) communication, communicate with the network via one or more network nodes (e.g., base station 105), or both.

[0079] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 can be an evolved packet core (EPC) or a 5G core (5GC), and can include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function Unit (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function Unit (UPF)) for routing or interconnecting packets to external networks. The control plane entity can manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for UE 115 served by base station 105 associated with core network 130. User IP packets can be transmitted through the user plane entity, which can provide IP address allocation and other functions. The user plane entity can connect to network operator IP service 150. Carrier IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0080] Some network devices (e.g., base station 105) may include sub-components such as access network entity 140, which may be an example of an access node controller (ANC). Each access network entity 140 may communicate with UE 115 through one or more other access network transport entities 145 (which may be referred to as a radio headend, smart radio headend, or transmit / receive point (TRP)). Each access network transport entity 145 may include one or more antenna panels. In some configurations, the various functions of each access network entity 140 or base station 105 may be distributed across individual network devices (e.g., radio headends and ANCs) or incorporated into a single network device (e.g., base station 105).

[0081] Wireless communication system 100 can operate using one or more frequency bands (typically in the range of 300 MHz to 300 GHz). The region from 300 MHz to 3 GHz is often referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range extends from approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but the waves can be sufficiently permeable to penetrate structures for use in macrocells to provide service to UE 115 located indoors. Compared to the transmission of smaller frequencies and longer waves in the lower 300 MHz portion of the spectrum in the High Frequency (HF) or Very High Frequency (VHF) regions, UHF wave transmission can be associated with smaller antennas and shorter distances (e.g., less than 100 km).

[0082] Wireless communication system 100 can utilize both licensed and unlicensed radio frequency spectrum bands. For example, wireless communication system 100 can employ Licensed Assisted Access (LAA), LTE Unlicensed (LTE-U) radio access technology, or NR technology in unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band). When operating in unlicensed radio frequency spectrum bands, devices (such as base station 105 and UE 115) can employ carrier sensing for collision detection and avoidance. In some examples, operation in unlicensed frequency bands can be based on carrier aggregation configurations that combine component carriers operating in licensed frequency bands (e.g., LAA). Among other examples, operation in unlicensed spectrum can include downlink transmissions, uplink transmissions, peer-to-peer (P2P) transmissions, or digital-to-digital (D2D) transmissions.

[0083] Base station 105 or UE 115 may be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 may be located within one or more antenna arrays or antenna panels (which may support MIMO operation or transmit or receive beamforming). For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with base station 105 may be located in different geographical locations. Base station 105 may have an antenna array with rows and columns of antenna ports that base station 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Alternatively or additionally, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0084] Beamforming (which may also be referred to as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., base station 105 or UE 115) to form or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating in a particular orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements can include applying amplitude offset, phase offset, or both to the signals carried via the antenna elements associated with the transmitting or receiving device. The adjustments associated with each antenna element can be defined by a set of beamforming weights associated with a particular orientation (e.g., relative to the antenna array of the transmitting or receiving device, or relative to some other orientation).

[0085] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can perform packet fragmentation and reassembly for transmission over logical channels. The Media Access Control (MAC) layer can perform priority handling and multiplexing of logical channels to transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmissions at the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can provide the establishment, configuration, and maintenance of RRC connections between the UE 115 and the base station 105 or core network 130 (which supports radio bearers for user plane data). At the physical layer, transport channels can be mapped to physical channels.

[0086] UE 115 and base station 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correct data reception on communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal and noise conditions). In some examples, the device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in a previous symbol within a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0087] As part of HARQ feedback, when a downlink message received from base station 105 is successfully received and decoded by UE 115, UE 115 can send a positive acknowledgment (e.g., ACK) feedback message. Alternatively, if UE 115 cannot successfully receive and / or decode the downlink message received from base station 105, UE 115 can then send a NACK feedback message. Therefore, the NACK feedback message can instruct base station 105 to retransmit the downlink message to UE 115 (e.g., in the same time slot or a subsequent time slot), where UE 115 can attempt to receive and decode the retransmission alone, or can combine the retransmission with the initial transmission of the downlink message to successfully and completely receive and decode the downlink message.

[0088] However, in some cases, base station 105 may be unaware of the configuration used for retransmitting downlink messages that would increase the chances of UE 115 successfully receiving and decoding downlink messages. For example, a NACK feedback message might only indicate that UE 115 cannot receive / decode downlink messages without further information to instruct base station 105 on adjustments to make. Thus, base station 105 could speculate on a new configuration with adjustments to the initial transmission of downlink messages for retransmission, but this new configuration might include overly conservative or overly extreme adjustments for retransmission, such that UE 115 still cannot decode the retransmission (e.g., overly conservative), or uses unnecessary resources for retransmission (e.g., overly extreme). To help base station 105 make more informed decisions about the configuration used for retransmission, UE 115 could send additional information about the state of the channel on which it receives downlink messages, along with the acknowledgment feedback. Figure 2 and Figure 3 The additional information provided by UE 115 along with the confirmation feedback is described in more detail.

[0089] Figure 2 An example of an acknowledgment feedback configuration 200 supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. In some examples, the acknowledgment feedback configuration 200 may implement aspects of the wireless communication system 100. The acknowledgment feedback configuration 200 may be used by the base station 105 and the UE 115 to allow the UE 115 to provide acknowledgment feedback for downlink messages received from the base station 105.

[0090] As described herein, UE 115 may support downlink SPS for receiving periodic downlink traffic from base station 105. For example, base station 105 may send permission for scheduling multiple timings (e.g., SPS timings) for downlink reception (e.g., SPS configuration), which UE 115 monitors for to receive periodic downlink traffic, wherein multiple timings occur according to a periodic configuration (e.g., every time slot, every second time slot, every fourth time slot, etc.). In some cases, base station 105 may send permission for SPS configuration in physical downlink control channel (PDCCH) 205. Additionally or alternatively, base station 105 may send permission for SPS configuration in a previous downlink message (e.g., RRC configuration message, DCI, or additional downlink message), and UE 115 may monitor and receive PDCCH 205 during the timing indicated by the SPS configuration.

[0091] Subsequently, UE 115 can identify and receive downlink permission 210 in PDCCH 205, which indicates information (e.g., resources, configuration information, etc.) about downlink messages from base station 105 intended for use by UE 115. For example, UE 115 can monitor and receive downlink messages in PDSCH 215 indicated by downlink permission 210. Additionally or alternatively, when downlink permission 210 includes SPS configuration, downlink permission 210 can indicate multiple PDSCH 215s for UE 115 to periodically monitor and receive (e.g., according to SPS configuration). In some cases, downlink permission 210 may include an indication of a first time delay (K0) between receiving PDCCH 205 and receiving PDSCH 215. For example, UE 115 may implicitly determine K0 based on the Time Domain Resource Allocation (TDRA) table received in downlink grant 210 (e.g., or in an additional downlink grant used to indicate SPS configuration; via DCI format 1_0, 1_1, or 1_2; via PDCCH 205; etc.). In some cases, K0 may be zero (0).

[0092] Additionally, base station 105 can configure UE 115 to provide acknowledgment feedback for periodic downlink traffic (e.g., PDSCH 215) transmitted according to the SPS configuration. For example, base station 105 can instruct resources (e.g., time-frequency resources) of the Physical Uplink Control Channel (PUCCH) 220 (e.g., uplink channel) for UE 115 to send acknowledgment feedback, wherein the acknowledgment feedback may include ACK / NACK feedback 225 (e.g., ACK for affirmative / successful reception and decoding of PDSCH 215 or NACK for negative / unsuccessful reception and / or decoding of PDSCH 215). In some cases, base station 105 can send configuration information for sending acknowledgment feedback when there is permission for the SPS configuration (e.g., downlink permission 210).

[0093] Resources used to send acknowledgment feedback can appear in any time slot that occurs after receiving periodic downlink traffic (e.g., the next time slot that occurs, two time slots after receiving downlink traffic, three time slots after that, etc.). In some cases, UE 115 may send acknowledgment feedback (e.g., ACK / NACK feedback 225) in PUCCH 220 after receiving PDSCH 215 (e.g., periodic traffic for SPS configuration), based on a second time delay (K1). For example, base station 105 may explicitly indicate K1 in downlink grant 210 (e.g., or in additional downlink grants for indicating SPS configuration; via DCI formats 1_0, 1_1, or 1_2; via PDCCH 205; etc.). Although periodicity and acknowledgment feedback transmission have been discussed above with respect to time slots, SPS configuration may include periods shorter than time slots (e.g., half-time slots, micro-time slots, two OFDM symbols, etc.). For example, multiple opportunities may occur within a time slot for sending / receiving downlink services for SPS configuration (e.g., two downlink SPS opportunities per time slot).

[0094] If UE 115 sends a NACK in response to ACK / NACK feedback 225 (e.g., acknowledgment feedback) to indicate that PDSCH 215 was not successfully received / decoded, base station 105 can use link adaptation to retransmit the downlink data / information / messages included in PDSCH 215. However, when a NACK is received at base station 105, the link adaptation (e.g., rate adjustment, MCS adjustment, transmit power adaptation, additional adjustments, etc.) used by base station 105 for retransmission of PDSCH 215 may be slow. Typically, no CQI, CSI, or additional channel information can be associated with the NACK (e.g., sent with ACK / NACK feedback 225 in PUCCH 220). Therefore, base station 105 may not know how to adjust the MCS / rate used for retransmission. For example, UE 115 may not include an indication of how many resources (e.g., time-frequency resources) are needed for retransmission, so base station 105 may guess the amount of resources to use for retransmission, which may result in a conservative or excessive amount of resources used for retransmission.

[0095] In some cases, UE 115 may send CQI / CSI feedback to indicate information about the downlink channel (e.g., PDSCH 215) to base station 105 based on periodic or aperiodic scheduling (e.g., CQI may be calculated based on the signal-to-interference-plus-noise ratio (SINR) of PDSCH 215). For example, periodic CSI (P-CSI) feedback may be inflexible (e.g., sent according to periodic scheduling rather than at other times), and aperiodic CSI (A-CSI) feedback may be triggered by separate uplink grants sent by base station 105 to UE 115 as needed when base station 105 needs / wants channel information, wherein the separate uplink grants indicate the resources that UE 115 uses to send A-CSI feedback. That is, A-CSI feedback can be triggered by uplink grants and cannot be sent autonomously by UE 115 (e.g., based on periodic scheduling or SPS configuration). Therefore, due to the need for separate uplink permission, the timeline for A-CSI feedback may be slower than that for ACK / NACK feedback 225 (e.g., UE 115 cannot send CSI feedback in the same time slot as scheduling PDSCH 215, even if both are scheduled in the same time slot). Although the above discussion concerns CSI feedback, the same obstacle applies to CQI feedback.

[0096] To mitigate the slower timelines associated with sending CSI / CQI feedback, UE 115 can associate or bundle CQI / CSI feedback with ACK / NACK feedback 225 to allow base station 105 to perform faster and more accurate MCS adjustments, rate adjustments, transmit power adaptations, or combinations thereof. For example, UE 115 can send CSI / CQI report 230 in PUCCH 220 while sending ACK / NACK feedback 225 (e.g., ACK / NACK feedback 225 and CSI / CQI report 230 can be included in a single message of PUCCH 220 or in separate messages of PUCCH 220). Therefore, UE 115 can maintain an uplink grant that will allocate resources for CSI / CQI feedback.

[0097] Specifically, the CSI / CQI report 230 can be triggered explicitly (e.g., via an information field in the DCI) or implicitly (e.g., via a NACK trigger) by the downlink grant 210. For example, a field in the DCI of the downlink grant 210 (e.g., an additional downlink grant in PDCCH 205, etc.) can instruct UE 115 to send the CSI / CQI report 230 based on an attempt to decode PDSCH 215 (e.g., in PUCCH 220 or in a subsequent Physical Uplink Shared Channel (PUSCH)). In some cases, this field can instruct UE 115 to send the CSI / CQI report 230 regardless of whether PDSCH 215 is successfully decoded. Base station 105 may instruct UE 115 to send CSI / CQI report 230 in such a manner as (e.g., regardless of whether an ACK or NACK is sent for PDSCH 215 in ACK / NACK feedback 225) to better adjust subsequent transmissions on the same channel (e.g., additional transmissions, retransmissions, etc.). Alternatively, this field may instruct UE 115 to send CSI / CQI report 230 only if PDSCH 215 is not successfully decoded / received (e.g., a NACK is sent for ACK / NACK feedback 225). When PDSCH 215 is unsuccessful (e.g., NACK), base station 105 may instruct UE 115 to send CSI / CQI report 230 to identify adjustments made for better retransmission of PDSCH 215 (e.g., the same transport block (TB)). For example, UE 115 can determine that TB has been successfully decoded by combining the first transmission of TB (e.g., in the first PDSCH 215) with the (e.g., adjusted) retransmission of TB (e.g., in a subsequent PDSCH).

[0098] For scenarios with high reliability and low latency requirements (e.g., URLLC), base station 105 can instruct UE 115 to send CSI / CQI report 230 along with ACK / NACK feedback 225. For example, a turbo HARQ acknowledgment (e.g., Turbo HARQ-ACK, Turbo-ACK, etc.) feedback system (e.g., sending CSI / CQI report 230 along with ACK / NACK feedback 225) can enable more reliable retransmissions, where one (1) retransmission is sufficient to guarantee high reliability (e.g., 10). -5 The system requires high reliability and low latency (e.g., five (5) ms delay). Alternatively, (e.g., using other HARQ-ACK systems), more retransmissions may be required because the adaptation of MCS, rate, power, etc. is slower.

[0099] In some cases, UE 115 may rely on DCI to trigger CSI / CQI reports. Furthermore, downlink-triggered CSI / CQI reports (e.g., via DCI) can be further categorized into two types. The first type (e.g., Type 1) may include regular triggering, where UE 115 sends a CSI / CQI report 230 along with ACK / NACK feedback 225 for each report (e.g., regardless of the acknowledgment feedback included in ACK / NACK feedback 225). For example, for Type 1 CSI / CQI reports, downlink CSI may not be triggered by UE 115 (e.g., L1 procedure / signaling / determination) (where a PDSCH decoding failure identified by UE 115 triggers UE 115 to send a CSI / CQI report 230). Alternatively, Type 1 CSI / CQI reporting can enable more flexible CSI / CQI triggering and transmission (e.g., on PUCCH 220), similar to A-CSI triggering as described above (e.g., using DCI to signal uplink permission and reporting CSI / CQI report 230 on PUSCH).

[0100] Additionally or alternatively, the second type (e.g., type 2) may include selective triggering similar to turbo HARQ acknowledgment triggering as described above, wherein UE 115 sends CSI / CQI report 230 along with ACK / NACK feedback 225 when ACK / NACK feedback 225 includes NACK. For example, this type 2 CSI / CQI report may include a downlink CSI / CQI trigger (e.g., L1 procedure / signaling / determining) driven by UE 115 (where a PDSCH decoding failure identified by UE 115 triggers UE 115 to send CSI / CQI report 230). PDSCH decoding failure can be used to trigger CSI / CQI report as a last resort in HARQ operations to complete an emergency task. In some cases, the type 2 CSI / CQI report may use implicit indication so that UE 115 sends CSI / CQI report 230 based on PDSCH decoding failure (e.g., NACK).

[0101] However, when UE 115 is configured for SPS communication (e.g., via one or more SPS configurations), UE 115 may not know which CSI / CQI reporting mode to use. Therefore, an efficient technique is needed to instruct UE 115 which CSI / CQI reporting mode (e.g., Type 1, Type 2, etc.) to use when sending acknowledgment feedback for downlink messages (e.g., PDSCH 215) received according to the SPS configuration. As described herein and Figure 3As described in more detail, the indication and activation of CSI reporting configuration can be used for each SPS configuration of UE 115. For example, for each SPS configuration, a type 1 or type 2 downlink CSI / CQI trigger configuration can be configured for UE 115 within the SPS configuration, within the activated DCI for the SPS configuration, or a combination thereof.

[0102] Figure 3 An example of a wireless communication system 300 supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. In some examples, the wireless communication system 300 may implement aspects of the wireless communication system 100 and the acknowledgment feedback configuration 200. The wireless communication system 300 may include a base station 105-a and a UE 115-a, which may be respectively referenced above. Figure 1 and Figure 2 Examples of corresponding base station 105 and UE 115 are described below. Additionally, as described herein, base station 105-a and UE 115-a can communicate according to SPS configuration 310 (e.g., downlink SPS configuration), wherein base station 105-a sends periodic downlink traffic to UE 115-a (e.g., every time slot, every second time slot, every half time slot, every micro time slot, every two OFDM symbols, etc.), and UE 115-a sends acknowledgment feedback to base station 105-a based on attempts to receive / decode periodic downlink traffic. For example, UE 115-a and base station 105-a can communicate according to SPS configuration 310 on the resources of carrier 305.

[0103] In some cases, UE 115-a may be configured with multiple SPS configurations 310 on a given carrier (e.g., carrier 305). Furthermore, the configuration for each SPS configuration 310 can be performed independently or separately. For example, each SPS configuration 310 may include specific parameters for that SPS configuration 310, which may include time resources, frequency resources, MCS, etc., specific to that SPS configuration 310. Therefore, each SPS configuration 310 may have a different configuration, a partially different configuration, or the same configuration as other SPS configurations 310.

[0104] Additionally, some wireless communication systems may support two-tiered priority acknowledgment feedback (e.g., HARQ-ACK) for dynamically scheduled PDSCH and SPS PDSCH transmissions (e.g., and acknowledgment feedback for SPS PDSCH release transmissions). In some cases, when SPS configuration 310 is activated (e.g., via DCI activation), UE 115-a may not need to send an acknowledgment feedback message indicating successful reception and decoding of the activation message before starting to use SPS configuration 310. Alternatively or additionally, when SPS configuration 310 is released (e.g., via a release message / transmission), UE 115-a may have to send an ACK to acknowledge that SPS configuration 310 has been released (e.g., UE 115 no longer communicates according to SPS configuration 310). In some cases, explicit indications (e.g., RRC parameters) in each SPS PDSCH configuration can provide a mapping to the corresponding acknowledgment codebook (e.g., HARQ-ACK codebook) for SPS PDSCH transmissions and the ACK for SPS PDSCH release transmissions.

[0105] Base station 105-a may send an indication of SPS configuration 310 to UE 115-a (e.g., in an RRC message, DCI, PDCCH, downlink grant, etc.) to configure UE 115-a to periodically monitor and receive downlink messages (e.g., downlink data, information, etc.) according to SPS configuration 310. For example, as described above, SPS configuration 310 may include resource allocation (e.g., time resources, frequency resources, etc.) for receiving periodic downlink messages and transmitting any associated uplink messages, as well as additional configuration parameters for periodic services (e.g., MCS, transmit power control (TPC) commands, redundancy version, etc.). However, UE 115-a may not use one of the indicated SPS configurations 310 until SPS configuration 310 is activated and DCI 320 is activated. For example, activating DCI 320 may include an instruction for UE 115-a to begin using one of the SPS configurations 310 for subsequent communication with base station 105-a.

[0106] As shown in the figure, activating DCI 320 can instruct UE 115-a to begin communicating with base station 105-a using SPS configuration 310-a. For example, SPS configuration 310-a may include one or more PDCCH 325s that UE 115-a will monitor from base station 105-a, one or more associated PDSCH 330s indicated by PDCCH 325, and one or more PUCCH 335s that UE 115-a will use to send acknowledgment feedback to base station 105-a based on attempts to receive and decode PDSCH 330s. In some cases, SPS configuration 310-a may include a first PDCCH 325-a for carrying downlink permission, which indicates or schedules each of subsequent PDSCH 330s and PUCCH 335s (e.g., including corresponding time delays K0 and K1). Additionally or alternatively, SPS configuration 310-a may exclude PDCCH 325 and may use previously received SPS configuration 310 to identify when and where the timing for PDSCH 330 and PUCCH 335 occurs.

[0107] However, as mentioned above Figure 2 As described above, based on communication with base station 105-a according to SPS configuration 310, UE 115-a may not know when to send CSI / CQI report 345 in PUCCH 335. For example, PUCCH 335 may carry ACK / NACK 340 (e.g., acknowledgment feedback) based on whether UE 115-a is able (e.g., ACK) or unable (e.g., NACK) to successfully receive and decode PDSCH 330, and UE 115-a may not know based on the above reference. Figure 2 The described Type 1 CSI report configuration (e.g., regardless of whether ACK or NACK is sent in ACK / NACK 340) or Type 2 CSI report configuration (e.g., only when NACK is sent in ACK / NACK 340) is used to include CSI / CQI report 345 together with ACK / NACK 340 in PUCCH 335.

[0108] As described herein, the wireless communication system 200 may include efficient techniques for triggering CSI / CQI reports for an SPS configuration. For example, for each SPS configuration 310, a CSI / CQI reporting configuration 315-a may be signaled along with each SPS configuration 310 (e.g., a configurable Type 1 or Type 2 downlink CSI / CQI trigger). Once an SPS configuration 310 is activated (e.g., via activated DCI 320), the UE 115-a may send a CSI / CQI report 345 according to the configuration mode for that SPS configuration 310. For example, SPS configuration 310 may include CSI / CQI reporting configuration 315-a (e.g., each SPS configuration 310 may be configured with a type 1 or type 2 CSI / CQI reporting configuration), and activating DCI 320 may trigger UE 115-a to use one of the SPS configurations 310 (e.g., SPS configuration 310-a) with the corresponding CSI / CQI reporting configuration 315-a.

[0109] For a Type 1 CSI / CQI reporting configuration, UE 115-a may send a CSI / CQI report 345 (e.g., and associated ACK / NACK 340) for a first received PDSCH 330 (e.g., or a specifically indicated PDSCH 330) in SPS configuration 310. For example, UE 115-a may, based on the Type 1 CSI / CQI reporting configuration, send a first CSI / CQI report 345-a in a first PUCCH 335-a for a first received PDSCH 330-a, along with a first ACK / NACK 340-a, but not send a CSI / CQI report 345 for subsequent received PDSCH 330s (e.g., to avoid sending a second CSI / CQI report 345-b in a second PUCCH 335-b for a second received PDSCH 330-b, along with a second ACK / NACK 340-b). Additionally or alternatively, for a Type 1 CSI / CQI reporting configuration, UE 115-a may send a CSI / CQI report 345 along with an ACK / NACK 340 for each PDSCH 330 received according to SPS configuration 310 (e.g., UE 115-a sends both a first CSI / CQI report 345-a and a second CSI / CQI report 345-b). For a Type 2 CSI / CQI reporting configuration, UE 115-a may send a CSI / CQI report 345 whenever any PDSCH 330 received according to SPS configuration 310 fails (e.g., when UE 115-a sends a NACK in an ACK / NACK 340 for the corresponding PDSCH 330). In some cases, including a CSI / CQI reporting configuration 315-a in SPS configuration 310 may be considered semi-persistent signaling or hard-coded with the corresponding SPS configuration 310.

[0110] Alternatively or additionally, for each SPS configuration 310, a Type 1 CSI / CQI reporting configuration, a Type 2 CSI / CQI reporting configuration, both types, or no type can be configured. Subsequently, activating a bit field (e.g., one or more bits) in the DCI 320 can indicate which CSI / CQI reporting configuration type (e.g., mode) UE 115-a should follow. For example, the bit field can be considered as indicating either a Type 1 CSI / CQI reporting configuration or a Type 2 CSI / CQI reporting configuration 315-b for the activated SPS configuration 310, allowing UE 115-a to switch between types. Therefore, signaling which CSI / CQI reporting configuration type to use can be considered dynamic signaling. In both cases (e.g., signaling which CSI / CQI reporting configuration type to use in SPS configuration 310 or in activated DCI 320), a single activated DCI 320 can be used to indicate the SPS configuration and corresponding CSI / CQI reporting configuration to be used by UE 115-a.

[0111] In some cases, for joint SPS activation (e.g., a single active DCI 320 activating multiple SPS configurations 310), signaling can be used to indicate which CSI / CQI reporting configuration type to use in the SPS configuration 310. Alternatively, when signaling in the active DCI 320 is used to indicate which CSI / CQI reporting configuration type to use, a multi-bit information field can be used to indicate the reporting mode (e.g., type 1 or type 2) for each active SPS configuration 310.

[0112] Furthermore, by signaling which CSI / CQI report configuration type to use in SPS configuration 310 (e.g., when a bit field is included in active DCI 320), if the received DCI instructs UE 115-a to release SPS configuration 310 (e.g., all 0s, all 1s, or a different signaling used to indicate release), UE 115-a may not send CSI / CQI report 345. For example, when releasing SPS configuration 310, the bit field in the DCI can be set to a predetermined value and used for release verification. In some cases, a table can be configured such that when UE 115-a recognizes a predetermined value for a bit field in the DCI, the table can instruct the DCI to carry a release instruction for SPS configuration 310. Therefore, UE 115-a can send an ACK to confirm that SPS configuration 310 has been released and can avoid sending CSI / CQI report 345.

[0113] Although two (2) PDCCH 325s, two (2) PDSCH 330s, and two (2) PUCCH 335s are shown in the example of SPS configuration 310-a, it should be understood that more or fewer corresponding channels may be available for communication between UE 115-a and base station 105-a. For example, UE 115-a and base station 105-a may use SPS configuration 310-a until SPS configuration 310-a is released, which may result in a single timing for monitoring a single PDSCH 330 (e.g., and sending a single PUCCH 335) or multiple timings for monitoring multiple PDSCH 330s (e.g., and sending multiple PUCCH 335s).

[0114] Figure 4 An example of a process flow 400 supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. In some examples, process flow 400 may implement aspects of wireless communication systems 100 and / or 300. Process flow 400 may include base station 105-b and UE 115-b, which may be respectively referenced above. Figures 1-3 Examples of corresponding base station 105 and UE 115 are described.

[0115] In the following description of process flow 400, the operations between UE 115-b and base station 105-b may be performed in a different order or at different times. Some operations of process flow 400 may also be omitted, or other operations may be added to process flow 400. Although UE 115-b and base station 105-b are shown performing multiple operations of process flow 400, any wireless device may perform the operations shown.

[0116] At 405, UE 115-b can receive SPS configuration for UE 115-b from base station 105-b. In some cases, the SPS configuration may include the following set of configuration parameters: time resources, frequency resources, MCS, or a combination thereof for the SPS configuration. Additionally, one or more SPS configurations may be configured for a single carrier of UE 115-a.

[0117] At 410, UE 115-b can receive a DCI (e.g., activate DCI) from base station 105-b for activating the SPS configuration. In some cases, the SPS configuration received at 405 may include multiple SPS configurations, and the DCI may belong to one or more of the multiple SPS configurations.

[0118] At 415, UE 115-b can determine the channel state reporting configuration (e.g., CSI / CQI reporting configuration) for the SPS configuration based on DCI, SPS configuration, or both.

[0119] For example, in some cases, UE 115-b can recognize that the SPS configuration includes an indication of a channel state report configuration within the channel state report configuration set, and can determine that the channel state report configuration is one of the channel state report configurations in the set based on the reception of DCI. In some cases, regardless of whether UE 115-b successfully decodes the downlink shared channel, the channel state report and the acknowledgment feedback for the downlink shared channel received according to the SPS configuration can be sent together. Alternatively, when UE 115-b fails to decode the downlink shared channel, the channel state report and the acknowledgment feedback for the downlink shared channel can be sent together.

[0120] Additionally or alternatively, in some cases, UE 115-b may recognize that the DCI includes an indication of a channel state report configuration within a set of channel state report configurations, wherein the channel state report configuration is one of the channel state report configurations indicated by the DCI within the set of channel state report configurations. In some cases, the indication in the DCI may include a bit field for activating a channel state report configuration included in an SPS configuration, wherein the SPS configuration includes one or more channel state report configurations. Furthermore, an SPS configuration may include multiple SPS configurations, and the indication in the DCI may include a multi-bit field for indicating a corresponding channel state report configuration for each of the multiple SPS configurations.

[0121] At 420, UE 115-b can receive the downlink shared channel from base station 105-b according to the SPS configuration, wherein the downlink shared channel is indicated by DCI.

[0122] At 425, UE 115-b can determine acknowledgment feedback (e.g., ACK / NACK feedback) for the downlink shared channel, where the acknowledgment feedback is based on an attempt to decode the downlink shared channel.

[0123] At 430, UE 115-b can send an acknowledgment feedback for the downlink shared channel to base station 105-b.

[0124] At position 435, UE 115-b can send a channel state report to base station 105-b, and according to the SPS configuration, for the downlink shared channel received according to the SPS configuration. In some cases, acknowledgment feedback can be sent together with the channel state report.

[0125] At 440, UE 115-b can receive an additional DCI indicating that the SPS configuration will be released, wherein the additional DCI includes a bit field indicating the channel state report configuration. Accordingly, UE 115-b can avoid future transmissions of channel state reports based on the reception of the additional DCI. In some cases, the bit field may include a predetermined value indicating the release of the SPS configuration.

[0126] Figure 5 A block diagram 500 of a device 505 supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. Device 505 may be an example of an aspect of UE 115 as described herein. Device 505 may include: a receiver 510, a UE communication manager 515, and a transmitter 520. Device 505 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0127] Receiver 510 can 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 downlink-triggered CSI reports for SPS). The information can be passed to other components of device 505. Receiver 510 can be a reference. Figure 8 Examples of various aspects of the transceiver 820 are described. The receiver 510 can use a single antenna or an array of antennas.

[0128] The UE communication manager 515 can receive SPS configuration for the UE from the base station. Furthermore, the UE communication manager 515 can receive DCI for activating the SPS configuration from the base station. In some cases, the UE communication manager 515 can determine the channel state report configuration for the SPS configuration based on the DCI, the SPS configuration, or both. Subsequently, the UE communication manager 515 can send a channel state report to the base station for the downlink shared channel received according to the SPS configuration, based on the channel state report configuration. The UE communication manager 515 can be an example of an aspect of the UE communication manager 810 described herein.

[0129] The UE communication manager 515 or its sub-components may be implemented in hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented in processor-executable code, the UE communication manager 515 or its sub-components may be executed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described in this disclosure.

[0130] The UE communication manager 515 or its sub-components may be physically located in various locations, including distributed such that some functions are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the UE communication manager 515 or its sub-components may be separate and distinct components. In some examples, according to various aspects of this disclosure, the UE communication manager 515 or its sub-components may be combined with one or more other hardware components, including but not limited to input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0131] Transmitter 520 can transmit signals generated by other components of device 505. In some examples, transmitter 520 can be co-located with receiver 510 in a transceiver module. For example, transmitter 520 can be a reference... Figure 8 Examples of various aspects of the transceiver 820 are described. The transmitter 520 can use a single antenna or an array of antennas.

[0132] Figure 6 A block diagram 600 of a device 605 supporting downlink-triggered CSI reporting for SPS, according to an aspect of this disclosure, is shown. Device 605 may be an example of a device 505 or an aspect of UE 115 as described herein. Device 605 may include a receiver 610, a UE communication manager 615, and a transmitter 640. Device 605 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0133] Receiver 610 can 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 downlink-triggered CSI reports for SPS). The information can be passed to other components of device 605. Receiver 610 can be a reference. Figure 8 Examples of various aspects of the transceiver 820 are described. The receiver 610 can use a single antenna or an array of antennas.

[0134] UE communication manager 615 may be an example of an aspect of UE communication manager 515 described herein. UE communication manager 615 may include an SPS configuration receiver 620, an active DCI receiver 625, a channel state report configuration component 630, and a channel state report transmitter 635. UE communication manager 615 may be an example of an aspect of UE communication manager 810 described herein.

[0135] The SPS configuration receiver 620 can receive SPS configuration for the UE from the base station.

[0136] The DCI receiver 625 can receive DCI from the base station to activate the SPS configuration.

[0137] The channel state report configuration component 630 can determine the channel state report configuration for the SPS configuration based on DCI, SPS configuration, or both.

[0138] The channel state report transmitter 635 can send a channel state report to the base station for the downlink shared channel received according to the SPS configuration, based on the channel state report configuration.

[0139] Transmitter 640 can transmit signals generated by other components of device 605. In some examples, transmitter 640 can be co-located with receiver 610 in a transceiver module. For example, transmitter 640 can be a reference... Figure 8 Examples of various aspects of the transceiver 820 are described. The transmitter 640 can use a single antenna or an array of antennas.

[0140] Figure 7 A block diagram 700 of a UE communication manager 705 supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. The UE communication manager 705 may be an example of aspects of the UE communication manager 515, UE communication manager 615, or UE communication manager 810 described herein. The UE communication manager 705 may include an SPS configuration receiver 710, an activated DCI receiver 715, a channel state report configuration component 720, a channel state report transmitter 725, an acknowledgment feedback determination component 730, and an SPS configuration release component 735. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0141] The SPS configuration receiver 710 can receive SPS configurations for the UE from the base station. In some cases, the SPS configuration may include the following set of configuration parameters: time resources, frequency resources, MCS, or a combination thereof for the SPS configuration. Additionally, one or more SPS configurations can be configured for a single carrier of the UE.

[0142] The DCI receiver 715 can receive a DCI from the base station to activate the SPS configuration. In some cases, the SPS configuration may include a set of SPS configurations, and the DCI may belong to one or more SPS configurations in the set of SPS configurations.

[0143] The Channel State Report Configuration Component 720 can determine the Channel State Report configuration for the SPS configuration based on DCI, SPS configuration, or both.

[0144] In some examples, the Channel State Report Configuration component 720 can recognize that the SPS configuration includes an indication of a Channel State Report Configuration within a set of Channel State Report Configurations, and can determine that the Channel State Report Configuration is one of the Channel State Report Configurations in the set based on the reception of the DCI. In some cases, the Channel State Report and acknowledgment feedback for the downlink shared channel can be sent together regardless of whether the UE successfully decodes the downlink shared channel. Alternatively, when the UE fails to decode the downlink shared channel, the Channel State Report and acknowledgment feedback for the downlink shared channel can be sent together.

[0145] Additionally or alternatively, the Channel State Report Configuration component 720 may recognize that the DCI includes an indication of a channel state report configuration within a set of channel state report configurations, wherein the channel state report configuration is one of the channel state report configurations indicated by the DCI within the set of channel state report configurations. In some cases, the indication in the DCI may include a bit field for activating a channel state report configuration included in an SPS configuration, wherein the SPS configuration includes one or more configured channel state report configurations. Additionally, an SPS configuration may include multiple SPS configurations, wherein the indication in the DCI includes a multi-bit field for indicating a corresponding channel state report configuration for each of the multiple SPS configurations.

[0146] The channel state report transmitter 725 can send a channel state report to the base station and according to the channel state report configuration for the downlink shared channel received according to the SPS configuration.

[0147] The acknowledgment feedback determining component 730 can receive the downlink shared channel from the base station according to the SPS configuration, wherein the downlink shared channel is indicated by the DCI. In some examples, the acknowledgment feedback determining component 730 can determine acknowledgment feedback for the downlink shared channel based on an attempt to decode the downlink shared channel. Subsequently, the acknowledgment feedback determining component 730 can send acknowledgment feedback for the downlink shared channel to the base station, wherein the acknowledgment feedback is sent together with the channel state report.

[0148] The SPS configuration release component 735 can receive an additional DCI indicating that the SPS configuration will be released. The additional DCI includes a bit field indicating a channel state report configuration. In some examples, the SPS configuration release component 735 can avoid future transmissions of channel state reports based on the receipt of the additional DCI. In some cases, the bit field may include a predetermined value indicating the release of the SPS configuration.

[0149] Figure 8A diagram of a system 800, including device 805 supporting downlink-triggered CSI reporting for SPS, is shown according to aspects of this disclosure. Device 805 may be an example of or include components of device 505, device 605, or UE 115 as described herein. Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including a UE communication manager 810, I / O controller 815, transceiver 820, antenna 825, memory 830, and processor 840. These components may communicate electronically via one or more buses (e.g., bus 845).

[0150] The UE communication manager 810 can receive SPS configuration for the UE from the base station. Additionally, the UE communication manager 810 can receive DCI for activating the SPS configuration from the base station. In some cases, the UE communication manager 810 can determine the channel state report configuration for the SPS configuration based on the DCI, the SPS configuration, or both. Accordingly, the UE communication manager 810 can send a channel state report to the base station for the downlink shared channel received according to the SPS configuration, based on the channel state report configuration.

[0151] I / O controller 815 can manage input and output signals for device 805. I / O controller 815 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 815 can represent a physical connection or port to an external peripheral device. In some cases, I / O controller 815 can use, for example... The operating system or other known operating system. In other cases, the I / O controller 815 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 815 may be implemented as part of a processor. In some cases, a user may interact with the device 805 via the I / O controller 815 or via hardware components controlled by the I / O controller 815.

[0152] As described above, transceiver 820 can communicate bidirectionally via one or more antennas, wired or wireless links. For example, transceiver 820 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 820 may also include a modem for modulating packets and providing modulated packets to the antenna for transmission, and for demodulating packets received from the antenna.

[0153] In some cases, a wireless device may include a single antenna 825. However, in other cases, the device may have more than one antenna 825, which is capable of transmitting or receiving multiple wireless transmissions simultaneously.

[0154] Memory 830 may include random access memory (RAM) and read-only memory (ROM). Memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, among other things, memory 830 may contain a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0155] Processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, central processing units (CPUs), microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any combination thereof). In some cases, processor 840 may be configured to use a memory controller to operate a memory array. In other cases, the memory controller may be integrated into processor 840. Processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting downlink-triggered CSI reporting for SPS).

[0156] Code 835 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 835 may be stored in a non-transitory computer-readable medium such as system memory or other types of memory. In some cases, code 835 may not be directly executable by processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein.

[0157] Figure 9 A block diagram 900 of a device 905 supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. Device 905 may be an example of an aspect of base station 105 as described herein. Device 905 may include a receiver 910, a base station communication manager 915, and a transmitter 920. Device 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0158] Receiver 910 can 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 downlink-triggered CSI reports for SPS). This information can be passed to other components of device 905. Receiver 910 can be a reference. Figure 12 Examples of various aspects of the transceiver 1220 are described. The receiver 910 can use a single antenna or an array of antennas.

[0159] The base station communication manager 915 can send an SPS configuration for communication with the UE to the UE. Additionally, the base station communication manager 915 can send a DCI to the UE to activate the SPS configuration, wherein the DCI activates a channel state report configuration for the SPS configuration. In some cases, the base station communication manager 915 can receive a channel state report from the UE for a downlink shared channel received according to the SPS configuration, and according to the channel state report configuration. The base station communication manager 915 can be an example of an aspect of the base station communication manager 1210 described herein.

[0160] The base station communication manager 915 or its sub-components may be implemented in hardware, in code (e.g., software or firmware) executed by a processor, or any combination thereof. If implemented in code executed by a processor, the functionality of the base station communication manager 915 or its sub-components may be performed by a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof designed to perform the functions described in this disclosure.

[0161] The base station communication manager 915 or its sub-components may be physically located in various locations, including distributed such that some functions are implemented by one or more physical components at different physical locations. In some examples, according to various aspects of this disclosure, the base station communication manager 915 or its sub-components may be separate and distinct components. In some examples, according to various aspects of this disclosure, the base station communication manager 915 or its sub-components may be combined with one or more other hardware components, including but not limited to I / O components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof.

[0162] Transmitter 920 can transmit signals generated by other components of device 905. In some examples, transmitter 920 can be co-located with receiver 910 in a transceiver module. For example, transmitter 920 can be a reference... Figure 12 Examples of various aspects of the transceiver 1220 are described. The transmitter 920 can use a single antenna or an array of antennas.

[0163] Figure 10 A block diagram 1000 of a device 1005 supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. Device 1005 may be an example of a device 905 as described herein or an aspect of base station 105. Device 1005 may include a receiver 1010, a base station communication manager 1015, and a transmitter 1035. Device 1005 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0164] Receiver 1010 can 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 downlink-triggered CSI reports for SPS). This information can be passed to other components of device 1005. Receiver 1010 can serve as a reference. Figure 12 Examples of various aspects of the transceiver 1220 are described. The receiver 1010 can use a single antenna or an array of antennas.

[0165] Base station communication manager 1015 may be an example of an aspect of base station communication manager 915 described herein. Base station communication manager 1015 may include SPS configuration transmitter 1020, DCI activation transmitter 1025, and channel state report receiver 1030. Base station communication manager 1015 may be an example of an aspect of base station communication manager 1210 described herein.

[0166] The SPS configuration transmitter 1020 can send SPS configurations to the UE for communication with the UE.

[0167] The DCI transmitter 1025 can send a DCI to the UE to activate the SPS configuration, wherein the DCI activates the channel state report configuration for the SPS configuration.

[0168] The channel state report receiver 1030 can receive channel state reports for downlink shared channels received according to the SPS configuration from the UE and according to the channel state report configuration.

[0169] Transmitter 1035 can transmit signals generated by other components of device 1005. In some examples, transmitter 1035 may be co-located with receiver 1010 in a transceiver module. For example, transmitter 1035 may be a reference... Figure 12 Examples of various aspects of the transceiver 1220 are described. The transmitter 1035 can use a single antenna or an array of antennas.

[0170] Figure 11A block diagram 1100 of a base station communication manager 1105 supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. The base station communication manager 1105 may be an example of aspects of the base station communication manager 915, base station communication manager 1015, or base station communication manager 1210 described herein. The base station communication manager 1105 may include an SPS configuration transmitter 1110, an active DCI transmitter 1115, a channel state report receiver 1120, an acknowledgment feedback component 1125, a channel state report configuration indicator 1130, and an SPS configuration release indicator 1135. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0171] SPS configuration transmitter 1110 can send SPS configurations for communication with the UE to the UE. In some cases, the SPS configuration may include the following set of configuration parameters: time resources, frequency resources, MCS, or a combination thereof for the SPS configuration. In addition, one or more SPS configurations can be configured for a single carrier of the UE.

[0172] The DCI transmitter 1115 can send a DCI to the UE to activate the SPS configuration, wherein the DCI activates the Channel State Reporting configuration for the SPS configuration. In some cases, the SPS configuration may include a set of SPS configurations, and the DCI may belong to one or more SPS configurations in the set of SPS configurations.

[0173] The channel state report receiver 1120 can receive channel state reports for downlink shared channels received according to the SPS configuration from the UE and according to the channel state report configuration.

[0174] The acknowledgment feedback component 1125 can send a downlink shared channel to the UE according to the SPS configuration, wherein the downlink shared channel is indicated by the DCI. Subsequently, the acknowledgment feedback component 1125 can receive acknowledgment feedback for the downlink shared channel from the UE, wherein the acknowledgment feedback is received together with the channel state report.

[0175] The channel state report configuration indicator 1130 can use SPS configuration to send an indication to the UE of a channel state report configuration set, wherein the channel state report configuration is one of the channel state report configurations in the set. In some cases, the channel state report and acknowledgment feedback for the downlink shared channel can be received together regardless of whether the UE successfully decodes the downlink shared channel. Alternatively, when the UE fails to decode the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel can be received together.

[0176] Additionally or alternatively, the Channel State Reporting Configuration Indicator 1130 may send an indication to the UE in the DCI for a Channel State Reporting Configuration set, wherein the Channel State Reporting Configuration is one of the Channel State Reporting Configurations in the set indicated by the DCI. In some cases, the indication in the DCI may include a bit field for activating a Channel State Reporting Configuration included in an SPS Configuration, wherein the SPS Configuration includes one or more configured Channel State Reporting Configurations. Alternatively, an SPS Configuration may include multiple SPS Configurations, wherein the indication in the DCI includes a multi-bit field for indicating a corresponding Channel State Reporting Configuration for each of the multiple SPS Configurations.

[0177] SPS configuration release indicator 1135 can send an additional DCI to the UE to indicate that the SPS configuration is to be released. The additional DCI includes a bit field indicating channel state report configuration, wherein, based on the additional DCI, no channel state report will be received in future transmissions from the UE. In some cases, the bit field may include a predetermined value indicating the release of the SPS configuration.

[0178] Figure 12 A diagram of a system 1200, including device 1205 supporting downlink-triggered CSI reporting for SPS, is shown according to aspects of this disclosure. Device 1205 may be an example of or include components of device 905, device 1005, or base station 105 as described herein. Device 1205 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, including base station communication manager 1210, network communication manager 1215, transceiver 1220, antenna 1225, memory 1230, processor 1240, and inter-site communication manager 1245. These components may communicate electronically via one or more buses (e.g., bus 1250).

[0179] The base station communication manager 1210 can send an SPS configuration for communication with the UE to the UE. Additionally, the base station communication manager 1210 can send a DCI to the UE to activate the SPS configuration, wherein the DCI activates the channel state report configuration for the SPS configuration. In some cases, the base station communication manager 1210 can receive a channel state report from the UE for a downlink shared channel received according to the SPS configuration, based on the channel state report configuration.

[0180] The network communication manager 1215 can manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1215 can manage the transmission of data communication to client devices (such as one or more UEs 115).

[0181] Transceiver 1220 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, transceiver 1220 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1220 may also include a modem for modulating packets and providing the modulated packets to the antenna for transmission, and demodulating packets received from the antenna.

[0182] In some cases, a wireless device may include a single antenna 1225. However, in other cases, the device may have more than one antenna 1225, which are capable of transmitting or receiving multiple wireless transmissions simultaneously.

[0183] Memory 1230 may include RAM, ROM, or a combination thereof. Memory 1230 may store computer-readable code 1235, which includes instructions that, when executed by a processor (e.g., processor 1240), cause the device to perform the various functions described herein. In some cases, in addition, memory 1230 may also include a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0184] Processor 1240 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1240 may be configured to use a memory controller to operate a memory array. In some cases, the memory controller may be integrated into processor 1240. Processor 1240 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1230) to cause device 1205 to perform various functions (e.g., functions or tasks supporting downlink-triggered CSI reporting for SPS).

[0185] Inter-site communication manager 1245 can manage communication with other base stations 105 and may include a controller or scheduler for cooperating with other base stations 105 to control communication with UE 115. For example, inter-site communication manager 1245 can coordinate the scheduling of transmissions to UE 115 to implement various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-site communication manager 1245 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0186] Code 1235 may include instructions for implementing various aspects of this disclosure, including instructions for supporting wireless communication. Code 1235 may be stored in a non-transitory computer-readable medium (e.g., system memory or other types of memory). In some cases, code 1235 may not be directly executable by processor 1240, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein.

[0187] Figure 13 A flowchart illustrating a method 1300 for supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. As described herein, operation of method 1300 can be implemented by UE 115 or its components. For example, operation of method 1300 can be achieved by reference to... Figures 5 to 8 The UE communication manager described herein performs these functions. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the functions described below. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0188] At point 1305, the UE can receive the SPS configuration for that UE from the base station. The operation at point 1305 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1305 can be derived from references... Figures 5 to 8 The described SPS configuration receiver is used to perform this.

[0189] At 1310, the UE can receive a DCI from the base station for activating the SPS configuration. The operation at 1310 can be performed according to the method described herein. In some examples, aspects of the operation at 1310 can be derived from references... Figures 5 to 8 The description describes how to activate the DCI receiver to perform this action.

[0190] At step 1315, the UE can determine the channel state report configuration for the SPS configuration based on DCI, SPS configuration, or both. The operation at step 1315 can be performed according to the methods described herein. In some examples, aspects of the operation at step 1315 can be referenced. Figures 5 to 8 The described channel state reporting configuration component is used to perform this.

[0191] At 1320, the UE can send a channel state report to the base station, and according to the channel state report configuration, for the downlink shared channel received according to the SPS configuration. The operation at 1320 can be performed according to the method described herein. In some examples, aspects of the operation at 1320 can be found in the references... Figures 5 to 8 The channel state report described is executed by the transmitter.

[0192] Figure 14 A flowchart illustrating a method 1400 for supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. As described herein, operation of method 1400 can be implemented by UE 115 or its components. For example, operation of method 1400 can be achieved by referring to... Figures 5 to 8 The UE communication manager described herein performs these functions. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the functions described below. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0193] At point 1405, the UE can receive the SPS configuration for that UE from the base station. The operation at point 1405 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1405 can be derived from references... Figures 5 to 8 The described SPS configuration receiver is used to perform this.

[0194] At point 1410, the UE can receive a DCI from the base station to activate the SPS configuration. The operation at point 1410 can be performed according to the method described herein. In some examples, aspects of the operation at point 1410 can be derived from references. Figures 5 to 8 The description describes how to activate the DCI receiver to perform this action.

[0195] At point 1415, the UE can determine the channel state report configuration for the SPS configuration based on the DCI, SPS configuration, or both. The operation at point 1415 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1415 can be derived from references... Figures 5 to 8 The described channel state reporting configuration component is used to perform this.

[0196] At 1420, the UE can recognize that the SPS configuration includes an indication of a channel state report configuration within the channel state report configuration set. The operation at 1420 can be performed according to the methods described herein. In some examples, aspects of the operation at 1420 can be derived from references... Figures 5 to 8 The described channel state reporting configuration component is used to perform this.

[0197] At point 1425, the UE can determine, based on the reception of the DCI, that the channel state report configuration is one of the channel state report configurations in the channel state report configuration set. The operation at point 1425 can be performed according to the method described herein. In some examples, aspects of the operation at point 1425 can be derived from references... Figures 5 to 8 The described channel state reporting configuration component is used to perform this.

[0198] At 1430, the UE can send a channel state report to the base station, and according to the channel state report configuration, for the downlink shared channel received according to the SPS configuration. The operation at 1430 can be performed according to the method described herein. In some examples, aspects of the operation at 1430 can be derived from references... Figures 5 to 8 The channel state report described is executed by the transmitter.

[0199] Figure 15 A flowchart illustrating a method 1500 for supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. As described herein, the operation of method 1500 can be implemented by UE 115 or its components. For example, the operation of method 1500 can be referenced... Figures 5 to 8 The UE communication manager described herein performs these functions. In some examples, the UE can execute a set of instructions to control the functional units of the UE to perform the functions described below. Alternatively, the UE can use dedicated hardware to perform aspects of the functions described below.

[0200] At point 1505, the UE can receive the SPS configuration for that UE from the base station. The operation at point 1505 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1505 can be derived from references. Figures 5 to 8 The described SPS configuration receiver is used to perform this.

[0201] At point 1510, the UE can receive a DCI from the base station to activate the SPS configuration. The operation at point 1510 can be performed according to the method described herein. In some examples, aspects of the operation at point 1510 can be derived from references. Figures 5 to 8 The description describes how to activate the DCI receiver to perform this action.

[0202] At step 1515, the UE can determine the channel state report configuration for the SPS configuration based on DCI, SPS configuration, or both. The operation at step 1515 can be performed according to the methods described herein. In some examples, aspects of the operation at step 1515 can be referenced. Figures 5 to 8 The described channel state reporting configuration component is used to perform this.

[0203] At point 1520, the UE can recognize that the DCI includes an indication of a channel state report configuration within a set of channel state report configurations, wherein the channel state report configuration is a channel state report configuration indicated by the DCI within the set of channel state report configurations. Operation at point 1520 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1520 may be derived from references... Figures 5 to 8 The described channel state reporting configuration component is used to perform this.

[0204] At step 1525, the UE can send a channel state report to the base station, and according to the channel state report configuration, for the downlink shared channel received according to the SPS configuration. The operation at step 1525 can be performed according to the method described herein. In some examples, aspects of the operation at step 1525 can be found in the references... Figures 5 to 8 The channel state report described is executed by the transmitter.

[0205] Figure 16 A flowchart illustrating a method 1600 for supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. As described herein, operation of method 1600 can be implemented by base station 105 or its components. For example, operation of method 1600 can be provided by reference to... Figures 9 to 12 The base station communication manager described herein performs this function. In some examples, the base station may execute a set of instructions to control the functional units of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0206] At step 1605, the base station can send the SPS configuration for communication with the UE. The operation at step 1605 can be performed according to the methods described herein. In some examples, aspects of the operation at step 1605 can be derived from references... Figures 9 to 12 The described SPS configuration transmitter is used to perform this.

[0207] At point 1610, the base station can send a DCI to the UE to activate the SPS configuration, wherein the DCI activates the Channel State Report configuration for the SPS configuration. The operation at point 1610 can be performed according to the method described herein. In some examples, aspects of the operation at point 1610 can be derived from references... Figures 9 to 12 The description describes activating the DCI transmitter to perform this action.

[0208] At point 1615, the base station can receive a channel state report for the downlink shared channel received according to the SPS configuration, from the UE and according to the channel state report configuration. The operation at point 1615 can be performed according to the method described herein. In some examples, aspects of the operation at point 1615 can be derived from references... Figures 9 to 12 The described channel state report is executed by the receiver.

[0209] Figure 17 A flowchart illustrating a method 1700 for supporting downlink-triggered CSI reporting for SPS, according to aspects of this disclosure, is shown. As described herein, operation of method 1700 can be implemented by base station 105 or its components. For example, operation of method 1700 can be achieved by referring to... Figures 9 to 12 The base station communication manager described herein performs this function. In some examples, the base station may execute a set of instructions to control the functional units of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0210] At point 1705, the base station can send the SPS configuration for communication with the UE. The operation at point 1705 can be performed according to the methods described herein. In some examples, aspects of the operation at point 1705 can be derived from references... Figures 9 to 12 The described SPS configuration transmitter is used to perform this.

[0211] At point 1710, the base station can send a DCI to the UE to activate the SPS configuration, wherein the DCI activates the Channel State Report configuration for the SPS configuration. The operation at point 1710 can be performed according to the method described herein. In some examples, aspects of the operation at point 1710 can be derived from references... Figures 9 to 12 The description describes activating the DCI transmitter to perform this action.

[0212] At point 1715, the base station can receive a channel state report from the UE, and according to the channel state report configuration, for the downlink shared channel received according to the SPS configuration. The operation at point 1715 can be performed according to the method described herein. In some examples, aspects of the operation at point 1715 can be derived from references... Figures 9 to 12 The described channel state report is executed by the receiver.

[0213] At 1720, the base station may send an additional DCI to the UE indicating that the SPS configuration is to be released. This additional DCI includes a bit field indicating the channel state report configuration, wherein, based on the additional DCI, no channel state report will be received in future transmissions from the UE. The operation at 1720 can be performed according to the method described herein. In some examples, aspects of the operation at 1720 may be derived from references... Figures 9 to 12 The SPS configuration release indicator is described for execution.

[0214] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0215] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used extensively in the description, the techniques described herein are applicable to areas beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0216] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0217] The various illustrative blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware component, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0218] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. If implemented using software executed by a processor, the functions can be stored as one or more instructions or code on or transmitted through a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including being distributed such that portions of the functions are implemented in different physical locations.

[0219] Computer-readable media include both non-transitory computer storage media and communication media, with communication media encompassing any medium that facilitates the transfer of computer programs from one place to another. Non-transitory storage media can be any available medium accessible by a general-purpose computer or a special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium capable of carrying or storing desired units of program code in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks typically copy data magnetically, while optical discs use lasers to copy data optically. The combinations described above are also included within the scope of computer-readable media.

[0220] As used herein (including in the claims), the word "or" in a list of items (e.g., a list of items ending with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same way as the phrase "at least partially based on".

[0221] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by a dash followed by a second reference numeral, used to differentiate between similar components. If only the first reference numeral is used in the specification, the description applies to any one of the similar components having the same first reference numeral, without regard to the second reference numeral or other subsequent reference numerals.

[0222] This document describes exemplary configurations with reference to the accompanying drawings, but does not represent all examples that can be implemented or that are within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details for the purpose of providing an understanding of the described techniques. However, these techniques may be implemented without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0223] The description herein is provided to enable those skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the scope of the disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but is given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: Receive semi-persistent scheduling configuration for the UE from the network device; Receive downlink control information from the network device to activate the semi-persistent scheduling configuration; Based on the downlink control information, the semi-persistent scheduling configuration, or both, the channel state report configuration for the semi-persistent scheduling configuration is determined, wherein determining the channel state report configuration for the semi-persistent scheduling configuration includes: Identifying the semi-persistent scheduling configuration includes an indication of one of a plurality of channel state reporting configurations; and The determination that the channel state report configuration is one of the plurality of channel state report configurations is based at least in part on the receipt of the downlink control information; and The network device sends a channel state report for the downlink shared channel received according to the semi-persistent scheduling configuration, in accordance with the channel state report configuration.

2. The method according to claim 1, further comprising: According to the semi-persistent scheduling configuration, the downlink shared channel is received from the network device, wherein the downlink shared channel is indicated by the downlink control information; Determine an acknowledgment feedback for the downlink shared channel, the acknowledgment feedback being at least partially based on an attempt to decode the downlink shared channel; and The acknowledgment feedback for the downlink shared channel is sent to the network device, wherein the acknowledgment feedback is sent together with the channel state report.

3. The method according to claim 1, wherein, Regardless of whether the UE successfully decodes the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are sent together.

4. The method according to claim 1, wherein, When the UE fails to decode the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are sent together.

5. The method according to claim 1, wherein, Determining the channel state report configuration for the semi-persistent scheduling configuration includes: Identifying the downlink control information includes an indication of one of a plurality of channel state report configurations, wherein the channel state report configuration is the one indicated by the downlink control information among the plurality of channel state report configurations.

6. The method according to claim 5, wherein, The indication in the downlink control information includes a bit field for activating a channel state reporting configuration included in the semi-persistent scheduling configuration, wherein the semi-persistent scheduling configuration includes one or more configured channel state reporting configurations.

7. The method according to claim 5, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and wherein the indication in the downlink control information includes a multi-bit field indicating the corresponding channel state report configuration for each of the multiple semi-persistent scheduling configurations.

8. The method according to claim 1, further comprising: Receive additional downlink control information indicating that the semi-persistent scheduling configuration will be released, the additional downlink control information including a bit field indicating the channel state report configuration; and The future transmission of the channel state report is avoided, at least in part, based on the receipt of the additional downlink control information.

9. The method according to claim 8, wherein, The bit field includes a predetermined value for indicating the release of the semi-persistent scheduling configuration.

10. The method according to claim 1, wherein, The semi-persistent scheduling configuration includes the following set of configuration parameters: time resources, frequency resources, modulation and coding schemes, or combinations thereof, used for the semi-persistent scheduling configuration.

11. The method according to claim 1, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and the downlink control information is related to one or more of the multiple semi-persistent scheduling configurations.

12. The method according to claim 1, wherein, One or more semi-persistent scheduling configurations are single-carrier configurations for the UE.

13. A method for wireless communication at a network device, comprising: Send a semi-persistent scheduling configuration for communication with the user equipment (UE); The semi-persistent scheduling configuration is used to send an indication of one of the multiple channel state report configurations, wherein the channel state report configuration is the one of the multiple channel state report configurations; Sending downlink control information to activate the semi-persistent scheduling configuration, wherein the downlink control information activates the channel state report configuration for the semi-persistent scheduling configuration; and According to the channel state report configuration, receive the channel state report for the downlink shared channel received according to the semi-persistent scheduling configuration.

14. The method of claim 13, further comprising: According to the semi-persistent scheduling configuration, the downlink shared channel is transmitted, wherein the downlink shared channel is indicated by the downlink control information; and Receive acknowledgment feedback for the downlink shared channel, wherein the acknowledgment feedback is received together with the channel state report.

15. The method according to claim 13, wherein, Regardless of whether the UE successfully decodes the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are received together.

16. The method according to claim 13, wherein, When the UE fails to decode the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are received together.

17. The method of claim 13, further comprising: The downlink control information sends an indication of one of the multiple channel state report configurations, wherein the channel state report configuration is the one channel state report configuration indicated by the downlink control information among the multiple channel state report configurations.

18. The method according to claim 17, wherein, The indication in the downlink control information includes a bit field for activating a channel state reporting configuration included in the semi-persistent scheduling configuration, wherein the semi-persistent scheduling configuration includes one or more configured channel state reporting configurations.

19. The method according to claim 17, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and wherein the indication in the downlink control information includes a multi-bit field indicating the corresponding channel state report configuration for each of the multiple semi-persistent scheduling configurations.

20. The method of claim 13, further comprising: Send additional downlink control information to indicate that the semi-persistent scheduling configuration is to be released, the additional downlink control information including a bit field for indicating the channel state report configuration, wherein, at least in part based on the additional downlink control information, the channel state report will not be received in future transmissions from the UE.

21. The method according to claim 20, wherein, The bit field includes a predetermined value for indicating the release of the semi-persistent scheduling configuration.

22. The method according to claim 13, wherein, The semi-persistent scheduling configuration includes the following set of configuration parameters: time resources, frequency resources, modulation and coding schemes, or combinations thereof, used for the semi-persistent scheduling configuration.

23. The method according to claim 13, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and the downlink control information is related to one or more of the multiple semi-persistent scheduling configurations.

24. The method according to claim 13, wherein, The one or more semi-persistent scheduling configurations are single-carrier configurations for the UE.

25. An apparatus for wireless communication at a user equipment (UE), comprising: processor; A memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor to cause the device to perform the following operations: Receive semi-persistent scheduling configuration for the UE from the network device; Receive downlink control information from the network device to activate the semi-persistent scheduling configuration; Based on the downlink control information, the semi-persistent scheduling configuration, or both, a channel state report configuration for the semi-persistent scheduling configuration is determined, wherein the instruction for determining the channel state report configuration for the semi-persistent scheduling configuration can be executed by the processor to cause the apparatus to: Identifying the semi-persistent scheduling configuration includes an indication of one of a plurality of channel state reporting configurations; and The determination that the channel state report configuration is one of the plurality of channel state report configurations is based at least in part on the receipt of the downlink control information; and The network device sends a channel state report for the downlink shared channel received according to the semi-persistent scheduling configuration, in accordance with the channel state report configuration.

26. The apparatus according to claim 25, wherein, The instructions can also be executed by the processor to make the device: According to the semi-persistent scheduling configuration, the downlink shared channel is received from the network device, wherein the downlink shared channel is indicated by the downlink control information; Determine an acknowledgment feedback for the downlink shared channel, the acknowledgment feedback being at least partially based on an attempt to decode the downlink shared channel; and The acknowledgment feedback for the downlink shared channel is sent to the network device, wherein the acknowledgment feedback is sent together with the channel state report.

27. The apparatus according to claim 25, wherein, Regardless of whether the UE successfully decodes the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are sent together.

28. The apparatus according to claim 25, wherein, When the UE fails to decode the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are sent together.

29. The apparatus according to claim 25, wherein, The instructions for determining the channel state report configuration for the semi-persistent scheduling configuration are executable by the processor to enable the apparatus to: Identifying the downlink control information includes an indication of one of a plurality of channel state report configurations, wherein the channel state report configuration is the one indicated by the downlink control information among the plurality of channel state report configurations.

30. The apparatus according to claim 29, wherein, The indication in the downlink control information includes a bit field for activating a channel state reporting configuration included in the semi-persistent scheduling configuration, wherein the semi-persistent scheduling configuration includes one or more configured channel state reporting configurations.

31. The apparatus according to claim 29, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and wherein the indication in the downlink control information includes a multi-bit field indicating the corresponding channel state report configuration for each of the multiple semi-persistent scheduling configurations.

32. The apparatus according to claim 25, wherein, The instructions can also be executed by the processor to make the device: Receive additional downlink control information indicating that the semi-persistent scheduling configuration will be released, the additional downlink control information including a bit field indicating the channel state report configuration; and The future transmission of the channel state report is avoided, at least in part, based on the receipt of the additional downlink control information.

33. The apparatus according to claim 32, wherein, The bit field includes a predetermined value for indicating the release of the semi-persistent scheduling configuration.

34. The apparatus according to claim 25, wherein, The semi-persistent scheduling configuration includes the following set of configuration parameters: time resources, frequency resources, modulation and coding schemes, or combinations thereof, used for the semi-persistent scheduling configuration.

35. The apparatus according to claim 25, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and the downlink control information is related to one or more of the multiple semi-persistent scheduling configurations.

36. The apparatus according to claim 25, wherein, One or more semi-persistent scheduling configurations are single-carrier configurations for the UE.

37. An apparatus for wireless communication at a network device, comprising: processor; A memory coupled to the processor; as well as Instructions stored in the memory and executable by the processor to cause the device to perform the following operations: Send a semi-persistent scheduling configuration for communication with the user equipment (UE); The semi-persistent scheduling configuration is used to send an indication of one of the multiple channel state report configurations, wherein the channel state report configuration is the one of the multiple channel state report configurations; Sending downlink control information to activate the semi-persistent scheduling configuration, wherein the downlink control information activates the channel state report configuration for the semi-persistent scheduling configuration; and According to the channel state report configuration, receive the channel state report for the downlink shared channel received according to the semi-persistent scheduling configuration.

38. The apparatus according to claim 37, wherein, The instructions can also be executed by the processor to make the device: According to the semi-persistent scheduling configuration, the downlink shared channel is transmitted, wherein the downlink shared channel is indicated by the downlink control information; and Receive acknowledgment feedback for the downlink shared channel, wherein the acknowledgment feedback is received together with the channel state report.

39. The apparatus according to claim 37, wherein, Regardless of whether the UE successfully decodes the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are received together.

40. The apparatus according to claim 37, wherein, When the UE fails to decode the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are received together.

41. The apparatus according to claim 37, wherein, The instructions can also be executed by the processor to make the device: The downlink control information sends an indication of one of the multiple channel state report configurations, wherein the channel state report configuration is the one channel state report configuration indicated by the downlink control information among the multiple channel state report configurations.

42. The apparatus according to claim 41, wherein, The indication in the downlink control information includes a bit field for activating a channel state reporting configuration included in the semi-persistent scheduling configuration, wherein the semi-persistent scheduling configuration includes one or more configured channel state reporting configurations.

43. The apparatus according to claim 41, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and wherein the indication in the downlink control information includes a multi-bit field indicating the corresponding channel state report configuration for each of the multiple semi-persistent scheduling configurations.

44. The apparatus according to claim 37, wherein, The instructions can also be executed by the processor to make the device: Send additional downlink control information to indicate that the semi-persistent scheduling configuration is to be released, the additional downlink control information including a bit field for indicating the channel state report configuration, wherein, at least in part based on the additional downlink control information, the channel state report will not be received in future transmissions from the UE.

45. The apparatus according to claim 44, wherein, The bit field includes a predetermined value for indicating the release of the semi-persistent scheduling configuration.

46. ​​The apparatus according to claim 37, wherein, The semi-persistent scheduling configuration includes the following set of configuration parameters: time resources, frequency resources, modulation and coding schemes, or combinations thereof, used for the semi-persistent scheduling configuration.

47. The apparatus according to claim 37, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and the downlink control information is related to one or more of the multiple semi-persistent scheduling configurations.

48. The apparatus according to claim 37, wherein, One or more semi-persistent scheduling configurations are single-carrier configurations for the UE.

49. An apparatus for wireless communication at a user equipment (UE), comprising: A unit for receiving semi-persistent scheduling configurations for the UE from a network device; A unit for receiving downlink control information from the network device for activating the semi-persistent scheduling configuration; A unit for determining the channel state report configuration for the semi-persistent scheduling configuration based on the downlink control information, the semi-persistent scheduling configuration, or both, wherein the unit for determining the channel state report configuration for the semi-persistent scheduling configuration includes: A unit for identifying the semi-persistent scheduling configuration, including an indication of one of a plurality of channel state reporting configurations; and Used to determine, at least in part based on the reception of the downlink control information, that the channel state report configuration is a unit of one of the plurality of channel state report configurations; and A unit for sending a channel state report to the network device and, according to the channel state report configuration, for the downlink shared channel received according to the semi-persistent scheduling configuration.

50. The apparatus of claim 49, further comprising: A unit for receiving the downlink shared channel from the network device according to the semi-persistent scheduling configuration, wherein the downlink shared channel is indicated by the downlink control information; A unit for determining acknowledgment feedback for the downlink shared channel, the acknowledgment feedback being at least partially based on an attempt to decode the downlink shared channel; and A unit for sending the acknowledgment feedback for the downlink shared channel to the network device, wherein the acknowledgment feedback is sent together with the channel state report.

51. The apparatus according to claim 49, wherein, Regardless of whether the UE successfully decodes the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are sent together.

52. The apparatus according to claim 49, wherein, When the UE fails to decode the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are sent together.

53. The apparatus according to claim 49, wherein, The unit for determining the channel state report configuration for the semi-persistent scheduling configuration includes: A unit for identifying the downlink control information including an indication of one of a plurality of channel state report configurations, wherein the channel state report configuration is the one indicated by the downlink control information among the plurality of channel state report configurations.

54. The apparatus according to claim 53, wherein, The indication in the downlink control information includes a bit field for activating a channel state reporting configuration included in the semi-persistent scheduling configuration, wherein the semi-persistent scheduling configuration includes one or more configured channel state reporting configurations.

55. The apparatus according to claim 53, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and wherein the indication in the downlink control information includes a multi-bit field indicating the corresponding channel state report configuration for each of the multiple semi-persistent scheduling configurations.

56. The apparatus of claim 49, further comprising: A unit for receiving additional downlink control information indicating that the semi-persistent scheduling configuration will be released, the additional downlink control information including a bit field indicating the channel state report configuration; as well as A unit for avoiding future transmissions of the channel state report based at least in part on the receipt of the additional downlink control information.

57. The apparatus according to claim 56, wherein, The bit field includes a predetermined value for indicating the release of the semi-persistent scheduling configuration.

58. The apparatus according to claim 49, wherein, The semi-persistent scheduling configuration includes the following set of configuration parameters: time resources, frequency resources, modulation and coding schemes, or combinations thereof, used for the semi-persistent scheduling configuration.

59. The apparatus according to claim 49, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and the downlink control information is related to one or more of the multiple semi-persistent scheduling configurations.

60. The apparatus according to claim 49, wherein, One or more semi-persistent scheduling configurations are single-carrier configurations for the UE.

61. An apparatus for wireless communication at a network device, comprising: A unit used to send semi-persistent scheduling configurations for communication with user equipment (UE); A unit for sending an indication of one of a plurality of channel state report configurations using the semi-persistent scheduling configuration, wherein the channel state report configuration is the one of the plurality of channel state report configurations; A unit for transmitting downlink control information for activating the semi-persistent scheduling configuration, wherein the downlink control information activates a channel state report configuration for the semi-persistent scheduling configuration; and A unit for receiving a channel state report for a downlink shared channel received according to the semi-persistent scheduling configuration, based on the channel state report configuration.

62. The apparatus of claim 61, further comprising: A unit for transmitting the downlink shared channel according to the semi-persistent scheduling configuration, wherein the downlink shared channel is indicated by the downlink control information; and A unit for receiving acknowledgment feedback for the downlink shared channel, wherein the acknowledgment feedback is received together with the channel state report.

63. The apparatus according to claim 61, wherein, Regardless of whether the UE successfully decodes the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are received together.

64. The apparatus according to claim 61, wherein, When the UE fails to decode the downlink shared channel, the channel state report and acknowledgment feedback for the downlink shared channel are received together.

65. The apparatus of claim 61, further comprising: A unit for transmitting an indication of one of a plurality of channel state report configurations in the downlink control information, wherein the channel state report configuration is the one channel state report configuration indicated by the downlink control information among the plurality of channel state report configurations.

66. The apparatus according to claim 65, wherein, The indication in the downlink control information includes a bit field for activating a channel state reporting configuration included in the semi-persistent scheduling configuration, wherein the semi-persistent scheduling configuration includes one or more configured channel state reporting configurations.

67. The apparatus according to claim 65, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and wherein the indication in the downlink control information includes a multi-bit field indicating the corresponding channel state report configuration for each of the multiple semi-persistent scheduling configurations.

68. The apparatus of claim 61, further comprising: The unit is used to send additional downlink control information indicating that the semi-persistent scheduling configuration is to be released, the additional downlink control information including a bit field indicating the channel state report configuration, wherein, at least in part based on the additional downlink control information, the channel state report will not be received in future transmissions from the UE.

69. The apparatus according to claim 68, wherein, The bit field includes a predetermined value for indicating the release of the semi-persistent scheduling configuration.

70. The apparatus according to claim 61, wherein, The semi-persistent scheduling configuration includes the following set of configuration parameters: time resources, frequency resources, modulation and coding schemes, or combinations thereof, used for the semi-persistent scheduling configuration.

71. The apparatus according to claim 61, wherein, The semi-persistent scheduling configuration includes multiple semi-persistent scheduling configurations, and the downlink control information is related to one or more of the multiple semi-persistent scheduling configurations.

72. The apparatus according to claim 61, wherein, The one or more semi-persistent scheduling configurations are single-carrier configurations for the UE.

73. A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code including instructions executable by a processor for the following operations: Receive semi-persistent scheduling configuration for the UE from the network device; Receive downlink control information from the network device to activate the semi-persistent scheduling configuration; Based on the downlink control information, the semi-persistent scheduling configuration, or both, the channel state report configuration for the semi-persistent scheduling configuration is determined, wherein... The instructions for determining the channel state report configuration for the semi-persistent scheduling configuration can be executed by the processor for: Identifying the semi-persistent scheduling configuration includes an indication of one of a plurality of channel state reporting configurations; and The channel state report configuration is determined to be one of the plurality of channel state report configurations based at least in part on the receipt of the downlink control information. as well as The network device sends a channel state report for the downlink shared channel received according to the semi-persistent scheduling configuration, in accordance with the channel state report configuration.

74. A non-transitory computer-readable medium storing code for wireless communication at a network device, the code including instructions executable by a processor for the following operations: Send a semi-persistent scheduling configuration for communication with the user equipment (UE); The semi-persistent scheduling configuration is used to send an indication of one of the multiple channel state report configurations, wherein, The channel state report configuration is one of the multiple channel state report configurations; Send downlink control information to activate the semi-persistent scheduling configuration, wherein the downlink control information activates the channel state report configuration for the semi-persistent scheduling configuration; as well as According to the channel state report configuration, receive the channel state report for the downlink shared channel received according to the semi-persistent scheduling configuration.

Images