EP4674078A1

EP4674078A1 - Uci multiplexing on pusch with multi-codeword retransmission

Info

Publication number: EP4674078A1
Application number: EP23720732.9A
Authority: EP
Inventors: Jia-Hong Liou; Yushu Zhang
Original assignee: Google LLC
Current assignee: Google LLC
Priority date: 2023-03-31
Filing date: 2023-03-31
Publication date: 2026-01-07
Also published as: WO2024197771A1; CN120883552A

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for UCI multiplexing on a PUSCH retransmission. A UE (102) receives (312), from a network entity (104), control signaling scheduling a PUSCH retransmission for a multi-codeword PUSCH. The UE (102) transmits (316), to the network entity (104), the PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH. The UCI multiplexing procedure prevents UCI from being multiplexed on a disabled codeword (202d) or on a codeword (502a, 803a) with a reserved MCS based on a value of the reserved MCS.

Description

UCI MULTIPLEXING ON PUSCH WITH MULTI-CODEWORD RETRANSMISSION

TECHNICAL FIELD

The present disclosure relates generally to wireless communication, and more particularly, to uplink control information (UCI) multiplexing on a multi-codeword physical uplink shared channel (PUSCH) retransmission.

BACKGROUND

The Third Generation Partnership Project (3GPP) specifies a radio interface referred to as fifth generation (5G) new radio (NR) (5G NR) . An architecture for a 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN) , a user equipment (UE) , etc. The 5G NR architecture seeks to provide increased data rates, decreased latency, and/or increased capacity compared to prior generation cellular communication systems.
Wireless communication systems, in general, provide various telecommunication services (e.g., telephony, video, data, messaging, broadcasts, etc. ) based on multiple-access technologies, such as orthogonal frequency division multiple access (OFDMA) technologies, that support communication with multiple UEs. Improvements in mobile broadband continue the progression of such wireless communication technologies. For example, a UE can multiplex uplink control information (UCI) on allocated physical uplink shared channel (PUSCH) resources that overlap in time with physical uplink control channel (PUCCH) resources configured for UCI transmission. However, codewords of a multi-codeword PUSCH may have different characteristics on a PUSCH retransmission than on an initial PUSCH transmission.
BRIEF SUMMARY
The following presents a simplified summary of one or more aspects in order to provide a basic understanding of such aspects. This summary is not an extensive overview of all contemplated aspects. This summary neither identifies key or critical elements of all aspects nor delineates 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 description that is presented later.
A network entity, such as a base station or a unit of a base station, may configure a user equipment (UE) to transmit uplink control information (UCI) on physical uplink shared channel (PUSCH) resources when the PUSCH resources overlap in time with physical uplink control channel (PUCCH) resources associated with the UCI. In some examples, the network entity schedules data on an initial PUSCH transmission for a multi-codeword PUSCH. The network entity may also schedule data on a PUSCH retransmission for the multi-codeword PUSCH. For the PUSCH retransmission, the network entity may disable a codeword of the multi-codeword PUSCH or indicate that a codeword of the multi-codeword PUSCH includes a reserved modulation and coding scheme (MCS) .
The UE can multiplex the UCI on both the initial PUSCH transmission and the PUSCH retransmission of a multi-codeword PUSCH. For example, the UE may multiplex the UCI for the initial PUSCH transmission on a first scheduled codeword of the multi-codeword PUSCH or on a codeword with the highest MCS. However, for the PUSCH retransmission, the first scheduled codeword or the codeword with the highest MCS may be disabled. Thus, multiplexing the UCI on the disabled codeword may increase power consumption at the UE and/or a demodulation reference signal (DMRS) overhead, since the UE has to transmit DMRS from ports that map to the disabled codeword. Further, while higher MCS codewords are often associated with an improved channel quality, the UE may default to codewords that include the reserved MCS given that the reserved MCS typically has a higher index number than the non-reserved MCS. However, the reserved MCS may not always provide better performance than the non-reserved MCS.
Aspects of the present disclosure address the above-noted and other deficiencies by implementing a UCI multiplexing procedure for when a codeword of the multi-codeword PUSCH is disabled and/or for when the MCS for a codeword of the multi-codeword PUSCH includes a reserved MCS. That is, the UCI multiplexing procedure prevents the UCI from being multiplexed on the disabled codeword and/or on codewords with the reserved MCS. Avoiding the UCI multiplexing on the disabled codeword may improve performance by reducing DMRS overhead. Further, preventing the UCI multiplexing from being defaulted to codewords with a reserved MCS over codewords that include a non-reserved MCS may allow the UE to identify codewords for UCI multiplexing that can provide better performance.
According to some aspects, the UE receives, from the network entity, control signaling scheduling a PUSCH retransmission for a multi-codeword PUSCH. The UE transmits, to the network entity, the PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH. The UCI multiplexing procedure prevents the UCI from being multiplexed on a disabled codeword or on a codeword with reserved MCS based on a value of the reserved MCS.
According to some aspects, the network entity transmits, to the UE, control signaling scheduling a PUSCH retransmission for the multi-codeword PUSCH. The network entity receives, from the UE, the PUSCH retransmission based on the UCI multiplexing procedure for the multi-codeword PUSCH. The UCI multiplexing procedure prevents the UCI from being multiplexed on a disabled codeword or on a codeword with reserved MCS based on a value of the reserved MCS, as described above.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a diagram of a wireless communications system that includes a plurality of user equipments (UEs) and network entities in communication over one or more cells.
FIGs. 2A-2B illustrate diagrams associated with uplink control information (UCI) multiplexing on a physical uplink shared channel (PUSCH) .
FIG. 3 illustrates a signaling diagram for UCI multiplexing on a PUSCH with multi-codeword retransmission.
FIG. 4 illustrates a diagram for UCI multiplexing on an enabled/scheduled codeword.
FIG. 5 illustrates diagrams for UCI multiplexing when a reserved MCS is indicated for a codeword.
FIG. 6 illustrates diagrams for UCI multiplexing when a reserved MCS is indicated for a codeword.
FIG. 7 illustrates diagrams for UCI multiplexing based on a spectral efficiency when a reserved MCS is indicated for a codeword.
FIG. 8 illustrates diagrams for UCI multiplexing on each codeword of a multi-codeword PUSCH retransmission.
FIG. 9 is a flowchart of a method of wireless communication at a UE.
FIG. 10 is a flowchart of a method of wireless communication at a network entity.
FIG. 11 is a diagram illustrating a hardware implementation for an example UE apparatus.
FIG. 12 is a diagram illustrating a hardware implementation for one or more example network entities.

DETAILED DESCRIPTION

FIG. 1 illustrates a diagram 100 of a wireless communications system associated with a plurality of cells 190. The wireless communications system includes user equipments (UEs) 102 and base stations/network entities 104. Some base stations may include an aggregated base station architecture and other base stations may include a disaggregated base station architecture. The aggregated base station architecture utilizes a radio protocol stack that is physically or logically integrated within a single radio access network (RAN) node. A disaggregated base station architecture utilizes a protocol stack that is physically or logically distributed among two or more units (e.g., radio unit (RU) 106, distributed unit (DU) 108, central unit (CU) 110) . For example, a CU 110 is implemented within a RAN node, and one or more DUs 108 may be co-located with the CU 110, or alternatively, may be geographically or virtually distributed throughout one or multiple other RAN nodes. The DUs 108 may be implemented to communicate with one or more RUs 106. Any of the RU 106, the DU 108 and the CU 110 can be implemented as virtual units, such as a virtual radio unit (VRU) , a virtual distributed unit (VDU) , or a virtual central unit (VCU) . The base station/network entity 104 (e.g., an aggregated base station or disaggregated units of the base station, such as the RU 106 or the DU 108) , may be referred to as a transmission reception point (TRP) .
Operations of the base station 104 and/or network designs may be based on aggregation characteristics of base station functionality. For example, disaggregated base station architectures are utilized in an integrated access backhaul (IAB) network, an open-radio access network (O-RAN) network, or a virtualized radio access network (vRAN) , which may also be referred to a cloud radio access network (C-RAN) . Disaggregation may include distributing functionality across the two or more units at various physical locations, as well as distributing functionality for at least one unit virtually, which can enable flexibility in network designs. The various units of the disaggregated base station architecture, or the disaggregated RAN architecture, can be configured for wired or wireless communication with at least one other unit. For example, the base stations 104d/104e and/or the RUs 106a-106d may communicate with the UEs 102a-102d and 102s via one or more radio frequency (RF) access links based on a Uu interface. In examples, multiple RUs 106 and/or base stations 104 may simultaneously serve the UEs 102, such as by intra-cell and/or inter-cell access links between the UEs 102 and the RUs 106/base stations 104.
The RU 106, the DU 108, and the CU 110 may include (or may be coupled to) one or more interfaces configured to transmit or receive information/signals via a wired or wireless transmission medium. For example, a wired interface can be configured to transmit or receive the information/signals over a wired transmission medium, such as via the fronthaul link 160 between the RU 106d and the baseband unit (BBU) 112 of the base station 104d associated with the cell 190d. The BBU 112 includes a DU 108 and a CU 110, which may also have a wired interface (e.g., midhaul link) configured between the DU 108 and the CU 110 to transmit or receive the information/signals between the DU 108d and the CU 110d. In further examples, a wireless interface, which may include a receiver, a transmitter, or a transceiver, such as an RF transceiver, configured to transmit and/or receive the information/signals via the wireless transmission medium, such as for information communicated between the RU 106a of the cell 190a and the base station 104e of the cell 190e via cross-cell communication beams 136-138 of the RU 106a and the base station 104e.
The RUs 106 may be configured to implement lower layer functionality. For example, the RU 106 is controlled by the DU 108 and may correspond to a logical node that hosts RF processing functions, or lower layer PHY functionality, such as execution of fast Fourier transform (FFT) , inverse FFT (iFFT) , digital beamforming, physical random access channel (PRACH) extraction and filtering, etc. The functionality of the RU 106 may be based on the functional split, such as a functional split of lower layers.
The RUs 106 may transmit or receive over-the-air (OTA) communication with one or more UEs 102. For example, the RU 106b of the cell 190b communicates with the UE 102b of the cell 190b via a first set of communication beams 132 of the RU 106b and a second set of communication beams 134b of the UE 102b, which may correspond to inter-cell communication beams or, in some examples, cross-cell communication beams. For instance, the UE 102b of the cell 190b may communicate with the RU 106a of the cell 190a via a third set of communication beams 134a of the UE 102b and a fourth set of communication beams 136 of the RU 106a. DUs 108 can control both real-time and non-real-time features of control plane and user plane communications of the RUs 106.
Any combination of the RU 106, the DU 108, and the CU 110, or reference thereto individually, may correspond to a base station 104. Thus, the base station 104 may include at least one of the RU 106, the DU 108, or the CU 110. The base stations 104 provide the UEs 102 with access to a core network. The base stations 104 may relay communications between the UEs 102 and the core network (not shown) . The base stations 104 may be associated with macrocells for higher-power cellular base stations and/or small cells for lower-power cellular base stations. For example, the cell 190e may correspond to a macrocell, whereas the cells 190a-190d may correspond to small cells. Small cells include femtocells, picocells, microcells, etc. A network that includes at least one macrocell and at least one small cell may be referred to as a “heterogeneous network. ”
Transmissions from a UE 102 to a base station 104/RU 106 are referred to as uplink (UL) transmissions, whereas transmissions from the base station 104/RU 106 to the UE 102 are referred to as downlink (DL) transmissions. Uplink transmissions may also be referred to as reverse link transmissions and downlink transmissions may also be referred to as forward link transmissions. For example, the RU 106d utilizes antennas of the base station 104d of cell 190d to transmit a downlink/forward link communication to the UE 102d or receive an uplink/reverse link communication from the UE 102d based on the Uu interface associated with the access link between the UE 102d and the base station 104d/RU 106d.
Communication links between the UEs 102 and the base stations 104/RUs 106 may be based on multiple-input and multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and/or transmit diversity. The communication links may be associated with one or more carriers. The UEs 102 and the base stations 104/RUs 106 may utilize a spectrum bandwidth of Y MHz (e.g., 5, 10, 15, 20, 100, 400, 800, 1600, 2000, etc. MHz) per carrier allocated in a carrier aggregation of up to a total of Yx MHz, where x component carriers (CCs) are used for communication in each of the uplink and downlink directions. The carriers may or may not be adjacent to each other along a frequency spectrum. In examples, uplink and downlink carriers may be allocated in an asymmetric manner, with more or fewer carriers allocated to either the uplink or the downlink. A primary component carrier and one or more secondary component carriers may be included in the component carriers. The primary component carrier may be associated with a primary cell (PCell) and a secondary component carrier may be associated with a secondary cell (SCell) .
Some UEs 102, such as the UEs 102a and 102s, may perform device-to-device (D2D) communications over sidelink. For example, a sidelink communication/D2D link utilizes a spectrum for a wireless wide area network (WWAN) associated with uplink and downlink communications. Such sidelink/D2D communication may be performed through various wireless communications systems, such as wireless fidelity (Wi-Fi) systems, Bluetooth systems, Long Term Evolution (LTE) systems, New Radio (NR) systems, etc.
The electromagnetic spectrum is often subdivided into different classes, bands, channels, etc., based on different frequencies/wavelengths associated with the electromagnetic spectrum. Fifth-generation (5G) NR is generally associated with two operating frequency ranges (FRs) referred to as frequency range 1 (FR1) and frequency range 2 (FR2) . FR1 ranges from 410 MHz -7.125 GHz and FR2 ranges from 24.25 GHz -71.0 GHz, which includes FR2-1 (24.25 GHz -52.6 GHz) and FR2-2 (52.6 GHz -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, but a near subset of, the “extremely high frequency” (EHF) band, which ranges from 30 GHz -300 GHz and is sometimes also referred to as a “millimeter wave” band. Frequencies between FR1 and FR2 are often referred to as “mid-band” frequencies. The operating band for the mid-band frequencies may be referred to as frequency range 3 (FR3) , which ranges 7.125 GHz -24.25 GHz. Frequency bands within FR3 may include characteristics of FR1 and/or FR2. Hence, features of FR1 and/or FR2 may be extended into the mid-band frequencies. Higher operating frequency bands have been identified to extend 5G NR communications above 52.6 GHz associated with the upper limit of FR2. Three of these higher operating frequency bands include FR2-2, which ranges from 52.6 GHz -71.0 GHz, FR4, which ranges from 71.0 GHz -114.25 GHz, and FR5, which ranges from 114.25 GHz -300 GHz. The upper limit of FR5 corresponds to the upper limit of the EHF band. Thus, unless otherwise specifically stated herein, the term “sub-6 GHz” may refer to frequencies that are less than 6 GHz, within FR1, or may include the mid-band frequencies. Further, unless otherwise specifically stated herein, the term “millimeter wave” , or mmW, refers to frequencies that may include the mid-band frequencies, may be within FR2-1, FR4, FR2-2, and/or FR5, or may be within the EHF band.
The UEs 102 and the base stations 104/RUs 106 may each include a plurality of antennas. The plurality of antennas may correspond to antenna elements, antenna panels, and/or antenna arrays that may facilitate beamforming operations. For example, the RU 106b transmits a downlink beamformed signal based on a first set of communication beams 132 to the UE 102b in one or more transmit directions of the RU 106b. The UE 102b may receive the downlink beamformed signal based on a second set of communication beams 134b from the RU 106b in one or more receive directions of the UE 102b. In a further example, the UE 102b may also transmit an uplink beamformed signal (e.g., sounding reference signal (SRS) ) to the RU 106b based on the second set of communication beams 134b in one or more transmit directions of the UE 102b. The RU 106b may receive the uplink beamformed signal from the UE 102b in one or more receive directions of the RU 106b.
The UE 102b may perform beam training to determine the best receive and transmit directions for the beamformed signals. The transmit and receive directions for the UEs 102 and the base stations 104/RUs 106 may or may not be the same. In further examples, beamformed signals may be communicated between a first base station/RU 106a and a second base station 104e. For instance, the base station 104e of the cell 190e may transmit a beamformed signal to the RU 106a based on the communication beams 138 in one or more transmit directions of the base station 104e. The RU 106a may receive the beamformed signal from the base station 104e of the cell 190e based on the RU communication beams 136 in one or more receive directions of the RU 106a. In further examples, the base station 104e transmits a downlink beamformed signal to the UE 102e based on the communication beams 138 in one or more transmit directions of the base station 104e. The UE 102e receives the downlink beamformed signal from the base station 104e based on UE communication beams 130 in one or more receive directions of the UE 102e. The UE 102e may also transmit an uplink beamformed signal to the base station 104e based on the UE communication beams 130 in one or more transmit directions of the UE 102e, such that the base station 104e may receive the uplink beamformed signal from the UE 102e in one or more receive directions of the base station 104e.
The base station 104 may include and/or be referred to as a network entity. That is, “network entity” may refer to the base station 104 or at least one unit of the base station 104, such as the RU 106, the DU 108, and/or the CU 110. The base station 104 may also include and/or be referred to as a next generation evolved Node B (ng-eNB) , a next generation NB (gNB) , an evolved NB (eNB) , an access point, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a basic service set (BSS) , an extended service set (ESS) , a TRP, a network node, network equipment, or other related terminology. The base station 104 or an entity at the base station 104 can be implemented as an IAB node, a relay node, a sidelink node, an aggregated (monolithic) base station, or a disaggregated base station including one or more RUs 106, DUs 108, and/or CUs 110. A set of aggregated or disaggregated base stations may be referred to as a next generation-radio access network (NG-RAN) . In some examples, the UE 102a operates in dual connectivity (DC) with the base station 104e and the base station/RU 106a. In such cases, the base station 104e can be a master node and the base station/RU 160a can be a secondary node.
Uplink/downlink signaling may also be communicated via a satellite positioning system (SPS) 114. In an example, the SPS 114 of the cell 190c may be in communication with one or more UEs 102, such as the UE 102c, and one or more base stations 104/RUs 106, such as the RU 106c. The SPS 114 may correspond to one or more of a Global Navigation Satellite System (GNSS) , a global position system (GPS) , a non-terrestrial network (NTN) , or other satellite position/location system. The SPS 114 may be associated with LTE signals, NR signals (e.g., based on round trip time (RTT) and/or multi-RTT) , wireless local area network (WLAN) signals, a terrestrial beacon system (TBS) , sensor-based information, NR enhanced cell ID (NR E-CID) techniques, downlink angle-of-departure (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.
Still referring to FIG. 1, in certain aspects, any of the UEs 102 may include an uplink control information (UCI) multiplexing component 140 configured to receive, from a network entity, control signaling scheduling a physical uplink shared channel (PUSCH) retransmission for a multi-codeword PUSCH; and transmit, to the network entity, the PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH, the UCI multiplexing procedure preventing UCI from being multiplexed on a disabled codeword or on a codeword with a reserved modulation and coding scheme (MCS) based on a value of the reserved MCS.
In certain aspects, any of the base stations 104 or a network entity of the base stations 104 may include a PUSCH scheduling component 150 configured to transmit, to a UE, control signaling scheduling a PUSCH retransmission for a multi-codeword PUSCH; and receive, from the UE, the PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH, the UCI multiplexing procedure preventing UCI from being multiplexed on a disabled codeword or on a codeword with a reserved MCS based on a value of the reserved MCS.
Accordingly, FIG. 1 describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein. Further, although the following description may be focused on 5G NR, the concepts described herein may be applicable to other similar areas, such as 5G-Advanced and future versions, LTE, LTE-advanced (LTE-A) , and other wireless technologies, such as 6G.
FIGs. 2A-2B illustrate diagrams 200-250 associated with UCI multiplexing on a PUSCH. A network entity can configure a UE to transmit UCI on a physical uplink control channel (PUCCH) 204, such as in the diagram 200, or on PUSCH 202b, such as in the diagram 250, based on UCI multiplexing. The UCI may include a scheduling request, hybrid automatic repeat request-acknowledgement (HARQ-ACK) , and channel state information (CSI) . Thus, the UCI may have 7 permutations corresponding to 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 the scheduling request on the PUSCH 202. The CSI can also include CSI part 1 and CSI part 2, where the CSI part 2 supports variable lengths, such as CSI part 2-only, and may be punctured into two sections by a symbol with demodulation reference signal (DMRS) resource elements and data resource elements. If the network entity configures the UE to transmit the UCI on PUCCH 204 and data on PUSCH 202a in overlapped symbols, such as in the diagram 200, the UE may transmit the UCI on PUSCH 202b, such as in the diagram 250, based on UCI multiplexing. In addition, the network entity may also schedule the UE to report aperiodic CSI on PUSCH 202.
The network entity may schedule a data transmission on PUSCH 202 with one or more codewords. For example, the network entity may schedule an initial transmission for the one or more codewords, followed by one or more retransmissions of the one or more codewords. For a retransmission on PUSCH 202 that includes multiple codewords, the network entity may disable a codeword of the multiple codewords via downlink control information (DCI) . In other implementations for retransmission on PUSCH 202, the network entity may indicate an MCS for a codeword via the DCI. The reserved MCS may indicate an MCS greater than V, where V may be equal to 27 or 28 in some examples. The reserved MCS indicates the modulation order for the PUSCH transmission. Hence, the UE can transmit a transport block (TB) for the initial PUSCH transmission based on the modulation order indicated by the reserved MCS.
For an initial PUSCH transmission based on multiple codewords, the UE may multiplex the UCI with a first codeword of the multiple codewords or with the codeword having the higher MCS. The codeword with the higher MCS may have a better channel quality than the codeword with the lower MCS. Thus, transmission of the UCI on the codeword with the higher MCS may correspond to transmitting the UCI in a layer with a higher channel quality. However, for PUSCH retransmission, the first codeword of the multiple codewords or the codeword with the higher MCS may be disabled. If the UCI is multiplexed on the disabled codeword, the power consumption and/or DMRS overhead may be increased at the UE, given that the UE may still have to transmit the DMRS from the ports that are mapped to the disabled codeword.
The UE may have to implement techniques for transmitting UCI on a multi-codeword PUSCH when one of the codewords is disabled on retransmission. For example, if the UE determines to multiplex the UCI on PUSCH retransmission, the UE may implement a procedure for multiplexing the UCI on the codeword with the higher MCS, as an index for the reserved MCS is higher than the initial MCS. However, the codeword with the reserved MCS may not always provide the best performance for the UE. Therefore, the UE may also have to implement techniques for transmitting the UCI on a multi-codeword PUSCH when the MCS for at least one codeword is the reserved MCS.
Accordingly, the UE may perform UCI multiplexing on a multi-codeword PUSCH with at least one codeword of the multiple codewords being configured for PUSCH retransmission when one of the multiple codewords is disabled and/or when the MCS for one of the multiple codewords is the reserved MCS. Such techniques may avoid multiplexing the UCI on the disabled codeword, which can improve a performance of the PUSCH 202 by reducing the DMRS overhead, and/or may help to identify the codeword with the better channel quality to transmit the UCI when the MCS for at least one of the codewords is the reserved MCS, which can improve the performance of the UCI.
FIG. 3 illustrates a signaling diagram 300 for UCI multiplexing on PUSCH with multi-codeword retransmission. The UE 102 may transmit 306, to the network entity 104 (e.g., in a UE capability report) , a capability of the UE for UCI multiplexing on a multi-codeword PUSCH with retransmission. In other implementations, the network entity 104 may receive an indication of the UE capability from a core network, such as from an access and mobility management function (AMF) . In yet other implementations, the network entity 104 may receive the indication of the UE capability from another base station/network entity (e.g., a gNB or an eNB) .
The network entity 104 indicates 308, to the UE 102, a configuration for UCI multiplexing on the multi-codeword PUSCH, including a configuration for UCI multiplexing on PUSCH retransmission (e.g., based on the UE capability) . The network entity 104 may transmit 308 the configuration for the UCI multiplexing through control signaling. The network entity 104 may use RRC signaling to indicate an RRCReconfiguration message to the UE 102 or a system information block (SIB) , where the SIB may be a traditional type of SIB (e.g., SIB1) or a different SIB (e.g., SIB J, where J corresponds to an integer greater than 21) transmitted by the network entity 104. The network entity 104 may also transmit 308 the configuration for the UCI multiplexing through a medium access control-control element (MAC-CE) . The configuration for the UCI multiplexing on PUSCH retransmission may indicate multiplexing procedures for when a codeword of the multiple codewords is disabled and/or for when an indicated MCS for a codeword of the multiple codewords is a reserved MCS.
The UE 102 transmits 310, to the network entity 104, an initial PUSCH transmission from multiple codewords. The initial PUSCH transmission may be for a first HARQ process. The network entity 104 can transmit 312, to the UE 102, a DCI scheduling/triggering indication for the PUSCH retransmission of at least one codeword of the multiple codewords for the first HARQ process. The DCI scheduling/triggering indication may be for a PUSCH retransmission with a codeword of the multiple codewords disabled or for a PUSCH retransmission with a codeword of the multiple codewords having a reserved MCS. In some implementations, the UCI may be on a PUCCH that overlaps with a PUSCH in time-domain.
The UE 102 determines 314 a UCI multiplexing procedure on retransmission for the multi-codeword PUSCH. The determination 314 may be based on the configuration and/or the DCI scheduling/triggering indication. The UCI multiplexing procedure determined 314 by the UE 102 may correspond to: a first UCI multiplexing procedure for performing the PUSCH retransmission when a codeword of the multiple codewords is disabled, or a second UCI multiplexing procedure for performing the PUSCH retransmission when a codeword of the multiple codewords has the reserved MCS.
The UE 102 multiplexes and transmits 316, to the network entity 104, the PUSCH and the UCI based on the determined UCI multiplexing procedure. The network entity 104 may also determine the UCI multiplexing procedure that the UE 102 used to multiplex and transmit 316 the PUSCH and the UCI to the network entity 104 based on similar techniques as the UE 102. Such techniques may be indicated to the UE 102 (e.g., via the configuration 308) or based on predefined protocols. The network entity 104 decodes 318 the PUSCH and the UCI received 316 from the UE 102 based on the determined UCI multiplexing procedure.
FIG. 4 illustrates a diagram 400 for UCI multiplexing on an enabled/scheduled codeword (e.g., when another codeword of a multi-codeword PUSCH retransmission is disabled) . That is, a first PUSCH 202c may have an enabled/scheduled codeword with multiplexed UCI on retransmission, and a second PUSCH 202d may have a disabled codeword on retransmission. Thus, DCI scheduling from the network entity may be dedicated to the PUSCH 202c with the enabled codeword, and not used for the PUSCH 202d with the disabled codeword.
In some implementations, the UE transmits the UCI on a first enabled/scheduled codeword. In some 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, a codeword with the lowest codeword index may be used for the UCI multiplexing. That is, the first enabled/scheduled codeword with same/highest MCS is selected for the UCI multiplexing.
In some implementations for UCI multiplexing on PUSCH retransmission, if the UCI is to be multiplexed on the PUSCH 202d with the disabled codeword, the UE may drop the UCI or skip the UCI transmission. That is, the UE refrains from transmitting the UCI on the PUSCH 202d with the disabled codeword. Similarly, the network entity may refrain from receiving (e.g., scanning for) the UCI on the PUSCH 202d with the disabled codeword. The UE may also drop the data or skip transmission of the data, if the UCI is to be multiplexed on the PUSCH with the disabled codeword. For example, the UE may drop data, such as all the scheduled TBs associated with the PUSCH 202d.
The UE transmits the UCI on PUSCH 202c based on scheduling information (e.g., MCS and precoder information) for the codeword that is to be multiplexed. The UE can also transmit the UCI on PUSCH 202c based on scheduling information for the enabled/scheduled codeword. The enabled/scheduled codeword may be the first codeword of the multiple codewords or the codeword of the multiple codewords with the highest MCS. In some implementations, the UE may transmit the UCI on PUCCH resources configured or indicated by the network entity via RRC signaling, MAC-CE, or DCI, and then drop the PUSCH transmission.
In some implementations, the network entity may indicate a configurable UCI multiplexing procedure when one of the codewords is disabled. The network entity configures whether the UE will transmit the UCI on the enabled/scheduled codeword. If the network entity configures the UE to transmit the UCI on the enabled/scheduled codeword, the UE performs the UCI multiplexing on the PUSCH 202c. Otherwise, the UE may transmit the UCI on the PUSCH 202d with the disabled codeword, drop the UCI, transmit the UCI on a PUCCH, or transmit the UCI on the PUSCH 202d and drop the data.
The network entity may configure more than one option for UCI transmission. Alternatively, more than one option for the UCI transmission may be predefined for the UE. The UE can select one of the options to transmit the UCI. The network entity may perform blind detection to detect which option the UE selected for decoding the UCI transmission received from the UE.
The UE may transmit, to the network entity, a UE capability report that indicates whether the supports UCI multiplexing on a disabled codeword. If the UE does not support the UCI multiplexing on the disabled codeword, the UE may drop the UCI, transmit the UCI on PUCCH, or transmit the UCI on PUSCH 202d and drop the data when the UCI is to be multiplexed on the disabled codeword based on the UCI multiplexing scheme. Alternatively, the network entity may refrain from disabling the codeword when UCI is to be multiplexed for a multi-codeword PUSCH retransmission.
FIGs. 5-8 illustrate diagrams 500-850 for UCI multiplexing when a reserved MCS is indicated for a codeword. For example, in the diagram 500 of FIG. 5, the network entity indicates the MCSs for initial transmission of the second codeword 506a, and also indicates a reserved MCS for the second codeword 506a of the multiple codewords 506a-506b (e.g., on retransmission) . In particular, 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 reserved MCS = 29. The network entity 104 can also indicate non-reserved MCS for retransmission.
If the DCI scheduling indicates that the MCS for a codeword includes reserved MCS, the network entity and/or the UE may determine the codeword 502b for UCI multiplexing based on the MCS indicated for the codeword 506b and other MCS indicated in the scheduling DCI for other codewords (e.g., 506a) . In the diagram 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. Thus, the UE selects the first codeword 506b/502b for UCI multiplexing. If the MCS for the codewords 506a-506b are the same, the UE may select the first codeword 502b of the multiple codewords 502a-502b for UCI multiplexing.
In the diagram 600 of FIG. 6, the network entity indicates a reserved MCS for one of the codeword 606a of the multiple codewords 606a-606b, and the network entity and/or the UE determines a nominal MCS based on the indicated reserved MCS for the codeword 606a. In particular, the first codeword 606b has MCS = 18 and the second codeword 606a has nominal MCS = 8. The second codeword 606a also has reserved MCS = 29.
If the DCI scheduling indicates that the MCS for a codeword includes reserved MCS, the network entity and/or the UE may determine the codeword 502b for UCI multiplexing based on the MCS for the codeword 606b and the nominal MCS for the other codeword 606a. The network entity and/or the UE determine the nominal MCS based on a spectral efficiency (SE) for the retransmission codeword and the spectral efficiency for the non-reserved MCS using an MCS table. 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. Thus, the UE selects the first codeword 606b/502b for UCI multiplexing. If the MCS for the codewords 606a-606b are the same, the UE may select the first codeword 502b of the multiple codewords 502a-502b for UCI multiplexing.
The nominal MCS may be calculated based on the reserved MCS. In some implementations, the nominal MCS is based on an average SE calculated for each layer for the corresponding codeword and an MCS table. The network entity may select the nominal MCS based on the largest MCS in the MCS table corresponding to a SE that is less than or equal to the calculated SE. For example, if the calculated SE is 1.5 and, in the MCS table, the SE for MCS = 6 is 1.5, then MCS = 6 is selected as the nominal MCS. Alternatively, the network entity may select the nominal MCS based on the smallest MCS in the MCS table corresponding to a higher SE than the calculated SE. For example, if the calculated SE is 1.4 and, in the MCS table, the smallest MCS with a SE higher than 1.4 is MCS = 6, then MCS = 6 is selected as the nominal MCS.
The SE per layer may be calculated based on:
where B corresponds to a TB size for the codeword, N_L corresponds to a number of layers for the codeword, N_RE corresponds to a number of resource elements scheduled for the PUSCH, and N_o corresponds to an overhead for DMRS and other signals.
In the diagram 700 of FIG. 7, in addition to indicating the MCSs for the multiple codewords 706a-706b, the network entity indicates the SE for each of the multiple codewords 706a-706b as well as a reserved MCS for one of the codeword 706a of the multiple codewords 706a-706b. In particular, the first codeword 706b has SE = 2.73 and the second codeword 706a has SE = 1.6. The second codeword 706a also has reserved MCS = 29 and first codeword 706b has MCS = 18.
If the DCI scheduling indicates that the MCS for a codeword includes reserved MCS, the network entity and/or the UE may determine the codeword 502b for UCI multiplexing based on an actual SE for the codeword 706b (e.g., derived from the reserved MCS for the second codeword 706a and the indicated MCS for 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. Thus, 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, such that the UE selects the second codeword 706a for UCI multiplexing. If the MCS for the codewords 706a- 706b have the same SE, the UE may select the first codeword 502b of the multiple codewords 502a-502b for UCI multiplexing.
The UE may determine the SE based on an MCS table that is for an indicated MCS other than the reserved MCS. For the indicated MCS other than the reserved MCS, the UE may also determine the SE based of an actual transmission for the codeword, which may be the same as the SE determination for the reserved MCS. The UE can determine the UCI multiplexing based on the average SE per layer. The average SE per layer may be based on parameters such as a TB size for the codeword, a number of layers mapped to the codeword, resource elements for a PUSCH, and overhead for other signals. In examples, the SE per layer may be calculated based on:
The UE may also determine the UCI multiplexing based on the total SE across layers mapped to a codeword determined based on the parameters (e.g., the TB size for the codeword, the number of layers mapped to the codeword, the resource elements for the PUSCH, and the overhead for the other signals) . For example, the SE per layer may be based on:
In some implementations, if the DCI scheduling indicates that the MCS for a codeword includes reserved MCS, the UE drops the UCI. That is, the UE refrains from transmitting the UCI to the network entity on PUSCH. The network entity may similarly refrain from receiving (e.g., scanning for) the UCI on the PUSCH. In other implementations, if the DCI scheduling indicates that only one codeword may apply/use the reserved MCS, the UE drops the UCI transmission/multiplexing. If the DCI scheduling indicates that either or both codewords may apply/use the reserved MCS, the UE may select/uses the first codeword for the UCI transmission/multiplexing.
In further implementations, if the DCI scheduling indicates that the MCS for a codeword includes reserved MCS, the UE may drop the data. For example, the UE drops all scheduled TBs. The UE transmits the UCI on the PUSCH based on scheduling information (e.g., MCS and precoder) for the codeword that is to be multiplexed on the PUSCH. The UE may transmit the UCI on the PUSCH based on the scheduling information (e.g., MCS and precoder) for one of: the first enabled/scheduled codeword, or the enabled/scheduled codeword with a higher or lower MCS based on the implementation. In other implementations, the UE transmits the UCI on a PUCCH resource configured or indicated by the network entity via RRC signaling, MAC-CE, or DCI, and the UE drops/skips the PUSCH transmission.
In the diagram 800 of FIG. 8, the network entity indicates MCSs for the multiple codewords 806a-806b. In particular, the first codeword 806b has an MCS = 18 and the second codeword 806a has a reserved MCS = 29. If the DCI scheduling indicates that the MCS for a codeword includes reserved MCS, the UE may transmit the UCI on all of the scheduled codewords 502b/803a, as illustrated in the diagram 850. That is, the diagram 850 includes both a first codeword 502b with UCI and a second codeword 803a with UCI.
In some implementations, where the DCI scheduling indicates that the MCS for a codeword includes reserved MCS, the UE transmits the UCI on all the enabled codewords 502b/803a. The UE may also transmit the UCI as multiple repetitions on multiple respective codewords. In other implementations, the UE transmits different coded bits of the UCI on different codewords, such that the UE may apply a single channel coding scheme for the whole UCI. The UE may transmit different parts (e.g., source bits) of the UCI in different codewords or perform separate channel coding for the UCI per codeword. A portion or part of the UCI coded bits or source bits to be multiplexed on a codeword may be pre-indicated or preconfigured by the network entity to the UE.
If the DCI scheduling indicates that the MCS for a codeword includes reserved MCS, the network entity may an index to the codeword for UCI multiplexing. The network entity may indicate the codeword index by RRC signaling, MAC-CE, or DCI. In examples, a field in the DCI used to schedule the PUSCH retransmission may indicate the codeword index for the UCI multiplexing. In other examples, if the DCI scheduling indicates that the MCS for a codeword includes reserved MCS, the UE multiplexes the UCI on a predefined codeword (e.g., a first scheduled codeword of the multiple codewords) .
The network entity may configure a UCI multiplexing scheme, such as through RRC signaling, MAC-CE, or DCI, when the indicated MCS for a codeword is the reserved MCS. For periodic UCI or Type 1 configured grant PUSCH, the network entity may configure the UCI multiplexing scheme via RRC signaling. For semi-persistent UCI, the network entity may configure the UCI multiplexing scheme via MAC-CE. For aperiodic UCI, dynamic grant PUSCH, or Type 2 configured grant PUSCH, the network entity may configure the UCI multiplexing scheme in the DCI used to trigger the aperiodic UCI transmission or in the DCI used to trigger/activate the PUSCH.
The UCI multiplexing scheme/procedure may be determined based on the content or type of the UCI. The network entity and the UE may determine different UCI multiplexing procedures for different types of UCIs (e.g., HARQ-ACK, CSI, a beam report, etc. ) . The CSI may correspond to a CSI report without layer 1-refernce signal received power (L1-RSRP) /layer 1-signal-to-interfernce plus noise ratio (L1-SINR) information. The beam report may correspond to a CSI report with L1-RSRP/L1-SINR information.
The UE may report, to the network entity, a UE capability indicating whether the UE supports UCI multiplexing on PUSCH retransmission from multiple codewords with reserved MCS indicated for at least one of the multiple codewords. If the UE does not support the UE capability, the UE may drop either the UCI or the data. Similarly, the network entity may refrain from indicating reserved MCS for a codeword when UCI is to be multiplexed on a multi-codeword PUSCH. If the UE does support the UE capability for UCI multiplexing on PUSCH retransmission from multiple codewords with reserved MCS indicated for at least one of the multiple codewords, the UE may report the supported capability to the network entity. FIGs. 3-8 illustrate UCI multiplexing on a multi-codeword PUSCH retransmission. FIGs. 9-10 show methods for implementing one or more aspects of FIGs. 3-8. In particular, FIG. 9 shows an implementation by the UE 102 of the one or more aspects of FIGs. 3-8. FIG. 10 shows an implementation by the network entity 104 of the one or more aspects of FIGs. 3-8.
FIG. 9 illustrates a flowchart 900 of a method of wireless communication at a UE. With reference to FIGs. 1, 3, and 11, the method may be performed by the UE 102, the UE apparatus 1102, etc., which may include the memory 1126′, 1106′, 1116, and which may correspond to the entire UE 102 or the entire UE apparatus 1102, or a component of the UE 102 or the UE apparatus 1102, such as the wireless baseband processor 1126 and/or the application processor 1106.
The UE 102 transmits 906, to a network entity, a UE capability report indicating a capability of a UE for a UCI multiplexing procedure on a PUSCH retransmission when a multi-codeword PUSCH includes at least one of: a disabled codeword or a codeword with reserved MCS. For example, referring to FIG. 3, the UE 102 transmits 306, to the network entity 104, a UE capability for UCI multiplexing on a multi-codeword PUSCH with retransmission.
The UE 102 receives 908, from the network entity, a configuration for the UCI multiplexing procedure on the PUSCH retransmission when the multi-codeword PUSCH includes the at least one of: the disabled codeword or the codeword with the reserved MCS. For example, referring to FIG. 3, the UE 102 receives 308, from a network entity 104, a configuration for UCI multiplexing on the multi-codeword PUSCH (e.g., based on a disabled codeword or reserved MCS) .
The UE 102 receives 912, from a network entity, control signaling scheduling a PUSCH retransmission for a multi-codeword PUSCH. For example, referring to FIG. 3, the UE 102 receives 312, from the network entity 104, DCI scheduling for PUSCH retransmission of at least one codeword of the multiple codewords for the first HARQ process (e.g., based on the disabled codeword or reserved MCS) .
The UE 102 determines 914 the UCI multiplexing procedure. For example, referring to FIG. 3, the UE 102 determines 314 the UCI multiplexing procedure on retransmission for the multi-codeword PUSCH. The UE 102 may determine to multiplex 914a the UCI on the PUSCH retransmission, as illustrated in the diagrams 400-850 in FIGs. 4-8. Alternatively, the UE 102 may determine to drop 914b the UCI or data from the PUSCH retransmission when the control signaling schedules the UCI on the disabled codeword or based on the reserved MCS.
The UE 102 transmits 916, to the network entity, the PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH-the UCI multiplexing procedure prevents UCI from being multiplexed on a disabled codeword or on a codeword with a reserved MCS based on a value of the reserved MCS. For example, referring to FIG. 3, the UE 102 transmits 316, to the network entity 104, PUSCH and UCI based on the UCI multiplexing procedure. FIG. 9 describes a method from a UE-side of a wireless communication link, whereas FIG. 10 describes a method from a network-side of the wireless communication link.
FIG. 10 is a flowchart 1000 of a method of wireless communication at a network entity. With reference to FIGs. 1, 3, and 12, the method may be performed by one or more network entities 104, which may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, the CU 110, an RU processor 1206, a DU processor 1226, a CU processor 1246, etc. The one or more network entities 104 may include memory 1206'/1226'/1246', which may correspond to an entirety of the one or more network entities 104, or a component of the one or more network entities 104, such as the RU processor 1206, the DU processor 1226, or the CU processor 1246.
The network entity 104 receives 1006, from a UE, a UE capability report indicating a capability of the UE for a UCI multiplexing procedure on a PUSCH retransmission when a multi-codeword PUSCH includes at least one of: a disabled codeword or a codeword with reserved MCS. For example, referring to FIG. 3, the network entity 104 receives 306, from the UE 102, a UE capability for UCI multiplexing on a multi-codeword PUSCH with retransmission.
The network entity 104 transmits 1008, to the UE, a configuration for the UCI multiplexing procedure on the PUSCH retransmission when the multi-codeword PUSCH includes the at least one of: the disabled codeword or the codeword with the reserved MCS. For example, referring to FIG. 3, the network entity 104 transmits 308, to the UE 102, a configuration for UCI multiplexing on the multi-codeword PUSCH (e.g., based on a disabled codeword or reserved MCS) .
The network entity 104 transmits 1012, to the UE, control signaling scheduling the PUSCH retransmission for the multi-codeword PUSCH. For example, referring to FIG. 3, the network entity 104 transmits 312, to the UE 102, DCI scheduling for PUSCH retransmission of at least one codeword of the multiple codewords for the first HARQ process (e.g., based on the disabled codeword or reserved MCS) .
The network entity 104 receives 1016, from the UE, the PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH-the UCI multiplexing procedure prevents UCI from being multiplexed on a disabled codeword or on a codeword with a reserved MCS based on a value of the reserved MCS. For example, referring to FIG. 3, the network entity 104 receives 316, from the UE 102, PUSCH and UCI based on the UCI multiplexing procedure. A UE apparatus 1102, as described in FIG. 11, may perform the method of flowchart 900. The one or more network entities 104, as described in FIG. 12, may perform the method of flowchart 1000.
FIG. 11 is a diagram 1100 illustrating an example of a hardware implementation for a UE apparatus 1102. The UE apparatus 1102 may be the UE 102, a component of the UE 102, or may implement UE functionality. The UE apparatus 1102 may include an application processor 1106, which may have on-chip memory 1106'. In examples, the application processor 1106 may be coupled to a secure digital (SD) card 1108 and/or a display 1110. The application processor 1106 may also be coupled to a sensor (s) module 1112, a power supply 1114, an additional module of memory 1116, a camera 1118, and/or other related components. For example, the sensor (s) module 1112 may control a barometric pressure sensor/altimeter, a motion sensor such as an inertial management unit (IMU) , a gyroscope, accelerometer (s) , 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 used for positioning.
The UE apparatus 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′. Along with, and similar to, the application processor 1106, the wireless baseband processor 1126 may also be coupled to the sensor (s) module 1112, the power supply 1114, the additional module of memory 1116, the camera 1118, and/or other related components. The wireless baseband processor 1126 may be additionally coupled to one or more subscriber identity module (SIM) card (s) 1120 and/or one or more transceivers 1130 (e.g., wireless RF transceivers) .
Within the one or more transceivers 1130, the UE apparatus 1102 may include a Bluetooth module 1132, a WLAN module 1134, an SPS module 1136 (e.g., GNSS module) , and/or a cellular module 1138. The Bluetooth module 1132, the WLAN module 1134, the SPS module 1136, and the cellular module 1138 may each include an on-chip transceiver (TRX) , or in some cases, just a transmitter (TX) or just a receiver (RX) . The Bluetooth module 1132, the WLAN module 1134, the SPS module 1136, and the cellular module 1138 may each include dedicated antennas and/or utilize antennas 1140 for communication with one or more other nodes. For example, the UE apparatus 1102 can communicate through the transceiver (s) 1130 via the antennas 1140 with another UE (e.g., sidelink communication) and/or with a network entity 104 (e.g., uplink/downlink communication) , where the network entity 104 may correspond to a base station or a unit of the base station, such as the RU 106, the DU 108, or the CU 110.
The wireless baseband processor 1126 and the application processor 1106 may each include a computer-readable medium /memory 1126′, 1106′, respectively. The additional module of memory 1116 may also be considered a computer-readable medium /memory. Each computer-readable medium /memory 1126′, 1106′, 1116 may be non-transitory. The wireless baseband processor 1126 and the application processor 1106 may each be responsible for general processing, including execution of software stored on the computer-readable medium /memory 1126′, 1106′, 1116. The software, when executed by the wireless baseband processor 1126 /application processor 1106, causes the wireless baseband processor 1126 /application processor 1106 to perform the various functions described herein. The computer-readable medium /memory may also be used for storing data that is manipulated by the wireless baseband processor 1126 /application processor 1106 when executing the software. The wireless baseband processor 1126 /application processor 1106 may be a component of the UE 102. The UE apparatus 1102 may be a processor chip (e.g., modem and/or application) and include just the wireless baseband processor 1126 and/or the application processor 1106. In other examples, the UE apparatus 1102 may be the entire UE 102 and include the additional modules of the apparatus 1102.
As discussed in FIG. 1 and implemented with respect to FIG. 8, the UCI multiplexing component 140 is configured to receive, from a network entity, control signaling scheduling a PUSCH retransmission for a multi-codeword PUSCH; and transmit, to the network entity, the PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH, the UCI multiplexing procedure preventing UCI from being multiplexed on a disabled codeword or on a codeword with a reserved MCS based on a value of the reserved MCS. The UCI multiplexing component 140 may be within the application processor 1106 (e.g., at 140a) , the wireless baseband processor 1126 (e.g., at 140b) , or both the application processor 1106 and the wireless baseband processor 1126. The UCI multiplexing component 140a-140b may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by the one or more processors, or a combination thereof.
FIG. 12 is a diagram 1200 illustrating an example of a hardware implementation for 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 functionality. The one or more network entities 104 may include, or may correspond to, at least one of the RU 106, the DU, 108, or the CU 110. The CU 110 may include a CU processor 1246, which may have on-chip memory 1246′. In some aspects, the CU 110 may further include an additional module of memory 1256 and/or a communications interface 1248, both of which may be coupled to the CU processor 1246. The CU 110 can communicate with the DU 108 through a midhaul link 162, such as an F1 interface between the communications interface 1248 of the CU 110 and a communications interface 1228 of the DU 108.
The DU 108 may include a DU processor 1226, which may have on-chip memory 1226′. In some aspects, the DU 108 may further include an additional module of memory 1236 and/or the communications interface 1228, both of which may be coupled to the DU processor 1226. The DU 108 can communicate with the RU 106 through a fronthaul link 160 between the communications interface 1228 of the DU 108 and a communications interface 1208 of the RU 106.
The RU 106 may include an RU processor 1206, which may have on-chip memory 1206′. In some aspects, the RU 106 may further include an additional module of memory 1216, the communications interface 1208, and one or more transceivers 1230, all of which may be coupled to the RU processor 1206. The RU 106 may further include antennas 1240, which may be coupled to the one or more transceivers 1230, such that the RU 106 can communicate through the one or more transceivers 1230 via the antennas 1240 with the UE 102.
The on-chip memory 1206′, 1226′, 1246′ and the additional modules of memory 1216, 1236, 1256 may each be considered a computer-readable medium /memory. Each computer-readable medium /memory may be non-transitory. Each of the processors 1206, 1226, 1246 is responsible for general processing, including execution of software stored on the computer-readable medium /memory. The software, when executed by the corresponding processor (s) 1206, 1226, 1246 causes the processor (s) 1206, 1226, 1246 to perform the various functions described herein. The computer-readable medium /memory may also be used for storing data that is manipulated by the processor (s) 1206, 1226, 1246 when executing the software. In examples, the PUSCH scheduling component 150 may sit at any of the one or more network entities 104, such as at the CU 110; both the CU 110 and the DU 108; each of the CU 110, the DU 108, and the RU 106; the DU 108; both the DU 108 and the RU 106; or the RU 106.
As discussed in FIG. 1 and implemented with respect to FIG. 9, the PUSCH scheduling component 150 is configured to transmit, to a UE, control signaling scheduling a PUSCH retransmission for a multi-codeword PUSCH; and receive, from the UE, the PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH, the UCI multiplexing procedure preventing UCI from being multiplexed on a disabled codeword or on a codeword with a reserved MCS based on a value of the reserved MCS. The PUSCH scheduling component 150 may be within one or more processors of the one or more network entities 104, such as the RU processor 1206 (e.g., at 150a) , the DU processor 1226 (e.g., at 150b) , and/or the CU processor 1246 (e.g., at 150c) . The PUSCH scheduling component 150a-150c may be one or more hardware components specifically configured to carry out the stated processes/algorithm, implemented by one or more processors 1206, 1226, 1246 configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by the one or more processors 1206, 1226, 1246, or a combination thereof.
The specific order or hierarchy of blocks in the processes and flowcharts disclosed herein is an illustration of example approaches. Hence, the specific order or hierarchy of blocks in the processes and flowcharts may be rearranged. Some blocks may also be combined or deleted. Dashed lines may indicate optional elements of the diagrams. The accompanying method claims present elements of the various blocks in an example order, and are not limited to the specific order or hierarchy presented in the claims, processes, and flowcharts.
The detailed description set forth herein describes various configurations in connection with the drawings and does not represent the only configurations in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough explanation of various concepts. However, these concepts may be practiced without these specific details. In some instances, well known structures and components are shown in block diagram form in order to avoid obscuring such concepts.
Aspects of wireless communication systems, such as telecommunication systems, are presented with reference to various apparatuses and methods. These apparatuses and methods are described in the following detailed description and are illustrated in the accompanying drawings by various blocks, components, circuits, processes, call flows, systems, algorithms, etc. (collectively referred to as “elements” ) . These elements may be implemented using electronic hardware, computer software, or combinations thereof. Whether such elements are implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system.
An element, or any portion of an element, or any combination of elements may be implemented as a “processing system” that includes 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, systems-on-chip (SoC) , 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 functionality described throughout this disclosure. One or more processors in the processing system may execute software, which may be referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, or any combination thereof.
If the functionality described herein is implemented in software, the 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 includes computer storage media and can include a random-access memory (RAM) , a read-only memory (ROM) , an 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 instructions or data structures that can be accessed by a computer. Storage media may be any available media that can be accessed by a computer.
Aspects, implementations, and/or use cases described herein may be implemented across many differing platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, the aspects, implementations, and/or use cases may come about via integrated chip implementations and other non-module-component based devices, such as end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail/purchasing devices, medical devices, artificial intelligence (AI) -enabled devices, machine learning (ML) -enabled devices, etc. The aspects, implementations, and/or use cases may range from chip-level or modular components to non-modular or non-chip-level implementations, and further to aggregate, distributed, or original equipment manufacturer (OEM) devices or systems incorporating one or more techniques described herein.
Devices incorporating the aspects and features described herein may also include additional components and features for the implementation and practice of the claimed and described aspects and features. For example, transmission and reception of wireless signals necessarily includes a number of components for analog and digital purposes, such as hardware components, antennas, RF-chains, power amplifiers, modulators, buffers, processor (s) , interleavers, adders/summers, etc. Techniques described herein may be practiced in a wide variety of devices, chip-level components, systems, distributed arrangements, aggregated or disaggregated components, end-user devices, etc., of varying configurations.
The description herein is provided to enable a person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects. Thus, the claims are not limited to the aspects described herein, but are to be interpreted in view of the full scope of the present disclosure consistent with the language of the claims.
Reference to an element in the singular does not mean “one and only one” unless specifically stated, but rather “one or more. ” Terms such as “if, ” “when, ” and “while” do not imply an immediate temporal relationship or reaction. That is, these phrases, e.g., “when, ” do not imply an immediate action in response to or during the occurrence of an action, but simply imply that if a condition is met then an action will occur, but without requiring a specific or immediate time constraint for the action to occur. The terms “may” , “might” , and “can” , as used in this disclosure, often carry certain connotations. For example, “may” refers to a permissible feature that may or may not occur, “might” refers to a feature that probably occurs, and “can” refers to a capability (e.g., capable of) . The phrase “For example” often carries a similar connotation to “may” and, therefore, “may” is sometimes excluded from sentences that include “for example” or other similar phrases.
Unless specifically stated otherwise, the term “some” refers to 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 multiples of A, multiples of B, and/or multiples of C, or may include A only, B only, or C only. Sets should be interpreted as a set of elements where the elements number one or more.
Unless otherwise specifically indicated, ordinal terms such as “first” and “second” do not necessarily imply an order in time, sequence, numerical value, etc., but are used to distinguish between different instances of a term or phrase that follows each ordinal term. Reference numbers, as used in the specification and figures, are sometimes cross-referenced among drawings to denote same or similar features. A feature that is exactly the same in multiple drawings may be labeled with the same reference number in the multiple drawings. A feature that is similar among the multiple drawings, but not exactly the same, may be labeled with reference numbers that have different leading numbers, but have one or more of the same trailing numbers (e.g., 206, 306, 406, etc., may refer to similar features in the drawings) . Sometimes an “X” is used to universally denote multiple variations of a feature. For instance, “X06” can universally refer to all reference numbers that end in “06” (e.g., 206, 306, 406, etc. ) .
Structural and functional equivalents to elements of the various aspects described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and are encompassed by the claims. The words “module, ” “mechanism, ” “element, ” “device, ” and the like may not be a substitute for the word “means. ” As such, no claim element is to be construed as a means plus function unless the element is expressly recited using the phrase “means for. ” As used herein, the phrase “based on” shall not be construed as a reference to a closed set of information, one or more conditions, one or more factors, or the like. In other words, the phrase “based on A” , where “A” may be information, a condition, a factor, or the like, shall be construed as “based at least on A” unless specifically recited differently.
The following examples are illustrative only and may be combined with other examples or teachings described herein, without limitation.
Example 1 is a method of wireless communication at a UE, including: receiving, from a network entity, control signaling scheduling a PUSCH retransmission for a multi-codeword PUSCH; and transmitting, to the network entity, the PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH, the UCI multiplexing procedure preventing UCI from being multiplexed on a disabled codeword or on a codeword with a reserved MCS based on a value of the reserved MCS.
Example 2 may be combined with Example 1 and includes that the control signaling indicates that the multi-codeword PUSCH includes the disabled codeword on the PUSCH retransmission.
Example 3 may be combined with Example 2 and includes that the transmitting the PUSCH retransmission further includes: transmitting, to the network entity, the UCI multiplexed on an enabled codeword of the multi-codeword PUSCH.
Example 4 may be combined with Example 2 and includes that the UCI multiplexing procedure includes: dropping the UCI or data from the PUSCH retransmission when the control signaling schedules the UCI on the disabled codeword.
Example 5 may be combined with Example 1 and includes that the control signaling indicates that the multi-codeword PUSCH includes the codeword with the reserved MCS on the PUSCH retransmission.
Example 6 may be combined with Example 5 and includes that the UCI multiplexing procedure includes: multiplexing the UCI on the PUSCH retransmission based on a different value than the value of the reserved MCS, the different value corresponding to at least one of: an MCS for an initial transmission codeword, a nominal MCS calculated from the reserved MCS, or a spectral efficiency.
Example 7 may be combined with Example 5 and includes that the UCI multiplexing procedure includes: dropping the UCI or data from the PUSCH retransmission when the control signaling schedules the UCI on the codeword with the reserved MCS.
Example 8 may be combined with Example 5 and includes that the UCI multiplexing procedure preventing the UCI from being multiplexed on the codeword with the reserved MCS based on the value of the reserved MCS includes: transmitting, to the network entity, the UCI multiplexed on each codeword of the multi-codeword PUSCH.
Example 9 may be combined with Example 5 and further includes multiplexing, for the PUSCH retransmission, the UCI on an indicated codeword of the multi-codeword PUSCH, the indicated codeword being indicated by the control signaling.
Example 10 may be combined with Example 5 and further includes multiplexing, for the PUSCH retransmission, the UCI on a predefined codeword associated with the multi-codeword PUSCH.
Example 11 may be combined with any of Examples 1-10 and further includes receiving, from the network entity, a configuration for the UCI multiplexing procedure on the PUSCH retransmission when the multi-codeword PUSCH includes the at least one of: the disabled codeword or the codeword with the reserved MCS.
Example 12 may be combined with any of Examples 1-11 and further includes transmitting, to the network entity, a UE capability report indicating a capability of the UE for the UCI multiplexing procedure on the PUSCH retransmission when the multi-codeword PUSCH includes the at least one of: the disabled codeword or the codeword with the reserved MCS.
Example 13 is a method of wireless communication at a network entity, including: transmitting, to a UE, control signaling scheduling a PUSCH retransmission for a multi-codeword PUSCH; and receiving, from the UE, the PUSCH retransmission based on a UCI multiplexing procedure for the multi-codeword PUSCH, the UCI multiplexing procedure preventing UCI from being multiplexed on a disabled codeword or on a codeword with a reserved MCS based on a value of the reserved MCS.
Example 14 may be combined with Example 13 and includes that the control signaling indicates that the multi-codeword PUSCH includes the disabled codeword on the PUSCH retransmission.
Example 15 may be combined with Example 14 and includes that the receiving the PUSCH retransmission further includes: receiving, from the UE, the UCI multiplexed on an enabled codeword of the multi-codeword PUSCH.
Example 16 may be combined with Example 14 and includes that the PUSCH retransmission drops the UCI or data when the control signaling schedules the UCI on the disabled codeword.
Example 17 may be combined with Example 13 and includes that the control signaling indicates that the multi-codeword PUSCH includes the codeword with the reserved MCS on the PUSCH retransmission.
Example 18 may be combined with Example 17 and includes that the UCI is multiplexed on the PUSCH retransmission based on a different value than the value of the reserved MCS, the different value corresponding to at least one of: an MCS for an initial transmission codeword, a nominal MCS calculated from the reserved MCS, or a spectral efficiency.
Example 19 may be combined with Example 17 and includes that the PUSCH retransmission drops the UCI or data when the control signaling schedules the UCI on the codeword with the reserved MCS.
Example 20 may be combined with Example 17 and includes that the receiving the PUSCH retransmission includes: receiving, from the UE, the UCI multiplexed on each codeword of the multi-codeword PUSCH.
Example 21 may be combined with Example 17 and includes that the UCI is multiplexed on the PUSCH retransmission based on an indicated codeword of the multi-codeword PUSCH, the indicated codeword being indicated by the control signaling.
Example 22 may be combined with Example 17 and includes that the UCI is multiplexed on the PUSCH retransmission based on a predefined codeword associated with the multi-codeword PUSCH.
Example 23 may be combined with any of Examples 13-22 and further includes transmitting, to the UE, a configuration for the UCI multiplexing procedure on the PUSCH retransmission when the multi-codeword PUSCH includes the at least one of: the disabled codeword or the codeword with the reserved MCS.
Example 24 may be combined with any of Examples 13-23 and further includes receiving, from the UE, a UE capability report indicating a capability of the UE for the UCI multiplexing procedure on the PUSCH retransmission when the multi-codeword PUSCH includes the at least one of: the disabled codeword or the codeword with the reserved MCS.
Example 25 is an apparatus for wireless communication for implementing a method as in any of Examples 1-24.
Example 26 is an apparatus for wireless communication including means for implementing a method as in any of Examples 1-24.
Example 27 is a non-transitory computer-readable medium storing computer executable code, the code when executed by a processor causes the processor to implement a method as in any of Examples 1-24.

Claims

A method of wireless communication at a user equipment (UE) (102) , comprising:

receiving (312) , from a network entity (104) , control signaling scheduling a physical uplink shared channel (PUSCH) retransmission for a multi-codeword PUSCH; and

transmitting (316) , to the network entity (104) , the PUSCH retransmission based on an uplink control information (UCI) multiplexing procedure for the multi-codeword PUSCH, the UCI multiplexing procedure preventing UCI from being multiplexed on a disabled codeword (202d) or on a codeword (502a, 803a) with a reserved modulation and coding scheme (MCS) based on a value of the reserved MCS.
The method of claim 1, wherein the control signaling indicates that the multi-codeword PUSCH includes the disabled codeword (202d) on the PUSCH retransmission.
The method of claim 2, wherein the transmitting (316) the PUSCH retransmission further comprises:

transmitting (316) , to the network entity (104) , the UCI multiplexed on an enabled codeword (202c) of the multi-codeword PUSCH.
The method of claim 2, wherein the UCI multiplexing procedure comprises:

dropping the UCI or data from the PUSCH retransmission when the control signaling schedules the UCI on the disabled codeword (202d) .
The method of claim 1, wherein the control signaling indicates that the multi-codeword PUSCH includes the codeword (502a, 803a) with the reserved MCS on the PUSCH retransmission.
The method of claim 5, wherein the UCI multiplexing procedure comprises:

multiplexing the UCI on the PUSCH retransmission based on a different value than the value of the reserved MCS, the different value corresponding to at least one of:

an MCS for an initial transmission codeword,

a nominal MCS calculated from the reserved MCS, or

a spectral efficiency (SE) .
The method of claim 5, wherein the UCI multiplexing procedure comprises:

dropping the UCI or data from the PUSCH retransmission when the control signaling schedules the UCI on the codeword (502a, 803a) with the reserved MCS.
The method of claim 5, wherein the UCI multiplexing procedure preventing the UCI from being multiplexed on the codeword (502a, 803a) with the reserved MCS based on the value of the reserved MCS comprises:

transmitting (316) , to the network entity (104) , the UCI multiplexed on each codeword (502b, 803a) of the multi-codeword PUSCH.
The method of claim 5, further comprising:

multiplexing, for the PUSCH retransmission, the UCI on an indicated codeword of the multi-codeword PUSCH, the indicated codeword being indicated by the control signaling.
The method of claim 5, further comprising:

multiplexing, for the PUSCH retransmission, the UCI on a predefined codeword associated with the multi-codeword PUSCH.
The method of any of claims 1-10, further comprising:

receiving (308) , from the network entity (104) , a configuration for the UCI multiplexing procedure on the PUSCH retransmission when the multi-codeword PUSCH includes the at least one of: the disabled codeword (202d) or the codeword (502a, 803a) with the reserved MCS.
The method of any of claim 1-11, further comprising:

transmitting (306) , to the network entity (104) , a UE capability report indicating a capability of the UE (102) for the UCI multiplexing procedure on the PUSCH retransmission when the multi-codeword PUSCH includes the at least one of: the disabled codeword (202d) or the codeword (502a, 803a) with the reserved MCS.
A method of wireless communication at a network entity (104) , comprising:

transmitting (312) , to a user equipment (UE) (102) , control signaling scheduling a physical uplink shared channel (PUSCH) retransmission for a multi-codeword PUSCH; and

receiving (316) , from the UE (102) , the PUSCH retransmission based on an uplink control information (UCI) multiplexing procedure for the multi-codeword PUSCH, the UCI multiplexing procedure preventing UCI from being multiplexed on a disabled codeword (202d) or on a codeword (502a, 803a) with a reserved modulation and coding scheme (MCS) based on a value of the reserved MCS.
The method of claim 13, wherein the control signaling indicates that the multi-codeword PUSCH includes the disabled codeword (202d) on the PUSCH retransmission.
The method of claim 13, wherein the control signaling indicates that the multi-codeword PUSCH includes the codeword (502a, 803a) with the reserved MCS on the PUSCH retransmission.
An apparatus for wireless communication comprising a memory, a transceiver, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of claims 1-15.