Type 1 Codebook Construction by Multiple Aggregation Factors

Abstract

A method, system, and device for wireless communications 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 in the UE. The UE may identify an applicable 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 based at least in part on the applicable repetition factor and whether the one or more downlink transmissions were successfully received and decoded. The UE may transmit a feedback report including the feedback codebook to the base station.

Description

Claim of Priority

[0001] Cross - Reference

[0001] 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" by FAKOORIAN et al., filed on April 7, 2020, and U.S. Patent Application No. 17 / 222,672, entitled "TYPE - 1 CODEBOOK CONSTRUCTION WITH MULTIPLE AGGREGATION FACTORS" by FAKOORIAN et al., filed on April 5, 2021, each of which is assigned to the assignee of the present specification.

Technical Field

[0002]

[0002] The following generally relates to wireless communication, and more particularly, to type 1 codebook construction with multiple aggregation factors.

Background Art

[0003]

[0003] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, messaging, and broadcast. These systems may be able to support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-connection systems include fourth-generation (4G) systems such as Long Term Evolution (LTE (registered trademark)) systems, LTE-Advanced (LTE-A) systems, or LTE-A Pro systems, and fifth-generation (5G) systems sometimes referred to as New Radio (NR) systems. These systems may employ 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-connection communication system may include one or more base stations or one or more network access nodes that each simultaneously support communication for a plurality of communication devices, sometimes known as user equipment (UE).

Summary of the Invention

[0004]

[0004] The described techniques relate to an improved method, system, device, and apparatus for supporting Type 1 codebook construction by multiple aggregation factors. Generally, the described techniques enable 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 (one or more) downlink transmissions, and each downlink transmission has an associated repetition factor (e.g., an aggregation factor such as 1, 2, 4, 8, etc.) from a plurality of configured repetition factors (e.g., aggregation factors) at the UE. However, the base station and the UE may identify an applied repetition factor that will be applied to feedback codebook generation for the (one or more) downlink transmissions. Broadly speaking, the applied repetition factor may be unrelated to 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 (one or more) downlink transmissions to the UE, and then the UE generates a feedback codebook to report feedback for the (one or more) downlink transmissions to the base station. When generating the feedback codebook, the UE may use the applied repetition factor in addition to whether the UE was able to successfully receive and decode one or more repetitions of the downlink transmission. Thus, the UE may transmit or otherwise convey a feedback report that carries or conveys the indication of the feedback codebook to the base station.

[0005] A method of wireless communication in a UE is described. The method may include the base station determining to 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 in the UE, identifying an applicable repetition factor for use in generating a feedback codebook 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 applicable repetition factor and 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.

[0006] An apparatus for wireless communication in a UE 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 determine that the base station has determined to 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 in the UE, identify an applicable repetition factor for use in generating a 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 applicable repetition factor and 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.

[0007] Another apparatus for wireless communication in a UE is described. The apparatus includes 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 in the UE, means for identifying an applicable repetition factor for use in generating a feedback codebook 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 based on the applicable repetition factor and whether the one or more downlink transmissions were successfully received and decoded, and means for transmitting a feedback report including the feedback codebook to the base station.

[0008] A non-transitory computer-readable medium storing code for wireless communication in a UE is described. The code includes 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 in the UE, identify an applicable repetition factor for use in generating a 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 applicable repetition factor and whether the one or more downlink transmissions were successfully received and decoded, and transmit a feedback report including the feedback codebook to the base station.

[0009] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for identifying an applicable repetition factor based on the maximum number of configured repetition factors from a set of configured repetition factors.

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

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

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

[0013] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for, for each of one or more downlink transmissions, determining that one or more instances of the downlink transmission may have been dropped, and generating a feedback codebook to be different between one or more instances of the downlink transmission that may have been dropped and one or more instances of the downlink transmission that may not have been dropped.

[0014] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for generating an acknowledgement / negative acknowledgement (ACK / NACK) indication for each actually received and decoded downlink transmission and refraining from generating an ACK / NACK indication for each instance of a dropped downlink transmission opportunity in generating the feedback codebook.

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

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

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

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

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

[0020]

[0020] 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 cause the processor to perform operations including 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 an applied repetition factor for the UE to apply for feedback codebook generation for the one or more downlink transmissions, receiving a feedback report including the feedback codebook from the UE, and the feedback codebook being generated to report feedback for the one or more downlink transmissions and being populated based on whether the applied repetition factor and the one or more downlink transmissions were successfully received and decoded by the UE.

[0021]

[0021] Another apparatus for wireless communication at a base station is described. The apparatus 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 an applied repetition factor for the UE to apply for feedback codebook generation for the one or more downlink transmissions, means for receiving a feedback report including the feedback codebook from the UE, and the feedback codebook being generated to report feedback for the one or more downlink transmissions and being populated based on whether the applied repetition factor and the one or more downlink transmissions were successfully received and decoded by the UE.

[0022] A non - transitory computer - readable medium storing code for wireless communication at a base station is described. The code causes a processor to perform operations including: scheduling a UE for one or more downlink transmissions; identifying an applicable repetition factor for the UE to apply for feedback codebook generation for the one or more downlink transmissions, where each of the one or more downlink transmissions has an associated repetition factor corresponding to one of a set of configured repetition factors configured at the UE; receiving a feedback report from the UE including a feedback codebook, where the feedback codebook is generated to report feedback for the one or more downlink transmissions and is populated based on whether the applicable repetition factor and the one or more downlink transmissions are successfully received and decoded by the UE.

[0023]

[0023] Some examples of the methods, apparatuses, and non - transitory computer - readable media described herein may further include operations, features, means, or instructions for identifying an applicable repetition factor based on the maximum number of configured repetition factors from a set of configured repetition factors.

[0024]

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

[0025]

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

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

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

[0028] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may further include operations, features, means, or instructions for determining for each of one or more downlink transmissions that one or more instances of the downlink transmission may have been dropped, and the feedback codebook may be generated to be different for one or more instances of the downlink transmission that may have been dropped and one or more instances of the downlink transmission that may not have been dropped.

[0029] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the feedback codebook may be generated based on the fact that an ACK / NACK indication may be generated for each downlink transmission actually received and decoded by the UE, and no ACK / NACK indication may be generated for each instance of a dropped downlink transmission opportunity.

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

[0031]

[0031] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the UE may be configured with a set of reporting offset values for transmitting a feedback report to the base station, each of the set of reporting offset values representing the number of 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 evaluating each of the set of reporting offset values within the evaluation window.

[0032]

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

[0033]

[0033] 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

[0034]

Figure 1

[0034] A diagram illustrating an example of a system for wireless communication supporting type 1 codebook construction with multiple aggregation factors, according to an aspect of the present disclosure.

Figure 2

[0035] A diagram illustrating an example of a feedback configuration supporting type 1 codebook construction with multiple aggregation factors, according to an aspect of the present disclosure.

Figure 3

[0036] A diagram illustrating an example of a feedback configuration supporting type 1 codebook construction with multiple aggregation factors, according to an aspect of the present disclosure.

Figure 4

[0037] A diagram showing an example of a process for supporting Type 1 codebook construction using multiple aggregation factors according to an aspect of the present disclosure.

Figure 5

[0038] A diagram showing an example of a feedback configuration for supporting Type 1 codebook construction using multiple aggregation factors according to an aspect of the present disclosure.

Figure 6

[0039] A block diagram of a device for supporting Type 1 codebook construction using multiple aggregation factors according to an aspect of the present disclosure.

Figure 7

Figure 8

[0040] A block diagram of a communication manager for supporting Type 1 codebook construction using multiple aggregation factors according to an aspect of the present disclosure.

Figure 9

[0041] A diagram of a system including a device for supporting Type 1 codebook construction using multiple aggregation factors according to an aspect of the present disclosure.

Figure 10

[0042] A block diagram of a device for supporting Type 1 codebook construction using multiple aggregation factors according to an aspect of the present disclosure.

Figure 11

Figure 12

[0043] A block diagram of a communication manager for supporting Type 1 codebook construction using multiple aggregation factors according to an aspect of the present disclosure.

Figure 13

[0044] A diagram of a system including a device for supporting Type 1 codebook construction using multiple aggregation factors according to an aspect of the present disclosure.

Figure 14

[0045] A flowchart showing a method for supporting Type 1 codebook construction by a plurality of aggregation factors according to an aspect of the present disclosure.

Figure 15

Figure 16

Figure 17

Figure 18

DETAILED DESCRIPTION OF THE INVENTION

[0035]

[0046] 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 codebook) that contains a series of bits generated based on the transmission configuration. For example, a base station may schedule a user equipment (UE) in a downlink transmission (e.g., a physical downlink shared channel (PDSCH) transmission), and this downlink transmission may include a repetition factor (or aggregation factor) for the downlink transmission and a related reporting offset value (e.g., a K1 value). The UE may be composed of multiple PDSCH aggregation factors, for example, for dynamic PDSCH and / or various 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 at least one repetition has been successfully received and decoded and reports its acknowledgement / negative acknowledgement (ACK / NACK) bit for the downlink transmission. However, some repetitions of the downlink transmission may be in conflict and thus excluded, and may therefore be unavailable for transmission to the UE. This can cause confusion and inaccuracies in the codebook generated by the UE and provided to the base station, which can lead to waste of resources due to unnecessary retransmissions and / or loss of communication between the UE and the base station.

[0036]

[0047] Initially, aspects of the present disclosure are described in the context of a wireless communication system. Generally, the techniques described enable more efficient and responsive codebook generation for HARQ-ACK reporting. For example, a base station may schedule a user equipment (UE) for a downlink transmission, and each downlink transmission has an associated repetition factor (e.g., an aggregation factor such as 1, 2, 4, 8, etc.) from a plurality of configured repetition factors at the UE. However, the base station and the UE may identify the applicable repetition factor to be applied to feedback codebook generation for the downlink transmission. Broadly speaking, the applicable repetition factor may be unrelated to 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 downlink transmission to the UE, and then the UE generates a feedback codebook to report feedback about the downlink transmission to the base station. When generating the feedback codebook, the UE may use the applicable repetition factor in addition to whether the UE was able to successfully receive and decode one or more repetitions of the downlink transmission. Accordingly, the UE may transmit or otherwise convey a feedback report that carries or conveys an indication of the feedback codebook to the base station.

[0037]

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

[0038]

[0049] FIG. 1 shows an example of a wireless communication system 100 that supports Type 1 codebook construction by a plurality of aggregation factors according to an aspect of the present disclosure. 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 extended broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, communication using low-cost and low-complexity devices, or any combination thereof.

[0039]

[0050] The base stations 105 may be distributed across a geographic area to form the wireless communication system 100 and may be devices of different forms or 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 in which the UE 115 and the base station 105 may establish one or more communication links 125. The coverage area 110 may be an example of a geographic area in which the base station 105 and the UE 115 may support signal communication according to one or more radio access technologies.

[0040]

[0051] UE 115 can be distributed across the coverage area 110 of the wireless communication system 100, and each UE 115 can be fixed, mobile, or both at different times. UE 115 can be a device with different forms or different capabilities. Some exemplary UEs 115 are shown in FIG. 1. The UE 115 described herein can communicate with various types of devices, such as other UEs 115, base stations 105, or network devices (e.g., core network nodes, relay devices, integrated access and backhaul (IAB) nodes, or other network devices), as shown in FIG. 1.

[0041]

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

[0042]

[0053] One or more of the base stations 105 described herein can include a base transceiver station, a radio base station, an access point, a radio transceiver, a Node B, an evolved Node B (eNB), a next-generation Node B or a giga Node B (any of which may be referred to as a gNB), a home Node B, a home eNode B, or other suitable terms, or may be so called by those skilled in the art.

[0043]

[0054] UE115 may include, or may be referred to as, a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term, where "device" may also be referred to as, among other examples, a unit, a station, a terminal, or a client. UE115 may also include, or may be referred to as, a personal electronic device such as a cellular phone, a personal digital assistant (PDA), a tablet computer, a laptop computer, or a personal computer. In some examples, UE115 may include, or may be referred to as, among other examples, a wireless local loop (WLL) station, an Internet of Things (IoT) device, any Internet of Everything (IoE) device, or a machine type communication (MTC) device that may be implemented in various objects such as an appliance, or a vehicle, a meter, etc.

[0044]

[0055] As shown in FIG. 1, the UE115 described herein may sometimes act as a relay and may be capable of communicating with various types of devices, such as other UE115s that may sometimes act as relays, and, among other examples, base station 105 and network equipment including a macro eNB or gNB, a small cell eNB or gNB, or a relay base station.

[0045]

[0056] UE115 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, the carrier used for communication link 125 may include a portion of a radio frequency spectrum band (e.g., a bandwidth part (BWP)) that operates according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling to coordinate the operation of the carrier, user data, or other signaling. The wireless communication system 100 may support communication with UE115 using carrier aggregation or multi-carrier operation. UE115 may be composed of a plurality of downlink component carriers and one or more uplink component carriers according to a carrier aggregation configuration. Carrier aggregation may be used with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers.

[0046]

[0057] In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling or control signaling to coordinate the operation for other carriers. A carrier may be associated with a frequency channel (e.g., an evolved universal terrestrial radio access (E-UTRA) absolute radio frequency channel number (EARFCN)) and may be arranged according to a channel raster for discovery by UE115. A carrier may operate in a stand-alone mode where initial acquisition and connection may be performed by UE115 via the carrier, or a carrier may operate in a non-stand-alone mode where a connection is established using different carriers (e.g., of the same or different radio access technologies).

[0047]

[0058] The communication link 125 shown in the wireless communication system 100 may include an uplink transmission from the UE 115 to the base station 105 or a downlink transmission from the base station 105 to the UE 115. A carrier may carry downlink communication 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).

[0048]

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

[0049]

[0060] The signal waveform transmitted on a carrier can be composed of a plurality of sub-carriers (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 adopting the MCM technique, a resource element can consist of one symbol period (e.g., the duration of one modulated symbol) and one sub-carrier, where the symbol period and the sub-carrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme, the coding rate of the modulation scheme, or both). Therefore, the higher the number of resource elements received by the UE115 and the higher the order of the modulation scheme, the higher the data rate for the UE115 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 the use of multiple spatial layers can further increase the data rate or data integrity for communication with the UE115.

[0050]

[0061] One or more numerologies can be supported for a carrier, where the numerology can include the sub-carrier spacing (Δf) and the cyclic prefix. A carrier can be divided into one or more BWPs having the same or different numerologies. In some examples, the UE115 can be composed of multiple BWPs. In some examples, a single BWP for a carrier can be active at a given time, and communication for the UE115 can be restricted to one or more active BWPs.

[0051]

[0062] The time interval for the base station 105 or the UE115 can be expressed in multiples of a basic time unit, for example, T s =1 / (Δf max ·N f ) seconds sampling period, where Δf max can represent the maximum supported sub-carrier spacing, and N fmay represent the maximum supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources may be organized according to radio frames each having a specified duration (e.g., 10 milliseconds (ms)). Each radio frame may be identified by a system frame number (SFN) (e.g., ranging from 0 to 1023).

[0052]

[0063] Each frame may include a plurality of consecutively numbered subframes or slots, and each subframe or slot may have the same duration. In some examples, a frame may be divided into subframes (e.g., in the time domain), and each subframe may be further divided into a number of slots. Alternatively, each frame may include a variable number of slots, and the number of slots may depend on the subcarrier spacing. Each slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix prepended to each symbol period). In some wireless communication systems 100, a slot may be further divided into a plurality of minislots each including one or more symbols. Excluding the cyclic prefix, each symbol period may include one or more (e.g., N f number of) sampling periods. The duration of the symbol period may depend on the subcarrier spacing or the frequency operating band.

[0053]

[0064] A subframe, slot, minislot, or symbol may be the smallest scheduling unit in the wireless communication system 100 (e.g., in the time domain) and may 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) may be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 may be dynamically selected (e.g., during a burst of shortened TTIs (sTTIs)).

[0054]

[0065] 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, for example, using 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 a number of symbol periods and can span the system bandwidth of the carrier or a subset of the system bandwidth. One or more control regions (e.g., CORESET) 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 at one or more aggregation levels configured in a cascaded manner. The aggregation level for a control channel candidate can refer to a 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 a plurality of UEs 115 and a UE-specific search space set for sending control information to a specific UE 115.

[0055]

[0066] Each base station 105 may provide communication coverage via one or more cells, such as macro cells, small cells, hotspots, or other types of cells, or any combination thereof. The term "cell" may refer to a logical communication entity used for communication with a base station 105 (e.g., on a carrier), and may be associated with an identifier (e.g., a physical cell identifier (PCID), a virtual cell identifier (VCID), or others) for distinguishing neighboring cells. In some examples, a cell may also refer to a geographical coverage area 110 in which the logical communication entity operates or a portion (e.g., a sector) of the geographical coverage area 110. Such cells may range from smaller areas (e.g., structures, subsets of structures) to larger areas depending on various factors such as the capabilities of the base station 105. For example, a cell may be, among other examples, a building, a subset of a building, or an external space that is between or overlaps with the geographical coverage areas 110 or includes them.

[0056]

[0067] A macro cell generally covers a relatively large geographical area (e.g., with a radius of several kilometers) and may enable unrestricted access by a UE 115 that subscribes to the services of the network provider supporting the macro cell. A small cell may be associated with a low-power base station 105 compared to a macro cell, and the small cell may operate in the same or a different (e.g., licensed, unlicensed) frequency band as the macro cell. A small cell may provide unrestricted access to a UE 115 that subscribes to the services of the network provider or may provide restricted access to a UE 115 associated with the small cell (e.g., a UE 115 in a closed subscriber group (CSG), a UE 115 associated with a user at home or in an 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.

[0057]

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

[0058]

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

[0059]

[0070] Wireless communication system 100 may support synchronous operation or asynchronous operation. In the case of synchronous operation, base stations 105 may have similar frame timings, and transmissions from different base stations 105 may be approximately time-aligned. In the case of asynchronous operation, base stations 105 may have different frame timings, and in some examples, transmissions from different base stations 105 may not be time-aligned. The techniques described herein may be used for either synchronous operation or asynchronous operation.

[0060]

[0071] Some UEs 115, such as MTC devices or IoT devices, can be low-cost or low-complexity devices and can provide automatic communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can refer to data communication technologies that enable devices to communicate with each other or with the base station 105 without human intervention. In some examples, M2M communication or MTC incorporates sensors or meters to measure or capture information and relays such information to a central server or application program that utilizes the information, or presents the information to a human who interacts with the application program, and can include communication from the device. Some UEs 115 can be designed to collect information or enable automated behavior of machines or other devices. Examples of applications for MTC devices include smart metering, inventory monitoring, water level monitoring, equipment monitoring, healthcare monitoring, wildlife monitoring, weather and geological event monitoring, fleet management and tracking, remote security detection, physical access control, and transaction-based business billing.

[0061]

[0072] Some UEs 115 can be configured to adopt an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports one-way communication via transmission or reception rather than simultaneous transmission and reception). In some examples, half-duplex communication can be implemented at a reduced peak rate. Other power-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not participating in active communication, operating on a limited bandwidth (e.g., in accordance with 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 the carrier, or outside the carrier (e.g., a set of subcarriers or resource blocks (RBs)).

[0062]

[0073] 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. The UE 115 can be designed to support an ultra-reliable function, a low-latency function, or a critical function (e.g., a mission-critical function). 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 use cases. The terms ultra-reliable, low-latency, mission-critical, and ultra-reliable low-latency can be used interchangeably herein.

[0063]

[0074] 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 a peer-to-peer (P2P) or D2D protocol). One or more UEs 115 that utilize D2D communication may be within the geographical coverage area 110 of the base station 105. Other UEs 115 in such a group may be outside the geographical coverage area 110 of the base station 105 or, otherwise, may not be able to receive transmissions from the base station 105. In some examples, a group of UEs 115 that communicate via D2D communication may utilize a one-to-many (1:M) system in which 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 UEs 115 without the involvement of the base station 105.

[0064]

[0075] In some systems, the D2D communication link 135 can be an example of a communication channel, such as a sidelink communication channel, between vehicles (e.g., UE 115). In some examples, vehicles can communicate using vehicle-to-everything (V2X) communication, vehicle-to-vehicle (V2V) communication, or some combination thereof. Vehicles can 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 can communicate with roadside infrastructure, such as a roadside unit, or a network via one or more network nodes (e.g., base station 105) using vehicle-to-network (V2N) communication, or both.

[0065]

[0076] 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 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 interconnectivity to an external network, and may be an evolved packet core (EPC) or a 5G core (5GC). The control plane entity may manage non-access stratum (NAS) functions such as mobility, authentication, and bearer management for the UE 115 served by the base station 105 associated with the core network 130. User IP packets may be transferred through a user plane entity that 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(s), an IP Multimedia Subsystem (IMS), or a packet-switched streaming service.

[0066]

[0077] Some of the network devices, such as base station 105, may include sub-components such as access network entity 140, which can be an example of an access node controller (ANC). Each access network entity 140 can communicate with UE 115 through one or more other access network transmission entities 145, which may be referred to as a radio head, a smart radio head, or a transmit / receive point (TRP). 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 head and ANC) or integrated into a single network device (e.g., base station 105).

[0067]

[0078] Wireless communication system 100 can typically operate using one or more frequency bands in the range of 300 megahertz (MHz) to 300 gigahertz (GHz). Generally, the region from 300 MHz to 3 GHz is known as the ultra-high frequency (UHF) region or the decimeter band because the wavelength ranges from approximately 1 decimeter to 1 meter. UHF waves can be blocked or redirected by buildings and environmental features, but the waves can penetrate the structure sufficiently for a macrocell to provide service to a UE 115 located indoors. Transmission of UHF waves can be associated with smaller antennas and shorter distances (e.g., less than 100 kilometers) compared to transmission using smaller frequencies and longer waves in the high frequency (HF) or very high frequency (VHF) portions of the spectrum below 300 MHz.

[0068]

[0079] The wireless communication system 100 can operate in the super high frequency (SHF) band that uses a frequency band from 3 GHz to 30 GHz, also known as the centimeter band, or in the extremely high frequency (EHF) band of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter band. In some examples, the wireless communication system 100 can support millimeter wave (mmW) communication between the UE 115 and the base station 105, and the EHF antennas of each device can be smaller and more closely spaced than UHF antennas. In some examples, this can facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions can experience greater atmospheric attenuation and shorter distances than SHF or UHF transmissions. The techniques disclosed herein can be employed across transmissions using one or more different frequency bands, and the specified use of the bands across these frequency bands can vary by country or regulatory body.

[0069]

[0080] The wireless communication system 100 can utilize both licensed radio frequency spectrum bands and unlicensed radio frequency spectrum bands. For example, the wireless communication system 100 can employ license-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 the unlicensed radio frequency spectrum band, devices such as the base station 105 and the UE 115 can employ carrier sensing for collision detection and avoidance. In some examples, operation in the unlicensed band can be based on a carrier aggregation configuration with a component carrier operating in a licensed band (e.g., LAA). Operation in the unlicensed spectrum can include, among other examples, downlink transmission, uplink transmission, peer-to-peer (P2P) transmission, or device-to-device (D2D) transmission.

[0070]

[0081] The base station 105 or the UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of the base station 105 or the UE 115 may 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 may be collocated in an antenna assembly, such as an antenna tower. In some examples, the antennas or antenna arrays associated with the base station 105 may be located in diverse geographical locations. The base station 105 may have an antenna array with several rows and columns of antenna ports that can be used to support beamforming for communication with the UE 115. Similarly, the UE 115 may have one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support radio frequency beamforming for signals transmitted via the antenna ports.

[0071]

[0082] The base station 105 or the UE 115 may use MIMO communication to increase spectral efficiency by leveraging multipath signal propagation and transmitting or receiving multiple signals via different spatial layers. Such techniques are sometimes referred to as spatial multiplexing. The multiple signals may be transmitted by a transmitting device via, for example, different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry bits associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). The different spatial layers may be associated with different antenna ports used 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.

[0072]

[0083] Beamforming, sometimes also referred to as spatial filtering, directional transmission, or directional reception, is a signal processing technique that can be used in a transmitting device or a receiving device (e.g., base station 105, UE 115) to shape or steer an antenna beam (e.g., a transmission beam, a reception beam) along a spatial path between the transmitting device and the receiving device. Beamforming can be achieved by combining signals communicated through antenna elements of an antenna array such that some signals propagating in a particular orientation with respect to the antenna array experience constructive interference and others experience destructive interference. Adjustment of the signals communicated through 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 through the antenna elements associated with the device. The adjustment associated with each of the antenna elements can be defined by a set of beamforming weights associated with a particular orientation (e.g., with respect to the antenna array of the transmitting device or the receiving device, or with respect to some other orientation).

[0073]

[0084] Base station 105 or UE 115 may use a beam sweeping technique as part of a beamforming operation. For example, base station 105 may perform a beamforming operation for directional communication with UE 115 using multiple antennas or antenna arrays (e.g., antenna panels). Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted by base station 105 in various directions multiple times. For example, base station 105 may transmit signals according to different sets of beamforming weights associated with different transmission directions. By using transmissions in various beam directions, the beam direction for subsequent transmission or reception by base station 105 can be identified (e.g., by a transmitting device such as base station 105 or by a receiving device such as UE 115).

[0074]

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

[0075]

[0086] In some examples, transmission by a device (e.g., by base station 105 or UE115) can be performed using multiple beam directions, and the device can use a combination of digital precoding or radio frequency beamforming to generate a composite beam for transmission (e.g., from base station 105 to UE115). UE115 can report feedback indicating precoding weights for one or more beam directions, and the feedback can correspond to the system bandwidth or the configured number of beams across one or more subbands. Base station 105 can transmit a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)) that can be precoded or ampliconverted. UE115 can provide feedback for beam selection that can be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel type codebook, a linear combination type codebook, a port selection type codebook). These techniques have been described with respect to signals transmitted by base station 105 in one or more directions, but UE115 can employ similar techniques for transmitting signals multiple times in different directions (e.g., to identify beam directions for subsequent transmission or reception by UE115) or for transmitting signals in a single direction (e.g., to transmit data to a receiving device).

[0076]

[0087] When a receiving device (e.g., UE 115) receives various signals such as synchronization signals, reference signals, beam selection signals, or other control signals from base station 105, it may attempt multiple receiving configurations (e.g., directional listening). For example, the receiving device may receive via various antenna sub-arrays, process received signals according to various antenna sub-arrays, receive according to various receiving beamforming weight sets (e.g., various directional listening weight sets) applied to the signals received at multiple antenna elements of the antenna array, or process the received signals according to various receiving beamforming weight sets applied to the signals received at multiple antenna elements of the antenna array, thereby attempting multiple receiving directions, all of which may be referred to as "listening" according to various receiving configurations or receiving directions. In some examples, the receiving device may receive along a single beam direction using a single receiving configuration (e.g., when receiving data signals). The single receiving configuration may be aligned with the beam direction determined based on listening according to various receiving configuration directions (e.g., the beam direction determined to have the highest signal strength, the highest signal-to-noise ratio (SNR), or otherwise acceptable signal quality based on listening according to multiple beam directions).

[0077]

[0088] The wireless communication system 100 can be a packet-based network that operates according to a hierarchical protocol stack. In the user plane, communication in 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 to communicate over logical channels. The Medium Access Control (MAC) layer can perform prioritization and multiplexing of logical channels onto transport channels. The MAC layer can also use error detection techniques, error correction techniques, or both to support retransmissions in the MAC layer to improve link efficiency. In the control plane, the Radio Resource Control (RRC) protocol layer can establish, configure, and maintain an RRC connection between the UE 115 and the base station 105 or the core network 130 that supports radio bearers for user plane data. In the physical layer, transport channels can be mapped to physical channels.

[0078]

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

[0079]

[0090] UE 115 may determine that the base station 105 has scheduled 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 in UE 115. UE 115 may identify an applicable repetition factor for use in generating a feedback codebook for one or more downlink transmissions. UE 115 may generate a feedback codebook for reporting feedback for one or more downlink transmissions, the feedback codebook being populated based at least in part on the applicable repetition factor and whether one or more downlink transmissions were successfully received and decoded at UE 115. UE 115 may transmit a feedback report including the feedback codebook to the base station 105.

[0080]

[0091] The base station 105 may schedule 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 in UE 115. The base station 105 may identify an applicable repetition factor for UE 115 to use in generating a feedback codebook for one or more downlink transmissions. The base station 105 may receive from UE 115 a feedback report including the feedback codebook, the feedback codebook being generated for reporting feedback for one or more downlink transmissions and being populated based at least in part on the applicable repetition factor and whether one or more downlink transmissions were successfully received and decoded by UE 115.

[0081]

[0092] FIG. 2 shows an example of a feedback configuration 200 that supports Type 1 codebook construction by a plurality of aggregation factors according to an aspect of the present disclosure. In some examples, the feedback 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, and the base station and / or the UE may be examples of corresponding devices described herein.

[0082]

[0093] Broadly speaking, the feedback configuration 200 spans a plurality of slots 205, and by way of example only, five slots 205 are shown. The slot 205 may be composed of one or more PDSCH occasions 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 reporting occasion when the UE transmits a feedback report on the downlink transmission to the base station).

[0083]

[0094] In some wireless communication systems, the UE typically reports HARQ-ACK information (e.g., a feedback report) about PDSCH reception (e.g., downlink transmission) from slot

[0084]

Number

[0085] to slot n for the PDSCH reception (e.g., downlink transmission) in the HARQ-ACK codebook included in the PUCCH or physical uplink shared channel (PUSCH) transmission in slot n + k.

[0086]

Number

[0087] If a PDSCH aggregation factor is provided to the UE or the UE is configured with a PDSCH aggregation factor in another way, it can be the value of the PDSCH aggregation or repetition factor (pdsch-AggregationFactor). Otherwise,

[0088]

Number

[0089] can be regarded as 1. k can be the number of slots indicated by the PDSCH-to-HARQ feedback timing indicator in the corresponding downlink control information (DCI) format (e.g., the offset reporting 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, it can be the number of slots provided by dl-DatatoUL-ACK. When the UE reports HARQ-ACK information for PDSCH reception in slots other than slot n, the UE sets the value of each corresponding HARQ-ACK information bit to NACK or N. If tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated is provided to the UE and none of the repetitions are received due to uplink / downlink interaction / conflict,

[0090]

Number

[0091] For the associated PDSCH with multiple repetitions, ACK / NACK bits are not generated in the codebook.

[0092]

[0095] In some wireless communication systems, a UE may be configured with multiple SPS configurations. For example, these wireless communication systems may utilize the configuration of the PDSCH aggregation factor (pdsch-AggregationFactor) for each downlink SPS configuration, and the aggregation factor value ranges from {1, 2, 4, 8} (e.g., an aggregation or repetition factor of 1, 2, 4, or 8). For a PDSCH scheduled using sps-Config without a corresponding PDCCH transmission (e.g., without DCI) and activated by DCI format 1_1 or 1_2, or for a PDSCH scheduled by DCI format 1_1 or 1_2 in a PDCCH that is CRC scrambled with a configured scheduling radio network temporary identifier (CS-RNTI) and has a new data indicator (NDI) set to 0, if the PDSCH aggregation factor signaled in sps-Config is configured, it 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 that is CRC scrambled with CS-RNTI and has an NDI set to 1, the PDSCH aggregation factor signaled in pdsch-Config is applied.

[0093]

[0096] Therefore, the UE can be configured with multiple downlink transmission aggregation factors (e.g., pdsch-AggregationFactor), for example, it can be configured for dynamic PDSCH in pdsch-Config and / or for various SPS configurations in sps-Config, and these configurations can have different values of aggregation or repetition factors (e.g., pdsch-AggregationFactor). When multiple aggregation or repetition factors are configured, this is used to determine when to send the type 1 HARQ-ACK codebook (e.g., in which subslot or slot the HARQ-ACK codebook such as feedback report is sent via PUCCH or PUSCH), and / or how to construct the type 1 HARQ-ACK codebook (e.g., this includes the codebook size and the ACK / NACK bit positions within the codebook),

[0094]

Number

[0095] raises the question of what should be set.

[0096]

[0097] In such a wireless communication system, Type 1 codebook construction has a size overhead problem when the PDSCH aggregation factor is greater than 1 and the PDSCH occasion is dropped (e.g., due to downlink / uplink interaction or contention). That is, the UE can be configured with only one PDSCH aggregation factor set to 2 (e.g., two repetitions for each of the first downlink transmission 215 and the second downlink transmission 220 in the example shown in feedback configuration 200). The configured set of K1 values (shown as K) can be {1, 2, 4, 8}. During slot n (e.g., slot 205-d), the second repetition of the second downlink transmission 220 is dropped due to contention with an uplink symbol / signal. In addition, 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 can have only two non-overlapping start length indicator value (SLIV) rows for the PDSCH (e.g., N, N for 205-b, A / N, N for slot 205-c, and N, A / N for slot 205-d). However, codewords generated using conventional techniques (e.g., the "old" codebook) contain excessive bits, which increases the size and / or complexity of the codebook. This can also cause confusion between the base station and the UE regarding how the codebook is generated and thus how it can be read by the base station. However, aspects of the techniques described enable dropped PDSCH occasions (e.g., occasions where a downlink transmission may or may not be scheduled for the UE) to be removed from the Type 1 codebook.

[0097]

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

[0098]

[0099] The base station may transmit downlink transmissions to the UE according to the configuration. For example, slot n-3 (e.g., slot 205-a) is scheduled in two PDSCH occasions 210. Generally speaking, PDSCH occasion 210 generally refers to an occasion (in the form of resources) in which downlink transmission can be scheduled for the UE. In feedback configuration 200, the illustrated PDSCH occasion 210 is a resource in which downlink transmission can be scheduled but is not scheduled. However, each downlink transmission occurs between PDSCH occasions. In feedback configuration 200, the actually scheduled transmission is shown as a PDSCH transmission, and the unused transmission resources or occasions are called PDSCH occasion 210. Each slot in which the PDSCH can be received is shown as having the same PDSCH occasion. As discussed, each part of slot n-2 (e.g., slot 205-b) is configured as an uplink part that overlaps both PDSCH occasions, and thus any PDSCH occurring within this slot (whether it be PDSCH occasion 210 or the first repetition of the first downlink transmission 215) is dropped. During slot n-1 (e.g., slot 205-c), the base station may transmit the second repetition of the first downlink transmission 215 (having a reporting offset of K or K1 = 2) and the first repetition of the second downlink transmission 220 (having a reporting offset of K or K1 = 1). Again, as discussed, during slot n (e.g., slot 205-d), the second repetition of the second downlink transmission 220 is in conflict and excluded, and thus is not transmitted or is dropped.

[0099]

[0100] Accordingly, the UE may generate a feedback codebook for reporting feedback for scheduled downlink transmissions that is populated based at least in part on an applied repetition factor and whether the scheduled downlink transmissions are successfully received and decoded by the UE. That is, the UE may utilize the applied repetition factor instead of the repetition factor configured by the base station for the downlink transmission. Various alternatives may be utilized for identifying and applying the applied repetition factor.

[0100]

[0101] One alternative may include identifying the applied repetition factor based on the maximum number of configured repetition factors from the UE's configured repetition factors (e.g., the maximum across all PDSCH aggregation factors or pdsch-AggregationFactor configurations). For example, both the UE and the base station may identify the maximum number of configured repetition factors without counting or otherwise considering the configured repetition factors corresponding to inactive SPS configurations (e.g., the PDSCH aggregation factor does not include inactive SPS configurations when configured for the UE). In another example, the base station and the UE may identify the maximum number of configured repetition factors by counting the configured repetition factors 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). During a given slot 205, the ACK / NACK bit position in the type 1 codebook corresponding to the PDSCH from the TDRA table is dropped only if this PDSCH is dropped during this slot 205 and all (e.g., max_pdsch-AggregationFactor)-1 slots 205. The codebook size will have a larger overhead when PDSCHs within the K-1 window are dropped (e.g., as shown in the "old" codebook).

[0101]

[0102] One alternative may include identifying the application repetition factor as 1. In this case, the UE may generate a feedback codebook based on the last instance of each downlink transmission that was actually received and decoded. For example,

[0102]

Number

[0103] may always be considered as 1, and the ACK / NACK bit positions for each PDSCH with repetition may be associated with the last actual PDSCH reception. As a result, the UE may generate the "new" codebook shown in feedback configuration 200. As can be seen, this approach halves the size of the codebook that the UE generates and transmits to the base station. That is, this reduces the codebook size when some PDSCH occasions are dropped and the PDSCH aggregation factor is greater than 1, and provides an even greater benefit when the PDSCH aggregation factor is large.

[0104]

[0103] Thus, the UE and the base station may determine that an instance of a downlink transmission has been dropped. Accordingly, the UE may generate a feedback codebook for the dropped downlink transmission that is different from that for the non-dropped downlink transmissions. For example, the UE may generate an ACK / NACK indication (e.g., an ACK / NACK bit) for each downlink transmission that was actually received and decoded, but may not generate an ACK / NACK indication for each instance of the dropped downlink transmission opportunity.

[0105]

[0104] In some aspects, the feedback codebook can be generated regardless of the DCI related to downlink transmission (e.g., it can be based on the SPS configuration). For example, the UE can generate a type 1 feedback codebook based on the SPS configuration provided by the base station.

[0106]

[0105] During slot n+1 (e.g., slot 205-e), the UE can send 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 described techniques. As discussed, these techniques can improve codebook generation by the UE, 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 expected to be received by the base station.

[0107]

[0106] FIG. 3 shows an example of a feedback configuration 300 that supports type 1 codebook construction by multiple aggregation factors according to an aspect of the present disclosure. In some examples, the feedback configuration 300 can implement aspects of the wireless communication system 100 and / or the feedback configuration 200. Aspects of the feedback configuration 300 can be implemented by the base station and / or the UE, and the base station and / or the UE can be examples of the corresponding devices described herein.

[0108]

[0107] Broadly speaking, the feedback configuration 300 spans multiple slots 305, and for example, five slots 305 are shown. The slot 305 can be composed of one or more PDSCH occasions 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 occasion when the UE sends a feedback report about the downlink transmission to the base station).

[0109] As discussed above, the base station may schedule the UE for one or more downlink transmissions (e.g., for example only, the first downlink transmission 315 and the second downlink transmission 320). Each downlink transmission may have an associated repetition factor (e.g., an aggregation factor which in this example 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 (e.g., {1, 2, 4, 8}) configured at the UE. However, the base station and the UE may identify an applied repetition factor (aggregation factor) to be applied for feedback codebook generation for the scheduled downlink transmission instead of the associated repetition or aggregation factor. For example, as discussed with respect to FIG. 2, the applied repetition factor may be 1.

[0110]

[0109] The base station may transmit downlink transmissions 315, 320 to the UE according to the configuration. For example, slot n-3 (e.g., slot 305-a) is scheduled for the first repetition of both the first downlink transmission 315 and the second downlink transmission 320. Slot n-2 (e.g., slot 305-b) is configured to include an uplink portion that overlaps with the scheduled repetitions of both downlink transmissions 315, 320, and thus any PDSCH occurring within this slot (e.g., both the first downlink transmission 315 and the second repetition of the second downlink transmission 320) is dropped. During slot n-1 (e.g., slot 305-c), the base station may transmit the third repetition of the second downlink transmission 320, and the PDSCH occasion 310 is not used. During slot n (e.g., slot 305-d), the PDSCH occasion 310 is also not used, and the fourth repetition of the second downlink transmission 320 is dropped (e.g., due to the specified uplink portion of slot n, it is competitively excluded). 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.

[0111]

[0110] Therefore, the UE may generate a feedback codebook for reporting feedback regarding the scheduled downlink transmissions, which is populated at least in part based on the applicable repetition factor and whether the scheduled downlink transmissions are successfully received and decoded by the UE. That is, the UE may utilize the applicable repetition factor rather than the repetition factor associated with the downlink transmissions configured by the base station.

[0112]

[0111] In the example of FIG. 3, when the application repetition factor is 1 and the UE is composed of a K1 window of {1, 2, 3}, the ACK / NACK bits for the downlink transmission 315 will not be incorporated into the feedback codebook. When the application repetition factor is 1, the UE will consider slots n, n - 1, and n - 2 (corresponding to the K1 window) when populating the feedback codebook. Using the process outlined with respect to FIG. 2, nothing will be included in the codebook corresponding to slot n - 2. In slot n - 1, a NACK will be included to correspond to the unused PDSCH occasion 310, and an ACK / NACK will be included to correspond to the third repetition of the downlink transmission 320. In slot n, only a NACK corresponding to the unused PDSCH occasion 310 will be included. Thus, the feedback codebook is still reduced, but there is no report for the downlink transmission 315 in the codebook. To avoid this scenario, scheduling rules can be used.

[0113]

[0112] In the feedback configuration 300, the scheduling rules can include that for a given PDSCH with a PDSCH aggregation factor greater than 1, it cannot be expected that the UE is configured with a set of K - 1 values such that none of the actual PDSCH receptions are within the K1 window. That is, it can be expected that the UE is configured such that at least one reception of the PDSCH is within the K1 window. For example, the UE can be composed of a plurality of reporting offset values for transmitting a feedback report to the base station, and each of the reporting offset values represents the number of slots after the last nominal downlink transmission. The reporting offset values can span an evaluation window, and the feedback codebook can be generated based on the UE evaluating each of the plurality of reporting offset values within the evaluation window. The UE can generate the feedback codebook based on this technique.

[0114]

[0113] During slot n+1 (e.g., slot 305-e), the UE may transmit or otherwise convey to the base station an indication of a feedback report (e.g., PUCCH 325) that includes a feedback codebook generated according to the described techniques. As discussed, these techniques may improve codebook generation by the UE, reduce the overall size of the codebook to minimize overhead, and more accurately guarantee consistency between the codebook generated by the UE and the codebook expected to be received by the base station.

[0115]

[0114] FIG. 4 shows an example of a process 400 that supports type 1 codebook construction by a plurality of aggregation factors, according to an aspect of the present disclosure. 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 corresponding devices described herein.

[0116]

[0115] At 415, the base station 410 may schedule the 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 a plurality of repetition factors configured by the base station 410 at the UE 405.

[0117]

[0116] At 420, the UE 405 may identify an application repetition factor for use in generating a feedback codebook for one or more downlink transmissions. Similarly, at 425, the base station may also identify an application repetition factor for the UE 405 to apply in generating a feedback codebook for one or more downlink transmissions. For example, the base station 410 may transmit (e.g., in RRC configuration signaling) to the UE 405 a configuration signal identifying the application repetition factor to be utilized in generating the feedback codebook. In another example, the base station 410 may configure the SPS configuration for the UE 405, which may implicitly indicate that an application repetition factor is to be used.

[0118]

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

[0119]

[0118] For example, the UE 405 may identify the application repetition factor based on the maximum number of configured repetition factors from a plurality of configured repetition factors. For example, the UE 405 may identify the maximum number of configured repetition factors without counting inactive SPS configurations. In another example, the UE 405 may identify the maximum number of configured repetition factors by counting both active and inactive SPS configurations. In some aspects, this may include the UE 405 identifying the application repetition factor as 1. Thus, the UE 405 may generate the feedback codebook based on the last instance of each downlink transmission that was actually successfully received and decoded.

[0120]

[0119] In some aspects, this may include the UE 405 determining that one or more instances of downlink transmissions have been dropped. Thus, the UE 405 may generate a feedback codebook that is different for dropped downlink transmissions than for non-dropped (e.g., actually transmitted) downlink transmissions. For example, the UE 405 may generate an ACK / NACK indication for each downlink transmission that is actually received and decoded, but may refrain from generating an ACK / NACK indication for dropped downlink transmissions.

[0121]

[0120] In some aspects, this may include the 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 slots after the last nominal downlink transmission, and the reporting offset values may span an evaluation window (e.g., K1 window). The UE 405 may generate a feedback codebook based on the evaluation of each reporting offset value within the evaluation window.

[0122]

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

[0123]

[0122] FIG. 5 shows an example of a feedback configuration 500 that supports type 1 codebook construction with multiple aggregation factors, according to aspects of the present disclosure. In some examples, the feedback configuration 500 may implement aspects of the wireless communication system 100, the feedback configurations 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.

[0124] <0123>Broadly speaking, the feedback configuration 500 spans a plurality of slots 505, five slots 505 being shown by way of example only. A slot 505 can be composed of a first downlink transmission 515 (for example, PDSCH#1), a second downlink transmission 520 (for example, PDSCH#2), and a PUCCH 525 (for example, a feedback reporting occasion when the UE transmits a feedback report on the downlink transmission to the base station).

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

[0126]

[0125] The base station may transmit downlink transmissions to the UE according to the configuration. For example, slot n-3 (e.g., slot 505-a) is scheduled for the first repetition transmission of the second downlink transmission 520. Slot n-2 (e.g., slot 505-b) is scheduled for the transmission of the first repetition of the first downlink transmission 515 and the second repetition of the second downlink transmission 520. Slot n-1 (e.g., slot 505-c) is scheduled for the transmission of the second repetition of the first downlink transmission 515 and the third repetition of the second downlink transmission 520. During slot n (e.g., slot 505-d), the second downlink transmission 520 is dropped (e.g., excluded due to contention). 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.

[0127]

[0126] Therefore, the UE may generate a feedback codebook for reporting feedback on scheduled downlink transmissions that is populated at least in part based on the applicable repetition factor and whether the scheduled downlink transmissions are successfully received and decoded by the UE. That is, the UE may utilize the applicable repetition factor instead of the repetition factor associated with the downlink transmissions configured by the base station.

[0128]

[0127] In the example shown in the feedback configuration 500, regardless of the number of PDSCH aggregation factors configured, the UE includes, in the HARQ-ACK codebook included in the PUCCH or PUSCH transmission in slot n + k, the slots

[0129]

Number

[0130] from slot

[0131]

Number

[0132] HARQ-ACK information about PDSCH with loop repetition can be reported, where k is indicated in the DCI.

[0133]

Number

[0134] can be defined for each PDSCH. For example, pdsch-AggregationFactor can be, for each composed downlink grant transmission and SPS-configured downlink transmission, for example, 2 or 4.

[0135]

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

[0136]

[0129] FIG. 6 shows a block diagram 600 of a device 605 that supports type 1 codebook construction with multiple aggregation factors, according to an aspect of the present disclosure. Device 605 may be an example of an aspect of UE115 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 communicate with each other (e.g., via one or more buses).

[0137]

[0130] The receiver 610 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to type 1 codebook construction by a plurality of aggregation factors, etc.). The information can be passed to other components of the device 605. The receiver 610 can be an example of an aspect of the transceiver 920 described with reference to FIG. 9. The receiver 610 can utilize a single antenna or a set of antennas.

[0138]

[0131] The communication manager 615 can determine that the base station has scheduled the UE for one or more downlink transmissions, and each of the one or more downlink transmissions has an associated repetition factor corresponding to one of a set of configured repetition factors configured in the UE. The communication manager 615 can identify an applicable repetition factor for use in generating a feedback codebook for one or more downlink transmissions, can generate a feedback codebook for reporting feedback for one or more downlink transmissions, and the feedback codebook is populated based on the applicable repetition factor and whether the one or more downlink transmissions are successfully received and decoded. The communication manager 615 can transmit a feedback report including the feedback codebook to the base station. The communication manager 615 can be an example of an aspect of the communication manager 910 described herein.

[0139]

[0132] The communication manager 615, or a subcomponent thereof, can be implemented in hardware, code executed by a processor (e.g., software or firmware), or any combination thereof. When implemented in code executed by a processor, the functions of the communication manager 615, or a subcomponent thereof, can be executed by a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gates or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0140]

[0133] The communication manager 615, or a subcomponent thereof, can be physically located in various positions, including being distributed such that portions of the functionality are implemented in one or more physical components at different physical locations. In some examples, the communication manager 615, or a subcomponent thereof, can be separate and distinct components according to various aspects of this disclosure. In some examples, the communication manager 615, or a subcomponent thereof, can be combined with one or more other hardware components including, but not limited to, input / output (I / O) components, transceivers, network servers, another computing device, one or more other components described in this disclosure, or combinations thereof according to various aspects of this disclosure.

[0141]

[0134] The transmitter 620 can transmit signals generated by other components of the device 605. In some examples, the transmitter 620 can be collocated with the receiver 610 in a transceiver module. For example, the transmitter 620 can be an example of an aspect of the transceiver 920 described with reference to FIG. 9. The transmitter 620 can utilize a single antenna or a set of antennas.

[0142]

[0135] FIG. 7 shows a block diagram 700 of a device 705 that supports construction of a type 1 codebook by a plurality of aggregation factors, according to an aspect of the present disclosure. The device 705 can be an example of an aspect of the device 605 or UE 115 described herein. The device 705 can include a receiver 710, a communication manager 715, and a transmitter 740. The device 705 can also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0143]

[0136] The receiver 710 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to construction of a type 1 codebook by a plurality of aggregation factors). The information can be passed to other components of the device 705. The receiver 710 can be an example of an aspect of the transceiver 920 described with reference to FIG. 9. The receiver 710 can utilize a single antenna or a set of antennas.

[0144]

[0137] The communication manager 715 can be an example of an aspect of the communication manager 615 described herein. The communication manager 715 can include a scheduling manager 720, an applicable repetition factor manager 725, a feedback codebook manager 730, and a feedback reporting manager 735. The communication manager 715 can be an example of an aspect of the communication manager 910 described herein.

[0145]

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

[0146]

[0139] The applicable repetition factor manager 725 can identify an applicable repetition factor for use in generating a feedback codebook for one or more downlink transmissions.

[0147]

[0140] The feedback codebook manager 730 can generate a feedback codebook for reporting feedback for one or more downlink transmissions, and the feedback codebook is populated based on the applicable repetition factor and whether one or more downlink transmissions were successfully received and decoded.

[0148]

[0141] The feedback reporting manager 735 can send a feedback report including the feedback codebook to the base station.

[0149]

[0142] The transmitter 740 can transmit signals generated by other components of the device 705. In some examples, the transmitter 740 can be collocated with the receiver 710 in a transceiver module. For example, the transmitter 740 can be an example of an aspect of the transceiver 920 described with reference to FIG. 9. The transmitter 740 can utilize a single antenna or a set of antennas.

[0150]

[0143] FIG. 8 shows a block diagram 800 of a communication manager 805 that supports Type 1 codebook construction by multiple aggregation factors according to an aspect of the present disclosure. The communication manager 805 can be an example of the aspect of the communication manager 615, the communication manager 715, or the communication manager 910 described herein. The communication manager 805 can include a scheduling manager 810, an applicable repetition factor manager 815, a feedback codebook manager 820, a feedback reporting manager 825, a configured repetition factor manager 830, a set repetition factor manager 835, a drop transmission manager 840, and a slot offset manager 845. Each of these modules can communicate with each other directly or indirectly (e.g., via one or more buses).

[0151]

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

[0152]

[0145] The scheduling manager 810 can receive the configuration of a plurality of SPS configurations, and each of the one or more downlink transmissions is related to a common SPS configuration or a different SPS configuration among the plurality of SPS configurations.

[0153]

[0146] The applicable repetition factor manager 815 can identify an applicable repetition factor for use in generating a feedback codebook for one or more downlink transmissions.

[0154]

[0147] The feedback codebook manager 820 may generate a feedback codebook for reporting feedback regarding one or more downlink transmissions, and the feedback codebook is populated based on an applied repetition factor and whether one or more downlink transmissions are successfully received and decoded.

[0155]

[0148] In some cases, the feedback codebook is generated regardless of the downlink control information related to one or more downlink transmissions.

[0156]

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

[0157]

[0150] The configured repetition factor manager 830 may identify an applied repetition factor based on the maximum number of configured repetition factors from a set of configured repetition factors. In some examples, the configured repetition factor manager 830 may identify the maximum number of configured repetition factors without counting the configured repetition factors corresponding to inactive SPS configurations. In some examples, the configured repetition factor manager 830 may identify the maximum number of configured repetition factors by counting 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 the feedback codebook based on the last instance of each downlink transmission that was actually received and decoded.

[0158]

[0151] For each of one or more downlink transmissions, the drop transmission manager 840 may determine that one or more instances of the downlink transmission have been dropped. In some examples, the drop transmission manager 840 may generate a feedback codebook differently for one or more instances of the dropped downlink transmission and one or more instances of the non-dropped downlink transmission. In some examples, the drop transmission manager 840 may generate an ACK / NACK indication for each actually received and decoded downlink transmission. In some examples, the drop transmission manager 840 may refrain from generating an ACK / NACK indication for each instance of the dropped downlink transmission.

[0159]

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

[0160]

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

[0161]

[0154] FIG. 9 shows a diagram of a system 900 including a device 905 that supports type 1 codebook construction with multiple aggregation factors, according to an aspect of the present disclosure. The device 905 may be an example of, or include, components of the device 605, the device 705, or the UE 115 described herein. The device 905 may include components for transmitting and receiving communication, including components for bi-directional voice and data communication, 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 communicate electronically via one or more buses (e.g., bus 945).

[0162]

[0155] The communication manager 910 may determine that the base station has scheduled the UE for one or more downlink transmissions, and each of the one or more downlink transmissions has an associated repetition factor corresponding to one of a set of configured repetition factors configured in the UE. The communication manager 910 may identify an applicable repetition factor for use in generating a feedback codebook for the one or more downlink transmissions, may generate a feedback codebook for reporting feedback for the one or more downlink transmissions, and the feedback codebook is populated based on the applicable repetition factor and whether the one or more downlink transmissions have been successfully received and decoded. The communication manager 910 may transmit a feedback report including the feedback codebook to the base station.

[0163]

[0156] The I / O controller 915 may manage input and output signals for the device 905. The I / O controller 915 may also manage peripheral devices not incorporated in 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 iOS (registered trademark), ANDROID (registered trademark), MS-DOS (registered trademark), MS-WINDOWS (registered trademark), OS / 2 (registered trademark), UNIX (registered trademark), LINUX (registered trademark), 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, the user may interact with the device 905 via the I / O controller 915 or via hardware components controlled by the I / O controller 915.

[0164]

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

[0165]

[0158] In some cases, the wireless device can include a single antenna 925. However, in some cases, the device can have multiple antennas 925, and these antennas can be capable of simultaneously transmitting or receiving multiple wireless transmissions.

[0166]

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

[0167]

[0160] Processor 940 may include an intelligent hardware device (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 incorporated into processor 940. Processor 940 may be configured to execute computer-readable instructions stored in a memory (e.g., memory 930) to cause the device 905 to perform various functions (e.g., functions or tasks that support the construction of a type 1 codebook by a plurality of aggregation factors).

[0168]

[0161] Code 935 may include instructions for implementing aspects of the present disclosure, including instructions for supporting wireless communication. Code 935 may be stored on 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 to perform the functions described herein (e.g., when compiled and executed).

[0169]

[0162] FIG. 10 shows a block diagram 1000 of a device 1005 that supports the construction of a type 1 codebook by a plurality of aggregation factors, according to an aspect of the present disclosure. Device 1005 may be an example of an aspect of base station 105 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 communicate with each other (e.g., via one or more buses).

[0170]

[0163] The receiver 1010 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to type 1 codebook construction by a plurality of aggregation factors, etc.). The information can be passed to other components of the device 1005. The receiver 1010 can be an example of an aspect of the transceiver 1320 described with reference to FIG. 13. The receiver 1010 can utilize a single antenna or a set of antennas.

[0171]

[0164] The communication manager 1015 can schedule the UE for one or more downlink transmissions, and each of the one or more downlink transmissions has an associated repetition factor corresponding to one of a set of configured repetition factors configured in the UE. The communication manager 1015 can identify an applicable repetition factor for the UE to apply for feedback codebook generation for one or more downlink transmissions, can receive a feedback report from the UE including the feedback codebook, and the feedback codebook is generated to report feedback for one or more downlink transmissions and is populated based on the applicable repetition factor and whether one or more downlink transmissions are successfully received and decoded by the UE. The communication manager 1015 can be an example of an aspect of the communication manager 1310 described herein.

[0172]

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

[0173]

[0166] The communication manager 1015, or sub-components thereof, can be physically located in various positions, including being distributed such that functional parts are implemented by one or more physical components at different physical locations. In some examples, the communication manager 915, or sub-components thereof, can be distinct and separate components according to various aspects of the present disclosure. In some examples, the communication manager 915, or sub-components thereof, can 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 the present disclosure, or combinations thereof, according to various aspects of the present disclosure.

[0174]

[0167] The transmitter 1020 can transmit signals generated by other components of the device 1005. In some examples, the transmitter 1020 can be collocated with the receiver 1010 in a transceiver module. For example, the transmitter 1020 can be an example of an aspect of the transceiver 1320 described with reference to FIG. 13. The transmitter 1020 can utilize a single antenna or a set of antennas.

[0175]

[0168] FIG. 11 shows a block diagram 1100 of a device 1105 that supports type 1 codebook construction by multiple aggregation factors, according to an aspect of the present disclosure. The device 1105 can be an example of an aspect of the device 1005 or the base station 105 described herein. The device 1105 can include a receiver 1110, a communication manager 1115, and a transmitter 1135. The device 1105 can also include a processor. Each of these components can communicate with each other (e.g., via one or more buses).

[0176]

[0169] The receiver 1110 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to type 1 codebook construction by multiple aggregation factors, etc.). The information can be passed to other components of the device 1105. The receiver 1110 can be an example of the aspect of the transceiver 1320 described with reference to FIG. 13. The receiver 1110 can utilize a single antenna or a set of antennas.

[0177]

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

[0178]

[0171] The scheduling manager 1120 can schedule the UE for one or more downlink transmissions, and each of the one or more downlink transmissions has an associated repetition factor corresponding to one of a set of configured repetition factors configured in the UE.

[0179]

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

[0180]

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

[0181]

[0174] The transmitter 1135 may transmit signals generated by other components of the device 1105. In some examples, the transmitter 1135 may be collocated with the receiver 1110 in a transceiver module. For example, the transmitter 1135 may be an example of an aspect of the transceiver 1320 described with reference to FIG. 13. The transmitter 1135 may utilize a single antenna or a set of antennas.

[0182]

[0175] FIG. 12 shows a block diagram 1200 of a communication manager 1205 that supports type 1 codebook construction by a plurality of aggregation factors, according to an aspect of the present disclosure. The communication manager 1205 may be an example of an aspect 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 reporting manager 1220, a configured repetition factor manager 1225, a set repetition factor manager 1230, a dropped transmission manager 1235, and a feedback codebook manager 1240. Each of these modules may communicate with each other directly or indirectly (e.g., via one or more buses).

[0183]

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

[0184]

[0177] The scheduling manager 1210 may transmit configurations of a plurality of SPS configurations, and each downlink transmission of the one or more downlink transmissions is related to a common SPS configuration or a different SPS configuration among the plurality of SPS configurations.

[0185] The applicable repetition factor manager 1215 can identify an applicable repetition factor for a UE to apply for feedback codebook generation for one or more downlink transmissions.

[0186]

[0179] The feedback reporting manager 1220 can receive a feedback report including a feedback codebook from the UE. The feedback codebook is generated to report feedback for one or more downlink transmissions and is populated based on the applicable repetition factor and whether one or more downlink transmissions are successfully received and decoded by the UE.

[0187]

[0180] The configured repetition factor manager 1225 can identify an applicable repetition factor based on the maximum number of configured repetition factors from a set of configured repetition factors. In some examples, the configured repetition factor manager 1225 can identify the maximum number of configured repetition factors without counting the configured repetition factors corresponding to inactive SPS configurations of the UE. In some examples, the configured repetition factor manager 1225 can identify the maximum number of configured repetition factors by counting the configured repetition factors corresponding to both active and inactive SPS configurations of the UE.

[0188]

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

[0189]

[0182] For each of one or more downlink transmissions, the drop transmission manager 1235 may determine that one or more instances of the downlink transmission have been dropped, and the feedback codebook is generated differently for one or more instances of the dropped downlink transmission and one or more instances of the non-dropped downlink transmission. In some cases, the feedback codebook is generated based on the fact that an ACK / NACK indication is generated for each downlink transmission actually received and decoded by the UE, and no ACK / NACK indication is generated for each instance of the dropped downlink transmission opportunity.

[0190]

[0183] The feedback codebook manager 1240 may monitor, control, or otherwise manage the manner of the feedback codebook generated regardless of the downlink control information related to one or more downlink transmissions. In some cases, the UE is composed of a set of reporting offset values for transmitting a feedback report to the base station, each of the set of reporting offset values represents the number of slots after the last nominal downlink transmission, the set of reporting offset values spans an evaluation window, and the feedback codebook is generated based on the UE evaluating each of the set of reporting offset values within the evaluation window.

[0191]

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

[0192] [

[0185] ]FIG. 13 shows a diagram of a system 1300 including a device 1305 that supports construction of a type 1 codebook by a plurality of aggregation factors according to an aspect of the present disclosure. The device 1305 may be an example of or include components of the device 1005, the device 1105, or the base station 105 described herein. The device 1305 may include components for transmitting and receiving communication, including components for bi-directional voice and data communication, including a communication manager 1210, 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 communicate electronically via one or more buses (e.g., bus 1350).

[0193] [

[0186] ]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 a set of configured repetition factors configured in the UE. The communication manager 1310 may identify an applied repetition factor for the UE to apply for feedback codebook generation for one or more downlink transmissions, may receive a feedback report including a feedback codebook from the UE, the feedback codebook being generated to report feedback for one or more downlink transmissions and being populated based on the applied repetition factor and whether one or more downlink transmissions were successfully received and decoded by the UE.

[0194] [

[0187] ]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 transfer of data communication for client devices such as one or more UEs 115.

[0195]

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

[0196]

[0189] In some cases, the wireless device can include a single antenna 1325. However, in some cases, the device can have two or more antennas 1325 that can concurrently transmit or receive multiple wireless transmissions.

[0197]

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

[0198]

[0191] Processor 1340 may include an intelligent hardware device (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 1340 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1340. 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., functions or tasks that support the construction of a type 1 codebook by a plurality of aggregation factors).

[0199]

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

[0200]

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

[0201] [

[0194] ]FIG. 14 shows a flowchart of a method 1400 that supports Type 1 codebook construction by a plurality of aggregation factors, according to an aspect of the present disclosure. The operations of method 1400 may be implemented by UE 115 or components thereof described herein. For example, the operations of method 1400 may be performed by the communication manager described with reference to FIGS. 6-9. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0202] [

[0195] ]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 in the UE. The operation at 1405 may be performed according to the methods described herein. In some examples, aspects of the operation at 1405 may be performed by the scheduling manager described with reference to FIGS. 6-9.

[0203] [

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

[0204]

[0197] At 1415, the UE may generate a feedback codebook for reporting feedback on one or more downlink transmissions, and the feedback codebook may be populated based on an applicable repetition factor and whether one or more downlink transmissions were 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 the feedback codebook manager described with reference to FIGS. 6-9.

[0205]

[0198] 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 the feedback report manager described with reference to FIGS. 6-9.

[0206]

[0199] FIG. 15 shows a flowchart illustrating a method 1500 for supporting type 1 codebook construction with multiple aggregation factors, according to an aspect of the present disclosure. The operations of method 1500 may be implemented by the UE 115 or components thereof described herein. For example, the operations of method 1500 may be performed by the communication manager described with reference to FIGS. 6-9. In some examples, the UE may execute a set of instructions for controlling the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to perform aspects of the functions described below.

[0207]

[0200] At 1505, the UE may determine that the base station has scheduled the UE for one or more downlink transmissions, and each of the one or more downlink transmissions has 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 method described herein. In some examples, the operation mode of 1505 may be performed by the scheduling manager described with reference to FIGS. 6-9.

[0208]

[0201] At 1510, the UE may identify an applicable repetition factor for use in generating a feedback codebook for one or more downlink transmissions. The operation of 1510 may be performed according to the method described herein. In some examples, the operation mode of 1510 may be performed by the applicable repetition factor manager described with reference to FIGS. 6-9.

[0209]

[0202] At 1515, the UE may identify an applicable repetition factor based on the maximum number of configured repetition factors from the set of configured repetition factors. The operation of 1515 may be performed according to the method described herein. In some examples, the operation mode of 1515 may be performed by the configured repetition factor manager described with reference to FIGS. 6-9.

[0210]

[0203] At 1520, the UE may generate a feedback codebook for reporting feedback for one or more downlink transmissions, and the feedback codebook is populated based on the applicable repetition factor and whether the one or more downlink transmissions were successfully received and decoded. The operation of 1520 may be performed according to the method described herein. In some examples, the operation mode of 1520 may be performed by the feedback codebook manager described with reference to FIGS. 6-9.

[0211]

[0204] At 1525, the UE may send a feedback report including a feedback codebook to the base station. The operation of 1525 may be implemented according to the method described herein. In some examples, the manner of operation of 1525 may be implemented by the feedback report manager described with reference to FIGS. 6-9.

[0212]

[0205] FIG. 16 shows a flowchart illustrating a method 1600 for supporting Type 1 codebook construction with multiple aggregation factors, according to an aspect of the present disclosure. The operations of method 1600 may be implemented by the UE 115 or components thereof described herein. For example, the operations of method 1600 may be implemented by the communication manager described with reference to FIGS. 6-9. In some examples, the UE may execute a set of instructions to control the functional elements of the UE to perform the functions described below. Additionally or alternatively, the UE may use dedicated hardware to implement aspects of the functions described below.

[0213]

[0206] 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 a set of configured repetition factors configured at the UE. The operation of 1605 may be implemented according to the method described herein. In some examples, the manner of operation of 1605 may be implemented by the scheduling manager described with reference to FIGS. 6-9.

[0214]

[0207] At 1610, the UE may identify an applicable repetition factor to apply for feedback codebook generation for one or more downlink transmissions. The operation of 1610 may be implemented according to the method described herein. In some examples, the manner of operation of 1610 may be implemented by the applicable repetition factor manager described with reference to FIGS. 6-9.

[0215]

[0208] At 1615, the UE may identify with an application repetition factor of 1. The operation of 1615 may be implemented according to the method described in this specification. In some examples, the operation mode of 1615 may be implemented by the configured repetition factor manager described with reference to FIGS. 6-9.

[0216]

[0209] At 1620, the UE may generate a feedback codebook for reporting feedback on one or more downlink transmissions, and the feedback codebook is populated based on the applicable repetition factor and whether one or more downlink transmissions are successfully received and decoded. The operation of 1620 may be implemented according to the method described in this specification. In some examples, the operation mode of 1620 may be implemented by the feedback codebook manager described with reference to FIGS. 6-9.

[0217]

[0210] At 1625, the UE may generate a feedback codebook based on the last instance of each actually received and decoded downlink transmission. The operation of 1625 may be implemented according to the method described in this specification. In some examples, the operation mode of 1625 may be implemented by the configured repetition factor manager described with reference to FIGS. 6-9.

[0218]

[0211] At 1630, the UE may transmit a feedback report including the feedback codebook to the base station. The operation of 1630 may be implemented according to the method described in this specification. In some examples, the operation mode of 1630 may be implemented by the feedback report manager described with reference to FIGS. 6-9.

[0219] [

[0212] ]FIG. 17 shows a flowchart illustrating a method 1700 for supporting type 1 codebook construction by a plurality of aggregation factors according to an aspect of the present disclosure. The operations of method 1700 may be implemented by the base station 105 described herein or components thereof. For example, the operations of method 1700 may be performed by the communication manager described with reference to FIGS. 10 - 13. In some examples, the base station may execute a set of instructions for controlling the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0220] [

[0213] ]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 in the UE. The operation at 1705 may be performed according to the methods described herein. In some examples, aspects of the operation at 1705 may be performed by the scheduling manager described with reference to FIGS. 10 - 13.

[0221] [

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

[0222]

[0215] At 1715, the base station may receive from the UE a feedback report including a feedback codebook, where the feedback codebook is generated to report feedback for one or more downlink transmissions and is populated based on an application repetition factor and whether one or more downlink transmissions are successfully received and decoded by the UE. The operation of 1715 may be implemented according to the methods described herein. In some examples, aspects of the operation of 1715 may be implemented by the feedback report manager described with reference to FIGS. 10 - 13.

[0223]

[0216] FIG. 18 shows a flowchart illustrating a method 1800 for supporting type 1 codebook construction with multiple aggregation factors, according to an aspect of the present disclosure. The operations of method 1800 may be implemented by the base station 105 or components thereof described herein. For example, the operations of method 1800 may be implemented by the communication manager described with reference to FIGS. 10 - 13. In some examples, the base station may execute a set of instructions to control the functional elements of the base station to perform the functions described below. Additionally or alternatively, the base station may use dedicated hardware to perform aspects of the functions described below.

[0224]

[0217] At 1805, the base station may schedule the UE for one or more downlink transmissions, where each of the one or more downlink transmissions has an associated repetition factor corresponding to one of a set of configured repetition factors configured in the UE. The operation of 1805 may be implemented according to the methods described herein. In some examples, aspects of the operation of 1805 may be implemented by the scheduling manager described with reference to FIGS. 10 - 13.

[0225]

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

[0226]

[0219] At 1815, the base station may receive a feedback report including a feedback codebook from the UE, where the feedback codebook is generated to report feedback for one or more downlink transmissions and is populated based on the application repetition factor and whether one or more instances of the one or more downlink transmissions are successfully received and decoded by the UE. The operation of 1815 may be implemented according to the methods described herein. In some examples, aspects of the operation of 1815 may be implemented by the feedback report manager described with reference to FIGS. 10-13.

[0227]

[0220] At 1820, for each of one or more downlink transmissions, the base station may determine that one or more instances of the downlink transmission have been dropped, and the feedback codebook is generated to be different for one or more instances of the dropped downlink transmission and one or more instances of the non-dropped downlink transmission. The operation of 1820 may be implemented according to the methods described herein. In some examples, aspects of the operation of 1820 may be implemented by the dropped transmission manager described with reference to FIGS. 10-13.

[0228]

[0221] Note that the methods described herein represent possible implementations, and that operations and steps may be reordered or otherwise modified in some cases, and that other implementations are possible. Additionally, aspects from two or more of the methods may be combined.

[0229]

[0222] The following provides an overview of aspects of the present disclosure.

[0230]

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

[0231]

[0224] Aspect 2: The method of aspect 1, further comprising identifying the applicable repetition factor based at least in part on a maximum number of configured repetition factors from the plurality of configured repetition factors.

[0232]

[0225] Aspect 3: The method of aspect 2, further comprising identifying the maximum number of configured repetition factors without counting configured repetition factors corresponding to inactive SPS configurations.

[0233]

[0226] Aspect 4: The method according to any one of aspects 2 to 3, further comprising identifying the maximum number of configured repetition factors by counting configured repetition factors corresponding to both active and inactive SPS configurations.

[0234] Aspect 5: The method according to any one of Aspects 1 to 4, further comprising identifying with an applicable repetition factor of 1 and generating a feedback codebook at least partially based on the last instance of each downlink transmission actually received and decoded.

[0235] Aspect 6: The method according to any one of Aspects 1 to 5, further comprising, for each of one or more downlink transmissions, determining that one or more instances of the downlink transmission have been dropped and generating a feedback codebook such that it is different between the one or more instances of the dropped downlink transmission and the one or more instances of the non-dropped downlink transmission.

[0236] Aspect 7: The method according to Aspect 6, wherein generating the feedback codebook further comprises generating an ACK / NACK indication for each downlink transmission actually received and decoded and refraining from generating an ACK / NACK indication for each instance of the dropped downlink transmission opportunity.

[0237] Aspect 8: The method according to any one of Aspects 1 to 7, further comprising receiving a configuration of a plurality of SPS configurations, wherein each downlink transmission among the one or more downlink transmissions is related to a common SPS configuration or different SPS configurations among the plurality of SPS configurations.

[0238] Aspect 9: The method according to any one of Aspects 1 to 8, wherein the feedback codebook is generated regardless of the DCI related to one or more downlink transmissions.

[0239] Aspect 10: The method according to any one of Aspects 1 to 9, wherein the UE is composed of a plurality of reporting offset values for transmitting a feedback report to the base station, each of the plurality of reporting offset values represents the number of slots after the last nominal downlink transmission, the plurality of reporting offset values span an evaluation window, and the method further comprises generating a feedback codebook at least partially based on evaluating each of the plurality of reporting offset values within the evaluation window.

[0240] Aspect 11: The method according to any one of Aspects 1 to 10, wherein the feedback codebook comprises a type 1 codebook.

[0241] 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 an applicable repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions, receiving a feedback report from the UE including the feedback codebook, and the feedback codebook being generated to report feedback for the one or more downlink transmissions and being populated at least partially based on whether the applicable repetition factor and the one or more downlink transmissions are successfully received and decoded by the UE.

[0242] Aspect 13: The method according to Aspect 12, further comprising identifying the applicable repetition factor at least partially based on the maximum number of configured repetition factors from the plurality of configured repetition factors.

[0243] Aspect 14: The method according to Aspect 13, further comprising identifying the maximum number of configured repetition factors without counting the configured repetition factors corresponding to the inactive SPS configuration of the UE.

[0244]

[0237] Aspect 15: The method according to any one of Aspects 13 to 14, further comprising identifying the maximum number of configured repetition factors by counting the configured repetition factors corresponding to both the active SPS configuration and the non-active SPS configuration of the UE.

[0245]

[0238] Aspect 16: The method according to any one of Aspects 12 to 15, further comprising identifying the applicable repetition factor as 1, and the feedback codebook is generated at least partially based on the last instance of each downlink transmission actually received and decoded.

[0246]

[0239] Aspect 17: The method according to Aspect 16, further comprising scheduling at least one non-conflicting instance of a downlink transmission between evaluation windows based at least in part on a reporting offset value based at least in part on a plurality of configured repetition factors.

[0247]

[0240] Aspect 18: The method according to any one of Aspects 12 to 17, further comprising determining for each of one or more downlink transmissions that one or more instances of the downlink transmission have been dropped, and the feedback codebook is generated to be different between one or more instances of the dropped downlink transmission and one or more instances of the non-dropped downlink transmission.

[0248]

[0241] Aspect 19: The method according to Aspect 18, wherein the feedback codebook is generated at least partially based on that an ACK / NACK indication is generated for each downlink transmission actually received and decoded by the UE, and no ACK / NACK indication is generated for each instance of the dropped downlink transmission opportunity.

[0249]

[0242] Aspect 20: A method according to any of aspects 12 to 19, further comprising transmitting configurations 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 with a different SPS configuration among the plurality of SPS configurations.

[0250]

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

[0251]

[0244] Aspect 22: A method according to any of aspects 12 to 21, wherein the UE is configured with multiple reporting offset values for sending feedback reports to the base station, each of the multiple reporting offset values representing a number of slots after the last nominal downlink transmission, the multiple 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 multiple reporting offset values within the evaluation window.

[0252]

[0245] Aspect 23: The method of any one of aspects 12 to 22, wherein the feedback codebook comprises a type-1 codebook.

[0253]

[0246] Aspect 24: An apparatus for wireless communication in 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 a method described in any of aspects 1 to 11.

[0254]

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

[0255] Aspect 26: A non-transitory computer-readable medium storing code for wireless communication in a UE, the code comprising instructions executable by a processor to implement the method according to any of Aspects 1 to 11.

[0256] Aspect 27: An apparatus for wireless communication in a base station, the apparatus 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 implement the method according to any of Aspects 12 to 23.

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

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

[0259] Aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described by way of example, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, but the techniques described herein are applicable beyond LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to various other wireless communication systems such as Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Flash OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0260]

[0253] The information and signals described in this specification can be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the description can be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0261]

[0254] The various exemplary blocks and components described in connection with the disclosure of this specification can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA, or other programmable logic device, discrete gates 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 cooperating with a DSP core, or any other such configuration).

[0262]

[0255] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. When implemented in software executed by a processor, the functions can be stored on a computer-readable medium as one or more instructions or code, or transmitted on a computer-readable medium. Other examples and implementations fall within the scope of the present disclosure and the scope of the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. 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.

[0263]

[0256] A computer-readable medium includes both a non-transitory computer storage medium and a communication medium including any medium that facilitates transfer of a computer program from one location to another. The 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, the non-transitory computer-readable medium can include RAM, ROM, electrically erasable programmable ROM (EEPROM (registered trademark)), flash memory, compact disc (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code means in the form of instructions or data structures and that can be accessed by a general purpose or special purpose computer, or a general purpose or special purpose processor. Also, any connection is properly termed a computer-readable medium. For example, if software is transmitted from a website, 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, 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 (registered trademark) (disc), optical disc (disc), digital versatile disc (disc) (DVD), floppy (registered trademark) disk (disk) and Blu-ray (registered trademark) disc (disc), where disk typically magnetically reproduces data and disc optically reproduces data with a laser. Combinations of the above are also included within the scope of computer-readable medium.

[0264] As used herein, including within the scope of the claims, the "or" used in a listing of items (e.g., a listing of items ending with phrases such as "at least one of" or "one or more of") indicates an inclusive listing such that, for example, a 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). Also, the phrase "based on" as used herein is not to be construed as a reference to a closed set of conditions. For example, an exemplary step described as "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, the phrase "based on" as used herein is to be construed in the same manner as the phrase "at least partially based on".

[0265]

[0258] In the accompanying drawings, similar components or features may have the same reference labels. Further, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes the similar components. If only the first reference label is used herein, the description applies to any of the similar components having the same first reference label regardless of the second reference label or any other subsequent reference labels.

[0266]

[0259] The descriptions provided herein with respect to the accompanying drawings describe exemplary configurations and do not necessarily represent all examples that may be implemented or fall within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" and does not mean "preferred" or "advantageous over other examples". The detailed description includes specific details to provide an understanding of the techniques described. However, these techniques 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 examples being described.

[0267]

[0260] The description in this specification is provided so that those skilled in the art can make or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Accordingly, the present disclosure should not be limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein. The invention described in the claims of the present application at the time of filing is appended below. [C1] A method for wireless communication in a user equipment (UE), comprising: determining that a base station schedules 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 in the UE; identifying an applied repetition factor for use in generating a feedback codebook 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 at least in part on the applied repetition factor and whether the one or more downlink transmissions are successfully received and decoded; transmitting a feedback report including the feedback codebook to the base station; A method comprising the steps of: [C2] The method of C1, further comprising identifying the applied repetition factor based at least in part on a maximum number of configured repetition factors from the plurality of configured repetition factors. [C3] The method of C2, further comprising identifying the maximum number of configured repetition factors without counting configured repetition factors corresponding to an inactive semi-persistent scheduling (SPS) configuration. [C4] The method of C2, further comprising identifying the maximum number of configured repetition factors by counting configured repetition factors corresponding to both an active semi-persistent scheduling (SPS) configuration and an inactive SPS configuration. [C5] The method of C1, further comprising identifying the applied repetition factor as 1, and generating the feedback codebook based at least in part on a last instance of each actually received and decoded downlink transmission. A method according to C1, further comprising the steps of: [C6] For each of the one or more downlink transmissions, determining that one or more instances of the downlink transmission have been dropped; Generating the feedback codebook such that the one or more instances of the dropped downlink transmission are different from the one or more instances of the downlink transmission that are not dropped; The method according to C1, further comprising. [C7] Generating the feedback codebook comprises: Generating an acknowledgement / negative acknowledgement (ACK / NACK) indication for each actually received and decoded downlink transmission; Refraining from generating an ACK / NACK indication for each instance of a dropped downlink transmission opportunity; The method according to C6, further comprising. [C8] Further comprising receiving a configuration of a plurality of semi-persistent scheduling (SPS) configurations, wherein each downlink transmission 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, the method according to C1. [C9] The feedback codebook is generated regardless of downlink control information related to the one or more downlink transmissions, the method according to C1. [C10] The UE is composed of 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 slots after the last nominal downlink transmission, the plurality of reporting offset values span an evaluation window, and the method The method according to C1, further comprising generating the feedback codebook at least partially based on evaluating each of the plurality of reporting offset values within the evaluation window. [C11] The feedback codebook comprises a type 1 codebook, the method according to C1. [C12] A method for wireless communication at a base station, 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 in the UE, and identifying an applied repetition factor for the UE to apply for feedback codebook generation for the one or more downlink transmissions Receiving 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 at least in part on whether the applied repetition factor and the one or more downlink transmissions were successfully received and decoded by the UE A method comprising. [C13] The method according to C12, further comprising identifying the applied repetition factor based at least in part on a maximum number of configured repetition factors from the plurality of configured repetition factors [C14] The method according to C13, further comprising identifying the maximum number of configured repetition factors without counting configured repetition factors corresponding to an inactive semi-persistent scheduling (SPS) configuration of the UE [C15] The method according to C13, further comprising identifying the maximum number of configured repetition factors by counting configured repetition factors corresponding to both an active and an inactive SPS configuration of the UE [C16] The method according to C12, further comprising identifying the applied repetition factor as 1, the feedback codebook being generated based at least in part on a last instance of each actually received and decoded downlink transmission [C17] The method according to C16, 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 based at least in part on the plurality of configured repetition factors [C18] The method according to C12, further comprising, for each of the one or more downlink transmissions, determining that one or more instances of the downlink transmission have been dropped, wherein the feedback codebook is generated to be different between the one or more instances of the downlink transmission that have been dropped and the one or more instances of the downlink transmission that have not been dropped. [C19] The method according to C18, wherein the feedback codebook is generated based at least in part on that an acknowledgement / negative acknowledgement (ACK / NACK) indication is generated for each downlink transmission actually received and decoded by the UE, and no ACK / NACK indication is generated for each instance of the dropped downlink transmission opportunity. [C20] The method according to C12, further comprising transmitting a configuration of a plurality of semi-persistent scheduling (SPS) configurations, wherein each of the one or more downlink transmissions is related to a common SPS configuration or different SPS configurations among the plurality of SPS configurations. [C21] The method according to C12, wherein the feedback codebook is generated regardless of the downlink control information related to the one or more downlink transmissions. [C22] The UE is composed of 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 slots after the last nominal downlink transmission, the plurality of reporting offset values span an evaluation window, and the feedback codebook is generated based at least in part on the UE evaluating each of the plurality of reporting offset values within the evaluation window. The method according to C12. [C23] The method according to C12, wherein the feedback codebook comprises a type 1 codebook. [C24] An apparatus for wireless communication in a user equipment (UE), 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 plurality of configured repetition factors configured in the UE, Means for identifying an application repetition factor for use in generating a feedback codebook 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 based at least in part on the application repetition factor and whether the one or more downlink transmissions were successfully received and decoded; Means for transmitting a feedback report including the feedback codebook to the base station; An apparatus comprising the above. [C25] The apparatus according to C24, further comprising means for identifying the application repetition factor based at least in part on a maximum number of configured repetition factors from the plurality of configured repetition factors. [C26] The apparatus according to C25, further comprising means for identifying the maximum number of configured repetition factors without counting configured repetition factors corresponding to an inactive semi-persistent scheduling (SPS) configuration. [C27] The apparatus according to C25, further comprising means for identifying the maximum number of configured repetition factors by counting configured repetition factors corresponding to both an active semi-persistent scheduling (SPS) configuration and an inactive SPS configuration. [C28] Means for identifying the application repetition factor as 1; Means for generating the feedback codebook based at least in part on a last instance of each downlink transmission that was actually received and decoded; The apparatus according to C24, further comprising the above. [C29] For each of the one or more downlink transmissions, means for determining that one or more instances of the downlink transmission were dropped; Means for generating the feedback codebook such that it is different for the one or more instances of the downlink transmission that were dropped and the one or more instances of the downlink transmission that were not dropped; The apparatus according to C24, further comprising the above. [C30] The means for generating the feedback codebook is Means for generating an acknowledgement / negative acknowledgement (ACK / NACK) indication for each downlink transmission actually received and decoded; Means for refraining from generating an ACK / NACK indication for each instance of a dropped downlink transmission opportunity; The apparatus according to C29, further comprising. [C31] The apparatus according to C24, further comprising means for receiving 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 different SPS configurations among the plurality of SPS configurations. [C32] The apparatus according to C24, wherein the feedback codebook is generated regardless of downlink control information related to the one or more downlink transmissions. [C33] The UE is composed of 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 slots after the last nominal downlink transmission, and the plurality of reporting offset values span an evaluation window. The apparatus The apparatus according to C24, further comprising means for generating the feedback codebook based at least in part on evaluating each of the plurality of reporting offset values within the evaluation window. The apparatus according to C24. [C34] The apparatus according to C24, wherein the feedback codebook comprises a type 1 codebook. [C35] An apparatus for wireless communication at a base station, 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 in the UE; Means for identifying an applicable repetition factor for application by the UE to feedback codebook generation for the one or more downlink transmissions; Means for receiving from the UE a feedback report including a feedback codebook, the feedback codebook being generated for reporting feedback on the one or more downlink transmissions and being populated at least in part based on whether the applied repetition factor and the one or more downlink transmissions were successfully received and decoded by the UE, An apparatus comprising the same. [C36] The apparatus according to C35, further comprising means for identifying the applied repetition factor based at least in part on the maximum number of configured repetition factors from the plurality of configured repetition factors. [C37] The apparatus according to C36, further comprising means for identifying the maximum number of configured repetition factors without counting the configured repetition factors corresponding to an inactive semi-persistent scheduling (SPS) configuration of the UE. [C38] The apparatus according to C36, further comprising means for identifying the maximum number of configured repetition factors by counting the configured repetition factors corresponding to both an active and an inactive SPS configuration of the UE. [C39] The apparatus according to C35, further comprising means for identifying the applied repetition factor as 1, the feedback codebook being generated at least in part based on the last instance of each downlink transmission actually received and decoded. [C40] The apparatus according to C39, further comprising means for 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 based at least in part on the plurality of configured repetition factors. [C41] The apparatus according to C35, further comprising means for determining for each of the one or more downlink transmissions that one or more instances of the downlink transmission have been dropped, the feedback codebook being generated to be different between the one or more instances of the downlink transmission that have been dropped and the one or more instances of the downlink transmission that have not been dropped. [C42] The feedback codebook is generated at least in part based on that an acknowledgement / negative acknowledgement (ACK / NACK) indication is generated for each downlink transmission actually received and decoded by the UE, and no ACK / NACK indication is generated for each instance of a dropped downlink transmission opportunity, the apparatus according to C41. [C43] The apparatus according to C35, further comprising means for 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 different SPS configurations among the plurality of SPS configurations. [C44] The feedback codebook is generated regardless of the downlink control information related to the one or more downlink transmissions, the apparatus according to C35. [C45] The UE is composed of 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 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, the apparatus according to C35. [C46] The feedback codebook comprises a type 1 codebook, the apparatus according to C35. [C47] An apparatus for wireless communication in a user equipment (UE), a processor, a memory coupled to the processor, and instructions stored in the memory, the instructions comprising 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 in the UE, identifying an applicable repetition factor to apply for generating a feedback codebook for the one or more downlink transmissions, Generating a feedback codebook for reporting feedback regarding the one or more downlink transmissions, wherein the feedback codebook is populated based at least in part on the applied repetition factor and whether the one or more downlink transmissions were successfully received and decoded, Transmitting a feedback report including the feedback codebook to the base station, An apparatus executable by a processor to cause the apparatus to perform the above. [C48] An apparatus for wireless communication at a base station, comprising A processor, A memory coupled to the processor, Instructions stored in the memory, the instructions 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 application by the UE to feedback codebook generation for the one or more downlink transmissions, Receiving from the UE a feedback report including a feedback codebook, the feedback codebook being generated for reporting feedback regarding the one or more downlink transmissions and being populated based at least in part on the applied repetition factor and whether the one or more downlink transmissions were successfully received and decoded by the UE, An apparatus executable by a processor to cause the apparatus to perform the above. [C49] A non-transitory computer-readable medium storing code for wireless communication at a user equipment (UE), the code comprising 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 for application to feedback codebook generation for the one or more downlink transmissions, Generating a feedback codebook for reporting feedback regarding the one or more downlink transmissions, wherein the feedback codebook is populated based at least in part on the applied repetition factor and whether the one or more downlink transmissions were successfully received and decoded, Transmitting a feedback report including the feedback codebook to the base station, A non-transitory computer-readable medium comprising instructions executable by a processor for performing the above. [C50] A non-transitory computer-readable medium storing code for wireless communication at a base station, the code 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, Receiving from the UE a feedback report including a feedback codebook, the feedback codebook being generated to report feedback regarding the one or more downlink transmissions and being populated based at least in part on the applied repetition factor and whether the one or more downlink transmissions were successfully received and decoded by the UE, A non-transitory computer-readable medium comprising instructions executable by a processor for performing the above.

Claims

1. A method for wireless communication in a user equipment (UE), comprising: determining that a network device schedules the UE for one or more downlink transmissions, wherein a related repetition factor for each of the one or more downlink transmissions corresponds to one of a plurality of configured repetition factors configured in the UE; identifying an applied repetition factor for applying to generation of a feedback codebook for the one or more downlink transmissions, wherein the applied repetition factor is identified based at least in part on a maximum number of configured repetition factors from the plurality of configured repetition factors; generating a feedback codebook for reporting feedback for the one or more downlink transmissions, wherein the feedback codebook is populated based at least in part on the applied repetition factor and whether the one or more downlink transmissions are successfully received and decoded; transmitting a feedback report including the feedback codebook to the network device; A method comprising the above steps.

2. For each of the one or more downlink transmissions, determining that one or more instances of the downlink transmission are dropped; generating the feedback codebook such that it is different for the one or more instances of the downlink transmission that are dropped and the one or more instances of the downlink transmission that are not dropped; The method according to claim 1, further comprising the above steps.

3. Generating the feedback codebook further comprises: generating an acknowledgement / negative acknowledgement (ACK / NACK) indication for each actually received and decoded downlink transmission; refraining from generating an ACK / NACK indication for each instance of a dropped downlink transmission opportunity; The method according to claim 2, further comprising the above steps.

4. The method according to claim 1, further comprising receiving a configuration of a plurality of semi-persistent scheduling (SPS) configurations, wherein each of the one or more downlink transmissions is related to a common SPS configuration or a different SPS configuration among the plurality of SPS configurations.

5. For the UE, a plurality of reporting offset values are configured for transmitting the feedback report to the network device, each of the plurality of reporting offset values represents the number of slots after the last nominal downlink transmission, and the plurality of reporting offset values span an evaluation window, and the method further comprises: generating the feedback codebook based at least in part on evaluating each of the plurality of reporting offset values within the evaluation window. The method according to claim 1.

6. A method for wireless communication in a network device, comprising: scheduling a user equipment (UE) for one or more downlink transmissions, wherein a related repetition factor for each of the one or more downlink transmissions corresponds to one of a plurality of configured repetition factors configured in the UE; identifying an applicable repetition factor for the UE to apply for feedback codebook generation for the one or more downlink transmissions, wherein the applicable repetition factor is identified based at least in part on the maximum number of configured repetition factors from the plurality of configured repetition factors; receiving from the UE a feedback report including a feedback codebook, wherein the feedback codebook is generated to report feedback for the one or more downlink transmissions and is populated based at least in part on whether the applicable repetition factor and the one or more downlink transmissions are successfully received and decoded by the UE; A method comprising.

7. The method according to claim 1 or 6, further comprising identifying the maximum number of configured repetition factors without counting the configured repetition factors corresponding to inactive semi-persistent scheduling (SPS) configurations of the UE.

8. The method according to claim 1 or 6, further comprising identifying the maximum number of configured repetition factors by counting configured repetition factors corresponding to both the active semi-persistent scheduling (SPS) configuration and the non-active SPS configuration of the UE.

9. The method according to claim 1 or 6, wherein the feedback codebook is generated regardless of the downlink control information related to the one or more downlink transmissions.

10. The method according to claim 1 or 6, wherein the feedback codebook comprises a type 1 codebook.

11. An apparatus for wireless communication in a user equipment (UE), means for determining that a network device has scheduled the UE for one or more downlink transmissions, wherein a respective repetition factor associated with each of the one or more downlink transmissions corresponds to one of a plurality of configured repetition factors configured in the UE, means for identifying an applicable repetition factor for applying to generate a feedback codebook for the one or more downlink transmissions, wherein the applicable repetition factor is identified based at least in part on the maximum number of configured repetition factors from the plurality of configured repetition factors, means for generating a feedback codebook for reporting feedback for the one or more downlink transmissions, wherein the feedback codebook is populated based at least in part on the applicable repetition factor and whether the one or more downlink transmissions are successfully received and decoded, means for transmitting a feedback report including the feedback codebook to the network device, An apparatus comprising.

12. An apparatus for wireless communication in a network device, means for scheduling a user equipment (UE) for one or more downlink transmissions, wherein a respective repetition factor associated with each of the one or more downlink transmissions corresponds to one of a plurality of configured repetition factors configured in the UE, Means for identifying an application repetition factor for the UE to apply to feedback codebook generation for the one or more downlink transmissions, wherein the application repetition factor is identified based at least in part on the maximum number of configured repetition factors from the plurality of configured repetition factors, Means for receiving from the UE a feedback report including a feedback codebook, wherein the feedback codebook is generated to report feedback for the one or more downlink transmissions and is populated based at least in part on whether the application repetition factor and the one or more downlink transmissions were successfully received and decoded by the UE, An apparatus comprising the same.

Images