Type 1 Codebook Construction with Multiple Aggregation Factors

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) may determine that a base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE. The UE may identify the applied repetition factor to apply to feedback codebook generation for the one or more downlink transmissions. The UE may generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded. The UE may transmit a feedback report to the base station that includes the feedback codebook.

Description

[0001] Cross-reference

[0002] This patent application claims the benefit of U.S. Provisional Patent Application No. 63 / 006,554, entitled "TYPE-1 CODEBOOK CONSTRUCTION WITH MULTIPLE AGGREGATION FACTORS," filed Apr. 7, 2020, by FAKOORIAN et al., and U.S. Patent Application No. 17 / 222,672, entitled "TYPE-1 CODEBOOK CONSTRUCTION WITH MULTIPLE AGGREGATION FACTORS," filed Apr. 5, 2021, by FAKOORIAN et al., each of which is assigned to the assignee of the present application. Technical Field

[0003] The following generally relates to wireless communication and, in particular, to type-1 codebook construction with multiple aggregation factors.

[0004] Background

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

[0006] Overview

[0007] The described techniques relate to improved methods, systems, devices, and apparatuses for supporting type 1 codebook construction with multiple aggregation factors. Generally, the described techniques provide for more efficient and responsive codebook generation for hybrid automatic repeat / request acknowledgement (HARQ-ACK) reporting. For example, a base station may schedule a user equipment (UE) for (a) downlink transmission(s), where each downlink transmission has an associated repetition factor (e.g., an aggregation factor) from among a plurality of repetition factors (e.g., one, two, four, eight, etc., aggregation factors) configured at the UE. However, the base station and the UE may identify the applied repetition factor to be applied to the feedback codebook generation for the (a) downlink transmission(s). Broadly, the applied repetition factor may be independent of the associated repetition factor for the configured downlink transmission (e.g., may be the same as or different from the aggregation factor configured for the downlink transmission). The base station may transmit the (a) downlink transmission(s) to the UE, and the UE may then generate a feedback codebook to report feedback for the (a) downlink transmission(s) to the base station. In addition to whether the UE was able to successfully receive and decode one or more repetitions of the downlink transmission, the UE may also use the applied repetition factor to generate the feedback codebook. Accordingly, the UE may transmit or otherwise convey a feedback report carrying or conveying an indication of the feedback codebook to the base station.

[0008] A method for wireless communication at a UE is described. The method may include: determining that a base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE; identifying an applied repetition factor to be applied to feedback codebook generation for the one or more downlink transmissions; generating a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated based on the applied repetition factor and based on whether the one or more downlink transmissions were successfully received and decoded; and transmitting a feedback report including the feedback codebook to the base station.

[0009] Describes an apparatus for wireless communication at a UE. The apparatus may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to: determine that a base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE; identify the applied repetition factor to apply to feedback codebook generation for the one or more downlink transmissions; generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded; and transmit a feedback report including the feedback codebook to the base station.

[0010] Describes another device for wireless communication at a UE. The device may include: means for determining that a base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE; means for identifying the applied repetition factor to apply to feedback codebook generation for the one or more downlink transmissions; means for generating a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded; and means for transmitting a feedback report including the feedback codebook to the base station.

[0011] Describes a non-transitory computer-readable medium storing code for wireless communication at a UE. The code may include instructions executable by a processor to: determine that a base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE; identify the applied repetition factor to apply to feedback codebook generation for the one or more downlink transmissions; generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded; and transmit a feedback report including the feedback codebook to the base station.

[0012] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying the applied repetition factor based on the maximum numerical value of the configured repetition factors in the set of configured repetition factors.

[0013] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for identifying the maximum value of the configured repetition factor without accounting for the configured repetition factor corresponding to an inactive semi-persistent scheduling (SPS) configuration.

[0014] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for identifying the maximum value of the configured repetition factor by accounting for the configured repetition factor corresponding to both active and inactive SPS configurations.

[0015] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for identifying the applied repetition factor as 1 and generating the feedback codebook based on the last instance of each downlink transmission actually received and decoded.

[0016] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for determining, for each downlink transmission among the one or more downlink transmissions, that one or more instances of the downlink transmission have been discarded and generating the feedback codebook differently for the one or more discarded instances of the downlink transmission and for the one or more non-discarded instances of the downlink transmission.

[0017] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, generating the feedback codebook may further include operations, features, apparatuses, or instructions for generating an acknowledgement / negative acknowledgement (ACK / NACK) indication for each downlink transmission actually received and decoded and suppressing the generation of ACK / NACK indications for each instance of a discarded downlink transmission opportunity.

[0018] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the feedback codebook may be generated without considering the downlink control information associated with the one or more downlink transmissions.

[0019] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for generating the feedback codebook based on an evaluation of each of the set of reporting offset values within the evaluation window.

[0020] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for receiving a configuration of a plurality of SPS configurations, where each of the one or more downlink transmissions is associated with a common SPS configuration or with a different SPS configuration among the plurality of SPS configurations.

[0021] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the feedback codebook is a type 1 codebook.

[0022] A method for wireless communication at a base station is described. The method may include: scheduling a UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE; identifying the applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions; and receiving, from the UE, a feedback report including a feedback codebook that is generated to report feedback for the one or more downlink transmissions and is populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

[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 may be executable by the processor to cause the apparatus to: schedule a UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE; identify the applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions; and receive, from the UE, a feedback report including a feedback codebook that is generated to report feedback for the one or more downlink transmissions and is populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

[0024] Describes another device for wireless communication at a base station. The device may include: means for scheduling a UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE; means for identifying the applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions; and means for receiving from the UE a feedback report including the feedback codebook, the feedback codebook being generated to report feedback for the one or more downlink transmissions and being populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

[0025] Describes a non-transitory computer-readable medium storing code for wireless communication at a base station. The code may include instructions executable by a processor to: schedule a UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE; identify the applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions; and receive from the UE a feedback report including the feedback codebook, the feedback codebook being generated to report feedback for the one or more downlink transmissions and being populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

[0026] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying the applied repetition factor based on the maximum value of the configured repetition factors in the set of configured repetition factors.

[0027] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying the maximum value of the configured repetition factors without counting the configured repetition factors corresponding to an inactive semi-persistent scheduling (SPS) configuration of the UE.

[0028] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying the maximum value of the configured repetition factors by counting the configured repetition factors corresponding to both active and inactive SPS configurations of the UE.

[0029] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for identifying the applied repetition factor as 1, where the feedback codebook may be generated based on the last instance of each downlink transmission actually received and decoded.

[0030] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for scheduling at least one non-conflicting instance of the downlink transmission during an evaluation window based on the reported offset value, based on the configured set of repetition factors.

[0031] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for determining, for each of the one or more downlink transmissions, that one or more instances of the downlink transmission have been discarded, where the feedback codebook is generated differently for the discarded one or more instances of the downlink transmission and for the non-discarded one or more instances of the downlink transmission.

[0032] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the feedback codebook may be generated based on: an ACK / NACK indication may be generated for each downlink transmission actually received and decoded by the UE, and an ACK / NACK indication may not be generated for each instance of a discarded downlink transmission opportunity.

[0033] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the feedback codebook may be generated without considering the downlink control information associated with the one or more downlink transmissions.

[0034] In some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein, the UE may be configured with a set of reporting offset values for transmitting the feedback report, each of the set of reporting offset values representing the number of time slots after the last nominal downlink transmission, the set of reporting offset values spanning an evaluation window, and the feedback codebook may be generated based on the UE's evaluation of each of the set of reporting offset values within the evaluation window.

[0035] Some examples of the methods, apparatuses (devices), and non-transitory computer-readable media described herein may further include operations, features, apparatuses, or instructions for transmitting a configuration of a plurality of SPS configurations, where each of the one or more downlink transmissions is associated with a common SPS configuration or with a different SPS configuration among the plurality of SPS configurations.

[0036] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the feedback codebook is a type 1 codebook. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] Figure 1 Examples of wireless communication systems for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure are illustrated.

[0039] Figure 2 Examples of feedback configurations for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure are illustrated.

[0040] Figure 3 Examples of feedback configurations for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure are illustrated.

[0041] Figure 4 Examples of processes for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure are illustrated.

[0042] Figure 5 Examples of feedback configurations for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure are illustrated.

[0043] Figure 6 and 7 A block diagram of an apparatus for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is shown.

[0044] Figure 8 A block diagram of a communication manager for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is shown.

[0045] Figure 9 A diagram of a system including an apparatus for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is shown.

[0046] Figure 10 and 11 A block diagram of an apparatus for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is shown.

[0047] Figure 12 A block diagram of a communication manager for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is shown.

[0048] Figure 13 A diagram of a system including an apparatus for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is shown.

[0049] Figures 14 to 18 A flowchart is shown that illustrates a method for supporting a type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure.

[0050] Detailed description

[0051] Wireless communication systems typically utilize hybrid automatic repeat / request acknowledgement (HARQ-ACK) feedback reports to confirm that a device has successfully received and decoded a transmission. The HARQ-ACK feedback report may include a feedback codebook (or simply a codebook) that includes a series of bits generated based on the configuration of the transmission. For example, a base station may schedule a user equipment (UE) with a downlink transmission (e.g., a physical downlink shared channel (PDSCH) transmission) that includes a repetition factor (or aggregation factor) for the downlink transmission and an associated reporting offset value (e.g., a K1 value). The UE may be configured with multiple PDSCH aggregation factors, e.g., for dynamic PDSCH and / or for different semi-persistent scheduling (SPS) configurations. When the repetition or aggregation factor for a downlink transmission is greater than 1, the UE may report a negative acknowledgement (NACK) bit for each repetition of the downlink transmission until the last repetition. For the last repetition, the UE determines whether it has successfully received and decoded at least one repetition and reports an acknowledgement / negative acknowledgement (ACK / NACK) bit for the downlink transmission. However, some repetitions of the downlink transmission may conflict and thus not be available for transmission to the UE. This may create confusion and inaccuracies in the codebook generated by the UE for providing to the base station, which may result in wasted resources for unnecessary retransmissions and / or a loss of communication between the UE and the base station.

[0052] Aspects of the present disclosure are initially described in the context of a wireless communication system. Generally, the described techniques provide for more efficient and responsive codebook generation for HARQ-ACK reporting. For example, a base station may schedule a UE for a (downlink) transmission, where each downlink transmission has an associated repetition factor (e.g., aggregation factor) from among a plurality of repetition factors (e.g., one, two, four, eight, etc.) configured at the UE. However, the base station and the UE may identify the applied repetition factor to be used for feedback codebook generation for the (downlink) transmission. Broadly, the applied repetition factor may be independent of the associated repetition factor used for the configured downlink transmission (e.g., may be the same as or different from the aggregation factor configured for the downlink transmission). The base station may transmit the (downlink) transmission to the UE, and the UE may then generate a feedback codebook to report feedback for the (downlink) transmission to the base station. In addition to whether the UE was able to successfully receive and decode one or more repetitions of the downlink transmission, the UE may also use the applied repetition factor to generate the feedback codebook. Accordingly, the UE may transmit or otherwise convey a feedback report carrying or conveying an indication of the feedback codebook to the base station.

[0053] Aspects of the present disclosure are further illustrated and described by and with reference to apparatus diagrams, system diagrams, and flowcharts related to type 1 codebook construction with multiple aggregation factors.

[0054] Figure 1 An example of a wireless communication system 100 supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is illustrated. 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 LTE-Advanced (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, communication with low-cost and low-complexity devices, or any combination thereof.

[0055] The base stations 105 may be dispersed over a geographic area to form the wireless communication system 100 and may be different forms of devices or devices with different capabilities. The base stations 105 and the UEs 115 may communicate wirelessly via one or more communication links 125. Each base station 105 may provide a coverage area 110, and the UEs 115 and the base stations 105 may establish one or more communication links 125 over the coverage area 110. The coverage area 110 may be an example of a geographic area over which the base stations 105 and the UEs 115 may support signal communication according to one or more radio access technologies.

[0056] Each UE 115 may be dispersed throughout the coverage area 110 of the wireless communication system 100, and each UE 115 may be stationary or mobile, or stationary and mobile at different times. Each UE 115 may be a device of different forms or with different capabilities. In Figure 1 some example UEs 115 are illustrated. The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115, base stations 105, or network equipment (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network equipment), as Figure 1 shown.

[0057] Each base station 105 may communicate with the core network 130, or with each other, or both. For example, the base station 105 may interface with the core network 130 via one or more backhaul links 120 (e.g., via S1, N2, N3, or other interfaces). The base stations 105 may communicate with each other directly (e.g., directly between the base stations 105), or indirectly (e.g., via the core network 130), or directly and indirectly over the backhaul links 120 (e.g., via X2, Xn, or other interfaces). In some examples, the backhaul link 120 may be or include one or more wireless links.

[0058] One or more of the base stations 105 described herein may include or may be referred to by those of ordinary skill in the art as a base transceiver station, radio base station, access point, radio transceiver, B node, evolved B node (eNB), next generation B node, or gigabit B node (any of which may be referred to as a gNB), home B node, home evolved B node, or other suitable terms.

[0059] The UE 115 may include or may be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, where "device" may also be referred to as a unit, station, terminal, or client, etc. The UE 115 may also include or may 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, the 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, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0060] The UEs 115 described herein may be capable of communicating with various types of devices, such as other UEs 115 that may sometimes act as relays, as well as base stations 105 and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, relay base stations, etc., as Figure 1 shown.

[0061] UE 115 and base station 105 may wirelessly communicate with each other via one or more communication links 125 over one or more carriers. The term "carrier" may refer 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 (e.g., bandwidth part (BWP)) of a radio frequency spectrum band operating 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 for coordinating carrier operation, user data, or other signaling. The wireless communication system 100 may support communicating with UE 115 using carrier aggregation or multi-carrier operation. UE 115 may be configured to have multiple downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) and time division duplex (TDD) component carriers.

[0062] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling for coordinating the operation of other carriers. A carrier may be associated with a frequency channel (e.g., evolved universal mobile telecommunications system terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and may be positioned according to a channel raster for discovery by UE 115. A carrier may operate in a stand-alone mode in which initial acquisition and connection may be performed by UE 115 via the carrier, or a carrier may operate in a non-stand-alone mode in which the connection is anchored using a different carrier (e.g., different carriers of the same or different radio access technologies).

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

[0064] A carrier can be associated with a specific bandwidth of the radio frequency spectrum, and in some examples, this carrier bandwidth can be referred to as the "system bandwidth" of the carrier or the wireless communication system 100. For example, the carrier bandwidth can be one of several determined bandwidths of a carrier of a specific radio access technology (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 megahertz (MHz)). Devices of the wireless communication system 100 (e.g., the base station 105, the UE 115, or both) can have a hardware configuration that supports communication on a specific carrier bandwidth, or can be configurable to support communication on one of the carrier bandwidths in a carrier bandwidth set. In some examples, the wireless communication system 100 can include a base station 105 or a 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, a BWP) or all of the carrier bandwidth.

[0065] The signal waveform transmitted on a carrier can include multiple subcarriers (e.g., using a multi-carrier modulation (MCM) technique, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform spread OFDM (DFT-S-OFDM)). In a system employing an MCM technique, a resource element can include a symbol period (e.g., the duration of a modulated symbol) and a subcarrier, where the symbol period and the 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 code rate of the modulation scheme, or both). Thus, the more resource elements the UE 115 receives and the higher the order of the modulation scheme, the higher the data rate of the UE 115 can be. Wireless communication resources can refer to a combination of radio frequency spectrum resources, time resources, and spatial resources (e.g., spatial layers or beams), and using multiple spatial layers can further increase the data rate or data integrity of communication with the UE 115.

[0066] One or more parameter sets can be supported for a carrier, where a parameter set can include a subcarrier spacing (Δf) and a cyclic prefix. A carrier can be divided into one or more BWPs with the same or different parameter sets. In some examples, the UE 115 can be configured with multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for the UE 115 can be limited to one or more active BWPs.

[0067] The time intervals of the base station 105 or the UE 115 can be expressed as multiples of a basic time unit, and the basic time unit can refer to, for example, a sampling period T s = 1 / (Δf max ·N f ) seconds, where Δf max can represent the maximum supported subcarrier spacing, and Nf It can represent the maximum supported Discrete Fourier Transform (DFT) size. The time intervals of communication resources can be organized according to 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).

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

[0069] A sub - frame, time slot, mini - slot, or symbol can be the smallest scheduling unit (e.g., in the time domain) of the wireless communication system 100 and can be referred to as a transmission time interval (TTI). In some examples, the TTI duration (e.g., the number of symbol periods in a TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in bursts of shortened TTI (sTTI)).

[0070] Physical channels can be multiplexed on a carrier according to various techniques. The physical control channel and the physical data channel can be multiplexed on a downlink carrier using, for example, one or more of time division multiplexing (TDM) techniques, frequency division multiplexing (FDM) techniques, or hybrid TDM-FDM techniques. A control region for the physical control channel (e.g., a control resource set (CORESET)) can be defined by the number of symbol periods and can extend across the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESETs) can be configured for a set of UEs 115. For example, one or more of the UEs 115 can monitor or search a control region for control information according to one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a cascaded manner. The aggregation level for a control channel candidate can refer to the number of control channel resources (e.g., control channel elements (CCEs)) associated with the encoded information for a control information format having a given payload size. The search space set can include a common search space set configured to send control information to multiple UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0071] Each base station 105 can 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" can refer to a logical communication entity for communicating with a base station 105 (e.g., on a carrier) and can be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others) for distinguishing adjacent cells. In some examples, a cell can also refer to a geographic coverage area 110 or a portion of the geographic coverage area 110 (e.g., a sector) on which the logical communication entity operates. The scope of such cells can vary depending on various factors (such as the capabilities of the base station 105) from a smaller area (e.g., a structure, a subset of a structure) to a larger area. For example, a cell can be or include a building, a subset of a building, or an external space between or overlapping with the geographic coverage area 110, and other examples.

[0072] Macro cells generally cover a relatively large geographical area (e.g., with a radius of several kilometers) and may allow unconstrained access by UEs 115 having a service subscription with the network provider supporting the macro cell. Small cells may be associated with a lower-power base station 105 (compared to macro cells), and small cells may operate in the same or different (e.g., licensed, unlicensed) frequency bands as macro cells. Small cells may provide unconstrained access to UEs 115 having a service subscription with the network provider, or may provide constrained access to UEs 115 associated with the small cell (e.g., UEs 115 in a closed subscriber group (CSG), UEs 115 associated with users in a home or office). The base station 105 may support one or more cells and may also support communication on one or more cells using one or more component carriers.

[0073] In some examples, a carrier may support multiple cells and may be configured with different cells according to different protocol types that may provide access for different types of devices (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)).

[0074] In some examples, the base station 105 may be mobile and thus provide communication coverage for a mobile geographical coverage area 110. In some examples, different geographical coverage areas 110 associated with different technologies may overlap, but different geographical coverage areas 110 may be supported by the same base station 105. In other examples, overlapping geographical coverage areas 110 associated with different technologies may be supported by different base stations 105. The wireless communication system 100 may include, for example, a heterogeneous network where different types of base stations 105 use the same or different radio access technologies to provide coverage for various geographical coverage areas 110.

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

[0076] Some UEs 115 (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 a base station 105 without human intervention. In some examples, M2M communication or MTC can include communication from devices integrated with sensors or meters to measure or capture information and relay such information to a central server or application that utilizes the information or presents the information to a person interacting with the application. Some UEs 115 can be designed to collect information or implement automated behavior of machines or other devices. Examples of applications for MTC devices include: smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, field survival monitoring, weather and geographical event monitoring, queue management and tracking, remote security sensing, physical access control, and transaction-based commercial charging.

[0077] Some UEs 115 can be configured to operate in power-saving modes, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UEs 115 include entering a deep sleep power-saving mode when not participating in active communication, operating on limited bandwidth (e.g., according to narrowband communication), or a combination of these techniques. For example, some UEs 115 can be configured for operation using a narrowband protocol type associated with a defined portion or range within a carrier, within a guard band of a carrier, or outside a carrier (e.g., a set of subcarriers or resource blocks (RBs)).

[0078] The wireless communication system 100 can be configured to support ultra-reliable communication or low-latency communication or various combinations thereof. For example, the wireless communication system 100 can be configured to support ultra-reliable low-latency communication (URLLC) or mission-critical communication. UEs 115 can be designed to support ultra-reliable, low-latency, or critical functions (e.g., mission-critical functions). Ultra-reliable communication can include private communication 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 prioritization of services, 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 can be used interchangeably herein.

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

[0080] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., the UE 115). In some examples, vehicles may communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination of these communications. Vehicles may signal information related to traffic conditions, signal scheduling, weather, safety, emergencies, or any other information related to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as a roadside unit), or with a network, or with both, using vehicle-to-network (V2N) communication via one or more network nodes (e.g., the base station 105).

[0081] The core network 130 may provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. The core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and the EPC or 5GC may include at least one control plane entity (e.g., a mobility management entity (MME), an access and mobility management function (AMF)) that manages access and mobility, and at least one user plane entity (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)) that routes packets or interconnects to an external network. The control plane entity may manage non-access stratum (NAS) functions, such as the mobility, authentication, and bearer management of the UE 115 served by the base station 105 associated with the core network 130. User IP packets may be passed through the user plane entity, which may provide IP address allocation and other functions. The user plane entity may be connected to the network operator IP services 150. The operator IP services 150 may include access to the Internet, an intranet, an IP multimedia subsystem (IMS), or a packet-switched streaming service.

[0082] Some network devices, such as base station 105, may include subcomponents, 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 respective UEs 115 via one or more other access network transmission entities 145, which may be referred to as radio heads, intelligent radio heads, or transmit / receive points (TRPs). Each access network transmission 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 various network devices (e.g., radio heads and ANCs) or consolidated into a single network device (e.g., base station 105).

[0083] Wireless communication system 100 may operate using one or more frequency bands, typically in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the 300 MHz to 3 GHz division is known as the ultra-high frequency (UHF) division or the decimeter band because the wavelengths are in the range of approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features, but these waves can sufficiently penetrate various structures for macrocells to provide service to UEs 115 located indoors. Compared to transmissions using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz, UHF wave transmissions may be associated with smaller antennas and shorter ranges (e.g., less than 100 kilometers).

[0084] Wireless communication system 100 may also operate in the super-high frequency (SHF) division using frequency bands from 3 GHz to 30 GHz (also known as the centimeter band) or in the extremely high frequency (EHF) division of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, wireless communication system 100 may support millimeter wave (mmW) communication between UEs 115 and base station 105, and the EHF antennas of the corresponding devices may be smaller and more closely spaced than UHF antennas. In some examples, this may enable the use of antenna arrays within the devices. However, the propagation of EHF transmissions may experience even greater atmospheric attenuation and shorter ranges than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency divisions, and the use of frequency bands designated across these frequency divisions may vary by country or regulatory body.

[0085] The wireless communication system 100 can utilize both licensed and unlicensed radio frequency bands. For example, the wireless communication system 100 can adopt licensed-assisted access (LAA), LTE-unlicensed (LTE-U) radio access technology, or NR technology in an unlicensed band (such as the 5 GHz industrial, scientific, and medical (ISM) band). When operating in an unlicensed radio frequency band, devices (such as base station 105 and UE 115) can adopt carrier sensing for collision detection and avoidance. In some examples, the operation in the unlicensed band can be based on a carrier aggregation configuration (e.g., LAA) in coordination with a component carrier operating in a licensed band. The operation in the unlicensed spectrum can include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0086] Base station 105 or UE 115 can be equipped with multiple antennas, which can be used to adopt techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of base station 105 or UE 115 can be located within one or more antenna arrays or antenna panels that can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays can 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 can be located at different geographical locations. Base station 105 can have an antenna array that has several rows and columns of antenna ports for beamforming that base station 105 can use to support communication with UE 115. Similarly, UE 115 can have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel can support radio frequency beamforming for signals transmitted via the antenna ports.

[0087] Base station 105 or UE 115 can use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. Such techniques can be referred to as spatial multiplexing. For example, the transmitting device can transmit multiple signals via different antennas or different combinations of antennas. Similarly, the receiving device can receive multiple signals via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers can be associated with different antenna ports for channel measurement and reporting. MIMO techniques include single-user MIMO (SU-MIMO), where multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), where multiple spatial layers are transmitted to multiple devices.

[0088] 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 device or a receiving device (e.g., base station 105, UE 115) to shape or steer an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated via the 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. The adjustment of the signals communicated via the antenna elements can include the transmitting device or the receiving device applying an amplitude offset, a phase offset, or both to the signals carried via the antenna elements associated with that device. The adjustment 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 device or the receiving device, or relative to some other orientation).

[0089] The base station 105 or the UE 115 can use beam sweeping techniques as part of beamforming operations. For example, the base station 105 can use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with the UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) can be transmitted by the base station 105 multiple times in different directions. For example, the base station 105 can transmit signals according to different sets of beamforming weights associated with different transmission directions. Transmissions in different beam directions can be used (e.g., by the transmitting device (such as the base station 105) or the receiving device (such as the UE 115)) to identify the beam direction used by the base station 105 for later transmission or reception.

[0090] Some signals (such as data signals associated with a particular receiving device) can be transmitted by the base station 105 in a single beam direction (e.g., the direction associated with the receiving device (such as the UE 115)). In some examples, the beam direction associated with transmission in a single beam direction can be determined based on signals transmitted in one or more beam directions. For example, the UE 115 can receive one or more signals transmitted by the base station 105 in different directions and can report an indication to the base station 105 of the signal received by the UE 115 with the highest signal quality or other acceptable signal quality.

[0091] In some examples, transmissions performed by a device (e.g., by base station 105 or UE 115) may be carried out using multiple beam directions, and the device may use a combination of digital precoding or radio frequency beamforming to generate a combined beam for transmission (e.g., from base station 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured number of beams across the system bandwidth or one or more subbands. Base station 105 may transmit reference signals that may or may not be precoded (e.g., cell-specific reference signal (CRS), channel state information reference signal (CSI-RS)). UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel type codebook, linear combination type codebook, port selection type codebook). Although these techniques are described with reference to signals transmitted by base station 105 in one or more directions, UE 115 may use similar techniques for transmitting signals multiple times in different directions (e.g., for identifying beam directions used by UE 115 for subsequent transmissions or receptions) or for transmitting signals in a single direction (e.g., for transmitting data to a receiving device).

[0092] A receiving device (e.g., UE 115) may attempt multiple receive configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from base station 105. For example, the receiving device may attempt multiple receive directions by: receiving via different antenna subarrays, processing received signals according to different antenna subarrays, receiving according to different sets of receive beamforming weights (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing received signals according to different sets of receive beamforming weights applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receive configurations or receive directions. In some examples, the receiving device may use a single receive configuration to receive along a single beam direction (e.g., when receiving a data signal). The single receive configuration may be aligned in a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0093] The wireless communication system 100 can be a packet-based network that operates according to a layered protocol stack. On the user plane, the communication of the bearer or Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can perform packet segmentation and reassembly for communication on the logical channels. The Media Access Control (MAC) layer can perform priority handling and multiplex the logical channels into the 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. On the control plane, the Radio Resource Control (RRC) protocol layer can provide the establishment, configuration, and maintenance of the RRC connection that supports the radio bearers for user plane data between the UE 115 and the base station 105 or the core network 130. On the physical layer, the transport channels can be mapped to the physical channels.

[0094] The UE 115 and the base station 105 can support retransmissions of data to increase the likelihood that the data is successfully received. Hybrid Automatic Repeat Request (HARQ) feedback is a technique for increasing the likelihood that data is correctly received on the 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 the throughput of the MAC layer in poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device can support simultaneous slot HARQ feedback, where the device can provide HARQ feedback for data received in previous symbols in a particular slot in that slot. In other cases, the device can provide HARQ feedback in a subsequent slot or according to some other time interval.

[0095] The UE 115 can determine that the base station 105 has scheduled the UE 115 for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE 115. The UE 115 can identify the applied repetition factor to apply to the generation of the feedback codebook for the one or more downlink transmissions. The UE 115 can generate a feedback codebook for reporting feedback for the one or more downlink transmissions, and populate the feedback codebook at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded. The UE 115 can transmit a feedback report including the feedback codebook to the base station 105.

[0096] The base station 105 may schedule the UE 115 for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE 115. The base station 105 may identify the applied repetition factor for the UE 115 to apply to feedback codebook generation for the one or more downlink transmissions. The base station 105 may receive from the UE 115 a feedback report including a feedback codebook that is generated to report feedback for the one or more downlink transmissions and is populated at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE 115.

[0097] Figure 2 An example of a feedback configuration 200 that supports a type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is illustrated. In some examples, the codebook configuration 200 may implement aspects of the wireless communication system 100. Aspects of the feedback configuration 200 may be implemented by a base station and / or a UE, which may be examples of the corresponding devices described herein.

[0098] Broadly, the feedback configuration 200 spans multiple time slots 205, with five time slots 205 shown by way of example only. The time slots 205 may be configured with one or more PDSCH opportunities 210, a first downlink transmission 215 (e.g., PDSCH #1), a second downlink transmission 220 (e.g., PDSCH #2), and a physical uplink control channel (PUCCH) 225 (e.g., a feedback report opportunity where the UE transmits a feedback report for the downlink transmission to the base station).

[0099] In some wireless communication systems, a UE typically reports HARQ-ACK information (e.g., a feedback report) for PDSCH reception (e.g., a downlink transmission) from time slot to time slot n in a HARQ-ACK codebook, and the UE includes the HARQ-ACK codebook in a PUCCH or physical uplink shared channel (PUSCH) transmission in time slot n + k. If the UE is provided or otherwise configured with a PDSCH aggregation factor, then may be the value of the PDSCH aggregation or repetition factor (pdsch-AggregationFactor). Otherwise, It can be assumed to be 1. k can be the number of time slots indicated by the PDSCH-to-HARQ feedback timing indicator in the corresponding downlink control information (DCI) format (e.g., the offset reporting time slot indicated by the K or K1 value), or if the PDSCH-to-HARQ feedback timing indicator field does not exist in the DCI format, the number of time slots provided by dl-Data to UL-ACK. If the UE reports HARQ-ACK information received for the PDSCH in a time slot other than time slot n, the UE sets the value used for each corresponding HARQ-ACK information bit to NACK or N. If the UE is provided with tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and does not receive any repetitions due to uplink / downlink interaction / collision, then for the associated PDSCH with repetitions, no ACK / NACK bits are generated in the codebook.

[0100] In some wireless communication systems, the UE can be configured with multiple SPS configurations. For example, these wireless communication systems can utilize the configuration of the PDSCH aggregation factor (pdsch-AggregationFactor) for each downlink SPS configuration, where the aggregation factor values range from {1, 2, 4, 8} (e.g., the aggregation or repetition factor is 1, 2, 4, or 8). For a PDSCH scheduled without a corresponding PDCCH transmission (e.g., without DCI) using sps-Config and activated by DCI format 1_1 or 1_2, or a PDSCH scheduled by DCI format 1_1 or 1_2 in a PDCCH scrambled with a configured scheduling radio network temporary identifier (CS-RNTI) and the new data indicator (NDI) is set to zero, the PDSCH aggregation factor signaled in sps-Config (if configured) is applied. Otherwise, the PDSCH aggregation factor signaled in pdsch-Config is applied. For a PDSCH scheduled by DCI format 1_1 or 1_2 in a PDCCH where the CRC is scrambled with CS-RNTI and NDI is set to 1, the PDSCH aggregation factor signaled in pdsch-Config is applied.

[0101] Accordingly, a UE may be configured with multiple downlink transmission aggregation factors (e.g., pdsch-AggregationFactor), e.g., for dynamic PDSCH in pdsch-Config and / or for different SPS configurations in sps-Config, and these configurations may have different values of the aggregation or repetition factor (e.g., pdsch-AggregationFactor). When multiple aggregation or repetition factors are configured, this raises the question of what setting should be used for the purpose of determining when to transmit a type 1 HARQ-ACK codebook (e.g., in which sub-slot or slot to transmit the HARQ-ACK codebook via PUCCH or PUSCH, such as a feedback report) and / or how to construct the type 1 HARQ-ACK codebook (e.g., including the codebook size and the ACK / NACK bit positions within the codebook). of the problem.

[0102] In such a wireless communication system, when the PDSCH aggregation factor is greater than 1 and a PDSCH occasion is dropped (e.g., due to downlink / uplink interaction or conflict), the type 1 codebook construction has a size overhead problem. That is, a UE may be configured with only one PDSCH aggregation factor, which is set to two (e.g., in the example illustrated in feedback configuration 200, repeated twice for each of the first downlink transmission 215 and the second downlink transmission 220). The configured set of K1 values (illustrated as K) may be {1, 2, 4, 8}. In slot n (e.g., slot 205-d), due to a conflict with an uplink symbol / signal, the second repetition of the second downlink transmission 220 is dropped. Additionally, both PDSCH occasions in slot n-2 (e.g., slot 205-b) overlap with an uplink symbol or signal, and thus the first repetition of the first downlink transmission 215 is dropped. As shown in the "old" codebook, the time domain resource allocation (TDRA) table may have only two non-overlapping start and length indicator value (SLIV) rows for PDSCH (e.g., N, N for slot 205-b, A / N, N for slot 205-c, and N, A / N for slot 205-d). However, the codewords generated using conventional techniques (e.g., the "old" codebook) include too many bits, which increases the size and / or complexity of the codebook. This may also cause confusion between the base station and the UE regarding how to generate the codebook, and may thus be read by the base station. However, aspects of the described techniques achieve removing the dropped PDSCH occasions (e.g., where the downlink transmission may be scheduled or the occasion is scheduled for the UE) from the type 1 codebook.

[0103] Accordingly, aspects of the described techniques provide for a base station to schedule a UE for one or more downlink transmissions (e.g., by way of example only, a first downlink transmission 215 and a second downlink transmission 220). Each downlink transmission may have an associated repetition factor corresponding to one of a plurality of repetition factors configured at the UE (e.g., {1, 2, 4, 8}) (e.g., in this example, the aggregation factor is 2 for both downlink transmissions). However, the base station and the UE may identify the applied repetition factor (aggregation factor) to be applied to the generation of the feedback codebook for the scheduled downlink transmission, rather than the associated repetition or aggregation factor.

[0104] The base station may transmit downlink transmissions to the UE according to a configuration. For example, slot n - 3 (e.g., slot 205 - a) is scheduled with two PDSCH opportunities 210. Broadly, a PDSCH opportunity 210 generally refers to an opportunity (in the form of resources) in which a downlink transmission may be scheduled for a UE. In the feedback configuration 200, the shown PDSCH opportunities 210 are resources in which a downlink transmission may be scheduled but is not scheduled. However, each of the downlink transmissions occurs during a PDSCH opportunity. In the feedback configuration 200, the actually scheduled transmission is indicated as a PDSCH transmission, and the unused transmission resources or opportunities are referred to as PDSCH opportunities 210. Each of the slots on which a PDSCH may be received is illustrated as having the same PDSCH opportunity. As discussed, a portion of slot n - 2 (e.g., slot 205 - b) has been configured as an uplink portion that overlaps with two PDSCH opportunities, and thus any PDSCH (e.g., whether a PDSCH opportunity 210 or a first repetition of the first downlink transmission 215) occurring within that slot is discarded. During slot n - 1 (e.g., slot 205 - c), the base station may transmit a second repetition of the first downlink transmission 215 (with a reporting offset of K or K1 = 2) and a first repetition of the second downlink transmission 220 (with a reporting offset of K or K1 = 1). Also as discussed, during slot n (e.g., slot 205 - d), a second repetition of the second downlink transmission 220 conflicts and is thus not transmitted or is discarded.

[0105] Accordingly, the UE may generate a feedback codebook for reporting feedback for the scheduled downlink transmission, the feedback codebook being populated at least in part based on the applied repetition factor and based on whether the scheduled downlink transmission was successfully received and decoded by the UE. That is, the UE may utilize the applied repetition factor rather than the repetition factor associated with the (one or more) downlink transmissions configured by the base station. Various alternative schemes may be used with respect to identifying and applying the applied repetition factor.

[0106] An alternative scheme may include identifying the applied repetition factor based on the maximum value of the configured repetition factor from the UE (e.g., across all PDSCH aggregation factors, or the maximum value of the pdsch-AggregationFactor configuration). For example, both the UE and the base station may identify the maximum value of the configured repetition factor without taking into account or otherwise considering the configured repetition factor corresponding to inactive SPS(s) (e.g., when configured for the UE, the PDSCH aggregation factor does not include inactive SPS configurations). In another example, the base station and the UE may identify the maximum value of the configured repetition factor by taking into account the configured repetition factor corresponding to both active and inactive SPS configurations (e.g., the PDSCH aggregation factor, or pdsch-AggregationFactor configuration, including both active and inactive SPS configurations when configured for the UE). In a given time slot 205, the ACK / NACK bit positions in the type 1 codebook corresponding to the PDSCH from the TDRA table are discarded only when the PDSCH is discarded in that time slot 205 and all (e.g., max_pdsch-AggregationFactor)-1 time slots 205. When discarding the PDSCH within the K-1 window (e.g., as illustrated in the "old" codebook), the codebook size will have a larger overhead.

[0107] An alternative scheme may include identifying the applied repetition factor as 1. In this instance, the UE may generate a feedback codebook based on the last instance of each downlink transmission actually received and decoded. For example, may always be considered as 1, and the ACK / NACK bit positions for each PDSCH with repetition may be bound to the last actual PDSCH reception. This may cause the UE to generate the "new" codebook illustrated in the feedback configuration 200. As can be seen, this approach reduces the size of the codebook generated by the UE and transmitted to the base station by half. That is, when some PDSCH opportunities are discarded and the PDSCH aggregation factor is greater than 1, this reduces the codebook size, and when the PDSCH aggregation factor is large, the benefit is even increased.

[0108] Accordingly, the UE and the base station may determine that the instance(s) of the downlink transmission have been discarded. Accordingly, the UE may generate the feedback codebook differently for the discarded downlink transmission than for the non-discarded downlink transmission. For example, the UE may generate an ACK / NACK indication (e.g., ACK / NACK bit) for each downlink transmission actually received and decoded, but does not generate the ACK / NACK indication for the violation instances of the discarded downlink transmission opportunities.

[0109] In some aspects, the feedback codebook may be generated without considering the DCI associated with the downlink transmission (e.g., may be based on the SPS configuration). For example, the UE may generate a type 1 feedback codebook based on the SPS configuration provided by the base station.

[0110] During slot n+1 (e.g., slot 205-e), the UE may transmit or otherwise convey to the base station an indication of a feedback report (e.g., PUCCH 225) that includes a feedback codebook (e.g., a "new" codebook) generated according to the techniques described. As discussed, these techniques may improve the UE's codebook generation, reduce the overall size of the codebook to minimize overhead, and more accurately ensure consistency between the codebook generated by the UE and the codebook that the base station expects to receive.

[0111] Figure 3 An example of a feedback configuration 300 that supports type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is illustrated. In some examples, aspects of the feedback configuration 300 may implement aspects of the wireless communication system 100 and / or the feedback configuration 200. Aspects of the feedback configuration 300 may be implemented by a base station and / or a UE, which may be examples of the corresponding devices described herein.

[0112] Broadly, the feedback configuration 300 spans multiple slots 305, shown as five slots 305 by way of example only. The slots 305 may be configured with one or more PDSCH opportunities 310, a first downlink transmission 315 (e.g., PDSCH #1), a second downlink transmission 320 (e.g., PDSCH #2), and a PUCCH 325 (e.g., a feedback report opportunity where the UE transmits a feedback report for the downlink transmission to the base station).

[0113] As discussed above, the base station may schedule the UE for one or more downlink transmissions (e.g., by way of example only, the first downlink transmission 315 and the second downlink transmission 320). Each downlink transmission may have an associated repetition factor (e.g., in this example, the aggregation factor is 2 for the first downlink transmission 315 and 4 for the second downlink transmission 320) corresponding to one of a plurality of repetition factors configured at the UE (e.g., {1, 2, 4, 8}). However, the base station and the UE may identify the applied repetition factor (aggregation factor) to be applied to the feedback codebook generation for the scheduled downlink transmission, rather than the associated repetition or aggregation factor. For example, the applied repetition factor may be 1, as discussed with respect to Figure 2 discussed.

[0114] The base station may transmit downlink transmissions 315, 320 to the UE according to the configuration. For example, time slot n-3 (e.g., time slot 305-a) is scheduled for the first repetition of both the first downlink transmission 315 and the second downlink transmission 320. Time slot n-2 (e.g., time slot 305-b) has been configured to include an uplink portion that overlaps with the scheduled repetitions of both downlink transmissions 315, 320, and thus any PDSCHs (e.g., both the second repetition of the first downlink transmission 315 and the second repetition of the second downlink transmission 320) that occur within this time slot are discarded. During time slot n-1 (e.g., time slot 305-c), the base station may transmit the third repetition of the second downlink transmission 320 without using the PDSCH opportunity 310. During time slot n (e.g., time slot 305-d), again without using the PDSCH opportunity 310, and the fourth repetition of the second downlink transmission 320 is discarded (e.g., due to a conflict with the designated uplink portion of time slot n). The first downlink transmission 315 has a corresponding reporting offset of K or K1 = 3, and the second downlink transmission 320 has a corresponding reporting offset of K or K1 = 1.

[0115] Accordingly, the UE may generate a feedback codebook for reporting feedback for the scheduled downlink transmissions, which is filled at least in part based on the applied repetition factor and based on whether the scheduled downlink transmissions are successfully received and decoded by the UE. That is, the UE may utilize the applied repetition factor rather than the repetition factor associated with the downlink transmission(s) configured by the base station.

[0116] In Figure 3 the example of, if the applied repetition factor is 1, and if the UE is configured with a K1 window of {1, 2, 3}, then the ACK / NACK bits for the downlink transmission 315 will not be captured in the feedback codebook. If the applied repetition factor is 1, the UE will consider time slots n, n-1, and n-2 (corresponding to the K1 window) when filling the feedback codebook. Using the process outlined with respect to Figure 2 no content corresponding to time slot n-2 will be included in the codebook. In time slot n-1, a NACK will be included to correspond to the unused PDSCH opportunity 310, and an ACK / NACK will be included to correspond to the third repetition of the downlink transmission 320. In time slot n, only a NACK corresponding to the unused PDSCH opportunity 310 will be included. Thus, although the feedback codebook is still reduced, the codebook lacks any reporting for the downlink transmission 315. Scheduling rules may be used to avoid this scenario.

[0117] In feedback configuration 300, the scheduling rule may include that the UE may not expect to be configured with the following set of K-1 values: for a given PDSCH with a PDSCH aggregation factor greater than 1, none of the actual PDSCH receptions is within the K1 window. That is, the UE may expect to be configured such that at least one PDSCH reception is within the K1 window. For example, the UE may be configured with multiple reporting offset values for transmitting a feedback report to the base station, where each of the reporting offset values represents the number of time slots after the last nominal downlink transmission. The reporting offset values may span an evaluation window, and the feedback codebook may be generated based on the UE's evaluation of each of the multiple reporting offset values within the evaluation window. The UE may generate a feedback codebook based on this technique.

[0118] During time slot n+1 (e.g., time slot 305-e), the UE may transmit or otherwise convey an indication of a feedback report (e.g., PUCCH 325) to the base station, the feedback report including a feedback codebook generated according to the described technique. As discussed, these techniques may improve the UE's codebook generation, reduce the overall size of the codebook to minimize overhead, and more accurately ensure consistency between the codebook generated by the UE and the codebook that the base station expects to receive.

[0119] Figure 4 An example of process 400 that supports type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is illustrated. In some examples, process 400 may implement aspects of wireless communication system 100 and / or feedback configuration 200 and / or 300. Aspects of process 400 may be implemented by UE 405 and / or base station 410, which may be examples of the corresponding devices described herein.

[0120] At 415, base station 410 may schedule UE 405 for one or more downlink transmissions (e.g., PDSCH transmissions), where each downlink transmission has an associated repetition factor (e.g., PDSCH aggregation factor) corresponding to one of the multiple repetition factors configured by base station 410 at UE 405.

[0121] At 420, UE 405 may identify the applied repetition factor to apply to feedback codebook generation for one or more downlink transmissions. Similarly and at 425, the base station may also identify the applied repetition factor for UE 405 to apply to feedback codebook generation for one or more downlink transmissions. For example, base station 410 may transmit a configuration signal (e.g., in RRC configuration signaling) to UE 405 that identifies the applied repetition factor to be used for feedback codebook generation. In another example, base station 410 may configure SPS configurations for UE 405, which may implicitly indicate the applied repetition factor to be used.

[0122] Accordingly, at 430, UE 405 may generate a feedback codebook for reporting feedback for downlink transmissions. The feedback codebook may be populated based on the applied repetition factor and based on whether one or more of the downlink transmissions were successfully received and decoded by UE 405. In some aspects, the feedback codebook may be generated without considering the DCI associated with the downlink transmission.

[0123] For example, UE 405 may identify the applied repetition factor based on the maximum value of the configured repetition factors among the plurality of configured repetition factors. For example, UE 405 may identify the maximum value of the configured repetition factors without accounting for inactive SPS configurations. In another example, UE 405 may identify the maximum value of the configured repetition factors by accounting for active and inactive SPS configurations. In some aspects, this may include UE 405 identifying the applied repetition factor as 1. Accordingly, UE 405 may generate the feedback codebook based on the last instance of each downlink transmission that was actually successfully received and decoded.

[0124] In some aspects, this may include UE 405 determining that one or more instances of the downlink transmission have been discarded. Accordingly, UE 405 may generate the feedback codebook differently for discarded downlink transmissions than for non-discarded (e.g., actually transmitted) downlink transmissions. For example, UE 405 may generate an ACK / NACK indication for each downlink transmission that was actually received and decoded, but suppress the generation of an ACK / NACK indication for discarded downlink transmissions.

[0125] In some aspects, this may include UE 405 being configured with a plurality of reporting offset values (e.g., K or K-1 values) for transmitting a feedback report to the base station. Each reporting offset value may represent the number of time slots after the last nominal downlink transmission, and the reporting offset values may span an evaluation window (e.g., K1 window). UE 405 may generate the feedback codebook based on an evaluation of each reporting offset value within the evaluation window.

[0126] Accordingly, at 435, UE 405 may transmit (and base station 410 may receive) a feedback report that includes the feedback codebook generated according to the described techniques. The feedback report may be transmitted by PUCCH and / or PUSCH.

[0127] Figure 5An example of a feedback configuration 500 that supports a type 1 codebook structure with multiple aggregation factors in accordance with aspects of the present disclosure is illustrated. In some examples, aspects of the feedback configuration 500 may implement aspects of the wireless communication system 100, the feedback configuration 200 and / or 300, and / or the process 400. Aspects of the feedback configuration 500 may be implemented by a base station and / or a UE, which may be examples of the corresponding devices described herein.

[0128] Broadly, the feedback configuration 500 spans multiple time slots 505, with five time slots 505 shown by way of example only. The time slots 505 may be configured with a first downlink transmission 515 (e.g., PDSCH#1), a second downlink transmission 520 (e.g., PDSCH#2), and a PUCCH 525 (e.g., a feedback reporting occasion where the UE transmits a feedback report for the downlink transmission to the base station).

[0129] As discussed above, the base station may schedule the UE for one or more downlink transmissions (e.g., by way of example only, the first downlink transmission 515 and the second downlink transmission 520). Each downlink transmission may have an associated repetition factor (e.g., in this example, the aggregation factor is 2 for the first downlink transmission 515 and 3 for the second downlink transmission 520) corresponding to one of a plurality of repetition factors configured at the UE (e.g., {1, 2, 4, 8}). However, the base station and the UE may identify the applied repetition factor (aggregation factor) to be applied to the feedback codebook generation for the scheduled downlink transmission, rather than the associated repetition or aggregation factor.

[0130] The base station may transmit the downlink transmission to the UE according to the configuration. For example, time slot n-3 (e.g., time slot 505-a) is scheduled for the first repetition of the second downlink transmission 520. Time slot n-2 (e.g., time slot 505-b) is scheduled for the first repetition of the first downlink transmission 515 and the second repetition of the second downlink transmission 520. Time slot n-1 (e.g., time slot 505-c) is scheduled for the second repetition of the first downlink transmission 515 and the third repetition of the second downlink transmission 520. During time slot n (e.g., time slot 505-d), the second downlink transmission 520 is dropped (e.g., in conflict). The first downlink transmission 515 has a corresponding reporting offset of K or K1 = 2, and the second downlink transmission 520 has a corresponding reporting offset of K or K1 = 1.

[0131] Accordingly, the UE may generate a feedback codebook for reporting feedback for the scheduled downlink transmission, which is at least partially filled based on the applied repetition factor and based on whether the scheduled downlink transmission is successfully received and decoded by the UE. That is, the UE may utilize the applied repetition factor instead of the repetition factor associated with the (downlink) transmission(s) configured by the base station.

[0132] In the example illustrated in feedback configuration 500, regardless of the number of PDSCH aggregation factors configured, the UE may report HARQ-ACK information for the PDSCH with repetition from slot n in the HARQ-ACK codebook included in the PUCCH or PUSCH transmission in slot n + k, where k is indicated in the DCI. in slot repetition, where k is indicated in the DCI. The pdsch-AggregationFactor may be defined per PDSCH. For example, for the downlink grants and downlink transmissions of the SPS configuration configured separately, the pdsch-AggregationFactor may be 2 or 4.

[0133] Accordingly, during slot n + 1 (e.g., slot 505-e), the UE may transmit (and the base station may receive) a feedback report (e.g., PUCCH 525) that includes a feedback codebook generated according to the described techniques. The feedback report may be transmitted by the PUCCH 525 and / or PUSCH.

[0134] Figure 6 Block diagram 600 illustrates a device 605 that supports a type 1 codebook structure with multiple aggregation factors in accordance with aspects of the present disclosure. Device 605 may be an example of aspects of UE 115 as described herein. Device 605 may include a receiver 610, a communication manager 615, and a transmitter 620. Device 605 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0135] The receiver 610 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to a type 1 codebook structure with multiple aggregation factors, etc.). The information may be passed to other components of device 605. The receiver 610 may be an example of aspects of the transceiver 920 described Figure 9 herein. The receiver 610 may utilize a single antenna or an antenna array.

[0136] The communication manager 615 may determine that the base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of the configured repetition factor sets configured at the UE; identify the applied repetition factor to apply to the generation of the feedback codebook for the one or more downlink transmissions; generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded; and transmit a feedback report including the feedback codebook to the base station. The communication manager 615 may be an example of aspects of the communication manager 910 described herein.

[0137] The communication manager 615 or its subcomponents may be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. If implemented in code executed by a processor, the functions of the communication manager 615 or its subcomponents may be performed 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, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0138] The communication manager 615 or its subcomponents may be physically located in various locations, including being distributed such that portions of the functionality are implemented by one or more physical components in different physical locations. In some examples, in accordance with aspects of this disclosure, the communication manager 615 or its subcomponents may be separate and distinct components. In some examples, in accordance with various aspects of this disclosure, the communication manager 615 or its subcomponents may be combined with one or more other hardware components, the 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.

[0139] The transmitter 620 may transmit signals generated by other components of the device 605. In some examples, the transmitter 620 may be co-located with the receiver 610 in a transceiver module. For example, the transmitter 620 may be an example of aspects of the transceiver 920 described with reference to Figure 9 The transmitter 620 may utilize a single antenna or an antenna array.

[0140] Figure 7FIG. 700 is a block diagram illustrating a device 705 that supports type 1 codebook construction with multiple aggregation factors, in accordance with aspects of the present disclosure. The device 705 may be an example of aspects of a device 605 or UE 115 as described herein. The device 705 may include a receiver 710, a communication manager 715, and a transmitter 740. The device 705 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

[0141] The receiver 710 may receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to type 1 codebook construction with multiple aggregation factors, etc.). The information may be passed to other components of the device 705. The receiver 710 may be an example of aspects of the transceiver 920 described with reference to Figure 9 The receiver 710 may utilize a single antenna or an antenna array.

[0142] The communication manager 715 may be an example of aspects of the communication manager 615 as described herein. The communication manager 715 may include a scheduling manager 720, an applied repetition factor manager 725, a feedback codebook manager 730, and a feedback reporting manager 735. The communication manager 715 may be an example of aspects of the communication manager 910 described herein.

[0143] The scheduling manager 720 may determine that the base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE.

[0144] The applied repetition factor manager 725 may identify the applied repetition factor to apply to feedback codebook generation for the one or more downlink transmissions.

[0145] The feedback codebook manager 730 may generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated based on the applied repetition factor and based on whether the one or more downlink transmissions were successfully received and decoded.

[0146] The feedback reporting manager 735 may transmit a feedback report including the feedback codebook to the base station.

[0147] The transmitter 740 may transmit signals generated by other components of the device 705. In some examples, the transmitter 740 may be co-located with the receiver 710 in a transceiver module. For example, the transmitter 740 may be an example of aspects of the transceiver 920 described with reference to Figure 9 The transmitter 740 may utilize a single antenna or an antenna array.

[0148] Figure 8 FIG. 800 is a block diagram illustrating a communication manager 805 that supports a type 1 codebook construction with multiple aggregation factors, in accordance with aspects of the present disclosure. The communication manager 805 may be an example of aspects of the communication manager 615, the communication manager 715, or the communication manager 910 described herein. The communication manager 805 may include a scheduling manager 810, an applied repetition factor manager 815, a feedback codebook manager 820, a feedback report manager 825, a configured repetition factor manager 830, a set repetition factor manager 835, a discard transmission manager 840, and a time slot offset manager 845. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0149] The scheduling manager 810 may determine that the base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE.

[0150] The scheduling manager 810 may receive a configuration of a plurality of SPS configurations, where each of the one or more downlink transmissions is associated with a common SPS configuration or a different SPS configuration of the plurality of SPS configurations.

[0151] The applied repetition factor manager 815 may identify an applied repetition factor to apply to feedback codebook generation for the one or more downlink transmissions.

[0152] The feedback codebook manager 820 may generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated based on the applied repetition factor and based on whether the one or more downlink transmissions were successfully received and decoded.

[0153] In some cases, the feedback codebook is generated without considering downlink control information associated with the one or more downlink transmissions.

[0154] The feedback report manager 825 may transmit a feedback report to the base station that includes the feedback codebook.

[0155] The configured repetition factor manager 830 may identify the applied repetition factor based on the maximum value of the configured repetition factors in the configured repetition factor set. In some examples, the configured repetition factor manager 830 may identify the maximum value of the configured repetition factors without considering the configured repetition factors corresponding to inactive SPS configurations. In some examples, the configured repetition factor manager 830 may identify the maximum value of the configured repetition factors by considering the configured repetition factors corresponding to both active and inactive SPS configurations. The set repetition factor manager 835 may identify the applied repetition factor as 1. In some examples, the set repetition factor manager 835 may generate a feedback codebook based on the last instance of each downlink transmission actually received and decoded.

[0156] The discarded transmission manager 840 may determine for each downlink transmission in one or more downlink transmissions that one or more instances of the downlink transmission have been discarded. In some examples, the discarded transmission manager 840 may generate a feedback codebook differently for the one or more discarded instances of the downlink transmission and for the one or more non-discarded instances of the downlink transmission. In some examples, the discarded transmission manager 840 may generate an ACK / NACK indication for each downlink transmission actually received and decoded. In some examples, the discarded transmission manager 840 may suppress generating an ACK / NACK indication for each instance of a discarded downlink transmission opportunity.

[0157] The time slot offset manager 845 may generate a feedback codebook based on evaluating each of a set of reported offset values within an evaluation window.

[0158] In some cases, the feedback codebook is a type 1 codebook.

[0159] Figure 9 FIG. shows a diagram of a system 900 including a device 905 that supports a type 1 codebook construction with multiple aggregation factors, in accordance with aspects of the present disclosure. The device 905 may be an example of the device 605, the device 705, or the UE 115 described herein or include components of these devices. The device 905 may include components for two-way voice and data communication, which include components for transmitting and receiving communications, including a communication manager 910, an I / O controller 915, a transceiver 920, an antenna 925, a memory 930, and a processor 940. These components may be in electronic communication via one or more buses (e.g., bus 945).

[0160] The communication manager 910 may determine that the base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of the configured repetition factor sets configured at the UE; identify the applied repetition factor to apply to the generation of the feedback codebook for the one or more downlink transmissions; generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded; and transmit a feedback report including the feedback codebook to the base station.

[0161] The I / O controller 915 may manage the input and output signals of the device 905. The I / O controller 915 may also manage peripheral devices not integrated into the device 905. In some cases, the I / O controller 915 may represent a physical connection or port to an external peripheral device. In some cases, the I / O controller 915 may utilize an operating system, such as or another known operating system. In other cases, the I / O controller 915 may represent or interact with a modem, keyboard, mouse, touch screen, or similar device. In some cases, the I / O controller 915 may be implemented as part of a processor. In some cases, a user may interact with the device 905 via the I / O controller 915 or via hardware components controlled by the I / O controller 915.

[0162] The transceiver 920 may perform two-way communication via one or more antennas, wired or wireless links, as described above. For example, the transceiver 920 may represent a wireless transceiver and may perform two-way communication with another wireless transceiver. The transceiver 920 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and to demodulate packets received from the antenna.

[0163] In some cases, the wireless device may include a single antenna 925. However, in some cases, the device may have more than one antenna 925, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

[0164] The memory 930 may include random access memory (RAM) and read-only memory (ROM). The memory 930 may store computer-readable, computer-executable code 935 including instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, the memory 930 may particularly include a BIOS, which may control basic hardware or software operations, such as interactions with peripheral components or devices.

[0165] Processor 940 may include intelligent hardware devices (e.g., a general-purpose processor, DSP, CPU, microcontroller, ASIC, FPGA, programmable logic device, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 940 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 940. Processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause device 905 to perform various functions (e.g., functions or tasks supporting type 1 codebook construction with multiple aggregation factors).

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

[0167] Figure 10 Block diagram 1000 of a device 1005 supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is shown. Device 1005 may be an example of aspects of base station 105 as described herein. Device 1005 may include a receiver 1010, a communication manager 1015, and a transmitter 1020. Device 1005 may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

[0168] Receiver 1010 may receive information, such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to type 1 codebook construction with multiple aggregation factors, etc.). The information may be passed to other components of device 1005. Receiver 1010 may be an example of aspects of transceiver 1320 described with reference to Figure 13 Receiver 1010 may utilize a single antenna or an antenna array.

[0169] The communication manager 1015 may schedule the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE; identify the applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions; and receive from the UE a feedback report including a feedback codebook, the feedback codebook being generated to report feedback for the one or more downlink transmissions and populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE. The communication manager 1015 may be an example of aspects of the communication manager 1310 described herein.

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

[0171] The communication manager 1015 or its subcomponents may be physically located at various positions, including being distributed such that portions of the functionality are implemented by one or more physical components at different physical locations. In some examples, in accordance with aspects of this disclosure, the communication manager 1015 or its subcomponents may be separate and distinct components. In some examples, in accordance with aspects of this disclosure, the communication manager 1015 or its subcomponents 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.

[0172] The transmitter 1020 may transmit signals generated by other components of the device 1005. In some examples, the transmitter 1020 may be co-located with the receiver 1010 in a transceiver module. For example, the transmitter 1020 may be an example of aspects of the transceiver 1320 described with reference to Figure 13 The transmitter 1020 may utilize a single antenna or an antenna array.

[0173] Figure 11FIG. 1100 is a block diagram showing an apparatus 1105 supporting a type 1 codebook construction with multiple aggregation factors, in accordance with aspects of the present disclosure. The apparatus 1105 may be an example of aspects of an apparatus 1005 or a base station 105 as described herein. The apparatus 1105 may include a receiver 1110, a communication manager 1115, and a transmitter 1135. The apparatus 1105 may also include a processor. Each of these components may be in communication with each other (e.g., via one or more buses).

[0174] The receiver 1110 may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to a type 1 codebook construction with multiple aggregation factors, etc.). The information may be passed to other components of the apparatus 1105. The receiver 1110 may be an example of aspects of the transceiver 1320 described with reference to Figure 13 The receiver 1110 may utilize a single antenna or an antenna array.

[0175] The communication manager 1115 may be an example of aspects of the communication manager 1015 as described herein. The communication manager 1115 may include a scheduling manager 1120, an applied repetition factor manager 1125, and a feedback reporting manager 1130. The communication manager 1115 may be an example of aspects of the communication manager 1310 described herein.

[0176] The scheduling manager 1120 may schedule a UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE.

[0177] The applied repetition factor manager 1125 may identify an applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions.

[0178] The feedback reporting manager 1130 may receive a feedback report from the UE including a feedback codebook, the feedback codebook being generated to report feedback for the one or more downlink transmissions and being populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

[0179] The transmitter 1135 may transmit signals generated by other components of the apparatus 1105. In some examples, the transmitter 1135 may be co-located with the receiver 1110 in a transceiver module. For example, the transmitter 1135 may be an example of aspects of the transceiver 1320 described with reference to Figure 13 The transmitter 1135 may utilize a single antenna or an antenna array.

[0180] Figure 12 FIG. 1200 is a block diagram showing a communication manager 1205 that supports type 1 codebook construction with multiple aggregation factors, in accordance with aspects of the present disclosure. The communication manager 1205 may be an example of aspects of the communication manager 1015, the communication manager 1115, or the communication manager 1310 described herein. The communication manager 1205 may include a scheduling manager 1210, an applied repetition factor manager 1215, a feedback report manager 1220, a configured repetition factor manager 1225, a set repetition factor manager 1230, a discard transmission manager 1235, and a feedback codebook manager 1240. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0181] The scheduling manager 1210 may schedule a UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE.

[0182] The scheduling manager 1210 may transmit configurations for a plurality of SPS configurations, where each of the one or more downlink transmissions is associated with a common SPS configuration or with a different SPS configuration of the plurality of SPS configurations.

[0183] The applied repetition factor manager 1215 may identify an applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions.

[0184] The feedback report manager 1220 may receive a feedback report from the UE that includes a feedback codebook that is generated to report feedback for the one or more downlink transmissions and is populated based on the applied repetition factor and based on whether the one or more downlink transmissions were successfully received and decoded by the UE.

[0185] The configured repetition factor manager 1225 may identify the applied repetition factor based on a maximum value of the configured repetition factors in the set of configured repetition factors. In some examples, the configured repetition factor manager 1225 may identify the maximum value of the configured repetition factors without accounting for configured repetition factors corresponding to inactive SPS configurations of the UE. In some examples, the configured repetition factor manager 1225 may identify the maximum value of the configured repetition factors by accounting for configured repetition factors corresponding to both active and inactive SPS configurations of the UE.

[0186] The configured repetition factor manager 1230 may identify the applied repetition factor as 1, where the feedback codebook is generated based on the last instance of each downlink transmission actually received and decoded. In some examples, the configured repetition factor manager 1230 may schedule at least one non-conflicting instance of a downlink transmission during an evaluation window based on a reported offset value, based on a configured set of repetition factors.

[0187] The discard transmission manager 1235 may determine that one or more instances of a downlink transmission have been discarded for each of one or more downlink transmissions, where the feedback codebook is generated differently for the one or more discarded instances and the one or more non-discarded instances of the downlink transmission. In some cases, the feedback codebook is generated based on: generating an ACK / NACK indication for each downlink transmission actually received and decoded by the UE, and not generating an ACK / NACK indication for each instance of a discarded downlink transmission opportunity.

[0188] The feedback codebook manager 1240 may monitor, control, or otherwise manage aspects of a feedback codebook generated without regard to downlink control information associated with one or more downlink transmissions. In some cases, the UE is configured with a set of reported offset values for transmitting a feedback report to the base station, each of which in the set of reported offset values represents the number of time slots after a last nominal downlink transmission, the set of reported offset values spans an evaluation window, and the feedback codebook is generated based on the UE's evaluation of each of the set of reported offset values within the evaluation window.

[0189] In some cases, the feedback codebook is a type 1 codebook.

[0190] Figure 13 A diagram of a system 1300 including a device 1305 that supports a type 1 codebook construction with multiple aggregation factors, in accordance with aspects of the present disclosure, is shown. The device 1305 may be an example of the device 1005, the device 1105, or the base station 105 described herein, or include components of the above-described devices. The device 1305 may include components for two-way voice and data communication, which include components for transmitting and receiving communication, including a communication manager 1310, a network communication manager 1315, a transceiver 1320, an antenna 1325, a memory 1330, a processor 1340, and an inter-station communication manager 1345. These components may be in electronic communication via one or more buses (e.g., bus 1350).

[0191] The communication manager 1310 may schedule the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of the configured repetition factor sets configured at the UE; identify the applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions; and receive from the UE a feedback report including a feedback codebook, the feedback codebook being generated to report feedback for the one or more downlink transmissions and being populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

[0192] The network communication manager 1315 may manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1315 may manage the delivery of data communication of client devices such as one or more UEs 115.

[0193] The transceiver 1320 may communicate bidirectionally via one or more antennas, wired or wireless links, as described above. For example, the transceiver 1320 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver 1320 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and to demodulate packets received from the antenna.

[0194] In some cases, the wireless device may include a single antenna 1325. However, in some cases, the device may have more than one antenna 1325, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.

[0195] The memory 1330 may include RAM, ROM, or a combination thereof. The memory 1330 may store computer-readable code 1335 including instructions that, when executed by a processor (e.g., processor 1340), cause the device to perform the various functions described herein. In some cases, the memory 1330 may in particular contain a basic input / output system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0196] The processor 1340 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, the processor 1340 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into the processor 1340. The processor 1340 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 1330) to cause the device 1305 to perform various functions (e.g., support functions or tasks for type 1 codebook construction with multiple aggregation factors).

[0197] The inter-station communication manager 1345 may manage communication with other base stations 105 and may include a controller or scheduler for collaboratively controlling communication with the UE 115 with other base stations 105. For example, the inter-station communication manager 1345 may coordinate the scheduling of transmissions to the UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, the inter-station communication manager 1345 may provide an X2 interface within the LTE / LTE-A wireless communication network technology to provide communication between base stations 105.

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

[0199] Figure 14 A flowchart illustrating a method 1400 for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure is shown. The operations of method 1400 may be implemented by the UE 115 or its components as described herein. For example, the operations of method 1400 may be performed by a communication manager as described with reference to Figures 6 to 9 As described. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the following functions.

[0200] At 1405, the UE may determine that the base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE. The operation of 1405 may be performed in accordance with the methods described herein. In some examples, aspects of the operation of 1405 may be performed by a communication manager as referenced Figures 6 to 9Execute by the described scheduling manager.

[0201] At 1410, the UE may identify the applied repetition factor to be applied to the generation of the feedback codebook for the one or more downlink transmissions. The operation of 1410 may be performed according to the methods described herein. In some examples, aspects of the operation of 1410 may be performed by an applied repetition factor manager as described with reference to Figures 6 to 9 the described applied repetition factor manager.

[0202] At 1415, the UE may generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded. The operation of 1415 may be performed according to the methods described herein. In some examples, aspects of the operation of 1415 may be performed by a feedback codebook manager as described with reference to Figures 6 to 9 the described feedback codebook manager.

[0203] At 1420, the UE may transmit a feedback report including the feedback codebook to the base station. The operation of 1420 may be performed according to the methods described herein. In some examples, aspects of the operation of 1420 may be performed by a feedback report manager as described with reference to Figures 6 to 9 the described feedback report manager.

[0204] Figure 15 FIG. 1500 is a flow chart illustrating a method 1500 for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure. The operations of method 1500 may be implemented by a UE 115 or components thereof as described herein. For example, the operations of method 1500 may be performed by a communication manager as described with reference to Figures 6 to 9 the described communication manager. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the following functions.

[0205] At 1505, the UE may determine that the base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE. The operation of 1505 may be performed according to the methods described herein. In some examples, aspects of the operation of 1505 may be performed by a scheduling manager as described with reference to Figures 6 to 9 the described scheduling manager.

[0206] At 1510, the UE may identify the applied repetition factor to be applied to the generation of the feedback codebook for the one or more downlink transmissions. The operation of 1510 may be performed according to the methods described herein. In some examples, aspects of the operation of 1510 may be performed by an applied repetition factor manager as described with reference to Figures 6 to 9Execute using the described applied repetition factor manager.

[0207] At 1515, the UE may identify the applied repetition factor based on the maximum value of the configured repetition factors in the configured repetition factor set. The operation of 1515 may be performed according to the methods described herein. In some examples, aspects of the operation of 1515 may be performed by a configured repetition factor manager as described with reference to Figures 6 to 9 Execute using the described applied repetition factor manager.

[0208] At 1520, the UE may generate a feedback codebook for reporting feedback for the one or more downlink transmissions, and the feedback codebook is filled based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded. The operation of 1520 may be performed according to the methods described herein. In some examples, aspects of the operation of 1520 may be performed by a feedback codebook manager as described with reference to Figures 6 to 9 Execute using the described feedback codebook manager.

[0209] At 1525, the UE may transmit a feedback report including the feedback codebook to the base station. The operation of 1525 may be performed according to the methods described herein. In some examples, aspects of the operation of 1525 may be performed by a feedback report manager as described with reference to Figures 6 to 9 Execute using the described feedback report manager.

[0210] Figure 16 A flowchart of a method 1600 is shown that illustrates a method for supporting a type 1 codebook construction with multiple aggregation factors according to aspects of the present disclosure. The operations of method 1600 may be implemented by the UE 115 or its components as described herein. For example, the operations of method 1600 may be performed by a communication manager as described with reference to Figures 6 to 9 Execute using the described communication manager. In some examples, the UE may execute an instruction set to control functional elements of the UE to perform the following functions. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the following functions.

[0211] At 1605, the UE may determine that the base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of the configured repetition factor sets configured at the UE. The operation of 1605 may be performed according to the methods described herein. In some examples, aspects of the operation of 1605 may be performed by a scheduling manager as described with reference to Figures 6 to 9 Execute using the described scheduling manager.

[0212] At 1610, the UE may identify the applied repetition factor to apply to the feedback codebook generation for the one or more downlink transmissions. The operation of 1610 may be performed according to the methods described herein. In some examples, aspects of the operation of 1610 may be performed by a manager as described with reference toFigures 6 to 9 Execute using the applied repetition factor manager described.

[0213] At 1615, the UE may identify the applied repetition factor as 1. The operation at 1615 may be performed according to the method described herein. In some examples, aspects of the operation at 1615 may be performed by, for example, the configured repetition factor manager as referenced Figures 6 to 9 described.

[0214] At 1620, the UE may generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded. The operation at 1620 may be performed according to the method described herein. In some examples, aspects of the operation at 1620 may be performed by, for example, the feedback codebook manager as referenced Figures 6 to 9 described.

[0215] At 1625, the UE may generate the feedback codebook based on the last instance of each downlink transmission that was actually successfully received and decoded. The operation at 1625 may be performed according to the method described herein. In some examples, aspects of the operation at 1625 may be performed by, for example, the configured repetition factor manager as referenced Figures 6 to 9 described.

[0216] At 1630, the UE may transmit a feedback report including the feedback codebook to the base station. The operation at 1630 may be performed according to the method described herein. In some examples, aspects of the operation at 1630 may be performed by, for example, the feedback report manager as referenced Figures 6 to 9 described.

[0217] Figure 17 FIG. 1700 is a flow diagram illustrating a method 1700 for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure. The operations of method 1700 may be implemented by base station 105 or its components as described herein. For example, the operations of method 1700 may be performed by, for example, the communication manager as referenced Figures 10 to 13 described. In some examples, the base station may execute an instruction set to control functional elements of the base station to perform the following functions. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the following functions.

[0218] At 1705, the base station may schedule the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE. The operation at 1705 may be performed according to the method described herein. In some examples, aspects of the operation at 1705 may be performed by, for example, as referenced Figures 10 to 13to be performed by the described scheduling manager.

[0219] At 1710, the base station may identify the applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions. The operation of 1710 may be performed according to the methods described herein. In some examples, aspects of the operation of 1710 may be performed by an applied repetition factor manager as described with reference to Figures 10 to 13 the described applied repetition factor manager.

[0220] At 1715, the base station may receive a feedback report from the UE that includes a feedback codebook that is generated to report feedback for the one or more downlink transmissions and is populated based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE. The operation of 1715 may be performed according to the methods described herein. In some examples, aspects of the operation of 1715 may be performed by a feedback report manager as described with reference to Figures 10 to 13 the described feedback report manager.

[0221] Figure 18 FIG. 1800 is a flow diagram illustrating a method 1800 for supporting type 1 codebook construction with multiple aggregation factors in accordance with aspects of the present disclosure. The operations of method 1800 may be implemented by a base station 105 or components thereof as described herein. For example, the operations of method 1800 may be performed by a communication manager as described with reference to Figures 10 to 13 the described communication manager. In some examples, the base station may execute an instruction set to control functional elements of the base station to perform the following functions. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the following functions.

[0222] At 1805, the base station may schedule the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE. The operation of 1805 may be performed according to the methods described herein. In some examples, aspects of the operation of 1805 may be performed by a scheduling manager as described with reference to Figures 10 to 13 the described scheduling manager.

[0223] At 1810, the base station may identify the applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions. The operation of 1810 may be performed according to the methods described herein. In some examples, aspects of the operation of 1810 may be performed by an applied repetition factor manager as described with reference to Figures 10 to 13 the described applied repetition factor manager.

[0224] In 1815, the base station may receive a feedback report including a feedback codebook from the UE, where the feedback codebook is generated for reporting feedback for the one or more downlink transmissions and is filled based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE. The operations of 1815 may be performed according to the methods described herein. In some examples, aspects of the operations of 1815 may be performed by a feedback report manager as described with reference to Figures 10 to 13 as described.

[0225] In 1820, the base station may determine for each of the one or more downlink transmissions that one or more instances of the downlink transmission have been discarded, where the feedback codebook is generated differently for the discarded one or more instances and the non-discarded one or more instances of the downlink transmission. The operations of 1820 may be performed according to the methods described herein. In some examples, aspects of the operations of 1820 may be performed by a discarded transmission manager as described with reference to Figures 10 to 13 as described.

[0226] It should be noted that the methods described herein describe possible implementations, and the operations and steps may be rearranged or otherwise modified and other implementations are also possible. In addition, aspects from two or more methods may be combined.

[0227] An overview of aspects of the present disclosure is provided below:

[0228] Aspect 1: A method for wireless communication at a UE, including: determining that a base station has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE; identifying an applied repetition factor to apply to feedback codebook generation for the one or more downlink transmissions; generating a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being filled at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded; and transmitting a feedback report including the feedback codebook to the base station.

[0229] Aspect 2: The method according to aspect 1, further including: identifying the applied repetition factor at least in part based on a maximum value of the configured repetition factors among the plurality of configured repetition factors.

[0230] Aspect 3: The method according to aspect 2, further including: identifying the maximum value of the configured repetition factors without taking into account the configured repetition factors corresponding to inactive SPS configurations.

[0231] Aspect 4: The method as described in any one of Aspects 2 to 3 further includes: identifying the maximum value of the configured repetition factor by taking into account the configured repetition factors corresponding to both active and inactive SPS configurations.

[0232] Aspect 5: The method as described in any one of Aspects 1 to 4 further includes: identifying the applied repetition factor as 1; and generating the feedback codebook at least in part based on the last instance of each downlink transmission actually received and decoded.

[0233] Aspect 6: The method as described in any one of Aspects 1 to 5 further includes: determining for each downlink transmission among the one or more downlink transmissions that one or more instances of the downlink transmission have been discarded; and generating the feedback codebook differently for the one or more discarded instances of the downlink transmission and for the one or more non-discarded instances of the downlink transmission.

[0234] Aspect 7: The method as described in Aspect 6, wherein generating the feedback codebook further includes: generating an ACK / NACK indication for each downlink transmission actually received and decoded; and suppressing the generation of an ACK / NACK indication for each instance of a discarded downlink transmission opportunity.

[0235] Aspect 8: The method as described in any one of Aspects 1 to 7 further includes: receiving the configuration of multiple SPS configurations, wherein each downlink transmission among the one or more downlink transmissions is associated with a common SPS configuration or with a different SPS configuration among the multiple SPS configurations.

[0236] Aspect 9: The method as described in any one of Aspects 1 to 8, wherein the feedback codebook is generated without considering the DCI associated with the one or more downlink transmissions.

[0237] Aspect 10: The method as described in any one of Aspects 1 to 9, wherein the UE is configured with multiple reporting offset values for transmitting the feedback report to the base station, each of the multiple reporting offset values represents the number of time slots after the last nominal downlink transmission, the multiple reporting offset values span an evaluation window, and the method further includes: generating the feedback codebook at least in part based on evaluating each of the multiple reporting offset values within the evaluation window.

[0238] Aspect 11: The method as described in any one of Aspects 1 to 10, wherein the feedback codebook includes a Type 1 codebook.

[0239] Aspect 12: A method for wireless communication at a base station, comprising: scheduling a UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE; identifying the applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions; and receiving from the UE a feedback report including a feedback codebook, the feedback codebook being generated for reporting feedback for the one or more downlink transmissions and being populated at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

[0240] Aspect 13: The method according to aspect 12, further comprising: identifying the applied repetition factor at least in part based on the maximum value of the configured repetition factors among the plurality of configured repetition factors.

[0241] Aspect 14: The method according to aspect 13, further comprising: identifying the maximum value of the configured repetition factors without taking into account the configured repetition factors corresponding to an inactive SPS configuration of the UE.

[0242] Aspect 15: The method according to any one of aspects 13 to 14, further comprising: identifying the maximum value of the configured repetition factors by taking into account the configured repetition factors corresponding to both active and inactive SPS configurations of the UE.

[0243] Aspect 16: The method according to any one of aspects 12 to 15, further comprising: identifying the applied repetition factor as 1, wherein the feedback codebook is generated at least in part based on the last instance of each downlink transmission that is actually received and decoded.

[0244] Aspect 17: The method according to aspect 16, further comprising: scheduling at least one non-conflicting instance of the downlink transmission during an evaluation window based at least in part on a reporting offset value and at least in part based on the plurality of configured repetition factors.

[0245] Aspect 18: The method according to any one of aspects 12 to 17, further comprising: determining for each of the one or more downlink transmissions that one or more instances of the downlink transmission have been discarded, wherein the feedback codebook is generated differently for the one or more discarded instances of the downlink transmission and for the one or more non-discarded instances of the downlink transmission.

[0246] Aspect 19: The method as described in aspect 18, wherein the feedback codebook is generated at least in part based on: generating an ACK / NACK indication for each downlink transmission actually received and decoded by the UE, and not generating an ACK / NACK indication for each instance of a discarded downlink transmission opportunity.

[0247] Aspect 20: The method as described in any one of aspects 12 to 19, further comprising: transmitting a configuration of a plurality of SPS configurations, wherein each downlink transmission among the one or more downlink transmissions is associated with a common SPS configuration or a different SPS configuration among the plurality of SPS configurations.

[0248] Aspect 21: The method as described in any one of aspects 12 to 20, wherein the feedback codebook is generated without considering the DCI associated with the one or more downlink transmissions.

[0249] Aspect 22: The method as described in any one of aspects 12 to 21, wherein the UE is configured with a plurality of reporting offset values for transmitting the feedback report to the base station, each of the plurality of reporting offset values represents the number of time slots after the last nominal downlink transmission, the plurality of reporting offset values span an evaluation window, and the feedback codebook is generated at least in part based on the UE evaluating each of the plurality of reporting offset values within the evaluation window.

[0250] Aspect 23: The method as described in any one of aspects 12 to 22, wherein the feedback codebook includes a type 1 codebook.

[0251] Aspect 24: An apparatus for wireless communication at a UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method as described in any one of aspects 1 to 11.

[0252] Aspect 25: An apparatus for wireless communication at a UE, comprising at least one means for performing the method as described in any one of aspects 1 to 11.

[0253] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication at a UE, the code comprising instructions executable by a processor to perform the method as described in any one of aspects 1 to 11.

[0254] Aspect 27: An apparatus for wireless communication at a base station, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform the method as described in any one of aspects 12 to 23.

[0255] Aspect 28: An apparatus for wireless communication at a base station, comprising at least one means for performing the method as described in any one of Aspects 12 to 23.

[0256] Aspect 29: A non-transitory computer-readable medium storing code for wireless communication at a base station, the code comprising instructions executable by a processor to perform the method as described in any one of Aspects 12 to 23.

[0257] Although aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for example purposes and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein may also be applied to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the described techniques may be applied to various other wireless communication systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0258] The information and signals described herein may be represented using any of a variety of different arts and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout this description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0259] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, DSP, ASIC, CPU, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any 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 in conjunction with a DSP core, or any other such configuration).

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

[0261] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium can be any available medium that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include random access memory (RAM), read only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, compact disc ROM (CD-ROM) or other optical disc storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Similarly, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a web site, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically with lasers. Combinations of the above media are also included within the scope of computer-readable media.

[0262] As used herein, including in the claims, the "or" used in a list of items (e.g., a list of items accompanied by language such as "at least one of" or "one or more of") indicates an inclusive listing such that, for example, the listing 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). Similarly, as used herein, the phrase "based on" should not be construed as reciting a closed set of conditions. For example, an example step described as being based on condition "A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0263] In the figures, similar components or features may have the same reference numeral. Additionally, each of the same type of components may be distinguished by following the reference numeral with a dash and a second label that differentiates between similar components. If only the first reference numeral is used in the specification, the description may apply to any one of the similar components having the same first reference numeral regardless of the second reference numeral, or any other subsequent reference numerals.

[0264] The description set forth herein in conjunction with the drawings describes example configurations and does not represent all examples that may be implemented or that fall within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration" and does not mean "superior to" or "better than" other examples. This detailed description includes specific details to provide an understanding of the described technologies. However, the technologies may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0265] The description provided herein is to enable a person of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to a person of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Thus, the present disclosure is not limited to the examples and designs described herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for wireless communication at a user equipment (UE), comprising: Determining that a network device has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE; Identifying an applied repetition factor to be applied to feedback codebook generation for the one or more downlink transmissions, wherein the applied repetition factor is different from the associated repetition factors of the one or more downlink transmissions; Generating a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded; And Transmitting a feedback report including the feedback codebook to the network device.

2. The method of claim 1, further comprising: Identifying the applied repetition factor at least in part based on a maximum value of the configured repetition factors among the plurality of configured repetition factors.

3. The method of claim 2, further comprising: Identifying the maximum value of the configured repetition factors without considering the configured repetition factors corresponding to inactive semi-persistent scheduling (SPS) configurations.

4. The method of claim 2, further comprising: Identifying the maximum value of the configured repetition factors by considering the configured repetition factors corresponding to both active and inactive semi-persistent scheduling (SPS) configurations.

5. The method of claim 1, further comprising: Identifying the applied repetition factor as 1; And Generating the feedback codebook at least in part based on a last instance of each downlink transmission that is actually received and decoded.

6. The method of claim 1, further comprising: Determining for each of the one or more downlink transmissions that one or more instances of the downlink transmission have been discarded; And Generating the feedback codebook differently for the one or more discarded instances of the downlink transmission and for the one or more non-discarded instances of the downlink transmission.

7. The method of claim 6, wherein generating the feedback codebook further comprises: Generating an acknowledgement / negative acknowledgement (ACK / NACK) indication for each downlink transmission that is actually received and decoded; And Suppressing generation of ACK / NACK indications for each instance of a discarded downlink transmission opportunity.

8. The method of claim 1, further comprising: Receiving configuration of a plurality of semi-persistent scheduling (SPS) configurations, wherein each of the one or more downlink transmissions is associated with a common SPS configuration or with a different SPS configuration among the plurality of SPS configurations.

9. The method of claim 1, wherein the feedback codebook is generated without considering downlink control information associated with the one or more downlink transmissions.

10. The method according to claim 1, wherein the UE is configured with a plurality of reporting offset values for transmitting the feedback report to the network device, each of the plurality of reporting offset values representing the number of time slots after the last nominal downlink transmission, the plurality of reporting offset values spanning an evaluation window, the method further comprising: Generating the feedback codebook at least in part based on evaluating each of the plurality of reporting offset values within the evaluation window.

11. The method according to claim 1, wherein the feedback codebook comprises a type 1 codebook.

12. A method for wireless communication at a network device, comprising: Scheduling a user equipment UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE; Identifying an applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions, wherein the applied repetition factor is different from the associated repetition factor of the one or more downlink transmissions; And Receiving from the UE a feedback report comprising a feedback codebook, the feedback codebook being generated to report feedback for the one or more downlink transmissions and being populated at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

13. The method according to claim 12, further comprising: Identifying the applied repetition factor at least in part based on the maximum value of the configured repetition factors among the plurality of configured repetition factors.

14. The method according to claim 13, further comprising: Identifying the maximum value of the configured repetition factors without considering the configured repetition factors corresponding to an inactive semi-persistent scheduling SPS configuration of the UE.

15. The method according to claim 13, further comprising: Identifying the maximum value of the configured repetition factors by taking into account the configured repetition factors corresponding to both active and inactive semi-persistent scheduling SPS configurations of the UE.

16. The method according to claim 12, further comprising: Identifying the applied repetition factor as 1, wherein the feedback codebook is generated at least in part based on the last instance of each downlink transmission that is actually received and decoded.

17. The method according to claim 16, further comprising: Scheduling at least one non-conflicting instance of a downlink transmission during an evaluation window based at least in part on the reporting offset value and at least in part based on the plurality of configured repetition factors.

18. The method according to claim 12, further comprising: Determining for each of the one or more downlink transmissions that one or more instances of the downlink transmission have been discarded, wherein the feedback codebook is generated differently for the discarded one or more instances and for the non-discarded one or more instances of the downlink transmission.

19. The method according to claim 18, wherein the feedback codebook is generated at least in part based on: generating an acknowledgement / negative acknowledgement ACK / NACK indication for each downlink transmission actually received and decoded by the UE, and not generating an ACK / NACK indication for each instance of a discarded downlink transmission opportunity.

20. The method according to claim 12, further comprising: transmitting a configuration of a plurality of semi-persistent scheduling SPS configurations, wherein each of the one or more downlink transmissions is associated with a common SPS configuration or a different SPS configuration among the plurality of SPS configurations.

21. The method according to claim 12, wherein the feedback codebook is generated without considering downlink control information associated with the one or more downlink transmissions.

22. The method according to claim 12, wherein the UE is configured with a plurality of reporting offset values for transmitting the feedback report to the network device, each of the plurality of reporting offset values represents the number of time slots after the last nominal downlink transmission, the plurality of reporting offset values span an evaluation window, and the feedback codebook is generated at least in part based on the UE evaluating each of the plurality of reporting offset values within the evaluation window.

23. The method according to claim 12, wherein the feedback codebook includes a type 1 codebook.

24. An apparatus for wireless communication at a user equipment UE, comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: determine that a network device has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE; identify an applied repetition factor to apply to the generation of a feedback codebook for the one or more downlink transmissions, wherein the applied repetition factor is different from the associated repetition factor of the one or more downlink transmissions; generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded; and transmit a feedback report including the feedback codebook to the network device.

25. The apparatus according to claim 24, wherein, The instructions are further executable by the processor to cause the apparatus to: identify the applied repetition factor at least in part based on a maximum value of the configured repetition factors among the plurality of configured repetition factors.

26. The apparatus according to claim 25, wherein, The instructions are further executable by the processor to cause the apparatus to: identify the maximum value of the configured repetition factors without taking into account the configured repetition factors corresponding to inactive semi-persistent scheduling SPS configurations.

27. The apparatus according to claim 25, wherein The instructions are further executable by the processor to cause the apparatus to: Identify the maximum value of the configured repetition factor by taking into account the configured repetition factor corresponding to both active and inactive semi-persistent scheduling (SPS) configurations.

28. The device according to claim 24, wherein The instructions can also be executed by the processor to cause the device to: Identify the applied repetition factor as 1; and Generate the feedback codebook at least in part based on the last instance of each downlink transmission actually received and decoded.

29. The apparatus according to claim 24, wherein, The instructions can also be executed by the processor to cause the device to: Determine that one or more instances of the downlink transmission have been discarded for each of the one or more downlink transmissions; And Generate the feedback codebook differently for the discarded one or more instances of the downlink transmission and for the non-discarded one or more instances of the downlink transmission.

30. The apparatus according to claim 29, wherein, The instructions can also be executed by the processor to cause the device to: Generate an acknowledgement / negative acknowledgement (ACK / NACK) indication for each downlink transmission actually received and decoded; and Suppress the generation of ACK / NACK indications for each instance of a discarded downlink transmission opportunity.

31. The apparatus according to claim 24, wherein, The instructions can also be executed by the processor to cause the device to: Receive a configuration of multiple semi-persistent scheduling (SPS) configurations, where each of the one or more downlink transmissions is associated with a common SPS configuration or with a different SPS configuration among the multiple SPS configurations.

32. The device according to claim 24, wherein, The instructions can be executed by the processor to cause the device to generate the feedback codebook without considering the downlink control information associated with the one or more downlink transmissions.

33. The device according to claim 24, wherein the UE is configured with multiple reporting offset values for transmitting the feedback report to the network device, each of the multiple reporting offset values representing the number of time slots after the last nominal downlink transmission, the multiple reporting offset values spanning an evaluation window, and the instructions can also be executed by the processor to cause the device to generate the feedback codebook at least in part based on evaluating each of the multiple reporting offset values within the evaluation window.

34. The device according to claim 24, wherein the feedback codebook includes a type 1 codebook.

35. A device for wireless communication at a network device, comprising: A processor; A memory coupled to the processor; And Instructions stored in the memory and executable by the processor to cause the device to: Schedule a user equipment (UE) for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE; Identify the applied repetition factor for use by the UE in generating a feedback codebook for the one or more downlink transmissions, where the applied repetition factor is different from the associated repetition factor of the one or more downlink transmissions; And Receive a feedback report from the UE, the feedback codebook being generated for reporting feedback for the one or more downlink transmissions and being filled at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

36. The device according to claim 35, wherein, The instructions can also be executed by the processor to cause the apparatus to: Identify the applied repetition factor at least in part based on the maximum value of the configured repetition factors among the plurality of configured repetition factors.

37. The apparatus according to claim 36, wherein, The instructions can also be executed by the processor to cause the apparatus to: Identify the maximum value of the configured repetition factors without taking into account the configured repetition factors corresponding to the inactive semi-persistent scheduling (SPS) configuration of the UE.

38. The apparatus according to claim 36, wherein, The instructions can also be executed by the processor to cause the apparatus to: Identify the maximum value of the configured repetition factors by taking into account the configured repetition factors corresponding to both the active and inactive semi-persistent scheduling (SPS) configurations of the UE.

39. The device according to claim 35, wherein, The instructions can also be executed by the processor to cause the apparatus to: Identify the applied repetition factor as 1, wherein the feedback codebook is generated at least in part based on the last instance of each downlink transmission actually received and decoded.

40. The apparatus according to claim 39, wherein, The instructions can also be executed by the processor to cause the apparatus to: Schedule at least one non-conflicting instance of a downlink transmission during an evaluation window based at least in part on the report offset value and at least in part on the plurality of configured repetition factors.

41. The device according to claim 35, wherein, The instructions can also be executed by the processor to cause the apparatus to: Determine that one or more instances of each of the one or more downlink transmissions have been discarded, wherein the feedback codebook is generated differently for the discarded one or more instances of the downlink transmission and for the non-discarded one or more instances of the downlink transmission.

42. The apparatus of claim 41, wherein the feedback codebook is generated at least in part based on: generating an acknowledgement / negative acknowledgement (ACK / NACK) indication for each downlink transmission actually received and decoded by the UE, and not generating an ACK / NACK indication for each instance of a discarded downlink transmission opportunity.

43. The apparatus according to claim 35, wherein, The instructions can also be executed by the processor to cause the apparatus to: Transmit a configuration of a plurality of semi-persistent scheduling (SPS) configurations, wherein each of the one or more downlink transmissions is associated with a common SPS configuration or with a different SPS configuration among the plurality of SPS configurations.

44. The apparatus of claim 35, wherein the feedback codebook is generated without considering the downlink control information associated with the one or more downlink transmissions.

45. The apparatus according to claim 35, wherein the UE is configured with a plurality of reporting offset values for transmitting the feedback report to the network device, each of the plurality of reporting offset values representing the number of time slots after the last nominal downlink transmission, the plurality of reporting offset values spanning an evaluation window, and the feedback codebook is generated at least in part based on the UE evaluating each of the plurality of reporting offset values within the evaluation window.

46. The apparatus according to claim 35, wherein the feedback codebook includes a type 1 codebook.

47. An apparatus for wireless communication at a user equipment (UE), comprising: means for determining that a network device has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE; means for identifying an applied repetition factor to be applied to feedback codebook generation for the one or more downlink transmissions, wherein the applied repetition factor is different from the associated repetition factor of the one or more downlink transmissions; means for generating a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being filled at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded; and means for transmitting a feedback report including the feedback codebook to the network device.

48. An apparatus for wireless communication at a network device, comprising: means for scheduling a user equipment (UE) for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE; means for identifying an applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions, wherein the applied repetition factor is different from the associated repetition factor of the one or more downlink transmissions; and means for receiving from the UE a feedback report including a feedback codebook, the feedback codebook being generated for reporting feedback for the one or more downlink transmissions and being filled at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

49. 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: determining that a network device has scheduled the UE for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE; Identify an applied repetition factor to be applied to feedback codebook generation for the one or more downlink transmissions, wherein the applied repetition factor is different from the associated repetition factor of the one or more downlink transmissions; Generate a feedback codebook for reporting feedback for the one or more downlink transmissions, the feedback codebook being populated at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded; And Transmit a feedback report including the feedback codebook to the network device.

50. A non-transitory computer-readable medium storing code for wireless communication at a network device, the code including instructions executable by a processor for: Schedule a user equipment (UE) for one or more downlink transmissions, each of the one or more downlink transmissions having an associated repetition factor corresponding to one of a plurality of configured repetition factors configured at the UE; Identify an applied repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions, wherein the applied repetition factor is different from the associated repetition factor of the one or more downlink transmissions; And Receive from the UE a feedback report including a feedback codebook, the feedback codebook being generated for reporting feedback for the one or more downlink transmissions and being populated at least in part based on the applied repetition factor and based on whether the one or more downlink transmissions are successfully received and decoded by the UE.

Images