UCI multiplexing on PUSCH retransmission with multiple codewords

Abstract

This disclosure provides systems, apparatus, apparatuses, and methods, including computer programs encoded on a storage medium, for UCI multiplexing on PUSCH retransmissions. The UE (102) receives (312), from the network entity (104), control signaling that schedules a multi-codeword (PUSCH) retransmission of a PUSCH. The UE (102) sends (316) a UCI multiplexing process based PUSCH retransmission of a multi-codeword PUSCH to the network entity (104). The UCI multiplexing process prevents the UCI from being multiplexed on the disabled codeword (202d) or on the basis of the value of the reserved MCS on the codeword (502a, 803a) having the reserved MCS.

Description

Technical Field

[0001] This disclosure relates generally to wireless communications, and more specifically to uplink control information (UCI) multiplexing on retransmissions of multi-codeword physical uplink shared channel (PUSCH). Background Technology

[0002] The 3rd Generation Partnership Project (3GPP) specifies a radio interface called Fifth Generation (5G) New Radio (NR) (5G NR). The architecture of a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), user equipment (UE), and more. Compared to previous generation cellular communication systems, the 5G NR architecture seeks to provide increased data rates, reduced latency, and / or increased capacity.

[0003] Wireless communication systems typically provide various telecommunications services (e.g., telephone, video, data, messaging, broadcasting, etc.) based on multiple access technologies (such as Orthogonal Frequency Division Multiple Access (OFDMA)) that support communication with multiple UEs. Improvements in mobile broadband have continued the development of such wireless communication technologies. For example, a UE can multiplex uplink control information (UCI) on allocated Physical Uplink Shared Channel (PUSCH) resources, which overlap temporally with the Physical Uplink Control Channel (PUCCH) resources configured for UCI transmission. However, the codewords of a multi-codeword PUSCH can have different characteristics in PUSCH retransmissions than in the initial PUSCH transmission. Summary of the Invention

[0004] The following is a simplified overview of one or more aspects to provide a basic understanding of such aspects. This overview is not a comprehensive summary of all anticipated aspects. It neither identifies key or essential elements of all aspects nor describes the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the more detailed descriptions that follow.

[0005] When a Physical Uplink Shared Channel (PUSCH) resource overlaps temporally with a Physical Uplink Control Channel (PUCCH) resource associated with Uplink Control Information (UCI), a network entity, such as a base station or a base station element, can configure a User Equipment (UE) to transmit UCI on that PUSCH resource. In some examples, the network entity schedules data on the initial PUSCH transmission of a multi-codeword PUSCH. The network entity can also schedule data on PUSCH retransmissions of a multi-codeword PUSCH. For PUSCH retransmissions, the network entity can disable the codewords of the multi-codeword PUSCH or indicate that the codewords of the multi-codeword PUSCH include a reserved modulation and coding scheme (MCS).

[0006] The UE can multiplex the UCI on both the initial PUSCH transmission and PUSCH retransmission of a multi-codeword PUSCH. For example, the UE can multiplex the UCI on the first scheduled codeword of the multi-codeword PUSCH or on the codeword with the highest MCS for the initial PUSCH transmission. However, for PUSCH retransmission, the first scheduled codeword or the codeword with the highest MCS may be disabled. Therefore, multiplexing the UCI on disabled codewords may increase power consumption and / or demodulation reference signal (DMRS) overhead at the UE, as the UE must transmit the DMRS from the port mapped to the disabled codeword. Furthermore, although higher MCS codewords are generally associated with improved channel quality, the UE may default to including codewords with reserved MCS, given that reserved MCS typically have higher index numbers than non-reserved MCS. However, reserved MCS may not always provide better performance than non-reserved MCS.

[0007] This disclosure addresses the aforementioned and other deficiencies by implementing a UCI multiplexing process when codewords for a multi-codeword PUSCH are disabled and / or when the MCS of the codewords for a multi-codeword PUSCH includes a reserved MCS. Specifically, the UCI multiplexing process prevents UCI multiplexing on disabled codewords and / or on codewords with reserved MCSs. Avoiding UCI multiplexing on disabled codewords can improve performance by reducing DMRS overhead. Furthermore, preventing UCI multiplexing from being defaulted to codewords with reserved MCSs instead of codewords including non-reserved MCSs allows the UE to identify codewords that offer better performance for UCI multiplexing.

[0008] According to some aspects, the UE receives control signaling from the network entity to schedule PUSCH retransmissions of multi-codeword PUSCHs. The UE sends PUSCH retransmissions of multi-codeword PUSCHs based on a UCI multiplexing procedure to the network entity. The UCI multiplexing procedure prevents the multiplexing of UCI on disabled codewords or, based on a reserved MCS value, prevents the multiplexing of UCI on codewords with that reserved MCS.

[0009] Depending on several factors, the network entity sends control signaling to the UE to schedule PUSCH retransmissions of multi-codeword PUSCHs. The network entity receives PUSCH retransmissions of multi-codeword PUSCHs from the UE based on a UCI multiplexing procedure. The UCI multiplexing procedure prevents the multiplexing of UCIs on disabled codewords or, based on a reserved MCS value, prevents the multiplexing of UCIs on codewords with that reserved MCS, as described above. Attached Figure Description

[0010] Figure 1 A diagram illustrating a wireless communication system comprising multiple user equipment (UEs) and network entities communicating through one or more cells.

[0011] Figures 2A to 2B This diagram illustrates the association of uplink control information (UCI) multiplexing with the Physical Uplink Shared Channel (PUSCH).

[0012] Figure 3 An example of a signaling diagram for UCI multiplexing on a PUSCH with multiple codeword retransmission is shown.

[0013] Figure 4 A diagram illustrating UCI multiplexing on a codeword that is enabled / scheduled.

[0014] Figure 5 This is an example of UCI multiplexing when a reserved MCS is specified for the codeword.

[0015] Figure 6 This is an example of UCI multiplexing when a reserved MCS is specified for the codeword.

[0016] Figure 7 This diagram illustrates spectral efficiency-based UCI multiplexing when a reserved MCS is specified for the codeword.

[0017] Figure 8 This diagram illustrates the UCI multiplexing on each codeword in a multi-codeword PUSCH retransmission.

[0018] Figure 9 This is a flowchart of the wireless communication method at the UE.

[0019] Figure 10 This is a flowchart of a wireless communication method at a network entity.

[0020] Figure 11 This is a diagram illustrating the hardware implementation of an example UE device.

[0021] Figure 12 It is a diagram illustrating the hardware implementation of one or more example network entities. Detailed Implementation

[0022] Figure 1 Figure 100 illustrates a wireless communication system associated with multiple cells 190. The wireless communication system includes user equipment (UE) 102 and base station / network entity 104. Some base stations may include an aggregated base station architecture, while others may include a decomposed base station architecture. An aggregated base station architecture utilizes a radio protocol stack physically or logically integrated within a single radio access network (RAN) node. A decomposed base station architecture utilizes a protocol stack physically or logically distributed across two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110). For example, CU 110 is implemented within a RAN node, and one or more DU 108s may be located in the same location as CU 110, or alternatively, may be geographically or virtually distributed across one or more other RAN nodes. DU 108 may be implemented to communicate with one or more RU 106s. Any of RU 106, DU 108, and CU 110 can be implemented as a virtual unit, such as a virtual radio unit (VRU), a virtual distributed unit (VDU), or a virtual central unit (VCU). Base station / network entity 104 (e.g., an aggregated base station or a decomposed unit of a base station, such as RU 106 or DU 108) can be referred to as a transmit receiver point (TRP).

[0023] The operation and / or network design of base station 104 can be based on the aggregation characteristics of base station functions. For example, a decomposed base station architecture can be utilized in an Integrated Access Backhaul (IAB) network, an Open Radio Access Network (O-RAN) network, or a Virtual Radio Access Network (vRAN) (which may also be referred to as a Cloud Radio Access Network (C-RAN)). Decomposition can include distributing functions among two or more units located in various physical locations, as well as virtually distributing the functions of at least one unit, which allows for flexibility in network design. Various units in a decomposed base station architecture or a decomposed RAN architecture can be configured to communicate wired or wirelessly with at least one other unit. For example, base stations 104d / 104e and / or RUs 106a-106d can communicate with UEs 102a-102d and 102s via one or more radio frequency (RF) access links based on a Uu interface. In the example, multiple RUs 106 and / or base stations 104 can simultaneously serve UE 102, such as through intra-cell and / or inter-cell access links between UE 102 and RUs 106 / base station 104.

[0024] RU 106, DU 108, and CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information / signals via wired or wireless transmission media. For example, a wired interface may be configured to transmit or receive information / signals via a wired transmission medium, such as a fronthaul link 160 between RU 106d and a baseband unit (BBU) 112 associated with base station 104d in cell 190d. BBU 112 includes DU 108 and CU 110, and may also have a wired interface (e.g., a midhaul link) configured between DU 108d and CU 110d to transmit or receive information / signals between DU 108d and CU 110d. In a further example, a wireless interface that may include a receiver, transmitter, or transceiver (such as an RF transceiver) may be configured to transmit and / or receive information / signals via a wireless transmission medium, such as information transmitted between RU 106a in cell 190a and base station 104e in cell 190e via inter-cell communication beams 136-138 of RU 106a and base station 104e.

[0025] RU 106 can be configured to implement low-level functions. For example, RU 106 is controlled by DU 108 and can correspond to a logical node that manages RF processing functions or low-level PHY functions such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, Physical Random Access Channel (PRACH) extraction, and filtering. The functionality of RU 106 can be based on functional partitioning, such as low-level functional partitioning.

[0026] RU 106 can send or receive over-the-air (OTA) communications with one or more UEs 102. For example, RU 106b of cell 190b communicates with UE 102b of cell 190b via a first communication beamset 132 of RU 106b and a second communication beamset 134b of UE 102b, which may correspond to inter-cell communication beams or, in some examples, inter-cell communication beams. For example, UE 102b of cell 190b can communicate with RU 106a of cell 190a via a third communication beamset 134a of UE 102b and a fourth communication beamset 136 of RU 106a. DU 108 can control the real-time and non-real-time characteristics of control plane and user plane communications of RU 106.

[0027] Any combination or individual reference to RU 106, DU 108, and CU 110 may correspond to base station 104. Therefore, base station 104 may include at least one of RU 106, DU 108, or CU 110. Base station 104 provides UE 102 with access to the core network. Base station 104 may relay communication between UE 102 and the core network (not shown). Base station 104 may be associated with macro cells of high-power cellular base stations and / or small cells of low-power cellular base stations. For example, cell 190e may correspond to a macro cell, while cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network including at least one macro cell and at least one small cell may be referred to as a "heterogeneous network".

[0028] Transmissions from UE 102 to base station 104 / RU 106 are called uplink (UL) transmissions, while transmissions from base station 104 / RU 106 to UE 102 are called downlink (DL) transmissions. Uplink transmissions can also be called reverse link transmissions, and downlink transmissions can also be called forward link transmissions. For example, RU 106d uses the antenna of base station 104d in cell 190d to send downlink / forward link communication to UE 102d, or receive uplink / reverse link communication from UE 102d, based on the Uu interface associated with the access link between UE 102d and base station 104d / RU 106d.

[0029] The communication link between UE 102 and base station 104 / RU 106 can be based on multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. The communication link can be associated with one or more carriers. UE 102 and base station 104 / RU 106 can utilize a per-carrier Y MHz spectral bandwidth (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, 800 MHz, 1600 MHz, 2000 MHz, etc.) allocated in carrier aggregation up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. Carriers can be adjacent to each other along the spectrum or can be non-adjacent. In the example, uplink and downlink carriers can be allocated asymmetrically, with more or fewer carriers allocated for the uplink or downlink. Component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier can be associated with the primary cell (PCell), and the secondary component carrier can be associated with the secondary cell (SCell).

[0030] Some UEs 102 (such as UEs 102a and 102s) can perform device-to-device (D2D) communication via sidelinks. For example, sidelink communication / D2D links utilize the spectrum of the Wireless Wide Area Network (WWAN) associated with uplink and downlink communication. Such sidelink / D2D communication can be performed by various wireless communication systems, such as Wi-Fi, Bluetooth, LTE, and NR systems.

[0031] The electromagnetic spectrum is typically subdivided into different categories, bands, channels, etc., based on the different frequencies / wavelengths associated with it. Fifth-generation (5G) NR is generally associated with two operating frequency ranges (FRs) known as Frequency Range 1 (FR1) and Frequency Range 2 (FR2). FR1 ranges from 410 MHz to 7.125 GHz, and FR2 ranges from 24.25 GHz to 71.0 GHz, which includes FR2-1 (24.25 GHz to 52.6 GHz) and FR2-2 (52.6 GHz to 71.0 GHz). Although a portion of FR1 is actually greater than 6 GHz, FR1 is often referred to as the "sub-6 GHz" band. In contrast, FR2 is often referred to as the "millimeter wave" (mmW) band. FR2 is different from the "extremely high frequency" (EHF) band, but is an approximate subset of it, the EHF band which ranges from 30 GHz to 300 GHz, and is sometimes also referred to as the "millimeter wave" band. The frequencies between FR1 and FR2 are generally referred to as the "mid-band" frequencies. The operating frequency band of the mid-band can be referred to as Frequency Range 3 (FR3), ranging from 7.125 GHz to 24.25 GHz. The frequency bands within FR3 can include the characteristics of FR1 and / or FR2. Therefore, the characteristics of FR1 and / or FR2 can be extended to the mid-band frequencies. Higher operating frequency bands have been identified to extend 5G NR communication above 52.6 GHz, which is associated with the upper limit of FR2. Three of these higher operating frequency bands are FR2-2 (ranging from 52.6 GHz to 71.0 GHz), FR4 (ranging from 71.0 GHz to 114.25 GHz), and FR5 (ranging from 114.25 GHz to 300 GHz). The upper limit of FR5 corresponds to the upper limit of the EHF band. Therefore, unless otherwise expressly stated herein, the term "below 6 GHz" may refer to frequencies less than 6 GHz, frequencies within FR1, or frequencies that may include mid-band frequencies. Furthermore, unless otherwise expressly stated herein, the term "millimeter wave" or mmW refers to frequencies that may include mid-band frequencies, frequencies within FR2-1, FR4, FR2-2, and / or FR5, or frequencies within the EHF band.

[0032] UE 102 and base station 104 / RU 106 may each include multiple antennas. These multiple antennas may correspond to antenna elements, antenna panels, and / or antenna arrays that facilitate beamforming operation. For example, RU 106b transmits downlink beamforming signals to UE 102b based on a first communication beamset 132 in one or more transmit directions of RU 106b. UE 102b may receive downlink beamforming signals from RU 106b based on a second communication beamset 134b in one or more receive directions of UE 102b. In a further example, UE 102b may also transmit uplink beamforming signals (e.g., sounding reference signals (SRS)) to RU 106b based on the second communication beamset 134b in one or more transmit directions of UE 102b. RU 106b may receive uplink beamforming signals from UE 102b in one or more receive directions of RU 106b.

[0033] UE 102b can perform beamforming to determine the optimal reception and transmission directions for the beamformed signal. The transmission and reception directions of UE 102b and base stations 104 / RU 106 may be the same or different. In a further example, the beamformed signal can be transmitted between a first base station / RU 106a and a second base station 104e. For example, base station 104e of cell 190e can transmit a beamformed signal to RU 106a based on communication beam 138 in one or more transmission directions of base station 104e. RU 106a can receive the beamformed signal from base station 104e of cell 190e based on RU communication beam 136 in one or more reception directions of RU 106a. In a further example, base station 104e transmits a downlink beamformed signal to UE 102e based on communication beam 138 in one or more transmission directions of base station 104e. UE 102e receives downlink beamforming signals from base station 104e based on UE communication beam 130 in one or more receiving directions of UE 102e. UE 102e can also transmit uplink beamforming signals to base station 104e based on UE communication beam 130 in one or more transmitting directions of UE 102e, so that base station 104e can receive uplink beamforming signals from UE 102e in one or more receiving directions of base station 104e.

[0034] Base station 104 may include and / or be referred to as a network entity. That is, a "network entity" may refer to base station 104 or at least one element of base station 104, such as RU 106, DU 108, and / or CU 110. Base station 104 may also include and / or be referred to as Next Generation Evolved Node B (ng-eNB), Next Generation NB (gNB), Evolved NB (eNB), access point, base transceiver, radio base station, radio transceiver, transceiver function, Basic Service Set (BSS), Extended Service Set (ESS), TRP, network node, network device, or other related terms. Base station 104 or the entity at base station 104 may be implemented as an IAB node, relay node, sidelink node, aggregated (monolithic) base station, or a decomposed base station including one or more RU 106, DU 108, and / or CU 110. Aggregated or decomposed base station sets may be referred to as Next Generation Radio Access Network (NG-RAN). In some examples, UE 102a operates in dual connectivity (DC) with base station 104e and base station / RU 106a. In such a case, base station 104e can be the primary node, while base station / RU 160a can be the secondary node.

[0035] Uplink / downlink signaling can also be communicated via a Satellite Positioning System (SPS) 114. In the example, the SPS 114 of cell 190c can communicate with one or more UEs 102 (such as UE 102c) and one or more base stations 104 / RU 106 (such as RU 106c). The SPS 114 can correspond to one or more of Global Navigation Satellite Systems (GNSS), Global Positioning Systems (GPS), Non-Terrestrial Networks (NTN), or other satellite positioning / location systems. The SPS 114 can be associated with LTE signals, NR signals (e.g., based on Round Trip Time (RTT) and / or multiple RTTs), Wireless Local Area Network (WLAN) signals, Terrestrial Beacon Systems (TBS), sensor-based information, NR Enhanced Cell ID (NR E-CID) technology, Downlink Angle of Arrival (DL-AoD), Downlink Time Difference of Arrival (DL-TDOA), Uplink Time Difference of Arrival (UL-TDOA), Uplink Angle of Arrival (UL-AoA), and / or other systems, signals, or sensors.

[0036] Still referencing Figure 1In some respects, any UE in UE 102 may include an uplink control information (UCI) multiplexing component 140 configured to: receive control signaling from a network entity to schedule PUSCH retransmissions of a multi-codeword physical uplink shared channel (PUSCH); and send to the network entity a PUSCH retransmission based on a UCI multiplexing procedure that prevents the multiplexing of UCI on disabled codewords or on codewords having a reserved modulation and coding scheme (MCS) based on a reserved value.

[0037] In some respects, any base station or network entity of base station 104 may include a PUSCH scheduling component 150 configured to: send control signaling to the UE to schedule PUSCH retransmission of multi-codeword PUSCH; and receive from the UE a PUSCH retransmission based on a UCI multiplexing procedure for multi-codeword PUSCH, the UCI multiplexing procedure preventing the multiplexing of UCI on disabled codewords or on codewords having a reserved MCS based on a reserved MCS value.

[0038] therefore, Figure 1 A wireless communication system is described, which can be implemented in conjunction with aspects of one or more other accompanying figures described herein. Furthermore, although the following description may focus on 5G NR, the concepts described herein are applicable to other similar fields, such as 5G-Advanced and future versions, LTE, LTE-Advanced (LTE-A), and other wireless technologies such as 6G.

[0039] Figures 2A to 2BIllustrations 200-250 illustrate the association of UCI multiplexing on the PUSCH. Network entities can configure the UE to transmit UCI on the Physical Uplink Control Channel (PUCCH) 204 (as shown in Illustration 200) or on PUSCH 202b (as shown in Illustration 250) based on UCI multiplexing. UCI may include a scheduling request, a Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK), and Channel State Information (CSI). Therefore, UCI can have seven permutations corresponding to the following: Hybrid Automatic Repeat Request (HARQ) only, scheduling request only, CSI only, HARQ and scheduling request, HARQ and CSI, scheduling request and CSI, and HARQ + scheduling request + CSI. However, the UE does not transmit a scheduling request on PUSCH 202. CSI can also include CSI Part 1 and CSI Part 2, where CSI Part 2 supports variable length (such as CSI Part 2 only) and can be segmented into two parts by puncturing symbols with demodulation reference signal (DMRS) resource elements and data resource elements. If the network entity configures the UE to transmit UCI on PUCCH 204 and transmit data on PUSCH 202a in overlapping symbols (such as in Figure 200), the UE can transmit UCI on PUSCH 202b based on UCI multiplexing (such as in Figure 250). Furthermore, the network entity can also schedule the UE to report aperiodic CSI on PUSCH 202.

[0040] Network entities can schedule data transmission on PUSCH 202 with one or more codewords. For example, a network entity can schedule an initial transmission for one or more codewords, followed by one or more retransmissions of the same codewords. For retransmissions on PUSCH 202 involving multiple codewords, the network entity can disable codewords among the multiple codewords via downlink control information (DCI). In other implementations of retransmissions on PUSCH 202, the network entity can indicate the MCS of the codeword via DCI. The reserved MCS can indicate an MCS greater than V, where in some examples, V can be equal to 27 or 28. The reserved MCS indicates the modulation order of the PUSCH transmission. Therefore, the UE can transmit a transport block (TB) for the initial PUSCH transmission based on the modulation order indicated by the reserved MCS.

[0041] For initial PUSCH transmissions based on multiple codewords, the UE can reuse the first codeword or the codeword with a higher MCS to reuse the UCI. A codeword with a higher MCS can provide better channel quality compared to a codeword with a lower MCS. Therefore, transmitting the UCI on a codeword with a higher MCS corresponds to transmitting the UCI in a layer with higher channel quality. However, for PUSCH retransmissions, the first codeword or the codeword with a higher MCS may be disabled. If the UCI is reused on a disabled codeword, the power consumption and / or DMRS overhead at the UE may increase, considering that the UE may still have to transmit DMRS from the port mapped to the disabled codeword.

[0042] The UE may need to implement techniques for transmitting UCIs on a multi-codeword PUSCH when one of the codewords is disabled for retransmission. For example, if the UE determines to multiplex UCIs on PUSCH retransmissions, it can implement a procedure for multiplexing UCIs on codewords with a higher MCS because the index of the reserved MCS is higher than the initial MCS. However, codewords with reserved MCSs may not always provide optimal performance for the UE. Therefore, the UE may also need to implement techniques for transmitting UCIs on a multi-codeword PUSCH when at least one codeword's MCS is a reserved MCS.

[0043] Therefore, when one of the multiple codewords is disabled and / or when the MCS of one of the multiple codewords is a reserved MCS, the UE can perform UCI multiplexing on a multi-codeword PUSCH, where at least one of the multiple codewords is configured for PUSCH retransmission. This technique avoids multiplexing UCI on disabled codewords, which can improve PUSCH 202 performance by reducing DMRS overhead; and / or helps identify codewords with better channel quality for UCI transmission when at least one codeword's MCS is a reserved MCS, which can improve UCI performance.

[0044] Figure 3 Signaling diagram 300 illustrates UCI multiplexing on a PUSCH with multiple codeword retransmissions. UE 102 may (e.g., in a UE capability report) send 306 a UE capability for UCI multiplexing on a multiple codeword PUSCH with retransmissions to network entity 104. In other implementations, network entity 104 may receive an indication of UE capability from the core network (such as from the Access and Mobility Management Function (AMF)). In yet another implementation, network entity 104 may receive an indication of UE capability from another base station / network entity (e.g., a gNB or eNB).

[0045] Network entity 104 instructs UE 102 of configuration 308 for UCI multiplexing on multi-codeword PUSCH, including configuration for UCI multiplexing on PUSCH retransmission (e.g., based on UE capabilities). Network entity 104 can send configuration 308 for UCI multiplexing via control signaling. Network entity 104 can instruct UE 102 of RRCReconfiguration messages using RRC signaling or using System Information Blocks (SIBs), where the SIB can be a traditional type of SIB (e.g., SIB1) or a different SIB sent by network entity 104 (e.g., SIB J, where J corresponds to an integer greater than 21). Network entity 104 can also send configuration 308 for UCI multiplexing via Media Access Control-Control Element (MAC-CE). Configuration for UCI multiplexing on PUSCH retransmission can instruct the multiplexing process when one of the multiple codewords is disabled and / or when the indicated MCS of the multiple codewords is a reserved MCS.

[0046] UE 102 sends 310 an initial PUSCH transmission from multiple codewords to network entity 104. The initial PUSCH transmission may be for a first HARQ procedure. Network entity 104 may send 312 a DCI scheduling / triggering indication for PUSCH retransmission for at least one of the multiple codewords for the first HARQ procedure to UE 102. The DCI scheduling / triggering indication may be for PUSCH retransmission where the codewords among the multiple codewords are disabled or for PUSCH retransmission where the codewords among the multiple codewords have a reserved MCS. In some implementations, the UCI may be on a PUCCH that overlaps with the PUSCH in the time domain.

[0047] UE 102 determines 314 the UCI multiplexing procedure for retransmission of multi-codeword PUSCH. This determination 314 may be based on configuration and / or DCI scheduling / trigger indication. The UCI multiplexing procedure determined by UE 102 314 may correspond to the following: a first UCI multiplexing procedure for performing PUSCH retransmission when a codeword in multiple codewords is disabled, or a second UCI multiplexing procedure for performing PUSCH retransmission when a codeword in multiple codewords has a reserved MCS.

[0048] UE 102 multiplexes the PUSCH and UCI based on the determined UCI multiplexing procedure and sends the PUSCH and UCI to network entity 104 316. Network entity 104 may also determine the UCI multiplexing procedure used by UE 102 to multiplex the PUSCH and UCI and send the PUSCH and UCI to network entity 104 316 based on a technique similar to that used by UE 102. Such a technique may be instructed to UE 102 (e.g., via configuration 308) or based on a predefined protocol. Network entity 104 decodes the PUSCH and UCI received from UE 102 316 based on the determined UCI multiplexing procedure 318.

[0049] Figure 4 Figure 400 illustrates UCI multiplexing on enabled / scheduled codewords (e.g., when another codeword in a multi-codeword PUSCH retransmission is disabled). That is, the first PUSCH 202c can have an enabled / scheduled codeword with multiplexed UCI during retransmission, and the second PUSCH 202d can have a disabled codeword during retransmission. Therefore, DCI scheduling from the network entity can be dedicated to PUSCH 202c with enabled codewords and not to PUSCH 202d with disabled codewords.

[0050] In some implementations, the UE transmits the UCI on the first enabled / scheduled codeword. In other implementations, the UE transmits the UCI on the enabled / scheduled codeword with the highest MCS. If multiple codewords are configured with the same MCS, the codeword with the lowest codeword index can be used for UCI multiplexing. That is, the first enabled / scheduled codeword with the same / highest MCS is selected for UCI multiplexing.

[0051] In some implementations of UCI multiplexing for PUSCH retransmission, if UCI is to be multiplexed on PUSCH 202d with disabled codewords, the UE can discard or skip UCI transmission. That is, the UE avoids transmitting UCI on PUSCH 202d with disabled codewords. Similarly, network entities can avoid receiving (e.g., scanning) UCI ​​on PUSCH 202d with disabled codewords. If UCI is to be multiplexed on a PUSCH with disabled codewords, the UE can also discard or skip the transmission of that data. For example, the UE can discard data such as all scheduled TBs associated with PUSCH 202d.

[0052] The UE transmits UCI on PUSCH 202c based on scheduling information (e.g., MCS and precoder information) for the codeword to be multiplexed. The UE can also transmit UCI on PUSCH 202c based on scheduling information for enabled / scheduled codewords. The enabled / scheduled codeword can be the first codeword among multiple codewords or the codeword with the highest MCS among multiple codewords. In some implementations, the UE can transmit UCI on PUCCH resources configured or indicated by a network entity via RRC signaling, MAC-CE, or DCI, and then discard the PUSCH transmission.

[0053] In some implementations, the network entity can instruct a configurable UCI multiplexing procedure when one of the codewords is disabled. The network entity configures whether the UE will transmit UCI on the enabled / scheduled codeword. If the network entity configures the UE to transmit UCI on the enabled / scheduled codeword, the UE performs UCI multiplexing on PUSCH 202c. Otherwise, the UE can transmit UCI on PUSCH 202d with the disabled codeword, discard the UCI, transmit the UCI on the PUCCH, or transmit the UCI on PUSCH 202d and discard the data.

[0054] Network entities can configure more than one option for UCI transmissions. Alternatively, more than one option can be predefined for the UE for UCI transmissions. The UE can select one of the options to send the UCI. The network entity can perform blind detection to determine which option the UE has selected for decoding the UCI transmission received from the UE.

[0055] The UE can send a UE capability report to the network entity, indicating whether it supports UCI multiplexing on disabled codewords. If the UE does not support UCI multiplexing on disabled codewords, based on the UCI multiplexing scheme, when multiplexing UCI on disabled codewords, the UE can discard the UCI and transmit the UCI on the PUCCH, or transmit the UCI on PUSCH 202d and discard the data. Alternatively, when multiplexing UCI for multi-codeword PUSCH retransmissions, the network entity can avoid disabling the codewords.

[0056] Figures 5 to 8 Illustrations 500-850 show UCI multiplexing when a reserved MCS is specified for a codeword. For example, in Figure 5In Figure 500, the network entity indicates the MCS for the initial transmission of the second codeword 506a, and also indicates the reserved MCS for the second codeword 506a among the plurality of codewords 506a-506b (e.g., in retransmissions). Specifically, the first codeword 506b has MCS=18, and the second codeword 506a has MCS=6 for the initial transmission. The second codeword 506a also has a reserved MCS=29. The network entity 104 may also indicate a non-reserved MCS for retransmissions.

[0057] If the MCS of the DCI scheduling indication codeword includes a reserved MCS, the network entity and / or UE can determine the codeword 502b for UCI multiplexing based on the MCS indicated for codeword 506b and other MCS indicated for other codewords (e.g., 506a) in the DCI scheduling. In Figure 550, the UE selects the codeword with the highest MCS for UCI multiplexing. For example, the first codeword 506b has a higher MCS than the second codeword 506a. Therefore, the UE selects the first codeword 506b / 502b for UCI multiplexing. If the MCS of codewords 506a-506b are the same, the UE can select the first codeword 502b from multiple codewords 502a-502b for UCI multiplexing.

[0058] exist Figure 6 In Figure 600, the network entity indicates a reserved MCS for one of the codewords 606a among a plurality of codewords 606a-606b, and the network entity and / or UE determine the nominal MCS based on the reserved MCS indicated by codeword 606a. Specifically, the first codeword 606b has MCS=18, and the second codeword 606a has a nominal MCS=8. The second codeword 606a also has a reserved MCS=29.

[0059] If the MCS of the DCI scheduling indication codeword includes a reserved MCS, the network entity and / or UE can determine the codeword 502b for UCI multiplexing based on the MCS of codeword 606b and the nominal MCS of another codeword 606a. The network entity and / or UE use an MCS table to determine the nominal MCS based on the spectral efficiency (SE) of the retransmitted codeword and the spectral efficiency of the non-reserved MCS. The UE selects the codeword with the highest indicated / nominal MCS for UCI multiplexing. For example, the first codeword 606b has a higher MCS than the second codeword 606a. Therefore, the UE selects the first codeword 606b / 502b for UCI multiplexing. If the MCS of codewords 606a-606b are the same, the UE can select the first codeword 502b from multiple codewords 502a-502b for UCI multiplexing.

[0060] The nominal MCS can be calculated based on a reserved MCS. In some implementations, the nominal MCS is based on the average SE calculated for each layer of the corresponding codeword and an MCS table. The network entity can select the nominal MCS based on the largest MCS in the MCS table corresponding to an SE less than or equal to the calculated SE. For example, if the calculated SE is 1.5, and the MCS table shows an SE of 1.5 with MCS=6, then MCS=6 is selected as the nominal MCS. Alternatively, the network entity can select the nominal MCS based on the smallest MCS in the MCS table corresponding to an SE higher than the calculated SE. For example, if the calculated SE is 1.4, and the MCS table shows the smallest MCS with an SE higher than 1.4 is MCS=6, then MCS=6 is selected as the nominal MCS.

[0061] The SE for each layer can be calculated based on the following: Where B corresponds to the size of the codeword TB. Corresponding to the number of layers of codewords, Corresponding to the number of resource elements scheduled for PUSCH, and This corresponds to the overhead of DMRS and other signals.

[0062] exist Figure 7 In diagram 700, in addition to indicating the MCS of multiple codewords 706a-706b, the network entity also indicates the SE of each codeword among the multiple codewords 706a-706b and the reserved MCS of one codeword 706a among the multiple codewords 706a-706b. Specifically, the first codeword 706b has SE=2.73, and the second codeword 706a has SE=1.6. The second codeword 706a also has a reserved MCS=29, and the first codeword 706b has MCS=18.

[0063] If the MCS of the DCI scheduling indication codeword includes a reserved MCS, the network entity and / or UE can determine the codeword 502b for UCI multiplexing based on the actual SE of codeword 706b (e.g., derived from the reserved MCS of the second codeword 706a and the indicated MCS of the first codeword 706b). In some implementations, the UE selects the codeword with the highest SE for UCI multiplexing. For example, the first codeword 706b has a higher SE than the second codeword 706a. Therefore, the UE selects the first codeword 706b / 502b for UCI multiplexing. In other implementations, the UE selects the codeword with the lowest SE for UCI multiplexing. For example, the second codeword 706a has a lower SE than the first codeword 706b, causing the UE to select the second codeword 706a for UCI multiplexing. If the MCS of codewords 706a-706b have the same SE, the UE can select the first codeword 502b among multiple codewords 502a-502b for UCI multiplexing.

[0064] The UE can determine the SE based on an MCS table for the indicated MCS instead of a reserved MCS. For the indicated MCS instead of a reserved MCS, the UE can also determine the SE based on the actual transmission of the codewords, which is the same as determining the SE for a reserved MCS. The UE can determine UCI multiplexing based on the average SE per layer. The average SE per layer can be based on parameters such as the TB size of the codeword, the number of layers mapped to the codeword, the resource elements of the PUSCH, and the overhead of other signals. In the example, the SE per layer can be calculated based on the following: .

[0065] The UE can also determine UCI multiplexing based on the total SE across layers mapped to codewords, which is determined based on parameters such as the TB size of the codeword, the number of layers mapped to the codeword, the resource elements of the PUSCH, and the overhead of other signals. For example, the SE for each layer can be based on the following: .

[0066] In some implementations, if the MCS of the DCI scheduling indicator codeword includes a reserved MCS, the UE discards the UCI. That is, the UE avoids sending the UCI to the network entity on the PUSCH. The network entity can similarly avoid receiving (e.g., scanning) the UCI on the PUSCH. In other implementations, if the DCI scheduling indicator allows only one codeword to apply / use the reserved MCS, the UE discards the UCI transmission / multiplexing. If the DCI scheduling indicator allows any one or both codewords to apply / use the reserved MCS, the UE can select / use the first codeword for UCI transmission / multiplexing.

[0067] In a further implementation, if the MCS of the DCI scheduling indicator codeword includes a reserved MCS, the UE may discard data. For example, the UE discards all scheduled TBs. The UE transmits UCI on the PUSCH based on scheduling information (e.g., MCS and precoder) for codewords to be multiplexed on the PUSCH. Based on this implementation, the UE may transmit UCI on the PUSCH based on scheduling information (e.g., MCS and precoder) for one of the following: the first enabled / scheduled codeword or an enabled / scheduled codeword with a higher or lower MCS. In other implementations, the UE transmits UCI on PUCCH resources configured or indicated by network entities via RRC signaling, MAC-CE, or DCI, and the UE discards / skips PUSCH transmissions.

[0068] exist Figure 8 In Figure 800, the network entity indicates the MCS of multiple codewords 806a-806b. Specifically, the first codeword 806b has MCS=18, and the second codeword 806a has a reserved MCS=29. If the MCS of the DCI scheduling indicator codeword includes the reserved MCS, the UE can transmit UCI on all scheduled codewords 502b / 803a, as illustrated in Figure 850. That is, Figure 850 includes both the first codeword 502b with UCI and the second codeword 803a with UCI.

[0069] In some implementations, where the MCS of the DCI scheduling indicator codeword includes a reserved MCS, the UE transmits the UCI on all enabled codewords 502b / 803a. The UE can also transmit the UCI as multiple repetitions on multiple corresponding codewords. In other implementations, the UE transmits different coded bits of the UCI on different codewords, allowing the UE to apply a single channel coding scheme to the entire UCI. The UE can transmit different portions of the UCI (e.g., source bits) in different codewords, or perform separate channel coding for the UCI on each codeword. The network entity can pre-indicate or pre-configure the UE with the UCI coded bits or a portion or component of the source bits to be multiplexed on the codeword.

[0070] If the MCS of the DCI scheduling indicator codeword includes a reserved MCS, the network entity can add an index to that codeword for UCI multiplexing. The network entity can indicate the codeword index via RRC signaling, MAC-CE, or DCI. In the example, a field in the DCI used to schedule PUSCH retransmissions can indicate the codeword index for UCI multiplexing. In other examples, if the MCS of the DCI scheduling indicator codeword includes a reserved MCS, the UE multiplexes the UCI on a predefined codeword (e.g., the first scheduled codeword among multiple codewords).

[0071] When the MCS indicated by the codeword is a reserved MCS, the network entity can configure the UCI multiplexing scheme via RRC signaling, MAC-CE, or DCI. For periodic UCI or Type 1 configuration-granted PUSCH, the network entity can configure the UCI multiplexing scheme via RRC signaling. For semi-persistent UCI, the network entity can configure the UCI multiplexing scheme via MAC-CE. For aperiodic UCI, dynamically granted PUSCH, or Type 2 configuration-granted PUSCH, the network entity can configure the UCI multiplexing scheme in the DCI used to trigger aperiodic UCI transmissions or in the DCI used to trigger / activate PUSCH.

[0072] UCI multiplexing schemes / procedures can be determined based on the content or type of the UCI. Network entities and UEs can determine different UCI multiplexing procedures for different types of UCIs (e.g., HARQ-ACK, CSI, beam reports, etc.). CSI can correspond to CSI reports without Layer 1-Reference Signal Received Power (L1-RSRP) / Layer 1-Signal-to-Interference-plus-Noise Ratio (L1-SINR) information. Beam reports can correspond to CSI reports with L1-RSRP / L1-SINR information.

[0073] The UE can report its capability to the network entity, indicating whether it supports UCI multiplexing on PUSCH retransmissions of multiple codewords from a reserved MCS indicating at least one of the multiple codewords. If the UE does not support this capability, it can discard the UCI or the data. Similarly, when multiplexing UCI on a multi-codeword PUSCH, the network entity can avoid MCSs reserved for codeword indications. If the UE supports the capability to perform UCI multiplexing on PUSCH retransmissions of multiple codewords from a reserved MCS indicating at least one of the multiple codewords, it can report the supported capability to the network entity. Figures 3 to 8 Example of UCI multiplexing on multi-codeword PUSCH retransmission. Figures 9 to 10 Showing the implementation Figures 3 to 8 One or more aspects of the method. Specifically, Figure 9 This shows the connection made by UE 102 to Figures 3 to 8 The implementation method of one or more aspects. Figure 10 This shows the network entity 104 pairs Figures 3 to 8 The implementation method of one or more aspects.

[0074] Figure 9 Flowchart 900 illustrates a method for wireless communication at the UE. (See reference) Figure 1 , Figure 3 and Figure 11The method can be executed by UE 102, UE equipment 1102, etc., which may include memories 1126', 1106', 1116 and may correspond to the entire UE 102 or the entire UE equipment 1102, or components of UE 102 or UE equipment 1102 (such as wireless baseband processor 1126 and / or application processor 1106).

[0075] UE 102 sends a 906 UE Capability Report to the network entity. This UE Capability Report indicates the UE's ability to perform UCI multiplexing procedures on PUSCH retransmissions when a multi-codeword PUSCH includes at least one of a disabled codeword or a codeword with a reserved MCS. For example, refer to... Figure 3 UE 102 sends 306 to network entity 104 regarding the UE capability to perform UCI multiplexing on a multi-codeword PUSCH with retransmission.

[0076] UE 102 receives 908 from a network entity for configuring a UCI multiplexing procedure on PUSCH retransmission when the multi-codeword PUSCH includes at least one of a disabled codeword or a codeword with a reserved MCS. For example, refer to Figure 3 UE 102 receives 308 from network entity 104 for configuration of UCI multiplexing on multi-codeword PUSCH (e.g., based on disabled codewords or reserved MCS).

[0077] UE 102 receives control signaling from the network entity for PUSCH retransmission of 912 scheduled multi-codeword PUSCH. For example, refer to Figure 3 UE 102 receives from network entity 104 312 DCI scheduling (e.g., based on disabled codewords or reserved MCS) for PUSCH retransmission of at least one of a plurality of codewords for the first HARQ procedure.

[0078] UE 102 defines the 914 UCI multiplexing process. For example, refer to... Figure 3 UE 102 determines the UCI multiplexing process on the retransmission of 314 multi-codeword PUSCH. UE 102 can determine the multiplexing of 914a UCI on PUSCH retransmission, such as... Figures 4 to 8 The illustrations are shown in Figures 400-850. Alternatively, when control signaling is on a disabled codeword or when a UCI is scheduled based on a reserved MCS, UE 102 can determine to discard the 914b UCI or data from the PUSCH retransmission.

[0079] UE 102 sends 916 multi-codeword PUSCH retransmissions to network entities using a UCI multiplexing procedure—the UCI multiplexing procedure prevents UCI multiplexing on disabled codewords or, based on a reserved MCS value, prevents UCI multiplexing on codewords with that reserved MCS. For example, refer to... Figure 3 UE 102 sends 316 PUSCH and UCI based on the UCI multiplexing process to network entity 104. Figure 9 Describes the method from the UE side of the wireless communication link, while Figure 10 Describes a method from the network side of a wireless communication link.

[0080] Figure 10 This is a flowchart 1000 illustrating a method for wireless communication at a network entity. (Reference) Figure 1 , Figure 3 and Figure 12 The method can be performed by one or more network entities 104, which may correspond to a base station or a unit of a base station (such as RU 106, DU 108, CU 110, RU processor 1206, DU processor 1226, CU processor 1246, etc.). One or more network entities 104 may include memories 1206' / 1226' / 1246', which may correspond to the entirety of one or more network entities 104, or components of one or more network entities 104 (such as RU processor 1206, DU processor 1226, or CU processor 1246).

[0081] Network entity 104 receives a UE capability report 1006 from the UE. This UE capability report indicates the UE's ability to perform a UCI multiplexing process on PUSCH retransmission when the multi-codeword PUSCH includes at least one of a disabled codeword or a codeword with a reserved MCS. For example, refer to Figure 3 Network entity 104 receives 306 from UE 102 regarding UE capability for UCI multiplexing on multi-codeword PUSCH with retransmission.

[0082] Network entity 104 sends 1008 to the UE for configuring a UCI multiplexing procedure on PUSCH retransmission when the multi-codeword PUSCH includes at least one of a disabled codeword or a codeword with a reserved MCS. For example, refer to Figure 3 Network entity 104 sends 308 to UE 102 for configuration of UCI multiplexing on multi-codeword PUSCH (e.g., based on disabled codewords or reserved MCS).

[0083] Network entity 104 sends control signaling 1012 to the UE to schedule PUSCH retransmission for multi-codeword PUSCH. For example, refer to Figure 3Network entity 104 sends 312 DCI scheduling (e.g., based on disabled codewords or reserved MCS) for PUSCH retransmission of the first HARQ procedure to UE 102 for at least one of a plurality of codewords.

[0084] Network entity 104 receives 1016 multi-codeword PUSCHs from the UE and performs a PUSCH retransmission based on a UCI multiplexing procedure—the UCI multiplexing procedure prevents the multiplexing of UCI on disabled codewords or on codewords with a reserved MCS based on the value of a reserved MCS. For example, refer to Figure 3 Network entity 104 receives 316 PUSCH and UCI based on the UCI multiplexing process from UE 102. For example... Figure 11 As described, UE equipment 1102 can execute the method of flowchart 900. For example... Figure 12 As described in the document, one or more network entities 104 can execute the methods of flowchart 1000.

[0085] Figure 11 Figure 1100 illustrates an example of a hardware implementation of UE device 1102. UE device 1102 may be UE 102, a component of UE 102, or may implement UE functions. UE device 1102 may include an application processor 1106, which may have on-chip memory 1106'. In the example, application processor 1106 may be coupled to a secure digital (SD) card 1108 and / or a display 1110. Application processor 1106 may also be coupled to a sensor module 1112, a power supply 1114, an additional memory module 1116, a camera 1118, and / or other related components. For example, sensor module 1112 may control a barometer / altimeter, motion sensors (such as an inertial management unit (IMU)), a gyroscope, an accelerometer, a light detection and ranging (LIDAR) device, a radio-assisted detection and ranging (RADAR) device, a sound navigation and ranging (SONAR) device, a magnetometer, an audio device, and / or other technologies for positioning.

[0086] The UE equipment 1102 may further include a wireless baseband processor 1126, which may be referred to as a modem. The wireless baseband processor 1126 may have on-chip memory 1126'. Together with and similarly to the application processor 1106, the wireless baseband processor 1126 may also be coupled to a sensor module 1112, a power supply 1114, an additional memory module 1116, a camera 1118, and / or other related components. The wireless baseband processor 1126 may additionally be coupled to one or more Subscriber Identity Module (SIM) cards 1120 and / or one or more transceivers 1130 (e.g., wireless RF transceivers).

[0087] Within one or more transceivers 1130, the UE equipment 1102 may include a Bluetooth module 1132, a WLAN module 1134, an SPS module 1136 (e.g., a GNSS module), and / or a cellular module 1138. The Bluetooth module 1132, WLAN module 1134, SPS module 1136, and cellular module 1138 may each include an on-chip transceiver (TRX), or in some cases, only a transmitter (TX) or only a receiver (RX). The Bluetooth module 1132, WLAN module 1134, SPS module 1136, and cellular module 1138 may each include a dedicated antenna and / or utilize antenna 1140 to communicate with one or more other nodes. For example, UE equipment 1102 can communicate with another UE (e.g., sidelink communication) and / or with network entity 104 (e.g., uplink / downlink communication) via transceiver 1130 and antenna 1140, where network entity 104 may correspond to a base station or a unit of a base station, such as RU 106, DU 108 or CU 110.

[0088] The wireless baseband processor 1126 and application processor 1106 may each include computer-readable media / memory 1126', 1106' respectively. An additional memory module 1116 may also be considered a computer-readable media / memory. Each computer-readable media / memory 1126', 1106', 1116 may be non-transitory. The wireless baseband processor 1126 and application processor 1106 may each be responsible for general processing, including executing software stored on the computer-readable media / memory 1126', 1106', 1116. When executed by the wireless baseband processor 1126 / application processor 1106, this software causes the wireless baseband processor 1126 / application processor 1106 to perform the various functions described herein. The computer-readable media / memory may also be used to store data manipulated by the wireless baseband processor 1126 / application processor 1106 during software execution. The wireless baseband processor 1126 / application processor 1106 may be a component of UE 102. UE equipment 1102 may be a processor chip (e.g., a modem and / or an application) and includes only the wireless baseband processor 1126 and / or the application processor 1106. In other examples, UE equipment 1102 may be the entire UE 102 and may include additional modules for equipment 1102.

[0089] like Figure 1 The discussion and about Figure 8The implemented UCI multiplexing component 140 is configured to: receive control signaling from a network entity to schedule PUSCH retransmissions of multi-codeword PUSCHs; and send PUSCH retransmissions of multi-codeword PUSCHs to the network entity based on a UCI multiplexing procedure that prevents UCI multiplexing on disabled codewords or on codewords having a reserved MCS based on a reserved MCS value. The UCI multiplexing component 140 may be located within an application processor 1106 (e.g., at 140a), a wireless baseband processor 1126 (e.g., at 140b), or both application processor 1106 and wireless baseband processor 1126. The UCI multiplexing components 140a-140b may be one or more hardware components specifically configured to execute the stated procedures / algorithms, implemented by one or more processors configured to execute the stated procedures / algorithms, stored in a computer-readable medium for implementation by one or more processors, or a combination thereof.

[0090] Figure 12 Figure 1200 illustrates an example of a hardware implementation of one or more network entities 104. The one or more network entities 104 may be a base station, a component of a base station, or may implement base station functions. The one or more network entities 104 may include or correspond to at least one of RU 106, DU 108, or CU 110. CU 110 may include a CU processor 1246, which may have on-chip memory 1246'. In some aspects, CU 110 may further include an additional memory module 1256 and / or a communication interface 1248, both of which may be coupled to the CU processor 1246. CU 110 may communicate with DU 108 via a midhaul link 162, such as an F1 interface between the communication interface 1248 of CU 110 and the communication interface 1228 of DU 108.

[0091] DU 108 may include a DU processor 1226, which may have on-chip memory 1226'. In some aspects, DU 108 may further include an additional memory module 1236 and / or a communication interface 1228, both of which may be coupled to the DU processor 1226. DU 108 may communicate with RU 106 via a frontlink 160 between DU 108's communication interface 1228 and RU 106's communication interface 1208.

[0092] RU 106 may include an RU processor 1206, which may have on-chip memory 1206'. In some aspects, RU 106 may further include an additional memory module 1216, a communication interface 1208, and one or more transceivers 1230, all of which may be coupled to the RU processor 1206. RU 106 may further include an antenna 1240, which may be coupled to one or more transceivers 1230, such that RU 106 can communicate with UE 102 via the antenna 1240 through one or more transceivers 1230.

[0093] On-chip memories 1206', 1226', 1246' and additional memory modules 1216, 1236, 1256 can each be considered as computer-readable media / memory. Each computer-readable medium / memory can be non-transitory. Each of processors 1206, 1226, 1246 is responsible for general processing, including executing software stored on the computer-readable medium / memory. When executed by the corresponding processor 1206, 1226, 1246, the software causes the processor 1206, 1226, 1246 to perform the various functions described herein. The computer-readable medium / memory can also be used to store data manipulated by the processors 1206, 1226, 1246 during software execution. In the example, the PUSCH scheduling component 150 may be located at any of the network entities in one or more network entities 104, such as at CU 110; at both CU 110 and DU 108; at each of CU 110, DU 108 and RU 106; at DU 108; at both DU 108 and RU 106; or at RU 106.

[0094] like Figure 1 The discussion and about Figure 9Implemented, the PUSCH scheduling component 150 is configured to: send control signaling to the UE to schedule PUSCH retransmissions of multi-codeword PUSCHs; and receive from the UE PUSCH retransmissions of multi-codeword PUSCHs based on a UCI multiplexing procedure, which prevents UCI multiplexing on disabled codewords or prevents multiplexing of codewords having a reserved MCS based on a reserved MCS value. The PUSCH scheduling component 150 may be located within one or more processors of one or more network entities 104 (such as RU processor 1206 (e.g., at 150a), DU processor 1226 (e.g., at 150b), and / or CU processor 1246 (e.g., at 150c)). PUSCH scheduling components 150a-150c may be one or more hardware components specifically configured to execute the stated process / algorithm, implemented by one or more processors 1206, 1226, 1246 configured to execute the stated process / algorithm, and stored in a computer-readable medium for use by one or more processors 1206, 1226, 1246, or a combination thereof.

[0095] The specific order or hierarchy of the boxes in the processes and flowcharts disclosed herein is an example of the exemplary methods. Therefore, the specific order or hierarchy of the boxes in the processes and flowcharts can be rearranged. Some boxes can also be combined or deleted. Dashed lines may indicate optional elements of the diagram. The appended method claims present the elements of each box in the exemplary order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.

[0096] The detailed descriptions presented herein, in conjunction with accompanying drawings, depict various configurations, but do not represent the only configurations in which the concepts described herein can be practiced. These detailed descriptions include specific details used to provide a comprehensive explanation of the various concepts. However, these concepts can be practiced without using these specific details. In some cases, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0097] Various aspects of wireless communication systems, such as telecommunications systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are shown in the accompanying drawings by various boxes, components, circuits, processes, call flows, systems, algorithms, etc. (collectively, "elements"). These elements can be implemented using electronic hardware, computer software, or a combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and design constraints imposed on the overall system.

[0098] An element, or any part of an element, or any combination of elements, can be implemented as a “processing system” including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, system-on-a-chip (SoCs), baseband processors, field-programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other similar hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software, which may be referred to as software, firmware, middleware, microcode, hardware description languages, or others. Software should be interpreted broadly as instructions, instruction sets, code, code segments, program code, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.

[0099] If the functions described herein are implemented in software, these functions may be stored on or encoded as one or more instructions or code on a computer-readable medium, such as a non-transitory computer-readable storage medium. Computer-readable media include computer storage media and may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, combinations of these types of computer-readable media, or any other medium that can be used to store computer-executable code in the form of computer-accessible instructions or data structures. Storage media can be any available medium that is computer-accessible.

[0100] The aspects, implementations, and / or use cases described herein can be implemented across many different platform types, devices, systems, form factors, sizes, and package arrangements. For example, aspects, implementations, and / or use cases can be generated via integrated chip implementations and other devices based on non-modular components, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / procurement devices, medical devices, devices supporting artificial intelligence (AI), devices supporting machine learning (ML), etc. The scope of aspects, implementations, and / or use cases can range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregated, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more of the technologies described herein.

[0101] Apparatus incorporating the aspects and features described herein may also include additional components and features for implementing and practicing the claimed and described aspects and features. For example, the transmission and reception of wireless signals necessarily include numerous components for analog and digital purposes, such as hardware components, antennas, RF chains, power amplifiers, modulators, buffers, processors, interleavers, adders / summers, etc. The techniques described herein can be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or decomposed components, end-user devices, etc., in various configurations.

[0102] The description herein is provided to enable those skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. Therefore, the claims are not limited to the aspects described herein, but should be interpreted in light of the full scope of this disclosure consistent with the language of the claims.

[0103] Unless explicitly stated otherwise, references to singular elements do not imply "one and only one," but rather "one or more." Terms such as "if," "when," and "at" do not imply an immediate temporal relationship or response. That is, these phrases (e.g., "when") do not imply an immediate action in response to the occurrence of an action or during the occurrence of an action, but simply imply that an action will occur if a certain condition is met, without requiring a specific or immediate temporal constraint on the occurrence of the action. The terms "may," "may," and "can" as used in this disclosure generally carry certain connotations. For example, "may" refers to a permissible feature that may or may not occur, "may" refers to a feature that is likely to occur, and "can" refers to a capability (e.g., being able to). The phrase "for example" generally carries a similar connotation to "may," and therefore, "may" is sometimes excluded from sentences that include "for example" or other similar phrases.

[0104] Unless otherwise expressly stated, the term "some" means one or more. Combinations such as "at least one of A, B, or C" or "one or more of A, B, or C" include any combination of A, B, and / or C, such as A and B, A and C, B and C, or A and B and C, and may include multiple A, multiple B, and / or multiple C, or may include only A, only B, or only C. A set should be interpreted as a set of elements having one or more elements.

[0105] Unless otherwise explicitly indicated, ordinal terms such as “first” and “second” do not necessarily imply order in time, sequence, numerical value, etc., but are used to distinguish different instances of the term or phrase following each ordinal term. As used in the specification and figures, reference numerals are sometimes cross-referenced between figures to indicate the same or similar features. Features that are identical in multiple figures may be labeled with the same reference numerals in multiple figures. Features that are similar but not identical in multiple figures may be labeled with reference numerals that have different leading numerals but share one or more of the same trailing numerals (e.g., 206, 306, 406, etc. may refer to similar features in the figures). Sometimes, “X” is used generally to indicate multiple variations of a feature. For example, “X06” may generally refer to all reference numbers ending in “06” (e.g., 206, 306, 406, etc.).

[0106] Structural and functional equivalents of the various aspects of the elements described throughout this disclosure, known or subsequently learned by those skilled in the art, are expressly incorporated herein by reference and are covered by the claims. The terms “module,” “mechanism,” “element,” “device,” etc., may not be substitutes for the term “component.” Therefore, no claim element shall be construed as means plus function unless explicitly stated using the phrase “component for…”. As used herein, the phrase “based on” should not be construed as a reference to a closed set of information, one or more conditions, one or more factors, etc. In other words, unless expressly stated otherwise, the phrase “based on A” (where “A” can be information, conditions, factors, etc.) shall be construed as “at least based on A”.

[0107] The examples below are merely illustrative and can be combined with other examples or teachings described herein without limitation.

[0108] Example 1 is a method for wireless communication at a UE, comprising: receiving control signaling from a network entity to schedule PUSCH retransmission of a multi-codeword PUSCH; and sending to the network entity a PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH, the UCI multiplexing procedure preventing the multiplexing of UCI on a disabled codeword or on a codeword having a reserved MCS based on a reserved MCS value.

[0109] Example 2 can be combined with Example 1 and includes: control signaling instructs multi-codeword PUSCH to include disabled codewords on PUSCH retransmission.

[0110] Example 3 can be combined with Example 2 and includes: sending a PUSCH retransmission, further including: sending a UCI multiplexed on the enabled codeword of the multi-codeword PUSCH to the network entity.

[0111] Example 4 can be combined with Example 2 and includes: The UCI multiplexing process includes: when control signaling schedules UCI on a disabled codeword, discarding UCI or data from the PUSCH retransmission.

[0112] Example 5 can be combined with Example 1 and includes: control signaling instructs multi-codeword PUSCH to include codewords with reserved MCS on PUSCH retransmission.

[0113] Example 6 can be combined with Example 5 and includes: the UCI multiplexing process includes: multiplexing UCI on PUSCH retransmission based on a value different from the value of the reserved MCS, the different value corresponding to at least one of: the MCS of the initial transmission codeword, the nominal MCS calculated from the reserved MCS, or the spectral efficiency.

[0114] Example 7 can be combined with Example 5 and includes: The UCI multiplexing process includes: when control signaling schedules UCI on a codeword with a reserved MCS, discarding UCI or data from the PUSCH retransmission.

[0115] Example 8 can be combined with Example 5 and includes: a UCI multiplexing process that prevents the multiplexing of UCI on codewords having the reserved MCS based on the value of the reserved MCS includes: sending the UCI multiplexed on each codeword of the multi-codeword PUSCH to the network entity.

[0116] Example 9 can be combined with Example 5 and further includes: multiplexing UCI on the codeword of the indication of the multi-codeword PUSCH for PUSCH retransmission, the codeword of which is indicated by control signaling.

[0117] Example 10 can be combined with Example 5 and further includes: multiplexing UCI on a predefined codeword associated with the multi-codeword PUSCH for PUSCH retransmission.

[0118] Example 11 may be combined with any of Examples 1 to 10, and further includes: receiving from a network entity a configuration for performing a UCI multiplexing process on PUSCH retransmission when the multi-codeword PUSCH includes at least one of a disabled codeword or a codeword with a reserved MCS.

[0119] Example 12 may be combined with any of Examples 1 to 11, and further includes: sending a UE capability report to a network entity, the UE capability report indicating the UE's ability to perform a UCI multiplexing process on PUSCH retransmission when the multi-codeword PUSCH includes at least one of a disabled codeword or a codeword with a reserved MCS.

[0120] Example 13 is a method for wireless communication at a network entity, comprising: sending control signaling to a UE to schedule PUSCH retransmission of a multi-codeword PUSCH; and receiving from the UE a PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH, the UCI multiplexing procedure preventing the multiplexing of UCI on a disabled codeword or on a codeword having a reserved MCS based on a value of a reserved MCS.

[0121] Example 14 can be combined with Example 13 and includes: control signaling instructing multi-codeword PUSCH to include disabled codewords on PUSCH retransmission.

[0122] Example 15 can be combined with Example 14 and includes: receiving PUSCH retransmissions further includes: receiving from the UE a UCI multiplexed on an enabled codeword of a multi-codeword PUSCH.

[0123] Example 16 can be combined with Example 14 and includes: when control signaling schedules UCI on a disabled codeword, PUSCH retransmission discards either UCI or data.

[0124] Example 17 can be combined with Example 13 and includes: control signaling instructs the multi-codeword PUSCH to include codewords with reserved MCS on PUSCH retransmission.

[0125] Example 18 can be combined with Example 17 and includes: UCI is multiplexed on PUSCH retransmission based on a value that is different from the value of the reserved MCS, which corresponds to at least one of the following: the MCS of the initial transmission codeword, the nominal MCS calculated from the reserved MCS, or the spectral efficiency.

[0126] Example 19 can be combined with Example 17 and includes: when control signaling schedules UCI on a codeword with a reserved MCS, PUSCH retransmission discards either UCI or data.

[0127] Example 20 can be combined with Example 17 and includes: receiving PUSCH retransmissions includes: receiving from the UE a UCI multiplexed on each codeword of the multi-codeword PUSCH.

[0128] Example 21 can be combined with Example 17 and includes: UCI multiplexes codewords indicated by a multi-codeword PUSCH over PUSCH retransmission, the codewords being indicated by control signaling.

[0129] Example 22 can be combined with Example 17 and includes: UCI is based on predefined codewords associated with the multi-codeword PUSCH for multiplexing on PUSCH retransmission.

[0130] Example 23 may be combined with any of Examples 13 to 22, and further includes: sending the UE a configuration for performing a UCI multiplexing procedure on PUSCH retransmission when the multi-codeword PUSCH includes at least one of a disabled codeword or a codeword with a reserved MCS.

[0131] Example 24 may be combined with any of Examples 13 to 23, and further includes: receiving a UE capability report from the UE, the UE capability report indicating the UE's ability to perform a UCI multiplexing process on PUSCH retransmission when the multi-codeword PUSCH includes at least one of a disabled codeword or a codeword with a reserved MCS.

[0132] Example 25 is an apparatus for wireless communication, which is used to implement the method as described in any one of Examples 1 to 24.

[0133] Example 26 is an apparatus for wireless communication, including components for implementing the method as described in any one of Examples 1 to 24.

[0134] Example 27 is a non-transitory computer-readable medium storing computer-executable code that, when executed by a processor, causes the processor to perform the method as described in any one of Examples 1 to 24.

Claims

1. A method for wireless communication at a user equipment (UE) (102), comprising: Receive (312) control signaling from network entity (104) to schedule PUSCH retransmission of the multi-codeword physical uplink shared channel (PUSCH); as well as The network entity (104) sends (316) a multi-codeword PUSCH based on the uplink control information UCI multiplexing process, the UCI multiplexing process preventing the multiplexing of UCI on a disabled codeword (202d) or on a codeword (502a, 803a) with a reserved MCS based on the value of the reserved modulation and coding scheme MCS.

2. The method of claim 1, wherein the control signaling instructs the multi-codeword PUSCH to include the disabled codeword (202d) in the PUSCH retransmission.

3. The method of claim 2, wherein sending (316) the PUSCH retransmission further comprises: Send (316) the UCI multiplexed on the enabled codeword (202c) of the multi-codeword PUSCH to the network entity (104).

4. The method of claim 2, wherein the UCI multiplexing process comprises: When the control signaling schedules the UCI on the disabled codeword (202d), the UCI or data is discarded from the PUSCH retransmission.

5. The method of claim 1, wherein the control signaling instructs the multi-codeword PUSCH to include the codeword (502a, 803a) having the reserved MCS in the PUSCH retransmission.

6. The method of claim 5, wherein the UCI multiplexing process comprises: The UCI is multiplexed on the PUSCH retransmission based on a value different from the value of the reserved MCS, wherein the different value corresponds to at least one of the following: MCS of the initial transmitted codeword, The nominal MCS calculated from the reserved MCS, or Spectral efficiency (SE).

7. The method of claim 5, wherein the UCI multiplexing process comprises: When the control signaling schedules the UCI on the codeword (502a, 803a) with the reserved MCS, the UCI or data is discarded from the PUSCH retransmission.

8. The method of claim 5, wherein the UCI multiplexing process, based on the value of the reserved MCS, prevents the multiplexing of the UCI on the codeword (502a, 803a) having the reserved MCS, comprising: Send (316) the UCI multiplexed on each codeword (502b, 803a) of the multi-codeword PUSCH to the network entity (104).

9. The method of claim 5, further comprising: For the PUSCH retransmission, the UCI is multiplexed on the codeword indicated by the multi-codeword PUSCH, where the codeword is indicated by the control signaling.

10. The method of claim 5, further comprising: For the PUSCH retransmission, the UCI is multiplexed on the predefined codeword associated with the multi-codeword PUSCH.

11. The method of any one of claims 1 to 10, further comprising: Receive (308) from the network entity (104) for configuring the UCI multiplexing process on the PUSCH retransmission when the multi-codeword PUSCH includes at least one of the disabled codeword (202d) or the codeword (502a, 803a) having the reserved MCS.

12. The method of any one of claims 1 to 11, further comprising: Send (306) a UE capability report to the network entity (104), the UE capability report indicating the UE (102)’s ability to perform the UCI multiplexing process on the PUSCH retransmission when the multi-codeword PUSCH includes at least one of the disabled codeword (202d) or the codeword (502a, 803a) having the reserved MCS.

13. A method for wireless communication at a network entity (104), comprising: Send (312) control signaling to the user equipment (UE) (102) to schedule PUSCH retransmission of the multi-codeword physical uplink shared channel (PUSCH); as well as The UE (102) receives (316) a multi-codeword PUSCH based on an uplink control information (UCI) multiplexing process, wherein the UCI multiplexing process prevents the retransmission of the PUSCH on a disabled codeword (202d) or on a codeword (502a, 803a) with a reserved MCS based on the value of a reserved modulation and coding scheme (MCS).

14. The method of claim 13, wherein the control signaling instructs the multi-codeword PUSCH to include the disabled codeword (202d) in the PUSCH retransmission.

15. The method of claim 13, wherein the control signaling instructs the multi-codeword PUSCH to include the codeword (502a, 803a) having the reserved MCS in the PUSCH retransmission.

16. An apparatus for wireless communication, comprising a memory, a transceiver, and a processor, the processor being coupled to the memory and the transceiver, the apparatus being configured to implement the method as claimed in any one of claims 1 to 15.

Images