Uplink control information multiplexing in presence of dynamic physical uplink shared channel skipping

Abstract

To provide methods for handling of UCI multiplexing in a PUSCH when dynamic PUSCH skipping is configured.SOLUTION: A method that may be implemented with user equipment (UE) includes: receiving an uplink grant for transmission on a plurality of physical uplink shared channels (PUSCHs), the plurality of PUSCHs being located on different component carriers (CCs); identifying one or more PUSCHs, of the plurality of PUSCHs, on which uplink control information (UCI) can be transmitted in a slot; assigning PUSCH data to the one or more identified PUSCHs on which the UCI can be transmitted before assigning PUSCH data to remaining PUSCHs of the plurality of PUSCHs; and transmitting the UCI and the PUSCH data in the slot on the assigned PUSCHs.SELECTED DRAWING: Figure 7B

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of and priority to U.S. Provisional Patent Application No. 62 / 901,619, filed September 17, 2019, which claims priority to U.S. Application No. 16 / 709,326, filed December 10, 2019, both of which are assigned to the assignee of the present application and are expressly incorporated herein by reference in their entirety as if fully set forth below and for all applicable purposes.

[0002] Aspects of the present disclosure relate to wireless communications, and more particularly, to techniques for sending uplink control information. [Background technology]

[0003] Wireless communication systems have been widely deployed to provide various telecommunication services, such as telephone, video, data, messaging, broadcast, and so on. These wireless communication systems may employ multiple access technologies capable of supporting communication with multiple users by sharing available system resources (e.g., bandwidth, transmit power, and so on). Examples of such multiple access systems include Third Generation Partnership Project (3GPP®) Long Term Evolution (LTE) systems, LTE-Advanced (LTE-A) systems, Code Division Multiple Access (CDMA) systems, Time Division Multiple Access (TDMA) systems, Frequency Division Multiple Access (FDMA) systems, Orthogonal Frequency Division Multiple Access (OFDMA) systems, Single Carrier Frequency Division Multiple Access (SC-FDMA) systems, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems, to name a few.

[0004] These multiple access technologies are being adopted in various telecommunications standards to provide a common protocol that allows different wireless devices to communicate on a city, national, regional, or even global scale. New Radio (e.g., 5G NR) is an example of an emerging telecommunications standard. NR is a set of extensions to the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectral efficiency, lowering costs, improving services, utilizing new spectrum, and better integrating with other open standards that use OFDMA with cyclic prefixes (CPs) on the downlink (DL) and uplink (UL). For these purposes, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0005] However, as the demand for mobile broadband access continues to grow, further improvements in NR and LTE technologies are needed, and preferably these improvements should be applicable to other multiple access technologies, and the telecommunications standards that employ these technologies. Summary of the Invention [Means for solving the problem]

[0006] The systems, methods, and devices of the present disclosure each have several aspects, no single aspect of which is solely responsible for its desirable attributes. Without limiting the scope of the present disclosure as expressed by the following claims, several features will now be briefly described. After considering this description, and in particular after reading the section entitled "Description of the Preferred Embodiments," it will be understood how the features of the present disclosure provide improved processing for uplink control information (UCI) multiplexing in a physical uplink shared channel (PUSCH) when dynamic PUSCH skipping is configured.

[0007] Certain aspects provide a method for wireless communication by a user equipment (UE). The method generally includes receiving an uplink grant for transmission on multiple PUSCHs, the multiple PUSCHs being located on different component carriers (CCs). The method generally includes identifying one or more PUSCHs of the multiple PUSCHs in which UCI may be transmitted in a slot. The method generally includes assigning PUSCH data to the one or more identified PUSCHs in which UCI may be transmitted before assigning PUSCH data to remaining PUSCHs of the multiple PUSCHs, and transmitting the UCI and the PUSCH data in the slot on the assigned PUSCH.

[0008] Some aspects provide a method for wireless communication by a UE. The method generally includes receiving an uplink grant for transmission on multiple PUSCHs in a slot, the multiple PUSCHs being located on different CCs. The method generally includes determining whether PUSCH data is to be transmitted in the slot. The method generally includes determining to transmit UCI in the slot on one or more PUCCHs or on one or more PUSCHs of the multiple PUSCHs based on a determination of whether PUSCH data is to be transmitted in the slot, before allocating the PUSCH data to a PUSCH of the multiple PUSCHs. The method generally includes transmitting UCI in the slot on the determined one or more PUCCHs or on the determined one or more PUSCHs.

[0009] Some aspects provide an apparatus for wireless communication. The apparatus generally includes means for receiving an uplink grant for transmission on a plurality of PUSCHs, the plurality of PUSCHs being located on different CCs. The apparatus generally includes means for identifying one or more PUSCHs of the plurality of PUSCHs in which UCI may be transmitted in a slot. The apparatus generally includes means for assigning PUSCH data to the one or more identified PUSCHs in which UCI may be transmitted before assigning PUSCH data to remaining PUSCHs of the plurality of PUSCHs, and means for transmitting UCI and the PUSCH data in the slot on the assigned PUSCH.

[0010] Some aspects provide an apparatus for wireless communication. The apparatus generally includes means for receiving an uplink grant for transmission on multiple PUSCHs in a slot, the multiple PUSCHs being located on different CCs. The apparatus generally includes means for determining whether PUSCH data is to be transmitted in the slot. The apparatus generally includes means for determining to transmit UCI in the slot on one or more PUCCHs or on one or more PUSCHs of the multiple PUSCHs based on a determination of whether PUSCH data is to be transmitted in the slot, prior to allocating PUSCH data to a PUSCH of the multiple PUSCHs. The apparatus generally includes means for transmitting UCI in the slot on the determined one or more PUCCHs or on the determined one or more PUSCHs.

[0011] Some aspects provide an apparatus for wireless communication. The apparatus generally includes a memory and at least one processor coupled to the memory. The at least one processor is generally configured to receive an uplink grant for transmission on a plurality of PUSCHs, the plurality of PUSCHs being located on different CCs. The at least one processor is generally configured to identify one or more PUSCHs of the plurality of PUSCHs in which UCI may be transmitted in a slot. The at least one processor is generally configured to assign PUSCH data to one or more identified PUSCHs in which UCI may be transmitted, before assigning PUSCH data to remaining PUSCHs of the plurality of PUSCHs, and to transmit the UCI and the PUSCH data in the slot on the assigned PUSCH.

[0012] Some aspects provide an apparatus for wireless communication. The apparatus generally includes a memory and at least one processor coupled to the memory. The at least one processor is generally configured to receive an uplink grant for transmission on a plurality of PUSCHs in a slot, the plurality of PUSCHs being located on different CCs. The at least one processor is generally configured to determine whether PUSCH data is to be transmitted in the slot. The at least one processor is generally configured to determine to transmit UCI in the slot on one or more PUCCHs or on one or more PUSCHs of the plurality of PUSCHs based on a determination of whether PUSCH data is to be transmitted in the slot, before allocating PUSCH data to a PUSCH of the plurality of PUSCHs. The at least one processor is generally configured to transmit UCI in the slot on the determined one or more PUCCHs or on the determined one or more PUSCHs.

[0013] Some aspects provide a computer-readable medium having stored thereon computer-executable code for wireless communication. The computer-readable medium generally includes code for receiving an uplink grant for transmission on a plurality of PUSCHs, the plurality of PUSCHs being located on different CCs. The computer-readable medium generally includes code for identifying one or more PUSCHs of the plurality of PUSCHs in which UCI may be transmitted in a slot. The computer-readable medium generally includes code for assigning PUSCH data to one or more identified PUSCHs in which UCI may be transmitted before assigning PUSCH data to remaining PUSCHs of the plurality of PUSCHs, and code for transmitting UCI and the PUSCH data in a slot on the assigned PUSCH.

[0014] Some aspects provide a computer-readable medium having stored thereon computer-executable code for wireless communication. The computer-readable medium generally includes code for receiving an uplink grant for transmission on multiple PUSCHs in a slot, the multiple PUSCHs being located on different CCs. The computer-readable medium generally includes code for determining whether PUSCH data is to be transmitted in the slot. The computer-readable medium generally includes code for determining to transmit UCI in the slot on one or more PUCCHs or on one or more PUSCHs of the multiple PUSCHs based on a determination of whether PUSCH data is to be transmitted in the slot before allocating PUSCH data to a PUSCH of the multiple PUSCHs. The computer-readable medium generally includes code for transmitting UCI in the slot on the determined one or more PUCCHs or on the determined one or more PUSCHs.

[0015] To the accomplishment of the foregoing and related ends, the one or more aspects comprise the features hereinafter fully described and particularly pointed out in the claims. The following description and the annexed drawings set forth in detail certain illustrative features of the one or more aspects. These features are indicative, however, of but a few of the various ways in which the principles of the various aspects may be employed.

[0016] So that the above-mentioned features of the present disclosure may be understood in detail, a more particular description may be had by reference to embodiments, some of which are illustrated in the drawings, briefly summarized above. It should be noted, however, that the present description may lead to other equally effective embodiments, and that the accompanying drawings illustrate only some typical embodiments of the present disclosure and therefore should not be considered as limiting the scope of the present disclosure. [Brief description of the drawings]

[0017] [Figure 1] FIG. 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure. [Diagram 2] FIG. 1 is a block diagram conceptually illustrating an example base station (BS) and user equipment (UE) design in accordance with certain aspects of the present disclosure. [Figure 3A] FIG. 1 is a call flow diagram illustrating an example uplink control information (UCI) fallback to a physical uplink control channel (PUCCH) when there is a physical uplink shared channel (PUSCH) skip. [Figure 3B] 1 is a block diagram illustrating an example overlapping PUSCH and PUCCH configured in a slot. [Figure 3C] FIG. 3B is a more detailed call flow diagram illustrating an example UCI fallback to PUCCH in the presence of PUSCH skipping in FIG. 3A. [Figure 3D] 1 is a block diagram illustrating exemplary UCI multiplexed in a PUSCH and data allocated to another PUSCH in a slot. [Figure 3E]FIG. 13 is a block diagram illustrating an example UCI fallback to PUCCH in a slot. [Figure 3F] 1 is a block diagram illustrating an example UCI fallback to PUCCH in a slot and PUSCH skipping. [Figure 4] 1 is a flow diagram illustrating example operations for wireless communication by a UE, in accordance with certain aspects of the present disclosure. [Diagram 5] 1 is a flow diagram illustrating example operations for wireless communication by a UE, in accordance with certain aspects of the present disclosure. [Figure 6A] 1 is a call flow diagram illustrating an example UCI transmission on a PUCCH in the presence of PUSCH skipping, according to an aspect of the disclosure. [Figure 6B] 1 is a more detailed call flow diagram illustrating an example UCI transmission on a PUCCH in the presence of PUSCH skipping, according to an aspect of the disclosure. [Figure 6C] 1 is a block diagram illustrating an example UCI transmitted on a PUCCH when there is no data assigned to a PUSCH in a slot, in accordance with an aspect of the disclosure. [Figure 6D] 1 is a block diagram illustrating an example UCI transmitted in a PUCCH and a PUSCH skip when there is no data assigned to the PUSCH in a slot, in accordance with one or more aspects of the present disclosure. [Figure 7A] 1 is a call flow diagram illustrating example UCI multiplexing on a PUSCH in the presence of PUSCH skipping, according to an aspect of the disclosure. [Figure 7B] 1 is a more detailed call flow diagram illustrating example UCI multiplexing on a PUSCH in the presence of PUSCH skipping, according to an aspect of the disclosure. [Figure 7C] 1 is a block diagram illustrating example data assigned to slots in which UCI is multiplexed, according to an aspect of the present disclosure. [Figure 7D]FIG. 13 is a block diagram illustrating example data assigned to slots in which UCI is multiplexed and PUSCH skips, in accordance with one or more aspects of the present disclosure. [Figure 8] FIG. 1 illustrates a communications device that may include various components configured to perform operations for the techniques disclosed herein, in accordance with aspects of the disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] For ease of understanding, wherever possible, identical reference numbers have been used to designate identical elements common to the figures. It is contemplated that elements disclosed in one embodiment may be advantageously utilized in other embodiments without specific recitation.

[0019] Aspects of the present disclosure provide an apparatus, a method, a processing system, and a computer-readable medium for processing uplink control information (UCI) multiplexing in a physical uplink shared channel (PUSCH) when dynamic PUSCH skipping is configured.

[0020] In some systems (e.g., New Radio or 5G NR systems), a user equipment (UE) is configured to transmit uplink control information (UCI), which may include a scheduling request (SR), a hybrid automatic repeat request (HARQ) feedback (e.g., positive / negative acknowledgement or HARQ-ACK information), and / or a channel state information (CSI) feedback, etc. The UE is also configured for data transmission on a PUSCH. The UE may be configured with multiple PUSCHs on different component carriers (CCs). In some cases, the UE may be scheduled to send data and UCI in overlapping time periods, such as in the same slot. The UE may transmit UCI in a physical uplink control channel (PUCCH). However, in some cases, the UE may transmit UCI in a PUSCH (e.g., not on a PUCCH) when the UCI and PUSCH overlap in time. For example, when the UE determines that a PUSCH is scheduled at a given time and the UE has UCI to send at that time, the UE is configured to multiplex the UCI in the PUSCH (eg, with uplink data).

[0021] In some systems (e.g., New Radio or 5G NR systems), the UE may be configured to skip transmission of a PUSCH that does not have any assigned data (e.g., dynamically when the UE does not have uplink data to send on the PUSCH at the scheduled time of the PUSCH). PUSCH skipping as used herein may refer to the UE dropping or not transmitting on some PUSCHs (e.g., some PUSCHs may include PUSCHs assigned via an uplink grant to the UE for uplink transmission). The PUSCH skipping may be based on a configured skip rule. In some scenarios, the UE may not know that the PUSCH will be skipped when the UE decides to multiplex UCI in the PUSCH. In such a scenario, the UE may fall back to transmitting UCI on the PUCCH. This may reduce efficiency, for example, by increasing the time and power consumption for transmitting UCI.

[0022] Aspects of the present disclosure provide a solution for multiplexing UCI on a PUSCH when PUSCH skipping is configured. For example, aspects provide that the UE checks whether there is uplink data to transmit before multiplexing UCI in a PUSCH. Thus, according to some aspects, when there is no uplink data, the UE can put UCI on a PUCCH. In this way, the UE prepares UCI on a PUSCH and then avoids falling back to sending UCI on a PUCCH when the UE decides to skip a PUSCH. Also, when there is uplink data, the UE can allocate data to a PUSCH on which UCI can be multiplexed before allocating data to other PUSCHs. In this way, the UE can ensure that UCI can be multiplexed on a PUSCH in a slot, since a PUSCH with data will not be skipped. In some examples, the multiplexed UCI can puncture the PUSCH (e.g., PUSCH data is rate matched). In some examples, UCI may be punctured onto the PUSCH when (e.g., only when) the number of UCI bits to be transmitted is for a small amount of UCI data (e.g., 2 bits or less of UCI), such as below a threshold number of UCI bits. For a larger amount of UCI data (e.g., above a threshold), the UCI may then be multiplexed by rate matching the PUSCH. For example, puncturing or rate matching may be performed as defined in a wireless standard (e.g., in an IEEE wireless standard). By multiplexing the UCI bits onto the PUSCH, the effective code rate of the PUSCH may be higher. In some cases (e.g., when polar coding is used for transmission), rate matching a large number of UCI bits (e.g., rather than puncturing them) may result in a lower effective code rate for the PUSCH (e.g., compared to puncturing).

[0023] Thus, in one or more aspects, a UE receives an uplink grant for transmission on multiple PUSCHs in a slot. The PUSCHs are located on different component carriers (CCs). The UE identifies PUSCHs on which UCI may be transmitted in the slot. The UE then assigns PUSCH data to those identified PUSCHs before assigning PUSCH data to the remaining PUSCHs. The UE transmits UCI and PUSCH data in the slot on the assigned PUSCHs.

[0024] In one or more aspects, a UE may receive an uplink grant for multiple PUSCHs in a slot. The multiple PUSCHs are located on different CCs. The UE may determine whether PUSCH data is to be transmitted in the slot. Based on whether there is PUSCH data, the UE may determine to transmit UCI in the slot on a PUCCH or on a PUSCH before allocating PUSCH data to any of the PUSCHs. The UE transmits UCI in the slot on the determined PUCCH or PUSCH.

[0025] The following description provides examples of UCI multiplexing in PUSCH when dynamic PUSCH skipping is configured in a communication system, and is not intended to limit the scope, applicability, or examples set forth in the claims. Changes may be made in the functionality and configuration of the elements described without departing from the scope of the present disclosure. Various examples may omit, substitute, or add various procedures or components, as appropriate. For example, the methods described may be performed in a different order than described, and various steps may be added, omitted, or combined. Also, features described with respect to some examples may be combined in some other examples. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects described herein. Furthermore, the scope of the present disclosure is intended to cover such apparatus or methods practiced using other structures, functions, or structures and functions in addition to or other than the various aspects of the present disclosure described herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim. The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects.

[0026] In general, any number of wireless networks may be deployed within a given geographic area. Each wireless network may support a particular radio access technology (RAT) and may operate on one or more frequencies. A RAT may also be referred to as a radio technology, an air interface, etc. A frequency may also be referred to as a carrier, a subcarrier, a frequency channel, a tone, a subband, etc. Each frequency may support a single RAT in a given geographic area to avoid interference between wireless networks of different RATs. In some cases, 5G NR RAT networks may be deployed.

[0027] 1 illustrates an example wireless communication network 100 in which aspects of the present disclosure may be implemented. For example, the wireless communication network 100 may be a NR system (e.g., a 5G NR network).

[0028] As shown in FIG. 1, the wireless communication network 100 may include several base stations (BSs) 110a-110z (each also referred to herein individually as BS 110 or collectively as BS 110), and other network entities. The BSs 110 may provide communication coverage to a particular geographic area, which may be referred to as a "cell," and may be fixed or may move according to the location of the mobile BS 110. In some examples, the BSs 110 may be interconnected to one another and / or to one or more other BSs or network nodes (not shown) in the wireless communication network 100 through various types of backhaul interfaces (e.g., direct physical connections, wireless connections, virtual networks, etc.) using any suitable transport network. In the example shown in FIG. 1, the BSs 110a, 110b, and 110c may be macro BSs for the macro cells 102a, 102b, and 102c, respectively. The BS 110x may be a pico BS for the pico cell 102x. BS 110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. A BS may support one or more cells. BS 110 communicates with user equipment (UE) 120a-120y (each also referred to herein individually as UE 120 or collectively as UE 120) within wireless communications network 100. UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout wireless communications network 100, and each UE 120 may be fixed or mobile.

[0029] According to some aspects, the UE 120 may be configured for UCI multiplexing and PUSCH skipping. As shown in FIG. 1, the UE 120a includes a UCI multiplexing manager 122. The UCI multiplexing manager 122 may be configured for UCI multiplexing in the presence of PUSCH skipping according to aspects of the present disclosure. In some examples, the UCI multiplexing manager 122 may receive an uplink grant for transmission on multiple PUSCHs, where the multiple PUSCHs may be located on different CCs. The UCI multiplexing manager 122 may further identify one or more PUSCHs of the multiple PUSCHs in which the UCI may be transmitted in a slot. Additionally, the UCI multiplexing manager 122 may also assign PUSCH data to one or more identified PUSCHs in which the UCI may be transmitted before assigning PUSCH data to the remaining PUSCHs of the multiple PUSCHs. The UCI multiplexing manager 122 may further transmit the UCI and PUSCH data in a slot on the assigned PUSCH. In some examples, the UCI multiplexing manager 122 may receive an uplink grant for transmission on multiple PUSCHs in a slot. The multiple PUSCHs are located on different CCs. The UCI multiplexing manager 122 may determine whether PUSCH data is to be transmitted in the slot. Before allocating PUSCH data to a PUSCH of the multiple PUSCHs, the UCI multiplexing manager 122 may determine to transmit UCI in the slot on one or more PUCCHs or on one or more PUSCHs of the multiple PUSCHs based on the determination of whether PUSCH data is to be transmitted in the slot. The UCI multiplexing manager 122 may transmit UCI in the slot on the determined one or more PUCCHs or on the determined one or more PUSCHs.

[0030] The wireless communication network 100 may also include relay stations (e.g., relay station 110r), also referred to as relays, that receive transmissions of data and / or other information from an upstream station (e.g., BS 110a or UE 120r) and send transmissions of data and / or other information to a downstream station (e.g., UE 120 or BS 110) or relay transmissions between UEs 120 to facilitate communication between the devices.

[0031] The network controller 130 may couple to a set of BSs 110 and provide coordination and control for these BSs 110. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other (e.g., directly or indirectly) via a wireless or wireline backhaul.

[0032] FIG. 2 illustrates example components of a BS 110a and a UE 120a (eg, in the wireless communication network 100 of FIG. 1) that may be used to implement aspects of the present disclosure.

[0033] At the BS 110a, the transmit processor 220 may receive data from the data source 212 and control information from the controller / processor 240. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), etc. The data may be for a physical downlink shared channel (PDSCH), etc. The processor 220 may process (e.g., encode and symbol map) the data and control information to obtain data symbols and control symbols, respectively. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a cell-specific reference signal (CRS). A transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​the data symbols, control symbols, and / or reference symbols, if applicable, and may provide output symbol streams to modulators (MODs) 232a-t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator may further process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a-t may be transmitted via antennas 234a-t, respectively.

[0034] At the UE 120a, the antennas 252a-252r may receive downlink signals from the BS 110a and may provide received signals to demodulators within the transceiver (DEMODs) 254a-254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal and obtain input samples. Each demodulator may further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. A MIMO detector 256 may obtain the received symbols from all demodulators 254a-254r, perform MIMO detection on the received symbols, if applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols and provide decoded data for the UE 120a to a data sink 260 and provide decoded control information to the controller / processor 280.

[0035] On the uplink, at the UE 120a, a transmit processor 264 may receive and process data (e.g., for the Physical Uplink Shared Channel (PUSCH)) from a data source 262 and control information (e.g., for the Physical Uplink Control Channel (PUCCH)) from a controller / processor 280. The transmit processor 264 may also generate reference symbols for a reference signal (e.g., for a Sounding Reference Signal (SRS)). The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 if applicable, further processed by modulators 254a-254r in the transceiver (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At the BS 110a, uplink signals from the UE 120a may be received by antennas 234, processed by a demodulator 232, detected by a MIMO detector 236 if applicable, and further processed by a receive processor 238 to obtain decoded data and control information sent by the UE 120a. The receive processor 238 may provide the decoded data to a data sink 239 and provide the decoded control information to the controller / processor 240.

[0036] The memories 242 and 282 may store data and program codes for the BS 110a and the UE 120a, respectively. The scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0037] The controller / processor 280 and / or other processors and modules in the UE 120a may perform processes or direct the execution of such processes for the techniques described herein. For example, as shown in FIG. 2, the controller / processor 280 of the UE 120a has a UCI multiplexing manager 281 that may be configured for UCI multiplexing in PUSCH processing when PUSCH skipping is configured according to aspects described herein. Although shown in the controller / processor 280, other components of the UE 120a may be used to perform the operations described herein.

[0038] As explained above, the UE may be configured for UCI multiplexing and PUSCH skipping, which may be problematic if the UE decides to send UCI in the PUSCH and then the PUSCH is skipped because it does not have any assigned data. Figure 3A is a call flow 300A illustrating an example UCI fallback to PUCCH in the presence of PUSCH skipping. Figure 3C is a more detailed call flow 300C illustrating an example UCI fallback to PUCCH in the presence of PUSCH skipping.

[0039] As shown in FIG. 3A, at 306, the UE 302 receives an uplink grant (e.g., in a PDCCH) from the serving gNB 304 that schedules a PUSCH in the slot. Different PUSCHs may be scheduled on different CCs in the slot. In an illustrative example, the UE 302 is scheduled (e.g., at 306) with eight PUSCHs (PUSCH1, PUSCH2, ..., PUSCH8) and at least one PUCCH in a given slot 301, as shown in FIG. 3B. As shown in FIG. 3B, PUSCHs 1-8 are configured on different CCs, such as CC0-CC7, in the slot 301.

[0040] At 308, the UE 302 is configured / scheduled by the serving gNB 304 to send UCI (e.g., HARQ-ACK, SR, and / or CSI) in the slot. Although in FIG. 3A the UCI configuration / scheduling (at 308) is shown after the uplink grant that schedules the PUSCH (at 306), in one or more examples, the UCI may be configured / scheduled before or at the same time as the uplink grant that schedules the PUSCH. In some examples, the UCI may be dynamically scheduled. In some examples, the UE 302 may be configured with a timeline, trigger, or periodicity for sending the UCI.

[0041] At 310, the UE 302 determines to multiplex UCI in one or more of the PUSCHs scheduled in the slot (e.g., when both PUSCH and PUCCH are scheduled in the slot). For example, the UE 302 may operate its multiplexing logic to determine in which PUSCH the UCI may be transmitted. The UE 302 may be configured with a rule for determining whether the UCI may be transmitted in the PUSCH. In some examples, the UCI multiplexing rule is hard-coded in the UE 302 according to the 3GPP technical specifications (e.g., 38.213 v15.4.0, section 9.3 specifies various rules for transmitting UCI on the PUSCH). In some examples, a PUSCH may be configured that may be multiplexed with UCI. As shown in FIG. 3C, the UCI multiplexing at 310 may be performed in the PHY layer 305 of the UE 302. In an illustrative example, based on the UCI multiplexing rules, the UE 302 determines (at 310) to multiplex the UCI on PUSCH2, as shown in FIG. 3D.

[0042] At 312, the UE 302 allocates data (e.g., higher-level medium access control (MAC) protocol data units (PDUs)) to one or more of the scheduled PUSCHs. As shown in FIG. 3C, the data allocation at 312 may occur at the MAC layer 303 of the UE 302. In an illustrative example, the UE 302 (e.g., at the MAC layer) has only a small amount of data to send, and the UE 302 (at 312) builds PUSCH1 with that data and has no data to fill the remaining PUSCHs 2-8, as shown in FIG. 3D.

[0043] In one example, the UE 302 may be configured for PUSCH skipping (e.g., via radio resource control (RRC) signaling). At 314, the UE 302 determines to skip (e.g., drop or not transmit) a PUSCH in a slot that does not have PUSCH data assigned for transmission in the slot. For example, the UE 302 may be configured to not transmit a PUSCH with only padding or only UCI, but to transmit a PUSCH only when there is PUSCH data to be transmitted on that PUSCH. However, PUSCH skipping may complicate UCI transmission if the PUSCH data assignment and / or skipping is not known to the UE when UCI multiplexing is determined. For example, as shown in Figure 3A, when the UE 302 (e.g., at the PHY layer) decides (at 310) to multiplex UCI on a PUSCH and the UE 302 (e.g., at the MAC layer) decides (at 312) not to assign any data to the PUSCH and thus to skip the PUSCH (at 314), then the UE 302 (e.g., at the PHY layer) must fall back to transmitting UCI on a PUCCH. Thus, at 316, the UE 302 transmits a PUSCH with assigned data in the slot (skipping the PUSCH without any data), and at 318, the UE transmits UCI on a PUCCH 309 in the slot. As shown in Figure 3C, the skip at 314 may be made in the PHY layer 305 after the PHY layer 305 makes the UCI multiplexing decision at 310. In the illustrative example in FIGS. 3A-3E, UE 302 may transmit PUSCH 1, but drop PUSCHs 2-8 according to the configured PUSCH skip, and UE 302 falls back (at 314) to transmitting UCI on the PUCCH.In this case, both the PUCCH and the PUSCH (at 316 and 318) are transmitted in the slot, as shown in FIG. 3E, and the remaining PUSCH 307 is dropped (skipped), as shown in FIG. 3F.

[0044] Thus, additional PUCCH / PUSCH resources may be used (e.g., because both PUSCH and PUCCH are transmitted) and there may be additional delays (e.g., to fall back to prepare the PUCCH), which in turn may incur additional power consumption.

[0045] Example UCI Multiplexing with PUSCH Skipping In some examples, prior to physical uplink shared channel (PUSCH) skipping and multiplexing of uplink control information (UCI) on the PUSCH, the physical (PHY) layer may check the medium access control (MAC) layer to determine whether the MAC layer has data to transmit (e.g., to schedule, to assign to the PUSCH). In some examples, the PHY layer may send a query (e.g., or a direct function call) to the MAC layer, and the MAC layer sends a response indicating whether there is MAC layer data. For example, the PHY layer may send a query to the MAC layer at or before the time when the UE initiates the skip logic (e.g., when the UE determines that the PUSCH / PUCCH overlaps and determines which PUSCH to skip based on the configured skip rules) and at or before the time when the multiplexing decision is made. In one example, the PUSCH / PUCCH overlap in a slot may be determined based on scheduling information received by the UE (if PUSCH and / or PUCCH are configured with bundling / repetition, this may be taken into account in determining whether PUSCH and / or PUCCH are scheduled in a slot). In some examples, additionally or alternatively, the MAC layer may inform the PHY layer when the MAC layer has data. For example, the MAC layer may periodically inform the PHY layer whether the MAC layer has data and / or the MAC layer may inform the UE whenever new data arrives at the MAC layer.

[0046] As described in more detail below with respect to Figures 6A-6D, if the MAC layer data is empty (e.g., the MAC layer has no PUSCH data to transmit / allocate), all PUSCHs will be skipped and UCI will be transmitted by PUCCH. Thus, the UE may not attempt to multiplex UCI on PUSCH first and then fall back to PUCCH later. As described in more detail below with respect to Figures 7A-7D, if the MAC layer data is not empty (e.g., the MAC layer has PUSCH data to transmit / allocate on PUSCH), the PHY layer may request the MAC layer to first place (e.g., allocate / transmit) data (e.g., MAC protocol data units (PDUs)) on a PUSCH that can multiplex UCI, and then on one or more remaining PUSCHs. For example, there may be multiple PUSCHs scheduled. The PUSCHs are ordered to allocate data. The MAC layer may order the PUSCHs based on a request from the PHY layer to allocate data to a PUSCH that can multiplex UCI first (e.g., based on a UCI multiplexing rule). In some examples, the PHY layer may send to a higher layer (e.g., MAC) an ordered list of PUSCHs to be built for a slot. The MAC layer may build the PUSCHs (e.g., allocate data such as MAC layer transport blocks (TBs) to the PUSCHs) in the order of the list. When the PHY layer sends the list, the PHY layer may order the list such that the PUSCHs that can multiplex UCI are ordered first in the list. In some examples, the PHY layer may send a list of PUSCHs and an indication of which PUSCH should be built first. Thus, the UCI multiplexing decision at the UE PHY layer may take into account whether there is MAC layer data to be sent (e.g., in addition to the multiplexing rule).

[0047] By avoiding UCI fallback to PUCCH and / or ensuring multiplexing of UCI on PUSCH, the UE can save resources and power. Since the UE knows whether there is data or not, the PHY can decide whether to multiplex UCI on PUSCH before the uplink PUSCH skip is decided. In this case, the UE can also build a data PDU, e.g., a MAC layer TB, and perform PHY layer data / UCI multiplexing in parallel with the formation of the data PDU. Thus, the uplink PHY timeline can be improved. Furthermore, by allocating data to a PUSCH that can multiplex UCI, in one or more examples, multiple PUSCHs carrying UCI (e.g., with a grant size of more than 2k bytes) can be transmitted in a slot (with overlapping PUCCH) even when there is a small MAC PDU.

[0048] 4 is a flow diagram illustrating example operations 400 for wireless communication according to some aspects of the disclosure. The operations 400 may be performed, for example, by a UE (e.g., UE 120a in wireless communication network 100, etc.). The operations 400 may be implemented as software components executed and operated on one or more processors (e.g., controller / processor 280 of FIG. 2). Furthermore, the transmission and reception of signals by the UE in the operations 400 may be enabled, for example, by one or more antennas (e.g., antenna 252 of FIG. 2). In some aspects, the transmission and / or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., controller / processor 280) that acquires and / or outputs the signals.

[0049] The operations 400 may begin, at 405, by receiving an uplink grant for transmission on multiple PUSCHs, the multiple PUSCHs being located on different component carriers (CCs).

[0050] At 410, the UE identifies one or more PUSCHs of a plurality of PUSCHs in which UCI may be transmitted in a slot. In some examples, the UE identifies one or more PUSCHs in which UCI may be transmitted based at least in part on one or more preconfigured rules. In some examples, the UE identifies one or more PUSCHs in which UCI may be transmitted based at least in part on a configuration of a PUCCH. For example, a PUCCH may schedule UCI for a CC, and the UE may determine a PUSCH scheduled for the CC as a PUSCH in which UCI may be multiplexed.

[0051] At 415, the UE assigns PUSCH data to one or more identified PUSCHs on which UCI may be transmitted before assigning PUSCH data to remaining PUSCHs of the plurality of PUSCHs. According to some aspects, the UE determines that the PUSCH data will be transmitted in a slot. For example, the UE determines that the PUSCH data will be transmitted in a slot before identifying one or more PUSCHs of the plurality of PUSCHs on which UCI may be sent and before assigning the PUSCH data. In some examples, the UE receives an indication corresponding to the PUSCH data from a MAC layer at the PHY layer. In some examples, the UE receives an indication corresponding to the PUSCH data in response to a query from the PHY layer to the MAC layer. In some examples, the UE periodically receives an indication corresponding to the PUSCH data from the MAC layer at the PHY layer. In some examples, the UE receives an indication corresponding to the PUSCH data from the MAC layer at the PHY layer when new data is received at the MAC layer. In some examples, the UE receives an indication corresponding to PUSCH data in response to a query, periodically, and / or in some combination when new data is received at the MAC layer.

[0052] At 420, the UE transmits UCI and PUSCH data in the slot on the assigned PUSCH. In some examples, the UE rate-matches the UCI around the PUSCH data. In some examples, the UE generates a MAC layer TB and performs PHY layer multiplexing of the UCI and PUSCH data in parallel. In some examples, the UE skips transmission of at least one empty PUSCH of the set of PUSCHs.

[0053] 5 is a flow diagram illustrating example operations 500 for wireless communication according to some aspects of the disclosure. The operations 500 may be performed, for example, by a UE (e.g., UE 120a in wireless communication network 100, etc.). The operations 500 may be implemented as software components executed and operated on one or more processors (e.g., controller / processor 280 of FIG. 2). Furthermore, the transmission and reception of signals by the UE in the operations 500 may be enabled, for example, by one or more antennas (e.g., antenna 252 of FIG. 2). In some aspects, the transmission and / or reception of signals by the UE may be implemented via a bus interface of one or more processors (e.g., controller / processor 280) that acquires and / or outputs the signals.

[0054] The operations 500 may begin, at 505, by receiving an uplink grant for transmission on multiple PUSCHs in a slot, the multiple PUSCHs being located on different CCs.

[0055] At 510, the UE determines whether PUSCH data is to be transmitted in the slot. In some examples, the UE receives an indication from the MAC layer at the PHY layer in response to a query from the PHY layer to the MAC layer. In some examples, the UE receives an indication from the MAC layer at the PHY layer periodically. In some examples, the UE receives an indication from the MAC layer at the PHY layer when new data is received at the MAC layer. According to some aspects, the UE determines to transmit UCI in the slot on one or more PUCCHs when one or more PUSCHs are empty (e.g., when there is no data to be transmitted in the PUSCH in the slot). According to some aspects, the UE determines to transmit UCI in the slot on one or more PUSCHs when PUSCH data is to be transmitted in the slot.

[0056] At 515, before allocating PUSCH data (e.g., any PUSCH data) to a PUSCH of the multiple PUSCHs, the UE determines to transmit UCI in the slot on one or more PUCCHs or on one or more PUSCHs of the multiple PUSCHs based on a determination of whether PUSCH data is to be transmitted in the slot.

[0057] According to some aspects, the UE identifies one or more PUSCHs of the multiple PUSCHs on which the UCI may be transmitted, and the UE assigns PUSCH data to those PUSCHs on which the UCI may be transmitted before assigning PUSCH data to the remaining PUSCHs. In some examples, the UE requests the MAC layer to assign PUSCH data on the PUSCHs on which the UCI may be sent before assigning PUSCH data on the remaining PUSCHs by the PHY layer. In some examples, the UE provides the MAC layer, by the PHY layer, with an ordered list for constructing a set of PUSCHs. The identified PUSCHs on which the UCI may be transmitted may be ordered before the remaining PUSCHs in the ordered list. In some examples, the UE identifies the PUSCHs on which the UCI may be transmitted based at least in part on one or more preconfigured rules. In some examples, the UE identifies the PUSCHs on which the UCI may be transmitted based at least in part on a configuration of the PUCCH.

[0058] At 520, the UE transmits UCI in the slot on the determined PUCCH(s) or on the determined PUSCH(s). In some examples, the UE sends UCI in the slot on both the PUCCH(s) and the PUSCH(s). In some examples, the UE rate-matches UCI around the PUSCH data. In some examples, the UE generates a MAC layer TB and performs PHY layer multiplexing of UCI and PUSCH data in parallel. In some examples, the UE skips transmission of at least one empty PUSCH.

[0059] As mentioned above, the UE may perform a check (e.g., a PHY layer check) to determine whether there is data (e.g., MAC layer data) to transmit in a duration (e.g., in a transmission time interval, such as in a slot). Thus, if there is no data to be transmitted (e.g., no MAC layer data or the MAC layer buffer is empty), all of the PUSCH may be skipped (e.g., according to a configured PUSCH skip rule). In this case, the UE may decide to send UCI on the PUCCH in the slot. FIG. 6A is a call flow 600A illustrating an example UCI transmission on the PUCCH with PUSCH skipping, according to one or more aspects of the present disclosure. FIG. 6B is a more detailed call flow 600B illustrating an example UCI transmission on the PUCCH with PUSCH skipping.

[0060] As shown in Figure 6A, at 606, the UE 602 receives an uplink grant (e.g., in a PDCCH) from a serving BS 604 (e.g., a gNB) that schedules a PUSCH in a slot (e.g., or other time interval). The PUSCH may be scheduled on a different CC in the slot, for example, as shown in slot 301 in Figure 3B.

[0061] At 608, the UE 602 is configured / scheduled by the serving BS 604 to send UCI (e.g., HARQ-ACK, SR, and / or CSI) in the slot. Although in FIG. 6A the UCI configuration / scheduling (at 608) is shown after the uplink grant that schedules the PUSCH (at 606), the UCI may be configured / scheduled before or at the same time as the uplink grant that schedules the PUSCH. In some examples, the UCI may be dynamically scheduled. In some examples, the UE 602 may be configured with a timeline, trigger, or periodicity for sending the UCI.

[0062] At 610, the UE checks for MAC layer data. For example, as shown in FIG. 6B, the PHY layer 605 may query the MAC layer 603. The MAC layer 603 may send an indication to the PHY layer 605 whether the MAC layer 603 has data, either periodically or in response to the query. Thus, compared to the UCI multiplexing shown in FIG. 3A-FIG. 3E, the UE 602 may know whether there is data to be transmitted before the UE 602 determines whether to multiplex UCI on a PUSCH. In this case, as shown in FIG. 6A, if the UE 602 determines that there is no data to be transmitted, at 612, the UE 602 may decide to put UCI on a PUCCH and skip the empty PUSCH (e.g., based on a configured PUSCH skip rule). For example, for empty PUSCHs (eg, that have no PUSCH data assigned to them in a slot), the UE 602 may decide to skip (eg, drop or not transmit) those empty PUSCHs in the slot.

[0063] At 614, the UE 602 transmits the UCI on the PUCCH to the serving BS 604. Thus, in the illustrated example in Figures 6A-6D, the UE 602 may avoid falling back (e.g., at the PHY layer) to transmitting the UCI on the PUCCH after preparing to transmit the UCI on the PUSCH, thereby avoiding incurring additional delay (e.g., to fall back to prepare the PUCCH) and in turn saving power consumption.

[0064] Referring again to the illustrative example described above with respect to Figures 3A-3E, the UE 602 may be scheduled (e.g., at 606) with eight PUSCHs (PUSCH1, PUSCH2, ..., PUSCH8) in a given slot, e.g., as shown in Figure 3B. However, the UE 602 may determine (e.g., at 610) based on a MAC layer check that there is no data to be transmitted in slot 301 and decide to place UCI on the PUCCH, as shown in Figure 6C. Because the MAC layer does not have any data, the UE 602 drops the remaining PUSCHs 607 (e.g., PUSCH1-8) according to the configured PUSCH skip, as shown in Figure 6D, but because the UE 602 has already placed UCI on the PUCCH (e.g., at 612), the UE 602 does not need to fall back to transmitting UCI on the PUCCH.

[0065] 7A is a diagram of a call flow 700A illustrating an example UCI multiplexing on a PUSCH with PUSCH skipping, according to an aspect of the disclosure. FIG. 7B is a more detailed call flow 700B illustrating an example UCI multiplexing on a PUSCH with PUSCH skipping.

[0066] As shown in FIG. 7A, at 706-710, the UE 702 receives an uplink grant and is configured / scheduled by the serving BS 704 to send UCI and checks for MAC layer data, which may be done as described above at 606-610 shown in FIG. 6A. In this case, as shown in FIG. 7A, if the UE 702 finds that there is data to be transmitted (e.g., MAC layer data, or buffer is not empty), the UE 702 decides to place (e.g., assign) the data on one or more PUSCHs on which the UCI can be multiplexed before placing the data on other PUSCHs in the slot at 712. For example, as shown in FIG. 7B, the PHY layer 705 may identify, at 712a, a PUSCH on which the UCI can be multiplexed and request the MAC layer 703 to place a MAC PDU on the identified PUSCH on which the UCI can be multiplexed and then on the other PUSCH at 712b. In this way, the UE 702 ensures that those PUSCHs in which UCI may be multiplexed are not skipped, thereby ensuring that the UE 702 multiplexes the UCI on the PUSCH in the slot. At 714, the UE 702 (e.g., the PHY layer 705) multiplexes the UCI on the PUSCH with the assigned data. In some examples, the multiplexing at 714 may be based on a configured UCI multiplexing rule. Thus, at 716, the UE 702 transmits a PUSCH with the assigned data in the slot, including the PUSCH with multiplexed UCI and the assigned data, and the UE 702 may drop any other PUSCH that was not assigned any data.

[0067] Referring again to the illustrative example above with respect to Figures 3A-3E with PUSCHs 1-8 scheduled in slot 301 and UCI that may be multiplexed on PUSCH2, the UE 702 ensures that PUSCH2 is sent first to the upper layer (e.g., MAC layer 703) so that PUSCH2 will be assigned data and therefore will not be skipped and may be sent with the multiplexed UCI, as shown in Figure 7C. Thus, in this illustrative example, PUSCH2 is sent with UCI, the remaining PUSCHs 707 (e.g., PUSCHs 1 and 3-8) may be skipped, and PUCCH is dropped so that only PUSCH2 is sent with UCI and data, as shown in Figure 7D. This may be more efficient than if both PUSCH and PUCCH were sent in the slot.

[0068] Thus, by performing data checks before preparing UCI on PUCCH or PUSCH and before allocating data on PUSCH, the UE can avoid fallback to PUCCH and can improve the efficiency of resource usage by ensuring that UCI can be multiplexed on PUSCH, which in turn can save power, save resources, enable PHY layer PUSCH and UCI multiplexing processing, and MAC TB formation in parallel, and improve the uplink PHY timeline.

[0069] 8 illustrates a communications device 800 that may include various components (e.g., corresponding to means-plus-function components) configured to perform operations for the techniques disclosed herein, such as those illustrated in FIGS. 4-7D for UCI multiplexing in the presence of PUSCH skipping. The communications device 800 includes a processing system 802 coupled to a transceiver 808. The transceiver 808 is configured to transmit and receive signals for the communications device 800 via an antenna 810, such as various signals as described herein. The processing system 802 may be configured to perform processing functions for the communications device 800, including processing signals received by and / or to be transmitted by the communications device 800.

[0070] The processing system 802 includes a processor 804 coupled to a computer-readable medium / memory 812 via a bus 806. In some aspects, the computer-readable medium / memory 812 is configured to store instructions (e.g., computer-executable code) that, when executed by the processor 804, cause the processor 804 to perform operations illustrated in at least one of Figures 4-7D or other operations to perform various techniques described herein for UCI multiplexing in the presence of PUSCH skipping.In some aspects, the computer-readable medium / memory 812 stores code 814 for receiving, such as code for receiving an uplink grant for transmission on a plurality of PUSCHs, where the plurality of PUSCHs are located on different CCs, in accordance with one or more aspects of the present disclosure; and stores code 816 for determining, such as code for determining whether PUSCH data is to be transmitted in a slot, in accordance with one or more aspects of the present disclosure, and / or code for determining to transmit UCI in a slot on one or more PUCCHs, or on one or more PUSCHs of the plurality of PUSCHs, based on a determination whether PUSCH data is to be transmitted in a slot, prior to allocating PUSCH data to a PUSCH of the plurality of PUSCHs, in accordance with one or more aspects of the present disclosure; or more aspects, store a code for identifying 818, such as a code for identifying one or more PUSCHs of the plurality of PUSCHs in which the UCI may be transmitted, in a slot, store a code for assigning 820, such as a code for assigning PUSCH data to one or more identified PUSCHs in which the UCI may be transmitted before assigning PUSCH data to the remaining PUSCHs of the plurality of PUSCHs, in accordance with one or more aspects of the present disclosure, and / or store a code for transmitting 822, such as a code for transmitting UCI and PUSCH data in a slot on an assigned PUSCH, in accordance with one or more aspects of the present disclosure, and / or a code for transmitting UCI in a slot on the determined one or more PUCCHs or on the determined one or more PUSCHs, in accordance with one or more aspects of the present disclosure. In some aspects, the processor 804 has circuitry configured to implement the codes stored in the computer-readable medium / memory 812. The processor 804 includes a circuit 824 for receiving, a circuit 826 for determining, a circuit 828 for identifying, a circuit 830 for allocating, and / or a circuit 832 for transmitting in accordance with one or more aspects of the present disclosure.The circuits 824-832 may perform operations provided by the codes 814-822 when the processor 804 executes the codes in the computer-readable medium / memory 812.

[0071] The techniques described herein may be used for various wireless communication technologies, such as NR (e.g., 5G NR or later releases), 3GPP Long Term Evolution (LTE), LTE-Advanced (LTE-A), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single Carrier Frequency Division Multiple Access (SC-FDMA), Time Division Synchronous Code Division Multiple Access (TD-SCDMA), and other networks. The terms "network" and "system" are often used interchangeably. A CDMA network may implement a radio technology, such as Universal Terrestrial Radio Access (UTRA), cdma2000, and the like. UTRA includes Wideband CDMA (WCDMA), and other variants of CDMA. cdma2000 covers IS-2000, IS-95, and IS-856 standards. A TDMA network may implement a radio technology such as Global System for Mobile Communications (GSM). An OFDMA network may implement a radio technology such as NR (e.g., 5G RA), Evolved UTRA (E-UTRA), Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDMA, etc. UTRA and E-UTRA are parts of the Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are releases of UMTS that use E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, and GSM are described in documents from an organization named "3rd Generation Partnership Project" (3GPP). cdma2000 and UMB are described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). NR is a new wireless communications technology under development.

[0072] The techniques described herein may be used for the wireless networks and radio technologies mentioned above, as well as other wireless networks and radio technologies. For clarity, aspects may be described herein using terminology commonly associated with 3G, 4G, and / or 5G wireless technologies, although aspects of the present disclosure may be applied in other generation-based communication systems.

[0073] In 3GPP, the term "cell" can refer to a coverage area of ​​a Node B (NB) and / or an NB subsystem serving this coverage area, depending on the context in which the term is used. In an NR system, the terms "cell" and BS, next generation Node B (gNB or gNode B), access point (AP), distributed unit (DU), carrier, or transmit reception point (TRP) may be used interchangeably. A BS may provide communication coverage for a macrocell, a picocell, a femtocell, and / or other types of cells. A macrocell may cover a relatively large geographic area (e.g., a few kilometers in radius) and may allow unrestricted access by UEs with a service subscription. A picocell may cover a relatively small geographic area and may allow unrestricted access by UEs with a service subscription. A femtocell may cover a relatively small geographic area (e.g., a home) and may allow restricted access by UEs having an association with the femtocell (e.g., UEs in a Closed Subscriber Group (CSG), UEs for users at home, etc.). A BS for a macro cell may be referred to as a macro BS, a BS for a pico cell may be referred to as a pico BS, and a BS for a femto cell may be referred to as a femto BS or a home BS.

[0074] A UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smartphone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, laptop computer, cordless phone, wireless local loop (WLL) station, tablet computer, camera, gaming device, netbook, smartbook, ultrabook, appliance, medical device or equipment, biometric sensor / device, wearable device such as smart watch, smart clothing, smart glasses, smart wristband, smart jewelry (e.g., smart ring, smart bracelet, etc.), entertainment device (e.g., music device, video device, satellite radio, etc.), vehicle component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate over a wireless or wired medium. Some UEs may be considered machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC UEs and eMTC UEs include, for example, a robot, a drone, a remote device, a sensor, a meter, a monitor, a location tag, etc., that may communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node may provide, for example, connectivity for or to a network (e.g., a wide area network such as the Internet or a cellular network) via a wired or wireless communication link. Some UEs may be considered Internet of Things (IoT) devices, which may be narrowband IoT (NB-IoT) devices.

[0075] Some wireless networks (e.g., LTE) utilize orthogonal frequency division multiplexing (OFDM) on the downlink and single-carrier frequency division multiplexing (SC-FDM) on the uplink. OFDM and SC-FDM partition the system bandwidth into multiple (K) orthogonal subcarriers, also commonly referred to as tones, bins, etc. Each subcarrier may be modulated with data. In general, modulation symbols are sent in the frequency domain with OFDM and in the time domain with SC-FDM. The spacing between adjacent subcarriers may be fixed, and the total number of subcarriers (K) may be dependent on the system bandwidth. For example, the spacing of the subcarriers may be 15 kHz, and the minimum resource allocation (called a "resource block" (RB)) may be 12 subcarriers (i.e., 180 kHz). Thus, the nominal fast Fourier transform (FFT) size may be equal to 128, 256, 512, 1024, or 2048 for a system bandwidth of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), respectively. The system bandwidth may also be partitioned into subbands. For example, a subband may cover 1.08 MHz (e.g., 6 RBs), and there may be 1, 2, 4, 8, or 16 subbands for a system bandwidth of 1.25, 2.5, 5, 10, or 20 MHz, respectively. In LTE, the basic transmission time interval (TTI) or packet duration is a 1 ms subframe.

[0076] NR utilizes OFDM with CP on the uplink and downlink and may include support for half-duplex operation using TDD. In NR, a subframe is still 1 ms, but the basic TTI is called a slot. A subframe contains a variable number of slots (e.g., 1, 2, 4, 8, 16, ... slots) depending on the subcarrier spacing. An NR RB is 12 consecutive frequency subcarriers. NR may support a base subcarrier spacing of 15 KHz, and other subcarrier spacings, such as 30 kHz, 60 kHz, 120 kHz, 240 kHz, etc., may be defined for the base subcarrier spacing. The length of the symbol and slot corresponds to the subcarrier spacing. The CP length also depends on the subcarrier spacing. Beamforming may be supported and the beam direction may be dynamically configured. MIMO transmission with precoding may also be supported. In some examples, MIMO configurations in the DL may support up to eight transmit antennas with multi-layer DL transmission of up to eight streams and up to two streams per UE. In some examples, multi-layer transmission with up to two streams per UE may be supported. Multiple cell aggregation may be supported with up to eight serving cells.

[0077] In some examples, access to the air interface may be scheduled. A scheduling entity (e.g., a BS) allocates resources for communication between some or all devices and equipment within its service area or cell. The scheduling entity may be responsible for scheduling, assigning, reconfiguring, and releasing resources for one or more subordinate entities. That is, for scheduled communication, the subordinate entities utilize the resources allocated by the scheduling entity. A base station is not the only entity that may function as a scheduling entity. In some examples, a UE may function as a scheduling entity and schedule resources for one or more subordinate entities (e.g., one or more other UEs), and the other UEs may utilize the resources scheduled by the UE for wireless communication. In some examples, a UE may function as a scheduling entity in a peer-to-peer (P2P) network and / or in a mesh network. In a mesh network example, the UEs may communicate directly with each other in addition to communicating with the scheduling entity.

[0078] In some examples, two or more subordinate entities (e.g., UEs) may communicate with each other using sidelink signals. Real-world applications of such sidelink communications may include public safety, proximity services, UE-to-network relaying, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh, and / or various other suitable applications. In general, a sidelink signal may refer to a signal communicated from one subordinate entity (e.g., UE1) to another subordinate entity (e.g., UE2) without relaying the communication through a scheduling entity (e.g., UE or BS), even though a scheduling entity may be utilized for scheduling and / or control purposes. In some examples, sidelink signals may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use unlicensed spectrum).

[0079] The methods disclosed herein comprise one or more operations or actions for achieving the method. The operations and / or actions of the methods may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of operations or actions is specified, the order and / or use of specific operations and / or actions may be modified without departing from the scope of the claims.

[0080] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items including single members. As an example, "at least one of a, b, or c" is intended to encompass a, b, c, ab, ac, bc, and abc, as well as any combination having multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other permutation of a, b, and c).

[0081] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, looking up (e.g., looking up in a table, database, or another data structure), ascertaining, and the like. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. Also, "determining" may include resolving, selecting, electing, establishing, and the like.

[0082] Exemplary Aspects In a first aspect, a method for wireless communication by a user equipment (UE) includes receiving an uplink grant for transmission on multiple physical uplink shared channels (PUSCHs), where the multiple PUSCHs are located on different component carriers (CCs), identifying one or more PUSCHs of the multiple PUSCHs in which uplink control information (UCI) may be transmitted in a slot, assigning PUSCH data to one or more identified PUSCHs in which UCI may be transmitted before assigning PUSCH data to remaining PUSCHs of the multiple PUSCHs, and transmitting UCI and PUSCH data in the slot on the assigned PUSCH. This may enable the UE to ensure that UCI may be multiplexed on the PUSCH and may avoid falling back to the PUCCH.

[0083] In a second aspect, alone or in combination with the first aspect, the UE determines in which slot PUSCH data will be transmitted, the determining being performed prior to identifying one or more PUSCHs of the multiple PUSCHs in which UCI may be sent and prior to allocating the PUSCH data. This may enable the UE to decide to place UCI on the PUCCH if there is no data, or to request that the data be placed first on the PUSCH in which UCI may be multiplexed, if there is data.

[0084] In a third aspect, alone or in combination with one or more of the first and second aspects, determining that PUSCH data is to be transmitted in a slot includes receiving, at a physical (PHY) layer, an indication from a medium access control (MAC) layer corresponding to the PUSCH data, the indication being received in response to a query from the PHY layer to the MAC layer, periodically, when new data is received at the MAC layer, or a combination thereof, which may enable the UE to make a determination of whether there is a PUSCH to be transmitted in the slot.

[0085] In a fourth aspect, alone or in combination with one or more of the first to third aspects, transmitting UCI and PUSCH data in a slot on an assigned PUSCH includes rate matching the UCI around the PUSCH data, which may result in a lower effective code rate for the transmission.

[0086] In a fifth aspect, alone or in combination with one or more of the first to fourth aspects, the UE generates a MAC layer transport block (TB) and performs PHY layer multiplexing of UCI and PUSCH data in parallel, which may improve the processing timeline.

[0087] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, identifying one or more PUSCHs among the plurality of PUSCHs on which the UCI may be transmitted may be based at least in part on one or more preconfigured rules, thereby providing a mechanism for the UE to determine the PUSCH on which the UCI may be multiplexed.

[0088] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, identifying one or more PUSCHs of the plurality of PUSCHs on which the UCI may be transmitted is based at least in part on a configuration of a physical uplink control channel (PUCCH), thereby providing a mechanism for the UE to determine a PUSCH on which the UCI may be multiplexed.

[0089] In an eighth aspect, alone or in combination with one or more of the first to seventh aspects, the UE skips transmission of at least one empty PUSCH of the set of PUSCHs, which may allow the UE to transmit more efficiently by not wasting resources when there is no PUSCH data to be transmitted in a slot for that PUSCH.

[0090] In a ninth aspect, a method for wireless communication by a UE includes receiving an uplink grant for transmission on multiple PUSCHs in a slot, the multiple PUSCHs being located on different CCs; determining whether PUSCH data is to be transmitted in the slot; before allocating the PUSCH data to a PUSCH of the multiple PUSCHs, based on the determination whether the PUSCH data is to be transmitted in the slot, determining to transmit UCI in the slot on one or more PUCCHs or on one or more PUSCHs of the multiple PUSCHs, and transmitting UCI in the slot on the determined one or more PUCCHs or on the determined one or more PUSCHs.

[0091] In a tenth aspect, alone or in combination with the ninth aspect, determining whether PUSCH data is to be transmitted in a slot includes receiving, at the PHY layer, an indication from the MAC layer corresponding to the PUSCH data, wherein the indication is received in response to a query from the PHY layer to the MAC layer, periodically, when new data is received at the MAC layer, or a combination thereof.

[0092] In an eleventh aspect, alone or in combination with the ninth or tenth aspect, determining to transmit UCI in a slot on one or more PUCCHs or on one or more PUSCHs includes determining to transmit UCI in a slot on one or more PUCCHs when the one or more PUSCHs are empty.

[0093] In a twelfth aspect, alone or in combination with one or more of the ninth to eleventh aspects, determining to transmit UCI in a slot on one or more PUCCHs or on one or more PUSCHs includes determining to transmit UCI in a slot on one or more PUSCHs when PUSCH data is to be transmitted in the slot.

[0094] In a thirteenth aspect, either alone or in combination with one or more of the ninth to twelfth aspects, the UE identifies one or more PUSCHs as PUSCHs among the plurality of PUSCHs on which UCI may be transmitted, and assigns PUSCH data to the one or more PUSCHs on which UCI may be transmitted before assigning PUSCH data to remaining PUSCHs among the plurality of PUSCHs.

[0095] In a fourteenth aspect, alone or in combination with one or more of the ninth to thirteenth aspects, the UE requests, by the PHY layer, the MAC layer to allocate PUSCH data on one or more PUSCHs on which UCI may be sent before allocating PUSCH data on the remaining PUSCHs of the plurality of PUSCHs, or alternatively, the PHY layer provides, by the MAC layer, an ordered list for constructing a set of PUSCHs, and the identified one or more PUSCHs are ordered in the ordered list before the remaining PUSCHs of the plurality of PUSCHs.

[0096] In a fifteenth aspect, alone or in combination with one or more of the ninth to fourteenth aspects, identifying one or more PUSCHs on which UCI may be transmitted is based at least in part on one or more preconfigured rules.

[0097] In a sixteenth aspect, alone or in combination with one or more of the ninth to fifteenth aspects, identifying one or more PUSCHs in which UCI may be transmitted is based at least in part on a configuration of a PUCCH.

[0098] In a seventeenth aspect, alone or in combination with one or more of the ninth to sixteenth aspects, transmitting UCI in a slot on one or more PUSCHs includes rate matching the UCI around the PUSCH data.

[0099] In an eighteenth aspect, either alone or in combination with one or more of the ninth to seventeenth aspects, the UE generates a MAC layer TB and performs PHY layer multiplexing of UCI and PUSCH data in parallel.

[0100] In a nineteenth aspect, either alone or in combination with one or more of the ninth to eighteenth aspects, the UE skips transmission of at least one null PUSCH among the plurality of PUSCHs.

[0101] The foregoing description is provided to enable any person skilled in the art to practice the various embodiments described herein. Various modifications of these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments. Thus, the claims are not limited to the embodiments shown herein, but are to be accorded the full scope consistent with the language of the claims, and references to elements in the singular shall mean "one and only," rather than "one or more," unless expressly stated as such. Unless otherwise stated, the term "several" refers to one or more. All structural and functional equivalents of the elements of the various embodiments described throughout this disclosure that are known or that later become known to those skilled in the art are expressly incorporated herein by reference and are intended to be encompassed by the claims. Moreover, nothing disclosed herein is made public, regardless of whether such disclosure is expressly set forth in the claims. No claim element is to be construed under the provisions of 35 U.S.C. 112(f) unless the element is expressly recited using the phrase "means for."

[0102] The various operations of the methods described above may be performed by any suitable means capable of performing the corresponding functions. The means may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. In general, where there are operations illustrated in figures, those operations may have corresponding counterpart means-plus-function components that are similarly numbered.

[0103] The various example logic blocks, modules and circuits described in connection with this disclosure may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but alternatively, the processor may be any commercially available processor, controller, microcontroller or state machine. A processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0104] When implemented in hardware, an exemplary hardware configuration may comprise a processing system in a wireless node. The processing system may be implemented using a bus architecture. The bus may include any number of interconnected buses and bridges depending on the particular application and overall design constraints of the processing system. The bus may link various circuits together, including the processor, the machine-readable medium, and the bus interface. The bus interface may be used to connect a network adapter to the processing system via the bus, among other things. The network adapter may be used to implement the signal processing functions of the PHY layer. In the case of a user terminal (see FIG. 8), a user interface (e.g., keypad, display, mouse, joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, etc., which are well known in the art and therefore will not be described further. The processor may be implemented using one or more general-purpose and / or special-purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits capable of executing software. Those skilled in the art will recognize how to best implement the described functionality for a processing system depending on the particular application and the overall design constraints imposed on the overall system.

[0105] If implemented in software, the functions may be stored on or transmitted over a computer-readable medium as one or more instructions or code. Software should be broadly construed to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise. Computer-readable media includes both computer storage media and communication media, including any medium that facilitates transfer of a computer program from one place to another. A processor may be responsible for general processing, including managing a bus and executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor such that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium may be integral to the processor. By way of example, a machine-readable medium may include a transmission line, a carrier wave modulated by data, and / or a computer-readable storage medium having instructions stored thereon separate from a wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, the machine-readable medium or any portion thereof may be integrated into the processor, such as a cache and / or a general-purpose register file. Examples of machine-readable storage media may include, by way of example, a RAM (random access memory), a flash memory, a ROM (read-only memory), a PROM (programmable read-only memory), an EPROM (erasable programmable read-only memory), an EEPROM (electrically erasable programmable read-only memory), a register, a magnetic disk, an optical disk, a hard drive, or any other suitable storage medium, or any combination thereof. The machine-readable medium may be embodied in a computer program product.

[0106] A software module may comprise a single instruction or many instructions and may be distributed across several different code segments, among different programs, and across multiple storage media. A computer-readable medium may comprise several software modules. A software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include a transmitting module and a receiving module. Each software module may reside in a single storage device or be distributed across multiple storage devices. As an example, a software module may be loaded into RAM from a hard drive when a trigger event occurs. During execution of a software module, a processor may load some of the instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general-purpose register file to be executed by the processor. When referring to a function of a software module below, it will be understood that such function is implemented by a processor when executing instructions from that software module.

[0107] Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared (IR), radio, and microwave, the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc, where disks typically reproduce data magnetically and discs reproduce data optically using lasers. Thus, in some aspects computer-readable medium may comprise non-transitory computer-readable medium (e.g., tangible media). In addition, in other aspects computer-readable media may comprise transitory computer-readable media (eg, a signal). Combinations of the above should also be included within the scope of computer-readable media.

[0108] Accordingly, some aspects may comprise a computer program product for performing operations presented herein. For example, such a computer program product may comprise a computer-readable medium having stored thereon (and / or encoded thereon) instructions executable by one or more processors to perform operations described herein, e.g., instructions for performing operations described herein and illustrated in at least one of Figures 4-7D.

[0109] Furthermore, it should be appreciated that modules and / or other suitable means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a user terminal and / or base station, where applicable. For example, such devices may be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein may be provided via a storage means such that the user terminal and / or base station may obtain the various methods upon coupling or providing the storage means (e.g., RAM, ROM, physical storage medium such as a compact disk (CD) or floppy disk, etc.) to the device. Moreover, any other suitable technique for providing the methods and techniques described herein to a device may be utilized.

[0110] It is to be understood that the claims are not limited to the precise configuration and components illustrated above. Various modifications, changes and variations may be made in the arrangement, operation and details of the methods and apparatus described above without departing from the scope of the claims. [Explanation of symbols]

[0111] 100 Wireless Communication Networks 102a, 102b, 102c Macrocells 102x picocell 102y, 102z Femtocell 110 BS, Mobile BS 110a~110z Base station (BS) 110a, 110b, 110c, 110x, 110y, 110z BS 110r relay station 120, 120a, 120r, 120x, 120y, 302, 602, 702UE 120a~120y User Equipment (UE) 122, 281 UCI Multiplexing Manager 130 Network Controller 212, 262 Data source 220 Transmitting Processor, Processor 230 Transmit (TX) Multiple Input Multiple Output (MIMO) Processor 232 Modulators and demodulators 232a~232t Modulator (MOD), Modulator 234, 234a-234t, 252, 252a-252r Antennas 236, 256 MIMO detector 238, 258 Receive Processor 239, 260 Data Sink 240, 280 Controller / Processor 242, 282 memory 244 Scheduler 254 Demodulator 254a~254r Demodulator (DEMOD), demodulator, modulator 264 Transmit Processor 266 TX MIMO Processor 301 Slots 303, 603, 703 MAC Layer 304 servings gNB 305, 605, 705 PHY Layer 307, 607, 707 Remaining PUSCH 309 PUCCH 604, 704 Serving BS 800 Communication Devices 802 Processing System 804 Processor 806 Bus 808 Transceiver 810 Antenna 812 Computer-readable medium / memory 814 receiving code, code 816 Code to determine, code 818 Identification code, code 820 Code to assign, code 822 code to send, code 824 Receiving circuits, circuits 826 Circuit for determining 828 Circuits for Identifying 830 Circuits for allocating, circuits 832 Transmitting circuits, circuits

Claims

1. 1. A method for wireless communication by a user equipment (UE), comprising: receiving an uplink grant for transmission on a plurality of Physical Uplink Shared Channels (PUSCHs), the plurality of PUSCHs being located on different Component Carriers (CCs); identifying one or more PUSCHs among the plurality of PUSCHs in which uplink control information (UCI) may be transmitted in a slot; allocating PUSCH data to the one or more identified PUSCHs on which the UCI may be transmitted before allocating PUSCH data to remaining PUSCHs of the plurality of PUSCHs; transmitting the UCI and the PUSCH data in the slot on the assigned PUSCH; The method includes:

2. The method further comprising:

2. The method of claim 1, further comprising: determining which PUSCH data is to be transmitted in the slot, the determining being performed before the identifying one or more PUSCHs among the plurality of PUSCHs for which the UCI may be sent and before the allocating the PUSCH data.

3. 3. The method of claim 2, wherein the step of determining that the PUSCH data is to be transmitted in the slot includes a step of receiving, at a physical (PHY) layer, an indication corresponding to the PUSCH data from a medium access control (MAC) layer, the indication being received in response to a query from the PHY layer to the MAC layer, periodically, when new data is received at the MAC layer, or a combination thereof.

4. 2. The method of claim 1, wherein the step of transmitting the UCI and the PUSCH data in the slot on the assigned PUSCH comprises rate matching the UCI around the PUSCH data.

5. generating a Medium Access Control (MAC) layer Transport Block (TB) and in parallel performing a Physical (PHY) layer multiplexing of the UCI and PUSCH data; The method of claim 1, further comprising:

6. 10. The method of claim 1, wherein identifying the one or more PUSCHs of the plurality of PUSCHs on which the UCI may be transmitted is based at least in part on one or more preconfigured rules.

7. 2. The method of claim 1, wherein identifying the one or more PUSCHs of the plurality of PUSCHs on which the UCI may be transmitted is based at least in part on a configuration of a physical uplink control channel (PUCCH).

8. The method of claim 1 , further comprising skipping transmission of at least one null PUSCH of the plurality of PUSCHs.

9. 1. A method for wireless communication by a user equipment (UE), comprising: receiving an uplink grant for transmission on a plurality of Physical Uplink Shared Channels (PUSCHs) in a slot, the plurality of PUSCHs being located on different component carriers (CCs); determining whether PUSCH data is to be transmitted in the slot; Before allocating the PUSCH data to a PUSCH among the plurality of PUSCHs, based on the determination of whether the PUSCH data will be transmitted in the slot, determining to transmit uplink control information (UCI) in the slot on one or more physical uplink control channels (PUCCHs) or on one or more PUSCHs among the plurality of PUSCHs; transmitting the UCI in the slot on the determined one or more PUCCHs or on the determined one or more PUSCHs; The method includes:

10. 10. The method of claim 9, wherein the step of determining whether the PUSCH data is to be transmitted in the slot includes a step of receiving, at a physical (PHY) layer, an indication corresponding to the PUSCH data from a medium access control (MAC) layer, the indication being received in response to a query from the PHY layer to the MAC layer, periodically, when new data is received at the MAC layer, or a combination thereof.

11. 10. The method of claim 9, wherein the step of determining to transmit the UCI in the slot on the one or more PUCCHs or on the one or more PUSCHs comprises the step of determining to transmit the UCI in the slot on the one or more PUCCHs when the one or more PUSCHs are empty.

12. 10. The method of claim 9, wherein the step of determining to transmit the UCI in the slot on the one or more PUCCHs or the one or more PUSCHs comprises determining to transmit the UCI in the slot on the one or more PUSCHs when the PUSCH data is to be transmitted in the slot.

13. identifying the one or more PUSCHs as PUSCHs among the plurality of PUSCHs on which the UCI may be transmitted; allocating PUSCH data to the one or more PUSCHs on which the UCI may be transmitted before allocating PUSCH data to remaining PUSCHs among the plurality of PUSCHs; 13. The method of claim 12, further comprising:

14. requesting, by a physical (PHY) layer, a medium access control (MAC) layer to allocate PUSCH data on the one or more PUSCHs on which the UCI may be sent before allocating PUSCH data on the remaining PUSCHs of the plurality of PUSCHs; or providing, by the PHY layer, to the MAC layer, an ordered list for constructing the plurality of PUSCHs, the identified one or more PUSCHs being ordered in the ordered list before the remaining PUSCHs of the plurality of PUSCHs.

14. The method of claim 13, further comprising:

15. 14. The method of claim 13, wherein the identifying the one or more PUSCHs over which the UCI may be transmitted is based at least in part on one or more preconfigured rules.

16. 14. The method of claim 13, wherein the step of identifying the one or more PUSCHs over which the UCI may be transmitted is based at least in part on a configuration of a PUCCH.

17. 13. The method of claim 12, wherein the step of transmitting the UCI in the slot on the one or more PUSCHs comprises rate matching the UCI around the PUSCH data.

18. 13. The method of claim 12, further comprising generating a Medium Access Control (MAC) layer Transport Block (TB) and performing a Physical (PHY) layer multiplexing of the UCI and PUSCH data in parallel.

19. The method of claim 9, further comprising skipping transmission of at least one null PUSCH of the plurality of PUSCHs.

20. 1. An apparatus for wireless communication, comprising: Memory, at least one processor coupled to the memory, the processor and memory comprising: receiving an uplink grant for transmission on a plurality of physical uplink shared channels (PUSCHs), the plurality of PUSCHs being located on different component carriers (CCs); identifying one or more PUSCHs among the plurality of PUSCHs in which uplink control information (UCI) may be transmitted in a slot; allocating PUSCH data to the one or more identified PUSCHs on which the UCI may be transmitted before allocating PUSCH data to remaining PUSCHs of the plurality of PUSCHs; and transmitting the UCI and the PUSCH data in the slot on the assigned PUSCH. An apparatus configured to:

21. The processor and memory include 21. The apparatus of claim 20, further configured to determine that the PUSCH data is to be transmitted in the slot, the determining being performed prior to the identifying the one or more PUSCHs of the plurality of PUSCHs for which the UCI may be sent and prior to the allocating the PUSCH data.

22. The processor and memory include receiving, at a physical (PHY) layer, an indication from a medium access control (MAC) layer corresponding to the PUSCH data, the indication being received in response to a query from the PHY layer to the MAC layer, periodically, when new data is received at the MAC layer, or a combination thereof; 22. The apparatus of claim 21, further configured to determine that the PUSCH data is to be transmitted in the slot by:

23. 21. The apparatus of claim 20, wherein the processor and memory are further configured to transmit the UCI and the PUSCH data in the slot on the assigned PUSCH by rate matching the UCI around the PUSCH data.

24. The processor and memory include generating a Medium Access Control (MAC) layer Transport Block (TB) and in parallel performing a Physical (PHY) layer multiplexing of the UCI and PUSCH data; The apparatus of claim 20 , further configured to:

25. 21. The apparatus of claim 20, wherein the processor and memory are further configured to identify, based at least in part on one or more preconfigured rules, the one or more PUSCHs among the plurality of PUSCHs in which the UCI may be transmitted.

26. 21. The apparatus of claim 20, wherein the processor and memory are further configured to identify the one or more PUSCHs among the plurality of PUSCHs in which the UCI may be transmitted based at least in part on a configuration of a physical uplink control channel (PUCCH).

27. The processor and memory include skipping transmission of at least one empty PUSCH among the plurality of PUSCHs. The apparatus of claim 20 , further configured to:

28. 1. An apparatus for wireless communication, comprising: Memory, at least one processor coupled to the memory, the processor and memory comprising: receiving an uplink grant for transmission on a plurality of physical uplink shared channels (PUSCHs) in a slot, the plurality of PUSCHs being located on different component carriers (CCs); determining whether PUSCH data is to be transmitted in the slot; Before allocating the PUSCH data to a PUSCH of the plurality of PUSCHs, based on the determination of whether the PUSCH data will be transmitted in the slot, determining to transmit uplink control information (UCI) in the slot on one or more physical uplink control channels (PUCCHs) or on one or more PUSCHs of the plurality of PUSCHs; and transmitting the UCI in the slot on the determined one or more PUCCHs or on the determined one or more PUSCHs. An apparatus configured to:

29. The processor and memory include receiving an indication at a physical (PHY) layer from a medium access control (MAC) layer, the indication being received in response to a query from the PHY layer to the MAC layer, periodically, when new data is received at the MAC layer, or a combination thereof; 30. The apparatus of claim 28, further configured to determine whether the PUSCH data is to be transmitted in the slot by:

30. 30. The apparatus of claim 28, wherein the processor and memory are further configured to determine to transmit the UCI in the slot on the one or more PUCCHs or on the one or more PUSCHs by determining to transmit the UCI in the slot on the one or more PUCCHs when the one or more PUSCHs are empty.

31. 30. The apparatus of claim 28, wherein the processor and memory are further configured to determine to transmit the UCI in the slot on the one or more PUCCHs or on the one or more PUSCHs by determining to transmit the UCI in the slot on the one or more PUSCHs when the PUSCH data is to be transmitted in the slot.

32. The processor and memory include identifying the one or more PUSCHs as PUSCHs among the plurality of PUSCHs on which the UCI may be transmitted; and allocating PUSCH data to the one or more PUSCHs on which the UCI may be transmitted before allocating PUSCH data to remaining PUSCHs among the plurality of PUSCHs; 32. The apparatus of claim 31, further configured to:

33. The processor and memory include requesting, by a physical (PHY) layer, a medium access control (MAC) layer to allocate PUSCH data on the one or more PUSCHs on which the UCI may be sent before allocating PUSCH data on the remaining PUSCHs of the plurality of PUSCHs; or providing, by the PHY layer, to the MAC layer, an ordered list for constructing the plurality of PUSCHs, wherein the identified one or more PUSCHs are ordered in the ordered list before the remaining PUSCHs of the plurality of PUSCHs; 33. The apparatus of claim 32, configured to:

34. 33. The apparatus of claim 32, wherein the processor and memory are further configured to identify the one or more PUSCHs over which the UCI may be transmitted based at least in part on one or more preconfigured rules.

35. 33. The apparatus of claim 32, wherein the processor and memory are further configured to identify the one or more PUSCHs over which the UCI may be transmitted based at least in part on a configuration of a PUCCH.

36. 32. The apparatus of claim 31, wherein the processor and memory are further configured to transmit the UCI in the slot on the one or more PUSCHs by rate matching the UCI around the PUSCH data.

37. The processor and memory include generating a Medium Access Control (MAC) layer Transport Block (TB) and in parallel performing a Physical (PHY) layer multiplexing of the UCI and PUSCH data; 32. The apparatus of claim 31, further configured to:

38. The processor and memory include skipping transmission of at least one empty PUSCH among the plurality of PUSCHs.

30. The apparatus of claim 28, further configured to:

39. 1. An apparatus for wireless communication, comprising: means for receiving an uplink grant for transmission on a plurality of physical uplink shared channels (PUSCHs), the plurality of PUSCHs being located on different component carriers (CCs); means for identifying one or more PUSCHs among the plurality of PUSCHs in which uplink control information (UCI) may be transmitted in a slot; means for allocating PUSCH data to the one or more identified PUSCHs on which the UCI may be transmitted before allocating PUSCH data to remaining PUSCHs of the plurality of PUSCHs; means for transmitting the UCI and the PUSCH data in the slot on the assigned PUSCH; An apparatus comprising:

40. 1. An apparatus for wireless communication, comprising: means for receiving an uplink grant for transmission on a plurality of physical uplink shared channels (PUSCHs) in a slot, the plurality of PUSCHs being located on different component carriers (CCs); means for determining whether PUSCH data is to be transmitted in the slot; means for determining, before allocating the PUSCH data to a PUSCH of the plurality of PUSCHs, to transmit uplink control information (UCI) in the slot on one or more physical uplink control channels (PUCCHs) or on one or more PUSCHs of the plurality of PUSCHs based on the determination of whether the PUSCH data will be transmitted in the slot; means for transmitting the UCI in the slot on the determined one or more PUCCHs or on the determined one or more PUSCHs; An apparatus comprising:

41. A computer readable medium having computer executable code stored thereon, comprising: and code for receiving an uplink grant for transmission on a plurality of physical uplink shared channels (PUSCHs), the plurality of PUSCHs being located on different component carriers (CCs). code for identifying one or more PUSCHs of the plurality of PUSCHs in which uplink control information (UCI) may be transmitted in a slot; code for allocating PUSCH data to the one or more identified PUSCHs on which the UCI may be transmitted before allocating PUSCH data to remaining PUSCHs of the plurality of PUSCHs; code for transmitting the UCI and the PUSCH data in the slot on the assigned PUSCH; 16. A computer readable medium comprising:

42. 42. The computer-readable medium of claim 41, further comprising code for determining which PUSCH data is to be transmitted in the slot, the code for determining being configured to be executed before executing the code for identifying the one or more PUSCHs of the plurality of PUSCHs in which the UCI may be sent and before executing the code for allocating the PUSCH data.

43. 43. The computer-readable medium of claim 42, wherein the code for determining that the PUSCH data is to be transmitted in the slot comprises code for receiving, at a physical (PHY) layer, an indication from a medium access control (MAC) layer corresponding to the PUSCH data, the indication being received in response to a query from the PHY layer to the MAC layer, periodically, when new data is received at the MAC layer, or a combination thereof.

44. A computer readable medium having computer executable code stored thereon, comprising: and code for receiving an uplink grant for transmission on a plurality of physical uplink shared channels (PUSCHs) in a slot, the plurality of PUSCHs being located on different component carriers (CCs). code for determining whether PUSCH data is to be transmitted in the slot; code for determining, prior to allocating the PUSCH data to a PUSCH of the plurality of PUSCHs, to transmit uplink control information (UCI) in the slot on one or more physical uplink control channels (PUCCHs) or on one or more PUSCHs of the plurality of PUSCHs based on the determination of whether the PUSCH data will be transmitted in the slot; a code for transmitting the UCI in the slot on the determined one or more PUCCHs or on the determined one or more PUSCHs; 16. A computer readable medium comprising:

Images