WO2024187309A1

WO2024187309A1 - Method for pusch with codebook-based precoder cycling

Info

Publication number: WO2024187309A1
Application number: PCT/CN2023/080806
Authority: WO
Inventors: Yushu Zhang; Jia-Hong Liou
Original assignee: Google LLC
Current assignee: Google LLC
Priority date: 2023-03-10
Filing date: 2023-03-10
Publication date: 2024-09-19
Anticipated expiration: 2025-09-10
Also published as: CN120770126A

Abstract

This disclosure provides systems, devices, apparatus, and methods, including computer programs encoded on storage media, for a PUSCH transmission with codebook-based precoder cycling. A UE (102) receives (304), from a network entity, a control signaling indicating a plurality of precoders for a PUSCH transmission. The PUSCH transmission comprises a plurality of PUSCH portions. The UE transmits (312), to the network entity, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions.

Description

METHOD FOR PUSCH WITH CODEBOOK-BASED PRECODER CYCLING

TECHNICAL FIELD

The present disclosure relates generally to wireless communication, and more particularly, to physical uplink shared channel (PUSCH) transmission techniques.

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 precoder from a pre-defined codebook for the PUSCH transmission may not be suitable due to the UE’s movement, rotation, and/or blockage. Using the same precoder may lead to the degradation of the performance of the wireless communication systems.

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, can configure the transmission scheme for a PUSCH transmission by a radio resource control (RRC) signaling. The transmission scheme may be a codebook-based transmission scheme or non-codebook based transmission scheme. For the codebook-based transmission scheme, the network entity may indicate a precoder from a pre-defined codebook for the PUSCH transmission. A user equipment (UE) may transmit the PUSCH transmission using the precoder based on the pre-defined codebook.

As a result of the UE’s movement, rotation, and/or blockage, the antenna port (s) with better channel energy for the PUSCH transmission may change. The precoder may be based on a combination of one or more antenna ports or a selection of one or more antenna ports from the configured antenna ports. Thus, the precoder may not be suitable in view of the change of the antenna port (s) with better channel energy for the PUSCH transmission. Using the same precoder may lead to the degradation of the performance of the wireless communication systems.

The present disclosure addresses the above-noted and other deficiencies by transmitting the PUSCH transmission with codebook-based precoder cycling. For example, the UE transmits the PUSCH transmission with a set of precoders. The set of precoders includes different precoders that may be applied to different portions of the PUSCH transmission. The codebook-based precoder cycling may include antenna port cycling, layer permutation, multiple precoder sets, multiple precoder indications and/or other precoder cycling configurations. In some examples, the UE reports one or more capabilities indicating one or more supported precoder cycling configurations for the PUSCH transmission. Based on the UE capability, the network entity transmits a RRC signaling, which configures the PUSCH transmission scheme as a codebook-based precoder cycling transmission scheme. In the RRC signaling, the network entity may configure one or more parameters on the mapping of the set of precoders and PUSCH portions. The network entity may indicate one or more parameters configuring antenna port cycling, layer permutation, a precoder set from a list of precoder sets, and/or multiple precoder indications, e.g., in the RRC signaling or a downlink control information (DCI) signaling. For each portion of the PUSCH, the UE may determine a precoder of the set of precoders to be applied to a respective portion of the PUSCH. Then, the UE transmits the PUSCH transmission with the determined set of precoders.

According to some aspects, a UE receives, from a network entity, a control signaling indicating a plurality of precoders for a PUSCH transmission. The PUSCH transmission comprises a plurality of PUSCH portions. The UE transmits, to the network entity, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions.

According to some aspects, a network entity transmits, to a UE, a control signaling indicating a plurality of precoders for a PUSCH transmission. The PUSCH transmission comprises a plurality of PUSCH portions. The network entity receives, from the UE, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions.

Advantageously, the codebook-based precoder cycling improves the reliability of the PUSCH transmission. Because the UE transmits the PUSCH transmission with different precoders, the reliability of the PUSCH transmission is increased in the scenario of the UE’s movement, rotation and/or blockage. By transmitting the PUSCH transmission with codebook-based precoder cycling, the overall performance of the wireless communication system is improved, especially for the PUSCH transmission carrying the traffic with higher reliability requirement.

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.

FIG. 2 is a diagram illustrating an example of a change of antenna port (s) with better channel energy due to UE’s movement or rotation.

FIG. 3 is a signaling diagram illustrating an example of communications between a user equipment (UE) and a network entity for a PUSCH transmission with codebook-based precoder cycling.

FIG. 4 is a flow diagram illustrating an example of UE behavior for the PUSCH transmission with codebook-based precoder cycling.

FIG. 5 is a flow diagram illustrating an example of network entity behavior for the PUSCH transmission with codebook-based precoder cycling.

FIG. 6 is a diagram illustrating an example of a mapping of precoders and PUSCH portions for the PUSCH transmission with codebook-based precoder cycling based on PRB bundles.

FIG. 7 is a diagram illustrating an example of a mapping of precoders and PUSCH portions for the PUSCH transmission with codebook-based precoder cycling based on transmission occasions.

FIGs. 8A-8B are diagrams illustrating an example of a mapping of indicated precoders and a nominal PUSCH transmission for the PUSCH transmission with codebook-based precoder cycling.

FIGs. 9A-9B are diagrams illustrating an example of a mapping of indicated precoders and an actual PUSCH transmission for the PUSCH transmission with codebook-based precoder cycling.

FIG. 10 is a diagram illustrating an example of a mapping of the precoders and PUSCH portions based on PRB bundles and transmission occasions with a frequency-first mapping scheme for the PUSCH transmission with codebook-based precoder cycling.

FIG. 11 is a diagram illustrating an example of a mapping of the precoders and PUSCH portions based on PRB bundles and transmission occasions with a time-first mapping scheme for the PUSCH transmission with codebook-based precoder cycling.

FIG. 12 is a diagram illustrating an example of antenna port cycling based precoder cycling for the PUSCH transmission with codebook-based precoder cycling.

FIG. 13 is a diagram illustrating an example of layer permutation based precoder cycling for the PUSCH transmission with codebook-based precoder cycling.

FIG. 14 is a diagram illustrating an example of a precoder set based precoder cycling for the PUSCH transmission with codebook-based precoder cycling.

FIG. 15 is a diagram illustrating an example of a precoder list indication based precoder cycling for the PUSCH transmission with codebook-based precoder cycling.

FIG. 16 is a flowchart of a method of wireless communication at a UE for the PUSCH transmission with codebook-based precoder cycling.

FIG. 17 is a flowchart of a method of wireless communication at a network entity for the PUSCH transmission with codebook-based precoder cycling.

FIG. 18 is a diagram illustrating a hardware implementation for an example UE apparatus.

FIG. 19 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 108 and the CU 110. 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 114 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 might or might 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 a precoder cycling component 140 configured to receive, from a network entity, a control signaling indicating a plurality of precoders for a PUSCH transmission. The PUSCH transmission comprises a plurality of PUSCH portions. The precoder cycling component 140 is further configured to transmit, to the network entity, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions.

In certain aspects, any of the base stations 104 or a network entity of the base stations 104 may include a configuration component 150 configured to transmit, to a UE, a control signaling indicating a plurality of precoders for a PUSCH transmission. The PUSCH transmission comprises a plurality of PUSCH portions. The configuration component 150 is further configured to receive, from the UE, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions.

Accordingly, FIG. 1 describes a wireless communication system that may be implemented in connection with aspects of one or more other figures described herein, such as aspects illustrated in FIGs. 2-19. 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.

FIG. 2 is a diagram 200 illustrating an example of a change of antenna port (s) with better channel energy due to UE’s movement or rotation. A UE 102 may move from one location to another location, and rotate its orientation. One or more obstacles may create blockage to block the communication between the UE 102 and a network entity 104. As a result of UE’s movement, rotation or blockage, the best antenna port (s) and/or associated precoder for the PUSCH transmission may change. The best antenna port (s) may refer to antenna port (s) with better channel energy for a PUSCH transmission. Referring to Figure 2, when the UE 102 is at a first location 201, the antenna ports with better channel energy for the PUSCH transmission may be antenna port 211B and 211D. However, when the UE 102 moves to a second location 202 and rotates to a different angle of orientation, the antenna ports with better channel energy for the PUSCH transmission may change to antenna port 211A and 211C. A precoder may be based on a combination of antenna ports from one or more antenna ports or a selection of antenna ports from the configured antenna ports. Thus, the precoder may not be suitable in view of the change of the antenna port (s) with better channel energy for the PUSCH transmission. Using the same precoder may lead to the degradation of the performance of the wireless communication systems.

The PUSCH transmission with codebook-based precoder cycling disclosed herein improves the reliability of the PUSCH transmission. For example, the UE transmits the PUSCH transmission with a set of precoders. The set of precoders includes different precoders that may be applied to different portions of the PUSCH transmission. The codebook-based precoder cycling may include antenna port cycling, layer permutation, multiple precoder sets, multiple precoder indications and/or other precoder cycling configurations.

Because the UE transmits the PUSCH transmission with different precoders, the reliability of the PUSCH transmission is increased in the scenario of the UE’s movement, rotation and/or blockage. Based on the codebook-based precoder cycling, the overall performance of the wireless communication system is improved, especially for the PUSCH transmission carrying the traffic with higher reliability requirement.

FIG. 3 is a signaling diagram 300 illustrating an example of communications between a UE 102 and a network entity 104 for a PUSCH transmission with codebook-based precoder cycling. The network entity 104 may correspond to a base station or a unit of a base station, such as the RU 106, the DU 108, the CU 110, etc. Referring to FIG. 3, the UE 102 may transmit 302 a UE capability report including one or more supported precoder cycling configurations based on a codebook for the PUSCH transmission with codebook-based precoder cycling. The precoder cycling may refer to transmitting the PUSCH transmission with different precoders, e.g., cycling through a set of precoders. The one or more supported precoder cycling configurations may include an antenna port cycling configuration, a layer permutation configuration, a precoder set configuration, a multiple precoder indication configuration, or a combination thereof, which will be discussed below in connection with FIGs. 12-15. In some other implementations, the network entity may receive the one or more capabilities from a core network (e.g., Access and Mobility Management Function (AMF) ) . In yet some other implementations, the network entity may receive the one or more capabilities from another base station (e.g., gNB or eNB) .

Based on the UE capability, the network entity 104 transmits 304 a RRC signaling, e.g., RRCReconfiguration for RRC (re) configuration, which indicates a set of precoders (e.g., multiple precoders) and configures the PUSCH transmission scheme as a codebook-based precoder cycling transmission scheme. The PUSCH transmission may include multiple PUSCH portions. In the RRC signaling, the network entity may configure one or more parameters on a mapping of the set of precoders (e.g., multiple precoders) and the multiple PUSCH portions. The network entity 104 may further configure the set of precoders (e.g., multiple precoders) for the PUSCH transmission with codebook-based precoder cycling based on a precoder cycling configuration. The precoder cycling configuration may include an antenna port cycling configuration, a layer permutation configuration, a precoder set configuration, a multiple precoder indication configuration, or a combination thereof. For configured-grant PUSCH (CG-PUSCH) , the network entity may configure an uplink grant for the PUSCH transmission indicating the set of precoders (e.g., multiple precoders) with at least one of: the parameter (s) configuring antenna port cycling, parameter (s) configuring layer permutation, and/or parameter (s) configuring the set of precoders (e.g., multiple precoders) (e.g., a precoder set of a list of precoder sets, or multiple precoder indications) in the RRC signaling.

In some examples, the network entity 104 transmits 306 a medium access control (MAC) control element (CE) signaling including at least one parameter configuring the set of precoders.

For dynamic-grant PUSCH (DG-PUSCH) , the network entity 104 may further transmit 308 a DCI signaling scheduling the PUSCH transmission. In the DCI signaling, the network entity 104 may additionally indicate at least one of: the parameter (s) configuring antenna port cycling, parameter (s) configuring layer permutation, and/or parameter (s) configuring the set of precoders (e.g., a precoder set of a list of precoder sets, or multiple precoder indications) .

Then the UE 102 may determine 310, for each portion of the configured or scheduled PUSCH, determine a precoder of the set of precoders (e.g., multiple precoders) to be applied for a respective PUSCH portion based on the received RRC signaling and/or DCI signaling.

Afterwards, the UE 102 transmits 312 the PUSCH transmission with the determined set of precoders (e.g., multiple precoders) . The network entity 104 receives 312 the PUSCH transmission with the determined set of precoders (e.g., multiple precoders) . Because the UE 102 transmits 312 the PUSCH transmission with different precoders, e.g., cycling through the set of precoders, the reliability of the PUSCH transmission is increased in the scenario of the UE’s movement, rotation and/or blockage.

In some examples, the network entity 104 transmits 304 the RRC signaling configuring the set of precoders for the PUSCH transmission to a single TRP for a single transmission and reception point (TRP) operation of the UE 102. In the single TRP operation, the network entity 104 may configure or indicate one sounding reference signal resource indicator (SRI) by the RRC signaling or DCI signaling. Then, the UE 102 transmits 312 the multiple PUSCH portions of the PUSCH transmission with the set of precoders (e.g., multiple precoders) to the single TRP. The multiple PUSCH portions with the set of precoders (e.g., multiple precoders) are transmitted to the same TRP based on the same uplink power control parameters. Thus, the multiple PUSCH portions with the set of precoders (e.g., multiple precoders) precoders are transmitted with the same power level, not multiple power levels. The UE 102 transmits 312 the multiple PUSCH portions with multiple precoders to the single TRP to avoid the situation that one precoder may become not suitable due to the UE’s movement, rotation and/or blockage.

In some other examples, the network entity 104 transmits 304 the RRC signaling configuring more than one set of precoders (e.g., multiple sets of precoders) for the PUSCH transmission to multiple TRPs for a multiple TRP operation of the UE 102, where each set of precoders includes more than one precoder (e.g., multiple precoders) . In the multiple TRP operation, the network entity 104 configures or indicates more than one SRI (e.g., multiple SRIs) by the RRC signaling or DCI signaling. The PUSCH transmission includes multiple sets of PUSCH portions, where each set of PUSCH portions includes multiple PUSCH portions. Then, the UE 102 transmits 312 the multiple sets of PUSCH portions of the PUSCH transmission with the multiple sets of precoders to the multiple TRPs for the multiple TRP operation. For each TRP of the multiple TRPs, the UE transmits a set of PUSCH portions of the multiple PUSCH portions with a set of precoders of the multiple precoders based on the same power control parameters. Thus, for a respective TRP, the set of PUSCH portions of the multiple PUSCH portions with the set of precoders of the multiple precoders are transmitted with the same power level, not multiple power levels. For the multiple TRPs, the multiple sets of PUSCH portions with the multiple sets of precoders are transmitted based on multiple sets of power control parameters. Thus, different sets of PUSCH portions with different sets of precoders are transmitted to different TRPs with different power levels.

By transmitting the PUSCH transmission with codebook-based precoder cycling, the overall performance of the wireless communication system is improved, especially for the PUSCH transmission carrying the traffic with higher reliability requirement. FIG. 4 illustrates the UE behavior for the PUSCH transmission with codebook-based precoder cycling. FIG. 5 illustrates the network entity behavior for the PUSCH transmission with codebook-based precoder cycling.

FIG. 4 is a flow diagram 400 illustrating an example of UE behavior for the PUSCH transmission with codebook-based precoder cycling. Referring to FIG. 4, the UE 102 may transmit 402 a UE capability report including one or more supported precoder cycling configurations based on a codebook for the PUSCH transmission with codebook-based precoder cycling. The one or more precoder cycling configurations may include an antenna port cycling configuration, a layer permutation configuration, a precoder set configuration, a multiple precoder indication configuration, or a combination thereof, which will discussed below in connection with FIGs. 12-15.

Based on the UE capability, the UE 102 receives 404 a RRC signaling, e.g., RRCReconfiguration for RRC (re) configuration, which indicates a set of precoders (e.g., multiple precoders) and configures the PUSCH transmission scheme as a codebook-based precoder cycling transmission scheme. The PUSCH transmission may include multiple PUSCH portions. In the RRC signaling, the network entity may configure one or more parameters on a mapping of the multiple precoders and the multiple PUSCH portions. The RRC signaling may further configure the multiple precoders, e.g., a set of precoders, for the PUSCH transmission with codebook-based precoder cycling based on a precoder cycling configuration. The precoder cycling configuration may include an antenna port cycling configuration, a layer permutation configuration, a precoder set configuration, a multiple precoder indication configuration, or a combination thereof. For configured-grant PUSCH (CG-PUSCH) , the RRC signaling may configure an uplink grant for the PUSCH transmission indicating a set of precoders (e.g., multiple precoders) with at least one of: the parameter (s) configuring antenna port cycling, parameter (s) configuring layer permutation, and/or parameter (s) configuring the multiple precoders (e.g., a precoder set of a list of precoder sets, or multiple precoder indications) .

In some examples, the UE 102 receives 406 a MAC CE signaling including at least one parameter configuring the set of precoders.

For dynamic-grant PUSCH (DG-PUSCH) , the UE 102 may further receive 408 a DCI signaling scheduling the PUSCH transmission. In the DCI signaling, the network entity 104 may additionally indicate at least one of: the parameter (s) configuring antenna port cycling, parameter (s) configuring layer permutation, and/or parameter (s) configuring the set of precoders (e.g., a precoder set of a list of precoder sets, or multiple precoder indications) .

Then the UE 102 may determine 410, for each portion of the configured or scheduled PUSCH, determine a precoder of the set of precoders to be applied for a respective PUSCH portion based on the received RRC signaling and/or DCI signaling.

Afterwards, the UE 102 transmits 412 the PUSCH transmission with the determined set of precoders. Because the UE 102 transmits 412 the PUSCH transmission with different precoders, e.g., cycling through the set of precoders, the reliability of the PUSCH transmission is increased in the scenario of the UE’s movement, rotation and/or blockage.

In some examples, the UE 102 transmits 412 the PUSCH transmission with the determined set of precoders (e.g., multiple precoders) to one TRP of the UE 102 with one power level. By transmitting the PUSCH transmission with codebook-based precoder cycling, the overall performance of the wireless communication system is improved, especially for the PUSCH transmission carrying the traffic with higher reliability requirement.

FIG. 5 is a flow diagram 500 illustrating an example of network entity behavior for PUSCH transmission with codebook-based precoder cycling. Referring to FIG. 5, the network entity 104 may receive 502 a UE capability report including one or more supported precoder cycling configurations based on a codebook for the PUSCH transmission with codebook-based precoder cycling. The one or more supported precoder cycling configurations may include an antenna port cycling configuration, a layer permutation configuration, a precoder set configuration, a multiple precoder indication configuration, or a combination thereof, which will be discussed below in connection with FIGs. 12-15. In some other implementations, the network entity may receive the one or more capabilities from a core network (e.g., Access and Mobility Management Function (AMF) ) . In yet some other implementations, the network entity may receive the one or more capabilities from another base station (e.g., gNB or eNB) .

Based on the UE capability, the network entity 104 transmits 504 a RRC signaling, e.g., RRCReconfiguration for RRC (re) configuration, which indicates a set of precoders (e.g., multiple precoders) and configures the PUSCH transmission scheme as a codebook-based precoder cycling transmission scheme. The PUSCH transmission may include multiple PUSCH portions. In the RRC signaling, the network entity may configure one or more parameters on a mapping of multiple precoders and the multiple PUSCH portions. The network entity 104 may further configure the set of precoders (e.g., multiple precoders) , for the PUSCH transmission with codebook-based precoder cycling based on a precoder cycling configuration. The precoder cycling configuration may include an antenna port cycling configuration, a layer permutation configuration, a precoder set configuration, a multiple precoder indication configuration, or a combination thereof. For configured-grant PUSCH (CG-PUSCH) , the network entity may configure an uplink grant for the PUSCH transmission indicating a set of precoders (e.g., multiple precoders) with at least one of: the parameter (s) configuring antenna port cycling, parameter (s) configuring layer permutation, and/or parameter (s) configuring the multiple precoders (e.g., a precoder set of a list of precoder sets, or multiple precoder indications) in the RRC signaling.

In some examples, the network entity 104 transmits 506 a MAC CE signaling including at least one parameter configuring the set of precoders (e.g., multiple precoders) .

For dynamic-grant PUSCH (DG-PUSCH) , the network entity 104 may further transmit 508 a DCI signaling scheduling the PUSCH transmission. In the DCI signaling, the network entity 104 may additionally indicate at least one of: the parameter (s) configuring antenna port cycling, parameter (s) configuring layer permutation, and/or parameter (s) configuring the multiple precoders (e.g., a precoder set of a list of precoder sets, or multiple precoder indications) .

Then, the network entity 104 receives 512 the PUSCH transmission with the determined set of precoders (e.g., multiple precoders) . Because network entity 104 receives 512 the PUSCH transmission with different precoders, e.g., cycling through the set of precoders, the reliability of the PUSCH transmission is increased in the scenario of the UE’s movement, rotation and/or blockage.

In some examples, the network entity 104 transmits 504 the RRC signaling configuring the set of precoders (e.g., multiple precoders) for a single TRP of the UE 102 with one power level. By receiving the PUSCH transmission with codebook-based precoder cycling, the overall performance of the wireless communication system is improved, especially for the PUSCH transmission carrying the traffic with higher reliability requirement. FIGs. 6-11 illustrates examples of the mapping of the multiple precoders and PUSCH portions for the PUSCH transmission with codebook-based precoder cycling.

FIG. 6 is a diagram 600 illustrating an example of the mapping of the multiple precoders and PUSCH portions for the PUSCH transmission with codebook-based precoder cycling based on physical resource block (PRB) bundles. In some examples, the mapping of the multiple precoders and PUSCH portions may include a frequency division multiplexing (FDM) based mapping. The multiple PUSCH portions may include multiple PRB bundles. The PUSCH transmission may include the multiple PRB bundles. The UE may transmit the PUSCH transmission with different precoders or different antenna ports in different sets of resource blocks (RBs) . The UE may transmit the PUSCH transmission in PRBs in a PRB bundle with the same precoder. The UE may apply different precoders for different PRB bundles. The network entity may configure the PRB bundles, for example, including the number of RBs in each PRB bundle, or the number of the PRB bundles in the PUSCH transmission.

Referring to FIG. 6, the PUSCH transmission 612 may include the multiple PRB bundles 605A, 605B, …, 605N. The UE may transmit the PUSCH transmission (e.g., 612) with different precoders (e.g., 611A, 611B, …, 611N) being applied for different PRB bundles (e.g., 605A, 605B, …, 605N) . The UE may transmit the PUSCH bundle 605A with precoder (or from antenna port set) 611A. The UE may transmit the PUSCH bundle 605B with precoder (or from antenna port set) 611B, and so on. The UE may transmit the PUSCH bundle 605N with precoder (or from antenna port set) 611N. The number of the multiple precoders for the PUSCH transmission may be N, which is an integer value, e.g., 2, 3, or any integer value which is more than two. The number of the multiple PRB bundles in the PUSCH transmission may be M, which is an integer value, e.g., 2, 3, or any integer value which is more than two. In this example, the number of the multiple precoders N for the PUSCH transmission is the same as the number of the multiple PRB bundles M.

In some examples, the network entity refrains from indicating the number of precoders N different from the number of PRB bundles M. In some examples, the network entity refrains from indicating more precoders than the number of PRB bundles. In some examples, the network entity refrains from indicating fewer precoders than the number of PRB bundles.

In some examples, if the number of indicated precoders N is smaller than the number of PRB bundles M, the UE may apply the N precoders to the first N PRB bundles. Then, the UE may apply the N precoders to the remaining M-N PRB bundles. In such examples, the first M-N precoders of the N precoders are applied to the remaining M-N PRB bundles (assuming M-N is less than N) , or the last M-N precoders of the N precoders are applied to the remaining M-N PRB bundles.

In some other examples, if the number of indicated precoders N is larger than the number of PRB bundles M, the UE may apply the first M precoders of the N precoders to the M PRB bundles. Alternatively, if the number of indicated precoders N is larger than the number of PRB bundles M, the UE may apply the last M precoders of the N precoders to the M PRB bundles.

In some examples, if the UE is able to transmit the PUSCH transmission with more than one spatial domain filters simultaneously, e.g., the UE supports more than one panel or the UE supports more than one indicated transmission configuration indicator (TCI) state for a PUSCH transmission occasion, the UE may apply more than one precoders per PRB bundle, where each precoder corresponds to one spatial domain filter; Otherwise, the UE may apply one precoder per PRB bundle.

In some examples, the network entity configures the (total) number of PRB bundles by the RRC signaling or the DCI signaling. The network entity may configure a single number of PRB bundles for all scheduled bandwidth. In some examples, the network entity may configure different number of PRB bundles for different sets of scheduled bandwidths. In one example, the network entity may configure the number of PRB bundles for 2 sets of scheduled bandwidths: small bandwidth (e.g., number of scheduled RBs is less than or equal to 50 RBs) and large bandwidth (e.g., number of scheduled RBs is more than 50 RBs) . The UE and network entity may further determine the number of PRB bundles for the PUSCH transmission based on the number of scheduled RBs. In one example, if the number of scheduled RBs is less than the configured number of PRB bundles, the number of PRB bundles is the same as the number of scheduled RBs.

In some examples, the PRBs in a PRB bundle are consecutive (e.g., contiguous) . In some other examples, the PRBs in a PRB bundle are non-consecutive (e.g., non-contiguous) . The PRBs may be distributed uniformly or non-uniformly in frequency domain.

In some examples, the network entity and UE determine the PRBs in a PRB bundle based on the number of PRB bundles and the number of scheduled PRBs. In one example, if a UE is scheduled with M PRB bundles and K PRBs, the number of PRBs for the first M-1 PRB bundles is floor (K/M) and the number of PRBs for the last PRB bundle is K- (M-1) floor (K/M) . Alternatively, if a UE is scheduled with M PRB bundles and K PRBs, the number of PRBs for the last M-1 PRB bundles is floor (K/M) and the number of PRBs for the first PRB bundle is K- (M-1) floor (K/M) .

In some other examples, the network entity configures or indicates the size of a PRB bundle by the RRC signaling or DCI signaling. The network entity may configure a single PRB bundle size for all scheduled bandwidth. In some examples, the network entity may configure different PRB bundle sizes for different sets of scheduled bandwidths. In one example, the network entity may configure the PRB bundle size for 2 sets of scheduled bandwidths: small bandwidth (e.g., number of scheduled RBs is less than or equal to 50 RBs) and large bandwidth (e.g., number of scheduled RBs is more than 50 RBs) . The network entity and UE may determine the number of PRB bundles based on the configured or indicated PRB bundle size and the scheduled RBs. In one example, if the PRB bundle size is P PRBs per PRB bundle and the UE is scheduled with K PRBs, the number of PRB bundles is ceil (K/P) .

In some examples, the mapping between the precoders and PRB bundle is predefined. For example, the first precoder is mapped to the first PRB bundle, and then the second precoder is mapped to the second PRB bundle. In some other examples, the mapping between the precoder and PRB bundle is configured by the network entity by the RRC signaling or DCI signaling. In one example, the network entity may configure the starting precoder, e.g., precoder k, to be applied to the first PRB bundle. Then the UE applies precoder k to the first PRB bundle, precoder { (k+1) mod N} for the second PRB bundle, etc. In another example, the network entity may configure or indicate the mapping order for the indicated precoders. In some other examples, the mapping between the precoder and PRB bundle is determined based on a symbol or slot index for the PUSCH transmission or a PUSCH repetition or transmission occasion. In one example, the starting precoder index k could be determined based on the symbol or slot index l, e.g., k = l mod N. In some other examples, the network entity configures the precoders and PRB bundle mapping scheme by the RRC signaling, MAC CE signaling or DCI signaling.

FIG. 7 is a diagram 700 illustrating an example of the mapping of precoders and PUSCH portions for the PUSCH transmission with codebook-based precoder cycling based on transmission occasions. In some examples, the mapping of the multiple precoders and PUSCH portions may include a time division multiplexing (TDM) based mapping. The multiple PUSCH portions may include multiple transmission occasions. The PUSCH transmission may include the multiple transmission occasions. The UE may transmit the PUSCH transmission with different precoders or different antenna ports in different transmission occasions. The network entity configures the UE to transmit the PUSCH transmission with more than one transmission occasions and the UE transmits different PUSCH transmission occasions with different precoders or different antenna ports. In some examples, the network entity may configure the UE to transmit at least one transport block (TB) repeatedly in each transmission occasion. In some examples, the network entity may configure the UE to transmit at least one TB across more than one transmission occasions. In some examples, the network entity may configure or indicate the UE to transmit different TBs in different transmission occasions, which may be scheduled by one DCI signaling.

Referring to FIG. 7, the PUSCH transmission 712 may include the multiple transmission occasions 707A, 707B, …, 707N. The UE may transmit the PUSCH transmission (e.g., 712) with different precoders (e.g., 711A, 711B, …, 711N) being applied for different transmission occasions (e.g., 707A, 707B, …, 707N) . The UE may transmit the transmission occasion 707A with precoder (or from antenna port set) 711A. The UE may transmit the transmission occasion 707B with precoder (or from antenna port set) 711B, and so on. The UE may transmit the transmission occasion 707N with precoder (or from antenna port set) 711N. The number of the multiple precoders for the PUSCH transmission may be N, which is an integer value, e.g., 2, 3, 4, or any integer value which is more than two. The number of the multiple transmission occasions in the PUSCH transmission may be O, which is an integer value, e.g., 2, 3, 4, or any integer value which is more than two. In this example, the number of the multiple precoders N for the PUSCH transmission is the same as the number of the multiple transmission occasions O.

In some examples, if the UE is able to transmit PUSCH with more than one spatial domain filter simultaneously, e.g., the UE supports more than one panel or the UE supports more than one indicated transmission configuration indicator (TCI) state for a PUSCH transmission occasion, the UE may apply more than one precoder per transmission occasion, where each precoder corresponds to one spatial domain filter; Otherwise, the UE may apply one precoder per transmission occasion.

In some examples, the mapping between the indicated precoders and the transmission occasion is predefined. The UE applies the precoder for the transmission occasion based on the order of the precoder. In one example, the UE applies the first precoder to the first transmission occasion, and then the second precoder to the second transmission occasion, etc. In some other examples, the mapping between the precoder and transmission occasion is configured by the network entity by the RRC signaling or DCI signaling. In one example, the network entity may configure the starting precoder, e.g., precoder k, to be applied to the first transmission occasion. Then if the network entity configures or indicates N precoders, the UE applies precoder k to the first transmission occasion, precoder { (k+1) mod N} for the second transmission occasion, etc. In another example, the network entity may configure or indicate the mapping order for the indicated precoders. In some other implementations, the mapping between the precoder and PRB bundle is determined based on a symbol or slot index for a PUSCH transmission. In one example, the starting precoder index k could be determined based on the symbol or slot index l for the first PUSCH transmission occasion, e.g., k = l mod N.

FIGs. 8A-8B are diagrams illustrating an example of the mapping of indicated precoders and a nominal PUSCH transmission for the PUSCH transmission with codebook-based precoder cycling. FIG. 8A illustrates a scheduled PUSCH transmission based on the received scheduling information. FIG. 8B illustrates an actual PUSCH transmission 812. In some examples, the mapping between the indicated precoders and PUSCH is based on the nominal transmission occasion. The nominal transmission occasion indicates the transmission occasion scheduled by the network entity, and the UE may refrain from transmitting some of the nominal transmissions as a result of collision with another uplink or downlink signal.

Referring to FIG. 8A, based on the received scheduling information, the UE is scheduled to transmit the transmission occasion 807A with precoder (or from antenna port set) 811A, to transmit the transmission occasion 807B with precoder (or from antenna port set) 811B, to transmit the transmission occasion 807C with precoder (or from antenna port set) 811C, and to transmit the transmission occasion 807D with precoder (or from antenna port set) 811D. However, the nominal transmission occasion 807C may collide with another uplink signal 809. Uplink collision handling 813 may require the UE to drop the PUSCH transmission occasion 807C. The UE may drop the PUSCH transmission occasion 807C to avoid the uplink collision.

Referring to FIG. 8B, although the UE drops the PUSCH transmission occasion 807C, the mapping between the indicated precoders (807A, 807B, 807C, 807D) and PUSCH transmission occasions (811A, 811B, 811C, 811D) is based on the nominal transmission occasion 807C. In the actual PUSCH transmission 812, the UE still transmits the transmission occasion 807D with precoder (or from antenna port set) 811D, skipping precoder (or from antenna port set) 811C.

FIG. 9A-9B are diagrams illustrating an example of a mapping of indicated precoders and an actual PUSCH transmission for the PUSCH transmission with codebook-based precoder cycling. FIG. 9A illustrates a scheduled PUSCH transmission based on the received scheduling information. FIG. 9B illustrates an actual PUSCH transmission 912. In some examples, the mapping between the indicated precoders and PUSCH transmission occasions is based on the actual transmission occasion. The actual transmission occasion indicates the PUSCH transmission occasion that is actually transmitted from the UE.

Referring to FIG. 9A, similarly as discussed above in connection with FIG. 8A, based on the received scheduling information, the UE is scheduled to transmit the transmission occasion 807A with precoder (or from antenna port set) 811A, to transmit the transmission occasion 807B with precoder (or from antenna port set) 811B, to transmit the transmission occasion 807C with precoder (or from antenna port set) 811C, and to transmit the transmission occasion 807D with precoder (or from antenna port set) 811D. However, the nominal transmission occasion 807C may collide with another uplink signal 909. Uplink collision handling 813 may require the UE to drop the PUSCH transmission occasion 807C. The UE may drop the PUSCH transmission occasion 807C to avoid the uplink collision.

Referring to FIG. 9B, after the UE drops the PUSCH transmission occasion 807C, the mapping between the indicated precoders (807A, 807B, 807C, 807D) and PUSCH transmission occasions (811A, 811B, 811C, 811D) is based on the actual transmission occasion. Because the UE drops the PUSCH transmission occasion 807C, the UE transmits the transmission occasion 807D with precoder (or from antenna port set) 811C, without skipping any precoder, in the actual PUSCH transmission 912.

In some examples, the network entity refrains from indicating the number of precoders different from the number of PUSCH transmission occasions. In some examples, the network entity refrains from indicating more precoders than the number of PUSCH transmission occasions. In some examples, the network entity refrains from indicating fewer precoders than the number of PUSCH transmission occasions. In some examples, if the number of indicated precoders N is smaller than the number of PUSCH transmission occasions O, the UE may apply the N precoders to the first or last N PUSCH transmission occasions. Then, the UE may apply the N precoders to the remaining O-N transmission occasions. In some other examples, if the number of indicated precoders N is larger than the number of transmission occasions O, the UE may apply the first or last O precoders to the O transmission occasions. In some other examples, the network entity configures the precoders and transmission occasion mapping scheme by the RRC signaling, MAC CE or DCI signaling.

FIG. 10 is a diagram 1000 illustrating an example of the mapping of the precoders and PUSCH portions based on PRB bundles and transmission occasions with a frequency-first mapping scheme for the PUSCH transmission with codebook-based precoder cycling. In some examples, the network entity configures the UE to transmit the PUSCH with more than one transmission occasions and more than one PRB bundles. The network entity configures or indicates more than one precoders by the RRC signaling or DCI signaling. The UE may transmit the PRB bundles in different transmission occasions by different precoders.

In some examples, the UE applies the precoders for the PRB bundles in the first transmission occasion at first. Then, the UE applies the precoders for the PRB bundles in the next transmission occasion, which may be referred to as a frequency-first mapping scheme.

Referring to FIG. 10, the UE transmits the PUSCH transmission with N (N=OM) precoders (e.g., antenna port sets) in O PUSCH transmission occasions from M PRB bundles with the frequency-first mapping scheme. The PUSCH transmission includes N PUSCH portions, where N (N=OM) precoders are applied to the N PUSCH portions. The UE may apply the precoders for the PRB bundles in the first transmission occasion at first. The UE may transmit the PUSCH portion 1012A with precoder (or from antenna port set) 1011A. The UE may transmit the PUSCH portion 1012B with precoder (or from antenna port set) 1011B, and so on. The UE may transmit the PUSCH portion 1012M with precoder (or from antenna port set) 1011M. Then, the UE applies the precoders for the PRB bundles in the second transmission occasion. The UE may transmit the PUSCH portion 1012 (M+1) with precoder (or from antenna port set) 1011 (M+1) . The UE may transmit the PUSCH portion 1012 (M+2) with precoder (or from antenna port set) 1011 (M+2) , and so on. The UE may transmit the PUSCH portion 1012 (2M) with precoder (or from antenna port set) 1011 (2M) . Then, the UE applies the precoders for the PRB bundles in the third transmission occasion, and so on. At last, the UE may transmit the PUSCH portion 1012 ( (O-1) M+1) with precoder (or from antenna port set) 1011 ( (O-1) M+1) . The UE may transmit the PUSCH portion 1012 ( (O-1) M+2) with precoder (or from antenna port set) 1011 ( (O-1) M+2) , and so on. The UE may transmit the PUSCH portion 1012 (OM) with precoder (or from antenna port set) 1011 (OM) .

FIG. 11 is a diagram 1100 illustrating an example of a mapping of the precoders and PUSCH portions based on PRB bundles and transmission occasions with a time-first mapping scheme for the PUSCH transmission with codebook-based precoder cycling. In some examples, the UE applies the precoders for first PRB bundle for all the transmission occasions first, and then precoders for the next PRB bundle for all the transmission occasions, which may be referred to as a time-first mapping scheme.

Referring to FIG. 11, the UE transmits the PUSCH transmission with N (N=OM) precoders (e.g., antenna port sets) in O PUSCH transmission occasions from M PRB bundles with the time-first mapping scheme. The PUSCH transmission includes N PUSCH portions, where N (N=OM) precoders are applied to the N PUSCH portions. The UE may apply the precoders for first PRB bundle for all the transmission occasions first. The UE may transmit the PUSCH portion 1112A with precoder (or from antenna port set) 1111A. The UE may transmit the PUSCH portion 1112B with precoder (or from antenna port set) 1111B, and so on. The UE may transmit the PUSCH portion 1112O with precoder (or from antenna port set) 1011O. Then, the UE may apply the precoders for the second PRB bundle for all the transmission occasions. The UE may transmit the PUSCH portion 1112 (O+1) with precoder (or from antenna port set) 1111 (O+1) . The UE may transmit the PUSCH portion 1112 (O+2) with precoder (or from antenna port set) 1111 (O+2) , and so on. The UE may transmit the PUSCH portion 1112 (2O) with precoder (or from antenna port set) 1111 (2O) . Then, the UE may apply the precoders for the third PRB bundle for all the transmission occasions, and so on. At last, the UE may transmit the PUSCH portion 1112 ( (M-1) O+1) with precoder (or from antenna port set) 1111 ( (M-1) O+1) . The UE may transmit the PUSCH portion 1112 ( (M-1) O+2) with precoder (or from antenna port set) 1111 ( (M-1) O+2) , and so on. The UE may transmit the PUSCH portion 1112 (MO) with precoder (or from antenna port set) 1111 (MO) .

In some other examples, the network entity configures the mapping scheme for the indicated precoders and the PRB bundles in each transmission occasion, e.g., time-first mapping or frequency-first mapping, by RRC signaling or DCI signaling. In some other examples, the UE reports a UE capability indicating the supported mapping scheme for the indicated precoders and the PRB bundles in each transmission occasion.

In some examples, the mapping between the indicated precoders and PUSCH is based on the nominal transmission occasion. In some other examples, the mapping between the indicated precoders and PUSCH is based on the actual transmission occasion.

In some examples, the network entity configures the mapping scheme for the indicated precoders, e.g., the TDM based mapping scheme, the FDM based mapping scheme, or a hybrid TDM/FDM mapping scheme, by the RRC signaling or DCI signaling. In some examples, the UE may further determine the mapping scheme based on the configuration of the number of PRB bundles and the number of transmission occasions. In one example, the UE determines the mapping scheme for the indicated precoders based on a look-up table, e.g., Table 1 below. In some examples, the UE may further report the UE capability indicating whether it supports the TDM based, and/or the FDM based, and/or the hybrid TDM/FDM mapping for the indicated precoder.

Table 1: An example for the precoder mapping scheme determination

FIGs. 12-15 illustrate examples of the precoder cycling configurations and/or the precoder indications for the PUSCH transmission with codebook-based precoder cycling. The precoder cycling configurations may include an antenna port cycling based precoder cycling configuration, a layer permutation based precoder cycling configuration, a precoder set based precoder cycling configuration, a precoder list indication based precoder cycling configuration, and/or a combination thereof. The network entity configures the multiple precoders based on one or more precoder cycling configurations for the PUSCH transmission with codebook-based precoder cycling. The details of each of the precoder cycling configurations will be discussed below.

FIG. 12 is a diagram 1200 illustrating an example of antenna port cycling based precoder cycling for the PUSCH transmission with codebook-based precoder cycling. In some examples, the network entity configures or indicates the enabled antenna ports and/or a number of transmission layers for the PUSCH transmission by the RRC signaling, MAC CE signaling, or DCI signaling. The number of transmission layers may be an integer value, for example, including 1, 2, 3, …or any other integer value. The number of transmission layers may refer to a quantity of transmission layers for the PUSCH transmission. In other words, the number of transmission layers may refer to how many transmission layers are for the PUSCH transmission.

In one example, the network entity configures or indicates a bitmap with a bit-width the same as a configured number of antenna ports, e.g., the number of antenna ports configured for a sounding reference signal (SRS) resource that is configured or indicated by the same RRC signaling, MAC CE signaling, or DCI signaling. As an example, the first state for bit x may indicate the port x is disabled for the PUSCH transmission, and the second state for bit x may indicate the port x is enabled for the PUSCH transmission. As another example, the first state for bit x may indicate the port x is enabled for the PUSCH transmission, and the second state for bit x may indicate the port x is disabled for the PUSCH transmission.

The UE may transmit a portion of the PUSCH, e.g., a PRB bundle or a transmission occasion, from a number of antenna ports (or a subset of antenna ports) , among the enabled antenna ports. The terms “antenna port” and “port” may be used interchangeably in this disclosure. The terms “transmission layer” and “layer” may be used interchangeably in this disclosure. For example, the number of total enabled antenna ports is S, and the number of antenna ports to transmit a portion of the PUSCH is R, where R and S are integer values, and R is less than S. The number of antenna ports R to transmit a portion of the PUSCH may be based on the number of transmission layers for the PUSCH transmission. In some examples, the number of antenna ports R is the same as the number of transmission layers. In some other examples, the number of antenna ports R is configured or indicated by the RRC signaling, MAC CE signaling, or DCI signaling. The UE may enable different antenna ports for different portions of the PUSCH transmission. In one example, if the network entity enables antenna ports {0, 1} from antenna ports {0, 1, 2, 3} and indicates the number of layers is 1, the number of antenna ports R is 1. The UE can transmit a portion of the PUSCH transmission from antenna port 0, and another portion of the PUSCH transmission from antenna port 1.

Referring to FIG. 12, in one example, if the network entity enables antenna ports {0, 1, 2} from the configured antenna ports {0, 1, 2, 3} and indicates the number of transmission layers is 2, the number of antenna ports R to transmit a portion of the PUSCH is 2. The UE can transmit a first portion 1212A of the PUSCH transmission from antenna ports 0 and 1, and a second portion 1212B of the PUSCH transmission from antenna ports 0 and 2, and a third portion 1212C of the PUSCH transmission from antenna ports 1 and 2. The UE may transmit a fourth, fifth and sixth portion of the PUSCH transmission with the same antenna ports as the first, second and third portion of the PUSCH transmission respectively, but with a different order for the transmission layers.

In some examples, the precoder is determined based on the enabled antenna ports, and the UE determines the precoder from the enabled antenna ports based on an identity matrix with normalization. In one example, the precoder for the first, second and third portion of the PUSCH transmission may beandrespectively, and the precoder for the fourth, fifth and sixth portion of the PUSCH transmission may beandrespectively.

In some other examples, the network entity can further indicate the precoder for the enabled antenna ports by the RRC signaling, MAC CE signaling, or DCI signaling. The network entity may configure whether the precoder for the enabled antenna ports should be fixed or indicated by the network entity by the RRC signaling. The UE may report a UE capability indicating whether the UE supports a fixed precoder, e.g., identity matrix with normalization, or a configurable precoder from the enabled antenna ports, or both. In one example, the network entity may indicate the precoder from a 2-port codebook with rank 2 transmission by indicating a transmission precoder matrix indicator (TPMI) . In one example, the network entity indicates TPMI=1, and then based on the codebook defined in Table 6.3.1.5-4 in 3GPP TS 38.211 v17.4.0, the indicated precoder may beThen the actual precoder for the first, second and third portion of the PUSCH may be andrespectively, and the precoder for the fourth, fifth and sixth portion of the PUSCH may beandrespectively.

In some examples, the network entity configures whether the PUSCH transmission is based on codebook-based transmission with or without antenna ports cycling by the RRC signaling. The DCI field for antenna ports indication is present when the network entity indicates the PUSCH transmission is based on codebook-based antenna port cycling. In some other examples, the network entity indicates whether the PUSCH transmission is based on codebook-based transmission with or without antenna ports cycling by the MAC CE signaling or DCI signaling. In one example, if the network entity enables all the antenna ports, the antenna ports cycling is disabled; otherwise, the antenna ports cycling is enabled.

In some examples, the network entity configures the antenna port cycling only when it configures the PUSCH transmission based on cyclic-prefix orthogonal frequency division multiplexing (CP-OFDM) waveform. Thus, the network entity may refrain from configuring the port cycling when it configures the PUSCH transmission based on Digital Fourier Transform spread OFDM (DFT-s-OFDM) waveform. In some examples, for DFT-s-OFDM waveform, the network entity refrains from configuring the number of layers. Thus, the UE transmits the DFT-s-OFDM based PUSCH with precoder cycling always based on single-layer transmission.

FIG. 13 is a diagram 1300 illustrating an example of a layer permutation based precoder cycling for the PUSCH transmission with codebook-based precoder cycling. In some examples, the network entity configures or indicates a precoder from a codebook for the PUSCH transmission by the RRC signaling, MAC CE signaling, and/or DCI signaling, and enables the layer permutation by the RRC signaling, MAC CE signaling, and/or DCI signaling. For example, the control signaling (e.g., the RRC signaling MAC CE signaling, and/or DCI signaling) indicates enabling the layer permutation to generate a set of precoders based on the precoder from the codebook. Then the UE applies the precoder with different order of the transmission layers for different portions of the PUSCH transmission. The order of the transmission layers for each layer permutation may be predefined, e.g., based on circular shift, or configured by the RRC signaling, MAC CE signaling, and/or DCI signaling.

Referring to FIG. 13, in one example, the network entity configures or indicates the TPMI is 1 and the number of transmission layers is 2 based on a 2-port codebook defined in Table 6.3.1.5-4 in 3GPP TS 38.211 v17.4.0 with TPMI = 1. Then, the indicated precoder may beFor a first PUSCH portion 1312A (e.g., a first PRB bundle) , the UE may apply the transmission layer order as {0, 1} , where the UE transmits the PUSCH based on precoderFor a second PUSCH portion 1312B, the UE may apply the transmission layer order as {1, 0} (e.g., switching the order of the transmission layers) , where the UE transmits the PUSCH based on precoderand so on.

In some examples, the network entity configures whether to enable the layer permutation or not by the RRC signaling. In some other examples, the network entity configures whether to enable the layer permutation or not by the DCI scheduling/activating the PUSCH. The UE ignores the layer permutation configuration when it is scheduled with a single-layer transmission.

In some examples, the UE applies the layer permutation within the transmission layers corresponding to a codeword. In one example, if a UE is scheduled with 8-layer transmission from 2 codewords, transmission layers {1, 2, 3, 4} are associated with the first codeword, and transmission layers {5, 6, 7, 8} are associated with the second codeword. The UE applies the layer permutation for the transmission layers {1, 2, 3, 4} and transmission layers {5, 6, 7, 8} separately, differently, or independently. The network entity may configure or indicate a common parameter to enable to disable the layer permutation for all codewords. Alternatively, the network entity may configure or indicate a respective parameter to enable to disable the layer permutation for each codeword. In some other examples, the UE applies the layer permutation for all the scheduled layers.

In some examples, the network entity configures the layer permutation only when it configures the PUSCH transmission based on CP-OFDM waveform. Thus, the network entity may refrain from configuring the layer permutation when it configures the PUSCH transmission based on DFT-s-OFDM waveform.

FIG. 14 is a diagram 1400 illustrating an example of a precoder set based precoder cycling for the PUSCH transmission with codebook-based precoder cycling. In some examples, the network entity configures a list of precoder sets by the RRC signaling or MAC CE signaling. The network entity indicates a precoder set of the precoder sets by RRC signaling or DCI signaling. Then the UE applies the precoders within the precoder set for the PUSCH transmission.

Referring to FIG. 14, in one example, by the RRC signaling or MAC CE signaling, the network entity configures a list of precoder sets 1411A, 1411B, 1411C, and 1411D. Then, by the DCI signaling, the network entity indicates the precoder set 1411B of the list of precoder sets 1411A, 1411B, 1411C, and 1411D, when the indicated precoder set index is 1. Then the UE applies the precoders within the precoder set 1411B for the PUSCH transmission.

In some examples, the network entity configures or indicates a precoder set for an uplink bandwidth part or a serving cell or a list of serving cells to the UE. In some examples, the network entity configures the precoders with the same rank within a precoder set. In some other examples, the network entity may configure the precoders with different ranks within a precoder set and indicate the number of transmission layers for the PUSCH transmission by the RRC signaling, MAC CE signaling, or DCI signaling. Then the UE applies the precoders with the same rank as the number of transmission layers from the indicated precoder set for the PUSCH transmission.

In some examples, the network entity configures whether to enable the precoder set configuration and indication or not by the RRC signaling. In some other examples, the network entity configures whether to enable precoder set indication or not by MAC CE signaling, e.g., the precoder set indication is enabled if a precoder set list is indicated by MAC CE signaling. The precoder set indication field in DCI may not be present if the precoder set indication is disabled.

In some examples, the network entity configures the precoder set only when it configures the PUSCH transmission based on CP-OFDM waveform. Thus, the network entity may refrain from configuring the precoder set when it configures the PUSCH transmission based on DFT-s-OFDM waveform. In some other examples, the network entity configures separate list of precoder sets for different waveforms. In one example, the network entity configures a first list of precoder sets for CP-OFDM waveform, and a second list of precoder sets for DFT-s-OFDM waveform. In some examples, for DFT-s-OFDM waveform, the network entity refrains from configuring number of layers. Thus, the UE transmits the DFT-s-OFDM based PUSCH with precoder cycling always based on single-layer transmission.

FIG. 15 is a diagram 1500 illustrating an example of a multiple precoder indications based precoder cycling for the PUSCH transmission with codebook-based precoder cycling. In some examples, the network entity configures or indicates a list of precoders for PUSCH transmission by the RRC signaling or DCI signaling. In some examples, the network entity indicates a common transmission rank indicator (TRI) indicating the rank for the list of precoders and a list of TPMIs for the list of precoders.

For Type1 CG-PUSCH, e.g., CG-PUSCH with the whole uplink grant configured by the RRC signaling, the network entity configures the TRI and TPMIs for the list of precoders by the RRC signaling. For Type2 CG-PUSCH, e.g., CG-PUSCH with some parameters configured by the RRC signaling and activated by a DCI signaling, the network entity may configure the TRI and TPMIs for the list of precoders by the RRC signaling or by the DCI signaling used for activation. For DG-PUSCH, in some examples, the network entity indicates the TRI and TPMIs by the scheduling DCI signaling.

In some examples, for DG-PUSCH, the network entity indicates the TRI and TPMIs in separate/different DCIs used to schedule a PUSCH transmission. In some examples, the network entity indicates the TRI in a first DCI signaling, and indicates the TPMIs in a second DCI signaling used for TPMI indication. If the UE only receives the first DCI signaling, the UE may transmit the PUSCH based on the TRI and a predefined TPMI, e.g., TPMI=0, or the UE may not transmit the PUSCH transmission. If the UE receives both of the first DCI and second DCI signaling, the UE transmits the PUSCH transmission based on the TRI and all the indicated TPMIs.

Referring to FIG. 15, in some examples, the network entity indicates a TRI and a first TPMI in a first DCI signaling 1508A. The network entity indicates remaining TPMIs in a second DCI signaling 1508B. If the UE only receives the first DCI signaling 1508A, the UE may transmit the PUSCH transmission 1512 based on the TRI and the first TPMI, or the UE may not transmit the PUSCH transmission. If the UE receives both of the first DCI signaling 1508A and second DCI signaling 1508B, the UE transmits the PUSCH transmission 1512 based on the TRI and all the indicated TPMIs or the TPMIs in the second DCI signaling 1508B.

In some examples, the network entity may configure whether it indicates the TRI and TPMIs from two DCIs or not by the RRC signaling. In some other examples, the first DCI signaling indicates whether the network entity indicates additional TPMIs in the second DCI signaling or not. In some examples, the UE does not monitor the second DCI if the first DCI signaling indicates the network entity does not indicate additional TPMIs in the second DCI signaling. In some other examples, the second DCI signaling is still counted for DCI blind detection. Thus, the UE still monitors the second DCI signaling regardless of indication of the presence of additional TPMIs in the second DCI signaling or not. In some other examples, the UE reports a UE capability indicating whether it still monitors the second DCI signaling when the first DCI signaling indicates there is no additional TPMI in the second DCI signaling.

In some examples, the network entity may transmit the two DCIs in a search space or control resource set on two PDCCH monitoring occasions. In some other examples, the network entity may transmit the two DCIs in two associated search spaces or control resource sets, and the network entity configures the search space association or control resource sets association by the RRC signaling. The network entity may transmit the two DCIs in the same slot or within a set of symbols, e.g., mini-slot or sub-slot. In some examples, the network entity may indicate (e.g. in the first DCI signaling) or configure a time duration, where the UE may receive/detect the second DCI after the UE receives the first DCI signaling.

In some examples, the network entity configures the list of TPMIs only when it configures the PUSCH transmission based on CP-OFDM waveform. Thus, the network entity may refrain from configuring the list of TPMIs when it configures the PUSCH transmission based on DFT-s-OFDM waveform. In some other examples, the network entity configures separate list of TPMIs for different waveform. In one example, the network entity configures a first list of TPMIs for CP-OFDM waveform, and a second list of TPMIs for DFT-s-OFDM waveform. In some examples, for DFT-s-OFDM waveform, the network entity refrains from configuring TRI. Thus, the UE transmits the DFT-s-OFDM based PUSCH with precoder cycling always based on single-layer transmission.

FIGs. 3-15 illustrate communications of the PUSCH transmission with codebook-based precoder cycling, the mapping of the precoders and the PUSCH transmission portions, and the precoder cycling configurations for the PUSCH transmission. FIGs. 16-17 illustrate methods for implementing one or more aspects of FIGs. 3-15. In particular, FIG. 16 illustrates an implementation by the UE 102 of the one or more aspects of FIGs. 3-15. FIG. 17 shows an implementation by the network entity 104 of the one or more aspects of FIGs. 3-15.

FIG. 16 illustrates a flowchart 1600 of a method of wireless communication at a UE for the PUSCH transmission with codebook-based precoder cycling. With reference to FIGs. 1 and 18, the method may be performed by the UE 102, the UE apparatus 1802, etc., which may include the memory 1826', 1806', 1816, and which may correspond to the entire UE 102 or the entire UE apparatus 1802, or a component of the UE 102 or the UE apparatus 1802, such as the wireless baseband processor 1826 and/or the application processor 1806.

As illustrated in FIG. 16, the UE 102 may transmit 1602, to the network entity, a UE capability report that indicates one or more UE capabilities including one or more supported precoder cycling configurations based on a codebook. For example, referring to FIG. 4, the UE 102 may transmit 402 a UE capability report including one or more supported precoder cycling configurations based on a codebook for the PUSCH transmission with codebook-based precoder cycling.

The UE 102 receives 1604, from the network entity, a control signaling indicating a plurality of precoders for a physical uplink shared channel (PUSCH) transmission. The PUSCH transmission includes a plurality of PUSCH portions. For example, referring to FIG. 4, the UE 102 receives 404 a RRC signaling, e.g., RRCReconfiguration for RRC (re) configuration, which indicates a set of precoders (e.g., multiple precoders) and configures the PUSCH transmission scheme as a codebook-based precoder cycling transmission scheme.

The UE 102 may determine 1610, for each PUSCH portion of the plurality of PUSCH portions, a precoder of the plurality of precoders to be applied for a respective PUSCH portion based on the control signaling. For example, referring to FIG. 4, the UE 102 may determine 410, for each portion of the configured or scheduled PUSCH, determine a precoder of the set of precoders to be applied for a respective PUSCH portion based on the received RRC signaling and/or DCI signaling.

Then, the UE 102 transmits 1612, to the network entity, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions. For example, referring to FIG. 4, the UE 102 transmits 412 the PUSCH transmission with the determined the set of precoders.

By using the method of flowchart 1600, the UE transmits the PUSCH transmission with different precoders, the reliability of the PUSCH transmission is increased in the scenario of the UE’s movement, rotation and/or blockage. The overall performance of the wireless communication system is improved, especially for the PUSCH transmission carrying the traffic with higher reliability requirement.

FIG. 17 is a flowchart 1700 of a method of wireless communication at a network entity for the PUSCH transmission with codebook-based precoder cycling. With reference to FIGs. 1 and 19, 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 1906, a DU processor 1926, a CU processor 1946, etc. The one or more network entities 104 may include memory 1906’/1926’/1946’, 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 1906, the DU processor 1926, or the CU processor 1946.

As illustrated in FIG. 17, the network entity 104 may receive 1702, from a UE, a UE capability report that indicates one or more UE capabilities including one or more supported precoder cycling configurations based on a codebook. For example, referring to FIG. 5, the network entity 104 may receive 502 a UE capability report including one or more supported precoder cycling configurations based on a codebook for the PUSCH transmission with codebook-based precoder cycling.

The network entity 104 transmits 1704, to the UE, a control signaling indicating a plurality of precoders for a physical uplink shared channel (PUSCH) transmission. The PUSCH transmission includes a plurality of PUSCH portions. For example, referring to FIG. 5, the network entity 104 transmits 504 a RRC signaling, e.g., RRCReconfiguration for RRC (re) configuration, which indicates a set of precoders (e.g., multiple precoders) and configures the PUSCH transmission scheme as a codebook-based precoder cycling transmission scheme.

Then, the network entity 104 receives 1712, from the UE, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions. For example, referring to FIG. 5, the network entity 104 receives 512 the PUSCH transmission with the determined set of precoders (e.g., multiple precoders) .

By using the method of flowchart 1700, the network entity 104 receives the PUSCH transmission with different precoders, the reliability of the PUSCH transmission is increased in the scenario of the UE’s movement, rotation and/or blockage. The overall performance of the wireless communication system is improved, especially for the PUSCH transmission carrying the traffic with higher reliability requirement. A UE apparatus 1802, as described in FIG. 18, may perform the method of flowchart 1600. The one or more network entities 104, as described in FIG. 19, may perform the method of flowchart 1700.

FIG. 18 is a diagram 1800 illustrating an example of a hardware implementation for a UE apparatus 1802. The UE apparatus 1802 may be the UE 102, a component of the UE 102, or may implement UE functionality. The UE apparatus 1802 may include an application processor 1806, which may have on-chip memory 1806’. In examples, the application processor 1806 may be coupled to a secure digital (SD) card 1808 and/or a display 1810. The application processor 1806 may also be coupled to a sensor (s) module 1812, a power supply 1814, an additional module of memory 1816, a camera 1818, and/or other related components. For example, the sensor (s) module 1812 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 1802 may further include a wireless baseband processor 1826, which may be referred to as a modem. The wireless baseband processor 1826 may have on-chip memory 1826'. Along with, and similar to, the application processor 1806, the wireless baseband processor 1826 may also be coupled to the sensor (s) module 1812, the power supply 1814, the additional module of memory 1816, the camera 1818, and/or other related components. The wireless baseband processor 1826 may be additionally coupled to one or more subscriber identity module (SIM) card (s) 1820 and/or one or more transceivers 1830 (e.g., wireless RF transceivers) .

Within the one or more transceivers 1830, the UE apparatus 1802 may include a Bluetooth module 1832, a WLAN module 1834, an SPS module 1836 (e.g., GNSS module) , and/or a cellular module 1838. The Bluetooth module 1832, the WLAN module 1834, the SPS module 1836, and the cellular module 1838 may each include an on-chip transceiver (TRX) , or in some cases, just a transmitter (TX) or just a receiver (RX) . The Bluetooth module 1832, the WLAN module 1834, the SPS module 1836, and the cellular module 1838 may each include dedicated antennas and/or utilize antennas 1840 for communication with one or more other nodes. For example, the UE apparatus 1802 can communicate through the transceiver (s) 1830 via the antennas 1840 with another UE 102 (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 1826 and the application processor 1806 may each include a computer-readable medium /memory 1826', 1806', respectively. The additional module of memory 1816 may also be considered a computer-readable medium /memory. Each computer-readable medium /memory 1826', 1806', 1816 may be non-transitory. The wireless baseband processor 1826 and the application processor 1806 may each be responsible for general processing, including execution of software stored on the computer-readable medium /memory 1826', 1806', 1816. The software, when executed by the wireless baseband processor 1826 /application processor 1806, causes the wireless baseband processor 1826 /application processor 1806 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 1826 /application processor 1806 when executing the software. The wireless baseband processor 1826 /application processor 1806 may be a component of the UE 102. The UE apparatus 1802 may be a processor chip (e.g., modem and/or application) and include just the wireless baseband processor 1826 and/or the application processor 1806. In other examples, the UE apparatus 1802 may be the entire UE 102 and include the additional modules of the apparatus 1802.

As discussed in FIG. 1 and implemented with respect to FIG. 16, the precoder cycling component 140 is configured to receive, from a network entity, a control signaling indicating a plurality of precoders for a PUSCH transmission. The PUSCH transmission comprises a plurality of PUSCH portions. The precoder cycling component 140 is further configured to transmit, to the network entity, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions. The precoder cycling component 140 may be within the application processor 1806 (e.g., at 140a) , the wireless baseband processor 1826 (e.g., at 140b) , or both the application processor 1806 and the wireless baseband processor 1826. The precoder cycling 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. 19 is a diagram 1900 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 1946, which may have on-chip memory 1946'. In some aspects, the CU 110 may further include an additional module of memory 1956 and/or a communications interface 1948, both of which may be coupled to the CU processor 1946. The CU 110 can communicate with the DU 108 through a midhaul link 162, such as an F1 interface between the communications interface 1948 of the CU 110 and a communications interface 1928 of the DU 108.

The DU 108 may include a DU processor 1926, which may have on-chip memory 1926'. In some aspects, the DU 108 may further include an additional module of memory 1936 and/or the communications interface 1928, both of which may be coupled to the DU processor 1926. The DU 108 can communicate with the RU 106 through a fronthaul link 160 between the communications interface 1928 of the DU 108 and a communications interface 1908 of the RU 106.

The RU 106 may include an RU processor 1906, which may have on-chip memory 1906'. In some aspects, the RU 106 may further include an additional module of memory 1916, the communications interface 1908, and one or more transceivers 1930, all of which may be coupled to the RU processor 1906. The RU 106 may further include antennas 1940, which may be coupled to the one or more transceivers 1930, such that the RU 106 can communicate through the one or more transceivers 1930 via the antennas 1940 with the UE 102.

The on-chip memory 1906', 1926', 1946' and the additional modules of memory 1916, 1936, 1956 may each be considered a computer-readable medium /memory. Each computer-readable medium /memory may be non-transitory. Each of the processors 1906, 1926, 1946 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) 1906, 1926, 1946 causes the processor (s) 1906, 1926, 1946 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) 1906, 1926, 1946 when executing the software. In examples, the configuration 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. 17, the configuration component 150 is configured to transmit, to a UE, a control signaling indicating a plurality of precoders for a PUSCH transmission. The PUSCH transmission comprises a plurality of PUSCH portions. The configuration component 150 is further configured to receive, from the UE, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions. The configuration component 150 may be within one or more processors of the one or more network entities 104, such as the RU processor 1906 (e.g., at 150a) , the DU processor 1926 (e.g., at 150b) , and/or the CU processor 1946 (e.g., at 150c) . The configuration 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 1906, 1926, 1946 configured to perform the stated processes/algorithm, stored within a computer-readable medium for implementation by the one or more processors 1906, 1926, 1946, 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, a control signaling indicating a plurality of precoders for a physical uplink shared channel (PUSCH) transmission, the PUSCH transmission comprising a plurality of PUSCH portions; and transmitting, to the network entity, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions.

Example 2 may be combined with example 1 and includes that the control signaling includes a radio resource control (RRC) signaling, or a medium access control (MAC) control element (CE) signaling, or a downlink control information (DCI) signaling.

Example 3 may be combined with any of examples 1-2 and includes that transmitting, to the network entity, a UE capability report that indicates one or more UE capabilities including one or more supported precoder cycling configurations based on a codebook.

Example 4 may be combined with any of examples 1-3 and further includes that the control signaling includes one or more parameters configuring the plurality of precoders based on a precoder cycling configuration, where the precoder cycling configuration includes an antenna port cycling based precoder cycling configuration, a layer permutation based precoder cycling configuration, a precoder set based precoder cycling configuration, a multiple precoder indications based precoder cycling configuration, or a combination thereof.

Example 5 may be combined with any of examples 1-4 and further includes that, for each PUSCH portion of the plurality of PUSCH portions, determining a precoder of the plurality of precoders to be applied for a respective PUSCH portion based on the control signaling.

Example 6 may be combined with any of examples 1-5 and includes that the control signaling indicates one or more enabled antenna ports and a number of transmission layers for the PUSCH transmission.

Example 7 may be combined with example 6 and includes that the plurality of precoders are determined based on the one or more enabled antenna ports and an identity matrix with normalization.

Example 8 may be combined with example 6 and includes that the control signaling further indicates a transmission precoder matrix indicator (TPMI) based on a codebook, and wherein the plurality of precoders are determined based on the TPMI and the number of transmission layers for the PUSCH transmission.

Example 9 may be combined with any of examples 1-5 and includes that the control signaling indicates enabling a layer permutation to generate the plurality of precoders.

Example 10 may be combined with example 9 and includes that wherein a base precoder is determined based on the control signaling, and wherein the plurality of precoders are determined based on the layer permutation of the base precoder.

Example 11 may be combined with any of examples 1-5 and includes that the control signaling indicates a precoder set from a list of precoder sets for the PUSCH transmission, and wherein the plurality of precoders are determined based on the precoder set indicated in the control signaling.

Example 12 may be combined with any of examples 1-5 and includes that the control signaling indicates a common transmission rank indicator (TRI) of the plurality of precoders and a plurality of TPMIs for the plurality of precoders, and wherein the plurality of precoders are determined based on the common TRI and the plurality of TPMIs.

Example 13 may be combined with any of examples 1-12 and includes that wherein the control signaling includes one or more parameters configuring the mapping between the plurality of precoders and the plurality of PUSCH portions.

Example 14 may be combined with any of examples 1-13 and includes that the plurality of PUSCH portions includes a plurality of physical resource block (PRB) bundles, and the transmitting, to the network entity, the plurality of PUSCH portions with the plurality of precoders includes: transmitting, to the network entity, the plurality of PRB bundles, wherein different precoders are applied to different PRB bundles.

Example 15 may be combined with any of examples 1-13 and includes that n the plurality of PUSCH portions includes a plurality of transmission occasions, and wherein the transmitting, to the network entity, the plurality of PUSCH portions with the plurality of precoders includes: transmitting, to the network entity, the plurality of transmission occasions, wherein different precoders are applied to different transmission occasions.

Example 16 is a method of wireless communication at a network entity, including: transmitting, to a user equipment (UE) , a control signaling indicating a plurality of precoders for a physical uplink shared channel (PUSCH) transmission, the PUSCH transmission comprising a plurality of PUSCH portions; and receiving, from the UE, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions.

Example 17 may be combined with example 16 and includes that receiving, from the UE, a UE capability report that indicates one or more UE capabilities including one or more supported precoder cycling configurations based on the codebook.

Example 18 may be combined with any of examples 16-17 and includes that the control signaling includes one or more parameters configuring the plurality of precoders based on a precoder cycling configuration.

Example 19 may be combined with any of examples 16-18 and includes that the control signaling indicates at least one of: one or more enabled antenna ports and a transmission layer number for the PUSCH transmission, enabling a layer permutation to generate the plurality of precoders, a precoder set from a list of precoder sets for the PUSCH transmission, or a common transmission rank indicator (TRI) of the plurality of precoders and a plurality of TPMIs for the plurality of precoders.

Example 20 may be combined with any of examples 16-19 and includes that the control signaling includes one or more parameters configuring the mapping between the plurality of precoders and the plurality of PUSCH portions.

Example 21 is an apparatus for wireless communication including a transceiver, a memory, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of examples 1-20.

Example 22 is an apparatus for wireless communication including means for implementing a method as in any of examples 1-20.

Example 23 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-20.

Claims

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

receiving, from a network entity, a control signaling indicating a plurality of precoders for a physical uplink shared channel (PUSCH) transmission, the PUSCH transmission comprising a plurality of PUSCH portions; and

transmitting, to the network entity, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions.
The method of claim 1, wherein the control signaling includes a radio resource control (RRC) signaling, or a medium access control (MAC) control element (CE) signaling, or a downlink control information (DCI) signaling.
The method of any of claims 1-2, further comprising:

transmitting, to the network entity, a UE capability report that indicates one or more UE capabilities including one or more supported precoder cycling configurations based on a codebook.
The method of any of claims 1-3, wherein the control signaling includes one or more parameters configuring the plurality of precoders based on a precoder cycling configuration, wherein the precoder cycling configuration includes an antenna port cycling based precoder cycling configuration, a layer permutation based precoder cycling configuration, a precoder set based precoder cycling configuration, a multiple precoder indications based precoder cycling configuration, or a combination thereof.
The method of any of claims 1-4, further comprising:

for each PUSCH portion of the plurality of PUSCH portions, determining a precoder of the plurality of precoders to be applied for a respective PUSCH portion based on the control signaling.
The method of any of claims 1-5, wherein the control signaling indicates one or more enabled antenna ports and a number of transmission layers for the PUSCH transmission.
The method of claim 6, wherein the plurality of precoders are determined based on the one or more enabled antenna ports and an identity matrix with normalization.
The method of claim 6, wherein the control signaling further indicates a transmission precoder matrix indicator (TPMI) based on a codebook, and wherein the plurality of precoders are determined based on the TPMI and the number of transmission layers for the PUSCH transmission.
The method of any of claims 1-5, wherein the control signaling indicates enabling a layer permutation to generate the plurality of precoders.
The method of claim 9, wherein a base precoder is determined based on the control signaling, and wherein the plurality of precoders are determined based on the layer permutation of the base precoder.
The method of any of claims 1-5, wherein the control signaling indicates a precoder set from a list of precoder sets for the PUSCH transmission, and wherein the plurality of precoders are determined based on the precoder set indicated in the control signaling.
The method of any of claims 1-5, wherein the control signaling indicates a common transmission rank indicator (TRI) of the plurality of precoders and a plurality of TPMIs for the plurality of precoders, and wherein the plurality of precoders are determined based on the common TRI and the plurality of TPMIs.
The method of any of claims 1-12, wherein the control signaling includes one or more parameters configuring the mapping between the plurality of precoders and the plurality of PUSCH portions.
The method of any of claims 1-13, wherein the plurality of PUSCH portions includes a plurality of physical resource block (PRB) bundles, and wherein the transmitting, to the network entity, the plurality of PUSCH portions with the plurality of precoders comprises:

transmitting, to the network entity, the plurality of PRB bundles, wherein different precoders are applied to different PRB bundles.
The method of any of claims 1-13, wherein the plurality of PUSCH portions includes a plurality of transmission occasions, and wherein the transmitting, to the network entity, the plurality of PUSCH portions with the plurality of precoders comprises:

transmitting, to the network entity, the plurality of transmission occasions, wherein different precoders are applied to different transmission occasions.
A method of wireless communication at a network entity, comprising:

transmitting, to a user equipment (UE) , a control signaling indicating a plurality of precoders for a physical uplink shared channel (PUSCH) transmission, the PUSCH transmission comprising a plurality of PUSCH portions; and

receiving, from the UE, the plurality of PUSCH portions with the plurality of precoders based on a mapping between the plurality of precoders and the plurality of PUSCH portions.
The method of claim 16, further comprising:

receiving, from the UE, a UE capability report that indicates one or more UE capabilities including one or more supported precoder cycling configurations based on a codebook.
The method of any of claims 16-17, wherein the control signaling includes one or more parameters configuring the plurality of precoders based on a precoder cycling configuration.
The method of any of claims 16-18, wherein the control signaling indicates at least one of:

one or more enabled antenna ports and a transmission layer number for the PUSCH transmission,

enabling a layer permutation to generate the plurality of precoders,

a precoder set from a list of precoder sets for the PUSCH transmission, or

a common transmission rank indicator (TRI) of the plurality of precoders and a plurality of TPMIs for the plurality of precoders.
The method of any of claims 16-19, wherein the control signaling includes one or more parameters configuring the mapping between the plurality of precoders and the plurality of PUSCH portions.
An apparatus for wireless communication comprising a transceiver, a memory, and a processor coupled to the memory and the transceiver, the apparatus being configured to implement a method as in any of claims 1-20.