Method, apparatus and computer readable medium for wireless communication

Abstract

Certain aspects of the present disclosure provide methods, apparatuses, and computer readable media for wireless communication. A method, which may be performed by a user equipment (UE), includes receiving an uplink grant for transmissions 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) may be transmitted in a time slot; assigning PUSCH data to the remaining PUSCHs of the plurality of PUSCHs only after assigning PUSCH data to the one or more identified PUSCHs on which the UCI can be transmitted; and transmitting the UCI and the PUSCH data on the assigned PUSCH in the time slot.

Description

[0001] This invention patent application is a divisional application of the invention patent application with international application number PCT / US2019 / 066051, international application date December 12, 2019, application number 201980100300.8 entering the Chinese national phase, and name “Uplink control information multiplexing with dynamic physical uplink shared channel skipping”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

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

[0004] Aspects of the present disclosure relate to wireless communications, and more particularly, to methods, apparatus, and computer-readable media for wireless communications. Background Art

[0005] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcast, etc. 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, etc.). 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 just a few.

[0006] These multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate at a city, country, region, and even global level. New radio (e.g., 5G NR) is an example of an emerging telecommunication standard. NR is an enhancement set of the LTE mobile standard promulgated by 3GPP. NR is designed to better support mobile broadband Internet access by improving spectrum efficiency, reducing costs, improving services, utilizing new spectrum, and better integrating with other open standards using OFDMA with cyclic prefix (CP) on downlink (DL) and uplink (UL). To this end, NR supports beamforming, multiple-input multiple-output (MIMO) antenna technology, and carrier aggregation.

[0007] However, as the demand for mobile broadband access continues to grow, there is a need for further improvements to NR and LTE technologies. Preferably, these improvements should be applicable to other multiple access technologies and the telecommunication standards that employ these technologies. Summary of the invention

[0008] The systems, methods, and apparatus of the present disclosure each have several aspects, no single one of which is solely responsible for its desirable attributes. Without limiting the scope of the disclosure as expressed in the appended claims, some features will now be briefly discussed. After considering this discussion, and particularly after reading the section entitled "Detailed Description," it will be understood how the features of the present disclosure provide improved handling of uplink control information (UCI) multiplexing in a physical uplink shared channel (PUSCH) when dynamic PUSCH skipping is configured.

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

[0010] Certain 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 time slot, the multiple PUSCHs being located on different CCs. The method generally includes determining whether PUSCH data will be transmitted in the time slot. The method generally includes determining, before assigning the PUSCH data to a PUSCH in the multiple PUSCHs, that UCI is to be transmitted in the time slot on one or more PUCCHs or on one or more PUSCHs in the multiple PUSCHs based on a determination as to whether the PUSCH data will be transmitted in the time slot. The method generally includes transmitting UCI on the determined one or more PUCCHs or on the determined one or more PUSCHs in the time slot.

[0011] Certain 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 in the plurality of PUSCHs on which UCI can be transmitted in a time slot. The apparatus generally includes means for assigning PUSCH data to the remaining PUSCHs in the plurality of PUSCHs only after assigning PUSCH data to the one or more identified PUSCHs on which UCI can be transmitted; and means for transmitting the UCI and the PUSCH data on the assigned PUSCHs in the time slot.

[0012] Certain aspects provide an apparatus for wireless communication. The apparatus generally includes a device for receiving an uplink grant for transmission on multiple PUSCHs in a time slot, the multiple PUSCHs being located on different CCs. The apparatus generally includes a device for determining whether PUSCH data will be transmitted in the time slot. The apparatus generally includes a device for determining, before assigning the PUSCH data to a PUSCH in the multiple PUSCHs, whether UCI is to be transmitted in the time slot on one or more PUCCHs or on one or more PUSCHs in the multiple PUSCHs based on a determination as to whether the PUSCH data will be transmitted in the time slot. The apparatus generally includes a device for transmitting UCI on the determined one or more PUCCHs or on the determined one or more PUSCHs in the time slot.

[0013] Certain 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 multiple PUSCHs, the multiple PUSCHs being located on different CCs. The at least one processor is generally configured to identify one or more PUSCHs in the multiple PUSCHs on which UCI can be transmitted in a time slot. The at least one processor is generally configured to assign PUSCH data to the remaining PUSCHs in the multiple PUSCHs only after assigning PUSCH data to one or more identified PUSCHs on which UCI can be transmitted; and transmit the UCI and PUSCH data on the assigned PUSCH in the time slot.

[0014] Certain 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 multiple PUSCHs in a time slot, the multiple PUSCHs being located on different CCs. The at least one processor is generally configured to determine whether PUSCH data will be transmitted in the time slot. The at least one processor is generally configured to determine whether UCI is to be transmitted on one or more PUCCHs or on one or more PUSCHs in the multiple PUSCHs in the time slot based on a determination as to whether the PUSCH data will be transmitted in the time slot before assigning the PUSCH data to a PUSCH in the multiple PUSCHs. The at least one processor is generally configured to transmit UCI on the determined one or more PUCCHs or on the determined one or more PUSCHs in the time slot.

[0015] Certain aspects provide a computer-readable medium having computer-executable code stored thereon for wireless communication. The computer-readable medium generally includes code for receiving an uplink grant for transmission on multiple PUSCHs, the multiple PUSCHs being located on different CCs. The computer-readable medium generally includes code for identifying one or more PUSCHs in the multiple PUSCHs on which UCI can be transmitted in a time slot. The computer-readable medium generally includes code for assigning PUSCH data to the remaining PUSCHs in the multiple PUSCHs only after assigning PUSCH data to one or more identified PUSCHs on which UCI can be transmitted; and code for transmitting the UCI and PUSCH data on the assigned PUSCH in the time slot.

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

[0017] To achieve the foregoing and related ends, the one or more aspects include the features fully described below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain illustrative features of the one or more aspects. However, these features are only indicative of several of the various ways in which the principles of the various aspects can be employed. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to understand in detail the manner in which the above-stated features of the present disclosure are used, a more particular description of the content briefly summarized above may be made with reference to various aspects, some of which are illustrated in the accompanying drawings. It should be noted, however, that the accompanying drawings illustrate only certain typical aspects of the present disclosure and are not to be considered limiting of its scope, as the description may admit to other equally effective aspects.

[0019] Figure 1 is a block diagram conceptually illustrating an example telecommunications system in accordance with certain aspects of the present disclosure.

[0020] Figure 2 is a block diagram conceptually illustrating designs of example base stations (BSs) and user equipment (UEs) in accordance with certain aspects of the present disclosure.

[0021] Figure 3A is a call flow diagram illustrating example uplink control information (UCI) fallback to physical uplink control channel (PUCCH) with physical uplink shared channel (PUSCH) skipping.

[0022] Figure 3B is a block diagram illustrating example overlapping PUSCH(s) and PUCCH configured in a time slot.

[0023] Figure 3C It is a commentary Figure 3A A more detailed call flow diagram illustrating UCI fallback to PUCCH with PUSCH skipping is shown in FIG.

[0024] Figure 3D is a block diagram showing example UCI being multiplexed in a PUSCH and data being assigned to another PUSCH in a slot.

[0025] Figure 3E is a block diagram illustrating example UCI fallback to PUCCH in a slot.

[0026] Figure 3F is a block diagram illustrating example UCI fallback to PUCCH and PUSCH skipping in a slot.

[0027] Figure 4 is a flow diagram illustrating example operations for wireless communications by a UE in accordance with certain aspects of the present disclosure.

[0028] Figure 5 is a flow diagram illustrating example operations for wireless communications by a UE in accordance with certain aspects of the present disclosure.

[0029] Fig. 6A is a call flow diagram illustrating example UCI transmission on PUCCH with PUSCH skipping in accordance with aspects of the present disclosure.

[0030] Figure 6B is a more detailed call flow diagram illustrating example UCI transmission on PUCCH with PUSCH skipping in accordance with aspects of the present disclosure.

[0031] Figure 6C is a block diagram illustrating example UCI being transmitted in a PUCCH when no data is assigned to the PUSCH in a slot in accordance with aspects of the present disclosure.

[0032] Fig.6D is a block diagram illustrating example UCI being transmitted in a PUCCH and PUSCH skipping when no data is assigned to the PUSCH in a slot according to one or more aspects of the present disclosure.

[0033] Fig. 7A is a call flow diagram illustrating example UCI multiplexing on PUSCH with PUSCH skipping in accordance with aspects of the present disclosure.

[0034] Figure 7B is a more detailed call flow diagram illustrating example UCI multiplexing on PUSCH with PUSCH skipping in accordance with aspects of the present disclosure.

[0035] Figure 7C is a block diagram illustrating example data assigned to time slots in which UCI is multiplexed according to aspects of the present disclosure.

[0036] Fig.7D is a block diagram illustrating example data being assigned to slots in which UCI is multiplexed and PUSCH skipping according to one or more aspects of the present disclosure.

[0037] Figure 8 Illustrated are communications devices that may include various components configured to perform operations for the techniques disclosed herein in accordance with aspects of the present disclosure.

[0038] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one aspect may be beneficially utilized in other aspects without specific recitation. DETAILED DESCRIPTION

[0039] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for handling uplink control information (UCI) multiplexing in a physical uplink shared channel (PUSCH) when dynamic PUSCH skipping is configured.

[0040] In certain systems (e.g., new radio or 5G NR systems), a user equipment (UE) is configured to transmit uplink control information (UCI), which may include scheduling requests (SRs), hybrid automatic repeat request (HARQ) feedback (e.g., acknowledgement / negative acknowledgement or HARQ-ACK information), and / or channel state information (CSI) feedback, among others. The UE is also configured for data transmission on the 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 time slot). The UE may transmit UCI in a physical uplink control channel (PUCCH). However, in some cases, when the UCI and PUSCH overlap in time, the UE may transmit UCI in the PUSCH (e.g., instead of on the PUCCH). 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, multiplex the UCI with uplink data).

[0041] In certain systems (e.g., new radio or 5G NR systems), a UE may be configured to skip transmission of a PUSCH without any assigned data (e.g., dynamically when the UE has no uplink data to send on the PUSCH at the scheduled time of the PUSCH). As used herein, PUSCH skipping may refer to the UE dropping or not transmitting on certain PUSCHs (e.g., certain PUSCHs may include PUSCHs assigned to the UE for uplink transmission via an uplink grant). PUSCH skipping may be based on configured skipping rules. In some scenarios, when the UE decides to multiplex UCI in the PUSCH, the UE may not be aware that the PUSCH will be skipped. In such scenarios, the UE may fall back to transmitting UCI on the PUCCH. This may reduce efficiency (e.g., by increasing the time and power consumption used to transmit UCI).

[0042] Various aspects of the present disclosure provide solutions for multiplexing UCI on PUSCH when PUSCH skipping is configured. For example, various aspects provide for the UE to check whether there is uplink data for transmission before multiplexing UCI in PUSCH. Therefore, according to certain aspects, when there is no uplink data, the UE can put UCI on PUCCH. In this way, when the UE determines to skip PUSCH, the UE avoids preparing UCI on PUSCH and then falls back to sending UCI on PUCCH. In addition, when there is uplink data, the UE can assign data to other PUSCHs only after assigning data to the PUSCH on which UCI can be multiplexed. In this way, the UE can ensure that UCI can be multiplexed on PUSCH in the time slot because the PUSCH with data will not be skipped. In some examples, the multiplexed UCI can puncture the PUSCH (e.g., the PUSCH data is rate matched). In some examples, UCI may be punctured into the PUSCH when (e.g., only when) the number of UCI bits to be transmitted is for a small amount of UCI data (such as below a threshold number of UCI bits (e.g., equal to or less than 2-bit UCI)). For larger amounts of UCI data (e.g., above a threshold), the UCI may be multiplexed by rate matching the PUSCH. For example, puncturing or rate matching may be performed as defined in a wireless standard (e.g., an IEEE wireless standard). By multiplexing UCI bits onto the PUSCH, the effective code rate of the PUSCH may be increased. 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).

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

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

[0045] The following description provides an example of UCI multiplexing in PUSCH when dynamic PUSCH skipping is configured in a communication system, without limiting the scope, applicability, or examples set forth in the claims. Changes may be made to the functions and arrangements of the elements discussed without departing from the scope of the present disclosure. Various examples may appropriately omit, replace, or add various procedures or components. For example, the described method may be performed in an order different from the order described, and various steps may be added, omitted, or combined. Moreover, the features described with reference to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functionalities, or structures and functionalities that are supplementary to or in addition to the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be implemented by one or more elements of the claims. The wording "exemplary" is used herein to mean "used as an example, instance, or illustration". Any aspect described herein as "exemplary" is not necessarily to be interpreted as being superior to or superior to other aspects.

[0046] In general, any number of wireless networks may be deployed in a given geographic area. Each wireless network may support a specific radio access technology (RAT) and may operate on one or more frequencies. RAT may also be referred to as radio technology, air interface, etc. Frequency may also be referred to as carrier, subcarrier, frequency channel, frequency modulation, 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, a 5G NR RAT network may be deployed.

[0047] Figure 1 An example wireless communication network 100 is illustrated in which aspects of the present disclosure may be performed. For example, the wireless communication network 100 may be a NR system (e.g., a 5G NR network).

[0048] like Figure 1As illustrated in , the wireless communication network 100 may include several base stations (BSs) 110a-z (each also individually referred to herein as BS 110 or collectively referred to as BS 110) and other network entities. BS 110 may provide communication coverage for a specific geographic area (sometimes referred to as a "cell"), which may be stationary or mobile depending on the location of the mobile BS 110. In some examples, BS 110 may be interconnected to each other and / or to one or more other BSs or network nodes (not shown) in the wireless communication network 100 using any suitable transport network via various types of backhaul interfaces (e.g., direct physical connections, wireless connections, virtual networks, etc.). Figure 1 In the example shown in , BS110a, 110b, and 110c may be macro BSs for macro cells 102a, 102b, and 102c, respectively. BS110x may be a pico BS for a pico cell 102x. BS110y and 110z may be femto BSs for femto cells 102y and 102z, respectively. The BS may support one or more cells. BS110 communicates with user equipment (UE) 120a-y (each also individually referred to herein as UE 120 or collectively referred to as UE 120) in the wireless communication network 100. UE 120 (e.g., 120x, 120y, etc.) may be dispersed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile.

[0049] According to certain aspects, UE 120 may be configured to perform UCI multiplexing and PUSCH skipping. Figure 1As shown in , UE120a includes a UCI multiplexing manager 122. According to various aspects of the present disclosure, the UCI multiplexing manager 122 may be configured to perform UCI multiplexing in the case of PUSCH skipping. In some examples, the UCI multiplexing manager 122 may receive an uplink grant for transmission on multiple PUSCHs, which may be located on different CCs. The UCI multiplexing manager 122 may further identify one or more PUSCHs in the multiple PUSCHs on which UCI can be transmitted in a time slot. Additionally, the UCI multiplexing manager 122 may also assign PUSCH data to the remaining PUSCHs in the multiple PUSCHs after assigning PUSCH data to one or more identified PUSCHs on which UCI can be transmitted. The UCI multiplexing manager 122 may further transmit UCI and PUSCH data on the assigned PUSCH in the time slot. In some examples, the UCI multiplexing manager 122 may receive an uplink grant for transmission on multiple PUSCHs in a time 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 time slot. The UCI multiplexing manager 122 may determine whether UCI is to be transmitted on one or more PUCCHs or on one or more PUSCHs in the multiple PUSCHs in the time slot based on a determination as to whether the PUSCH data is to be transmitted in the time slot before assigning the PUSCH data to a PUSCH in the multiple PUSCHs.

[0050] The UCI multiplexing manager 122 may transmit UCI on the determined one or more PUCCHs or on the determined one or more PUSCHs in the time slot.

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

[0052] A network controller 130 may couple to a set of BSs 110 and provide coordination and control for the BSs 110. The network controller 130 may communicate with the BSs 110 via a backhaul. The BSs 110 may also communicate with each other (eg, directly or indirectly) via a wireless or wired backhaul.

[0053] Figure 2 1 and 120a (eg, in a BS 110a and a UE 120a) that can be used to implement various aspects of the present disclosure are illustrated. Figure 1Example components of the wireless communication network 100).

[0054] At BS 110a, a transmit processor 220 may receive data from a data source 212 and control information from a 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 the 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)). The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to modulators (MODs) 232a-232t. 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 up-convert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a-232t may be transmitted via antennas 234a-234t, respectively.

[0055] At UE 120a, antennas 252a-252r may receive downlink signals from BS 110a and may provide received signals to demodulators (DEMODs) in transceivers 254a-254r, respectively. Each demodulator 254 may condition (e.g., filter, amplify, downconvert, and digitize) a respective received signal to 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 received symbols from all demodulators 254a-254r, perform MIMO detection on the received symbols where applicable, and provide detected symbols. A receive processor 258 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for UE 120a to a data sink 260, and provide decoded control information to a controller / processor 280.

[0056] On the uplink, at the UE 120a, the transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 280 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 264 may also generate reference symbols for reference signals (e.g., 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 a modulator in a transceiver 254a-254r (e.g., for SC-FDM, etc.), and transmitted to the BS 110a. At the BS 110a, the uplink signal from the UE 120a may be received by the antenna 234, processed by the modulator 232, detected by the MIMO detector 236, if applicable, and further processed by the receive processor 238 to obtain decoded data and control information sent by the UE 120a. Receive processor 238 may provide decoded data to data sink 239 and decoded control information to controller / processor 240 .

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

[0058] The controller / processor 280 and / or other processors and modules at the UE 120a may perform or direct the execution of processes for the techniques described herein. Figure 2 As shown in , according to various aspects described herein, the controller / processor 280 of the UE 120a has a UCI multiplexing manager 281, which can be configured to perform UCI multiplexing in PUSCH handling when PUSCH skipping is configured. Although shown at the controller / processor 280, other components of the UE 120a can also be used to perform the operations described herein.

[0059] As discussed above, a UE may be configured for UCI multiplexing and PUSCH skipping, which may be problematic if the UE determines to send UCI in PUSCH, and then skips PUSCH because PUSCH does not have any assigned data. Figure 3A is a call flow 300A illustrating example UCI fallback to PUCCH with PUSCH skipping. Figure 3C is a more detailed call flow 300C illustrating example UCI fallback to PUCCH in case of PUSCH skipping.

[0060] like Figure 3AAs shown in FIG. 1 , at 306, UE 302 receives an uplink grant (e.g., in a PDCCH) from serving gNB 304 to schedule a PUSCH in a time slot. Different PUSCHs may be scheduled on different CCs in a time slot. In the illustrative example, as in FIG. Figure 3B As shown in FIG. 3 , UE 302 (e.g., at 306) is scheduled with eight PUSCHs (PUSCH 1, PUSCH 2, ..., PUSCH 8) in a given time slot 301, and at least one PUCCH. Figure 3B As shown in , PUSCHs 1-8 are configured on different CCs, such as CC 0-CC 7 in time slot 301.

[0061] At 308, UE 302 is configured / scheduled by serving gNB 304 to send UCI (e.g., HARQ-ACK, SR, and / or CSI) in this time slot. Figure 3A , UCI configuration / scheduling (at 308) is shown after uplink grant scheduling PUSCH (at 306), but in one or more examples, UCI can be configured / scheduled before or simultaneously with uplink grant scheduling PUSCH. In some examples, UCI can be dynamically scheduled. In some examples, UE 302 can be configured with a timeline, trigger, or periodicity for sending UCI.

[0062] At 310, UE 302 determines to multiplex UCI in one or more of the PUSCHs scheduled in the timeslot (e.g., when both PUSCH and PUCCH are scheduled in the timeslot). For example, UE 302 may execute its multiplexing logic to determine in which PUSCHs UCI may be transmitted. UE 302 may be configured with rules for determining whether UCI may be transmitted in the PUSCH. In some examples, the UCI multiplexing rules are hard-coded at UE 302 according to a 3GPP technical standard (e.g., 38.213 v15.4.0, Section 9.3, specifying various rules for transmitting UCI on the PUSCH). In some examples, the PUSCH that may be multiplexed with UCI may be configured. As Figure 3C As shown in , at 310, UCI multiplexing can be done at the PHY layer 305 of the UE 302. In the illustrative example, based on the UCI multiplexing rule, the UE 302 determines (at 310) to multiplex UCI on PUSCH 2, such as Figure 3D shown.

[0063] At 312, UE 302 assigns data (e.g., upper layer media access control (MAC) protocol data units (PDUs)) to one or more of the scheduled PUSCHs. Figure 3CAs shown in , at 312, data assignment can be completed at the MAC layer 303 of the UE 302. In the 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) constructs PUSCH 1 with data and has no data to fill the remaining PUSCHs 2-8, as shown in FIG. Figure 3D shown.

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

[0065] Thus, additional PUCCH / PUSCH resources may be used (eg, because both PUSCH and PUCCH are transmitted), and there may be additional delay (eg, due to falling back to preparing PUCCH), which in turn may incur additional power consumption.

[0066] Example UCI multiplexing in case of PUSCH skipping

[0067] In some examples, before physical uplink shared channel (PUSCH) skipping and multiplexing uplink control information (UCI) on PUSCH, the physical (PHY) layer can check the medium access control (MAC) layer to determine whether the MAC layer has data to transmit (e.g., scheduled, assigned to PUSCH). In some examples, the PHY layer sends a query to the MAC layer (e.g., or a direct function call) and the MAC layer sends a response indicating whether there is MAC layer data. For example, the PHY layer can send a query to the MAC layer at or before the time when the UE initiates skip logic (e.g., when the UE determines PUSCH / PUCCH overlap 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, PUSCH / PUCCH overlap in a time slot can be determined based on scheduling information received by the UE (if PUSCH and / or PUCCH are configured with bundling / repetition, this can be taken into account when determining whether PUSCH and / or PUCCH are scheduled in the time 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 notify the UE any time new data arrives at the MAC layer.

[0068] As will be discussed below Figures 6A-6C As discussed in more detail, if the MAC layer data is empty (e.g., the MAC layer has no PUSCH data to transmit / assign), then all PUSCH will be skipped and UCI will be transmitted by PUCCH. Therefore, the UE may not first attempt to multiplex UCI on PUSCH and then fall back to PUCCH. As will be discussed below with respect to Figures 7A-7CDiscussed in more detail, if the MAC layer data is not empty (e.g., the MAC layer has PUSCH data to transmit / assign to the PUSCH), the PHY layer may request the MAC layer to place (e.g., assign / transmit) data (e.g., MAC protocol data unit (PDU)) first on the PUSCH that may multiplex the UCI, and then on one or more remaining PUSCHs. For example, there may be multiple scheduled PUSCHs. The PUSCHs are sorted for assigning data. The MAC layer may sort the PUSCHs based on a request from the PHY layer so that data is first assigned to the PUSCH that may multiplex the UCI (e.g., based on the UCI multiplexing rules). In some examples, the PHY layer may send an ordered list of PUSCHs to be constructed for the timeslot to an upper layer (e.g., MAC). The MAC layer may construct the PUSCHs in the order of the list (e.g., assign data (such as MAC layer transport blocks (TBs)) to the PUSCHs). When the PHY layer sends the list, the PHY layer may sort the list, where the PUSCH that can multiplex UCI is sorted first in the list. In some examples, the PHY layer may send the PUSCH list and an indication of which PUSCH should be constructed first. Thus, the UCI multiplexing decision at the UE PHY layer may take into account whether there is MAC layer data to send (e.g., in addition to the multiplexing rules).

[0069] The UE can save resources and power by avoiding UCI fallback to PUCCH and / or by ensuring that UCI is multiplexed on PUSCH. Because the UE knows whether data is present, the PHY can determine uplink PUSCH skipping only after determining whether to multiplex UCI on PUSCH. In this case, the UE can construct a data PDU (e.g., a MAC layer TB) and can also perform PHY layer data / UCI multiplexing in parallel with forming the data PDU. Therefore, the uplink PHY timeline can be improved. In addition, in one or more examples, by assigning data to a PUSCH that can multiplex UCI, multiple PUSCHs can be transmitted in a time slot (with overlapping PUCCH) carrying UCI (e.g., with a grant size of more than 2k bytes), even in the presence of a small MAC PDU.

[0070] Figure 4 4 is a flow diagram illustrating example operations 400 for wireless communication in accordance with certain aspects of the present disclosure. Operations 400 may be performed, for example, by a UE (such as, for example, UE 120a in wireless communication network 100). Operations 400 may be implemented as a processor (e.g., Figure 2 Further, in operation 400, the transmission and reception of signals by the UE may be performed, for example, by one or more antennas (e.g., Figure 2 In some aspects, the transmission and / or reception of signals by the UE may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 280).

[0071] Operations 400 may begin, at 405, with receiving an uplink grant for transmission on a plurality of PUSCHs located on different component carriers (CCs).

[0072] At 410, the UE identifies one or more PUSCHs on which UCI may be transmitted in a time slot from among the multiple PUSCHs. In some examples, the UE identifies the one or more PUSCHs on which UCI may be transmitted based at least in part on one or more preconfigured rules. In some examples, the UE identifies the one or more PUSCHs on 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 on which the UCI may be multiplexed.

[0073] At 415, the UE may assign PUSCH data to the remaining PUSCHs in the multiple PUSCHs only after assigning PUSCH data to one or more identified PUSCHs on which UCI can be transmitted. According to certain aspects, the UE determines that the PUSCH data will be transmitted in the time slot. For example, the UE determines that the PUSCH data will be transmitted in the time slot before identifying one or more PUSCHs on which UCI can be sent in the multiple PUSCHs and before assigning the PUSCH data. In some examples, the UE 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 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 from the MAC layer at the PHY layer. In some examples, the UE receives an indication corresponding to the PUSCH 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 the PUSCH in some combination in response to a query, periodically, and / or when new data is received at the MAC layer.

[0074] At 420, the UE transmits UCI and PUSCH data on the assigned PUSCH in the time slot. 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 in the PUSCH set.

[0075] Figure 5 5 is a flow diagram illustrating example operations 500 for wireless communication in accordance with certain aspects of the present disclosure. Operations 500 may be performed, for example, by a UE (such as UE 120a in wireless communication network 100, for example). Operations 500 may be implemented as a processor (e.g., Figure 2 Further, in operation 500, the transmission and reception of signals by the UE may be performed, for example, by one or more antennas (e.g., Figure 2 In some aspects, the transmission and / or reception of signals by the UE may be achieved by obtaining and / or outputting signals via a bus interface of one or more processors (eg, controller / processor 280).

[0076] Operations 500 may begin, at 505, with receiving an uplink grant for transmission on multiple PUSCHs in a time slot, the multiple PUSCHs being located on different CCs.

[0077] At 510, the UE determines whether PUSCH data will be transmitted in the time 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 periodically receives the indication from the MAC layer at the PHY layer. In some examples, the UE receives the indication from the MAC layer at the PHY layer when new data is received at the MAC layer. According to certain aspects, when one or more PUSCHs are empty (e.g., when no data will be transmitted in the PUSCH in the time slot), the UE determines that UCI is to be transmitted on the one or more PUCCHs in the time slot. According to certain aspects, when PUSCH data is to be transmitted in the time slot, the UE determines that UCI is to be transmitted on one or more PUSCHs in the time slot.

[0078] At 515, the UE determines to transmit UCI on one or more PUCCHs or on one or more PUSCHs among the multiple PUSCHs in the time slot based on a determination as to whether the PUSCH data will be transmitted in the time slot before assigning PUSCH data (e.g., any PUSCH data) to a PUSCH among the multiple PUSCHs.

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

[0080] At 520, the UE transmits UCI on the determined one or more PUCCHs or on the determined one or more PUSCHs in the time slot. In some examples, the UE sends UCI on both the one or more PUCCHs and the one or more PUSCHs in the time slot. 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.

[0081] 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 be transmitted in a duration (e.g., in a transmission time interval, such as in a time slot). Therefore, if there is no data to be transmitted (e.g., no MAC layer data or the MAC layer buffer is empty), all PUSCHs may be skipped (e.g., according to a configured PUSCH skipping rule). In this case, the UE may decide to send UCI on the PUCCH in the time slot. Fig. 6A is a call flow 600A illustrating example UCI transmission on PUCCH with PUSCH skipping in accordance with one or more aspects of the present disclosure. Figure 6B is a more detailed call flow 600B illustrating example UCI transmission on PUCCH with PUSCH skipping.

[0082] like Fig. 6AAs shown in FIG. 6 , at 606, UE 602 receives (e.g., in a PDCCH) an uplink grant scheduling a PUSCH in a time slot (e.g., or other time interval) from a serving BS 606 (e.g., a gNB). The PUSCH may be scheduled on different CCs in a time slot, e.g., as in Figure 3B As shown in time slot 301 in .

[0083] At 608, UE 602 is configured / scheduled by serving BS 604 to send UCI (e.g., HARQ-ACK, SR, and / or CSI) in this time slot. Fig. 6A , UCI configuration / scheduling (at 608) is shown after uplink grant scheduling PUSCH (at 606), but UCI can be configured / scheduled before or simultaneously with uplink grant scheduling PUSCH. In some examples, UCI can be dynamically scheduled. In some examples, UE 602 can be configured with a timeline, trigger, or periodicity for sending UCI.

[0084] At 610, the UE checks the MAC layer data. For example, Figure 6B As shown in FIG. 1 , the PHY layer 605 can query the MAC layer 603. The MAC layer 603 can periodically or in response to the query send an indication to the PHY layer 605 as to whether it has data. Figures 3A-3E Compared with the UCI multiplexing explained in , the UE 602 may determine whether to multiplex the UCI on the PUSCH after the UE 602 knows whether there is data to be transmitted. Fig. 6A As shown in , if UE 602 determines that there is no data to transmit, then at 612, UE 602 may determine to place UCI on PUCCH and skip empty PUSCHs (e.g., based on configured PUSCH skipping rules). For example, for empty PUSCHs (e.g., no PUSCH data assigned to them in the timeslot), UE 602 may determine to skip (e.g., discard or not transmit) those empty PUSCHs in the timeslot.

[0085] At 614, UE 602 transmits UCI in the PUCCH to serving BS 604. Figures 6A-6D In the example illustrated in , UE 602 can avoid falling back to transmitting UCI on PUCCH after having prepared to transmit UCI on PUSCH (e.g., at the PHY layer), thereby avoiding incurring additional delay (e.g., due to falling back to preparing PUCCH), thereby saving power consumption.

[0086] Return to the above reference Figures 3A-3EIn the illustrative example described, UE 602 may (eg, at 606) schedule eight PUSCHs (PUSCH1, PUSCH2, ..., PUSCH8) in a given time slot, for example, Figure 3B However, UE 602 may (e.g., at 610) determine based on a MAC layer check that there is no data to be transmitted in time slot 301, and decide to place the UCI on the PUCCH, as shown in FIG. Figure 6C As shown in . Since the MAC layer does not have any data, UE 602 Fig.6D The configured PUSCH skipping shown in 612 is used to drop the remaining PUSCHs 603 (eg, PUSCHs 1-8); however, the UE 602 does not need to fall back to transmitting UCI on the PUCCH because the UE 602 (eg, at 612) has already placed the UCI on the PUCCH.

[0087] Fig. 7A is a call flow diagram 700A illustrating example UCI multiplexing on PUSCH with PUSCH skipping in accordance with aspects of the present disclosure. Figure 7B is a more detailed call flow 700B illustrating example UCI multiplexing on PUSCH with PUSCH skipping.

[0088] like Fig. 7A As shown, at 706-710, UE 702 receives an uplink grant, is configured / scheduled by serving BS 704 to send UCI, and checks the MAC layer data, which may be as described above in Fig. 6A In this case, if Fig. 7A As shown in , if UE 702 finds that there is data to be transmitted (e.g., MAC layer data or buffer is not empty), then at 712, UE 702 places the data on other PUSCHs in the time slot after determining to place the data on (e.g., assigned to) one or more PUSCHs of the multiplexable UCI. Figure 7BAs shown in , the PHY layer 705 may identify the PUSCH(s) on which UCI may be multiplexed at 712a, and request the MAC layer 703 to place the MAC PDU on the identified PUSCH(s) on which UCI may be multiplexed at 712b, and then on other PUSCHs. In this way, the UE 702 ensures that those PUSCHs on which UCI may be multiplexed will not be skipped, thereby ensuring that the UE 702 multiplexes UCI on the PUSCH in the time slot. At 714, the UE 702 (e.g., the PHY layer 705) multiplexes the UCI with the assigned data on the PUSCH. In some examples, the multiplexing at 714 may be based on the configured UCI multiplexing rule. Therefore, at 716, the UE 702 transmits a PUSCH with the assigned data (including a PUSCH with multiplexed UCI and the assigned data) in the time slot, and the UE 702 may discard any other PUSCH that is not assigned any data.

[0089] Refer back to the above Figures 3A-3E illustrative example of , with PUSCH 1-8 scheduled in slot 301 and UCI that may be multiplexed on PUSCH 2. In this case, UE 702 ensures that PUSCH 2 is sent first to the upper layers (e.g., MAC layer 703) so that PUSCH 2 will be assigned with data and therefore will not be skipped and can be transmitted together with the multiplexed UCI, as shown in FIG. Figure 7C Thus, in this illustrative example, PUSCH 2 is transmitted with UCI, the remaining PUSCH 703 (e.g., PUSCH 1 and 3-8) may be skipped, and the PUCCH is dropped so that only PUSCH 2 is sent with UCI and data, as shown in FIG. Fig.7D This may be more efficient than transmitting both PUSCH and PUCCH in a time slot.

[0090] Therefore, by preparing UCI on PUCCH or PUSCH and assigning data to PUSCH only after performing data check, the UE can avoid falling back to PUCCH and can improve the efficiency of resource usage by ensuring that UCI can be multiplexed on PUSCH. These in turn can save power, save resources, allow PHY layer PUSCH and UCI multiplexing processing and MAC TB formation in parallel, and improve uplink PHY timeline.

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

[0092] 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 Figure 4-7D814 or other operations for performing the various techniques discussed herein for UCI multiplexing with PUSCH skipping. In certain aspects, the computer-readable medium / memory 812 stores code 814 for receiving (such as code for receiving an uplink grant for transmission on multiple PUSCHs, the multiple PUSCHs being located on different CCs, according to one or more aspects of the present disclosure); code 816 for determining (such as code for determining whether PUSCH data will be transmitted in the time slot, according to one or more aspects of the present disclosure); and / or code for determining, before assigning the PUSCH data to a PUSCH in the multiple PUSCHs, to transmit UCI in the time slot on one or more PUCCHs or on one or more PUSCHs in the multiple PUSCHs based on a determination as to whether the PUSCH data will be transmitted in the time slot, according to one or more aspects of the present disclosure; code 818 for identifying (such as a root 820 for assigning (such as code for assigning PUSCH data to the one or more identified PUSCHs on which the UCI may be transmitted in the time slot according to one or more aspects of the present disclosure); and / or code for transmitting 822 (such as code for transmitting the UCI and the PUSCH data on the assigned PUSCH in the time slot according to one or more aspects of the present disclosure; and / or code for transmitting the UCI on the determined one or more PUCCHs or on the determined one or more PUSCHs in the time slot according to one or more aspects of the present disclosure). In certain aspects, the processor 804 has a circuit system configured to implement the code stored in the computer-readable medium / memory 812. Processor 804 includes circuitry 824 for receiving, circuitry 826 for determining, circuitry 828 for identifying, circuitry 830 for assigning, and / or circuitry 832 for transmitting in accordance with one or more aspects of the present disclosure. When processor 804 executes code in computer-readable medium / memory 812, circuitry 824-832 may implement operations provided by code 814-822.

[0093] The techniques described herein may be used for various wireless communication technologies, such as NR (e.g., 5G NR or later versions), 3GPP Long Term Evolution (LTE), Advanced LTE (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 radio technologies 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 radio technologies such as Global System for Mobile Communications (GSM). OFDMA networks can implement radio technologies 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 Universal Mobile Telecommunications System (UMTS). LTE and LTE-A are versions 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 an emerging wireless communication technology under development.

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

[0095] In 3GPP, the term "cell" may refer to the coverage area of ​​a B node (NB) and / or a NB subsystem serving the coverage area, depending on the context in which the term is used. In NR systems, the terms "cell" and BS, next-generation B node (gNB or g B node), access point (AP), distributed unit (DU), carrier, or transmission reception point (TRP) may be used interchangeably. The BS may provide communication coverage for macro cells, pico cells, femto cells, and / or other types of cells. A macro cell may cover a relatively large geographic area (e.g., a radius of several thousand meters) and may allow unrestricted access by UEs with service subscriptions. A pico cell may cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions. A femto cell may cover a relatively small geographic area (e.g., a residence) and may allow restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs of users in a residence, 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. A BS for a femto cell may be referred to as a femto BS or a home BS.

[0096] UE may also be referred to as a mobile station, terminal, access terminal, subscriber unit, station, customer premises equipment (CPE), cellular phone, smart phone, 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 medical 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.), transportation component or sensor, smart meter / sensor, industrial manufacturing equipment, global positioning system device, or any other suitable device configured to communicate via wireless or wired medium. Some UEs may be considered machine type communication (MTC) devices or evolved MTC (eMTC) devices. MTC and eMTC UEs include, for example, robots, drones, remote devices, sensors, meters, monitors, location tags, etc., which can communicate with a BS, another device (e.g., a remote device), or some other entity. A wireless node can provide connectivity for or to a network (e.g., a wide area network (such as the Internet) or a cellular network), for example, 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.

[0097] 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 divide the system bandwidth into multiple (K) orthogonal subcarriers, which are also often referred to as frequency modulation, frequency bins, etc. Each subcarrier can be modulated with data. In general, modulation symbols are sent in the frequency domain for OFDM and in the time domain for SC-FDM. The spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system bandwidth. For example, the spacing of subcarriers can be 15kHz, and the minimum resource allocation (called a "resource block" (RB)) can be 12 subcarriers (or 180kHz). Therefore, for system bandwidths of 1.25, 2.5, 5, 10, or 20 megahertz (MHz), the nominal fast Fourier transform (FFT) size can be equal to 128, 256, 512, 1024, or 2048, respectively. The system bandwidth may also be divided 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 system bandwidths 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.

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

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

[0100] 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 relay, vehicle-to-vehicle (V2V) communications, Internet of Everything (IoE) communications, IoT communications, mission-critical mesh networks, and / or various other suitable applications. Generally, a sidelink signal may refer to a signal that is 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 if the scheduling entity may be used for scheduling and / or control purposes. In some examples, the sidelink signal may be communicated using a licensed spectrum (unlike wireless local area networks, which typically use an unlicensed spectrum).

[0101] Each method disclosed herein includes one or more operations or actions for implementing the method. These method operations and / or actions can be interchangeable with each other 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 can be changed without departing from the scope of the claims.

[0102] 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 cover: a, b, c, ab, ac, bc, and abc, as well as any combination with multiple identical elements (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc, or any other ordering of a, b, and c).

[0103] As used herein, the term "determining" encompasses a wide variety of actions. For example, "determining" may include calculating, computing, processing, deriving, investigating, searching (e.g., searching in a table, a 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, choosing, establishing, and the like.

[0104] Example aspects

[0105] In a first aspect, 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 in the plurality of PUSCHs on which uplink control information (UCI) can be transmitted in a time slot; assigning PUSCH data to the remaining PUSCHs in the plurality of PUSCHs after assigning PUSCH data to the one or more identified PUSCHs on which the UCI can be transmitted; and transmitting the UCI and the PUSCH data on the assigned PUSCHs in the time slot. This can allow the UE to ensure that the UCI can be multiplexed on the PUSCH and can avoid falling back to the PUCCH.

[0106] In a second aspect, either alone or in combination with the first aspect, the UE determines that PUSCH data will be transmitted in a time slot, the determination being performed before identifying one or more PUSCHs in the plurality of PUSCHs on which UCI may be sent and before assigning PUSCH data. This may allow the UE to determine that UCI is to be placed on the PUCCH when there is no data, or to request that the data be placed first on the PUSCH that may multiplex the UCI when there is data.

[0107] 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 time slot comprises receiving an indication corresponding to the PUSCH data from a medium access control (MAC) layer at a physical (PHY) layer, 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. This may allow the UE to make a determination as to whether there is a PUSCH to be transmitted in the time slot.

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

[0109] 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. This can improve the processing timeline.

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

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

[0112] 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 in the PUSCH set. This may allow the UE to transmit more efficiently by not wasting resources when no PUSCH data is to be transmitted for the PUSCH in the time slot.

[0113] In a ninth aspect, a method for wireless communication by a UE comprises: receiving an uplink grant for transmission on multiple PUSCHs in a time slot, the multiple PUSCHs being located on different CCs; determining whether PUSCH data will be transmitted in the time slot; before assigning the PUSCH data to a PUSCH among the multiple PUSCHs, determining, based on the determination as to whether the PUSCH data will be transmitted in the time slot, to transmit UCI on one or more PUCCHs or on one or more PUSCHs among the multiple PUSCHs in the time slot; and transmitting the UCI on the determined one or more PUCCHs or on the determined one or more PUSCHs in the time slot.

[0114] In the tenth aspect, alone or in combination with the ninth aspect, determining whether PUSCH data will be transmitted in a time slot includes receiving an indication corresponding to the PUSCH from the MAC layer at the PHY layer, 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.

[0115] In the eleventh aspect, alone or in combination with the ninth or tenth aspect, determining that UCI is to be transmitted on one or more PUCCHs or on one or more PUSCHs in the time slot includes determining that the UCI is to be transmitted on the one or more PUCCHs in the time slot when one or more PUSCHs are empty.

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

[0117] In the thirteenth aspect, alone or in combination with one or more of the ninth to twelfth aspects, the UE identifies one or more PUSCHs as PUSCHs among multiple PUSCHs on which UCI can be transmitted; and assigns PUSCH data to the remaining PUSCHs among the multiple PUSCHs only after assigning PUSCH data to one or more PUSCHs on which UCI can be transmitted.

[0118] In the fourteenth aspect, alone or in combination with one or more of the ninth to thirteenth aspects, the UE requests the MAC layer by the PHY layer to assign PUSCH data to the remaining PUSCHs in the multiple PUSCHs only after assigning PUSCH data to one or more PUSCHs on which UCI can be sent; or the PHY layer provides an ordered list to the MAC layer to construct a PUSCH set, wherein the identified one or more PUSCHs are sorted in the ordered list before the remaining PUSCHs in the multiple PUSCHs.

[0119] 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.

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

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

[0122] In an eighteenth aspect, 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.

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

[0124] The previous description is provided to enable any person skilled in the art to practice the various aspects described herein. Various modifications to these aspects will be easily understood by those skilled in the art, and the universal principles defined herein can be applied to other aspects. Thus, the claims are not intended to be limited to the various aspects shown herein, but should be granted the full scope consistent with the language of the claims, wherein the singular reference to the element is not intended to mean "there is and only one" (unless specifically stated) but "one or more". Unless otherwise specifically stated, the term "some / some" refers to one or more. The elements of the various aspects described throughout this disclosure are all structural and functional equivalents currently or hereafter known to those of ordinary skill in the art and are expressly incorporated herein by reference, and are intended to be covered by the claims. In addition, nothing disclosed herein is intended to be donated to the public, regardless of whether such disclosure is explicitly recorded in the claims. No claim element should be interpreted under the provisions of 35 U.S.C. § 112 (f), unless the element is explicitly described using the phrase "device for...".

[0125] The various operations of the methods described above may be performed by any suitable device capable of performing the corresponding functions. These devices may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs), or processors. Generally, where there are operations illustrated in the accompanying drawings, these operations may have corresponding paired device-plus-function components with similar numbers.

[0126] The various illustrative logical blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed with 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 in the alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0127] If implemented in hardware, an example hardware configuration may include a processing system in a wireless node. The processing system may be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link together various circuits including a processor, a machine-readable medium, and a bus interface. The bus interface may be used to connect a network adapter, etc., to the processing system via the bus. The network adapter may be used to implement the signal processing functions of the PHY layer. In a user terminal (see Figure 8 ), a user interface (e.g., a 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, and the like, which are well known in the art and will not be described further. The processor may be implemented with one or more general and / or special purpose processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuit systems capable of executing software. Those skilled in the art will recognize how to best implement the functionality described with respect to the processing system, depending on the specific application and the overall design constraints imposed on the overall system.

[0128] If implemented in software, each function may be stored on or transmitted by a computer-readable medium as one or more instructions or codes. Software should be broadly interpreted to mean instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include both computer storage media and communication media, which include any media that facilitate the transfer of computer programs from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a machine-readable storage medium. A computer-readable storage medium may be coupled to a processor so that the processor can read and write information from / to the storage medium. In an alternative, a storage medium may be integrated into a processor. As an example, a machine-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium having instructions stored thereon that is separated from a wireless node, all of which may be accessed by a processor through a bus interface. Alternatively or additionally, a machine-readable medium or any part thereof may be integrated into a processor, such as a cache and / or a general register file, which may be the case. As an example, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. Machine-readable media may be implemented in a computer program product.

[0129] A software module may include a single instruction, or many instructions, and may be distributed over several different code segments, distributed between different programs, and distributed across multiple storage media. A computer-readable medium may include several software modules. These software modules include instructions that cause a processing system to perform various functions when executed by an apparatus such as a processor. These software modules may include a transmission module and a receiving module. Each software module may reside in a single storage device or may be distributed across multiple storage devices. As an example, when a triggering event occurs, a software module may be loaded into a RAM from a hard drive. During the execution of a software module, a processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When describing the functionality of a software module as described below, it will be understood that such functionality is implemented by the processor when the processor executes instructions from the software module.

[0130] Likewise, 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 a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared (IR), radio, and microwave), then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) is included in the definition of medium. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Disks, where disks often reproduce data magnetically, and discs reproduce data optically with lasers. Thus, in some aspects, computer-readable media may include non-transitory computer-readable media (e.g., tangible media). Additionally, for other aspects, computer-readable media may include transient computer-readable media (e.g., signals). Combinations of the above should also be included within the scope of computer-readable media.

[0131] Thus, certain aspects may include a computer program product for performing the operations presented herein. For example, such a computer program product may include a computer-readable medium having stored (and / or encoded) thereon instructions that can be executed by one or more processors to perform the operations described herein, such as for performing the operations described herein and in Figure 4-7D Instructions for the operations described in at least one of the embodiments.

[0132] In addition, it should be appreciated that modules and / or other appropriate 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 a device can be coupled to a server to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein can be provided via a storage device (e.g., RAM, ROM, a physical storage medium such as a compact disc (CD) or a floppy disk, etc.) so that once the storage device is coupled to or provided to a user terminal and / or base station, the device can obtain the various methods. In addition, any other suitable technology suitable for providing the methods and techniques described herein to a device may be utilized.

[0133] It will be understood that the claims are not limited to the precise configuration and components illustrated above. Various changes, substitutions 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.

Claims

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 (CC); identifying one or more PUSCHs among the plurality of PUSCHs on which uplink control information UCI can be transmitted in a time slot; assigning PUSCH data for transmission in the time slot to remaining PUSCHs of the plurality of PUSCHs after assigning PUSCH data for transmission in the time slot to one or more identified PUSCHs on which the UCI can be transmitted; and The UCI and the PUSCH data are transmitted on the assigned PUSCH in the time slot.

2. The method of claim 1, further comprising: Determining that the PUSCH data is to be transmitted in the time slot, wherein the determining is performed before identifying one or more PUSCHs among the plurality of PUSCHs on which UCI can be sent and before assigning the PUSCH data.

3. The method of claim 2, wherein determining that the PUSCH data is to be transmitted in the time slot comprises receiving an indication corresponding to the PUSCH data from a medium access control (MAC) layer at a physical (PHY) layer, and 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. 4 . The method of claim 1 , wherein transmitting the UCI and the PUSCH data on the assigned PUSCH in the time slot comprises rate matching the UCI around the PUSCH data.

5. The method of claim 1, further comprising: A medium access control MAC layer transport block TB is generated and physical PHY layer multiplexing of the UCI and PUSCH data is performed in parallel. 6 . The method of claim 1 , wherein identifying the one or more PUSCHs among the plurality of PUSCHs on which the UCI can be transmitted is based at least in part on one or more preconfigured rules. 7 . The method of claim 1 , wherein identifying the one or more PUSCHs among the plurality of PUSCHs on which the UCI can 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 empty PUSCH among the plurality of PUSCHs.

9. 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 time slot, the plurality of PUSCHs being located on different component carriers CC; determining whether PUSCH data is to be transmitted in the time slot; Before assigning the PUSCH data to a PUSCH of the plurality of PUSCHs, determining, based on the determination as to whether the PUSCH data is to be transmitted in the time slot, whether to transmit uplink control information (UCI) on one or more physical uplink control channels (PUCCHs) in the time slot or to transmit the UCI on one or more PUSCHs of the plurality of PUSCHs in the time slot; as well as The UCI is transmitted on the determined one or more PUCCHs or on the determined one or more PUSCHs in the time slot.

10. The method of claim 9, wherein determining that the PUSCH data is to be transmitted in the time slot comprises receiving an indication corresponding to the PUSCH data from a medium access control (MAC) layer at a physical (PHY) layer, and 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.

Images