Uplink control information multiplexing on uplink shared channel with multiple transport blocks

Through flexible resource allocation strategies, multiplexing and mapping of UCI in wireless communication systems, the problem of UCI multiplexing and mapping on PUSCH is solved, which improves resource utilization and signal reliability and enhances wireless communication performance.

CN119054386APending Publication Date: 2024-11-29QUALCOMM INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095126.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-29
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

In wireless communication systems, the challenge of multiplexing uplink control information (UCI) on physical uplink shared channel (PUSCH), especially when multiplexing UCI on multiple transport blocks (TBs), how to effectively map and Allocate UCI content to improve channel resource utilization and signal reliability.

Method used

By determining how to multiplex UCI on PUSCH, leveraging different sending parameters of multiple TBs, adopting flexible resource allocation strategies, such as multiplexing UCI on all TB layers, or multiplexing on different TB layers according to UCI type, ensure UCI's robustness and payload balance.

Benefits of technology

It improves the utilization rate of PUSCH resources and the reliable delivery of UCI, solves the problems of multiplexing and mapping of UCI in multi-TB environments, and enhances the performance of wireless communication systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119054386A_ABST
    Figure CN119054386A_ABST
Patent Text Reader

Abstract

Certain aspects of the present disclosure provide techniques for wireless communication that generally include receiving signaling that schedules a physical uplink shared channel (PUSCH) having at least a first transport block (TB) and a second TB, where the first TB and the second TB have separate transmission parameters; determining how to multiplex uplink control information (UCI) on the PUSCH; and transmitting the PUSCH on which the UCI has been multiplexed on the PUSCH in accordance with the determination.
Need to check novelty before this filing date? Find Prior Art

Description

Background Art Technical Field

[0001] Aspects of the present disclosure relate to wireless communications and, more particularly, to techniques for sending uplink control information (UCI).

[0002] Related technologies

[0003] Wireless communication systems are widely deployed to provide various telecommunication services such as telephony, video, data, messaging, broadcasts, or other similar types of services. These wireless communication systems may employ multiple-access technologies capable of supporting communication with multiple users by sharing available wireless communication system resources with the multiple users.

[0004] Although wireless communication systems have made tremendous technical progress over the years, challenges still exist. For example, complex and dynamic environments can still attenuate or block signals between wireless transmitters and wireless receivers. Therefore, there is a continuous desire to improve the technical performance of wireless communication systems, including, for example: improving the speed and data carrying capacity of communications, improving the efficiency of using shared communication media, reducing the power used by transmitters and receivers when performing communications, improving the reliability of wireless communications, avoiding redundant transmission and / or reception and related processing, improving the coverage area of ​​wireless communications, increasing the number and types of devices that can access wireless communication systems, increasing the ability of different types of devices to communicate with each other, increasing the number and types of wireless communication media available for use, etc. Therefore, there is a need to further improve wireless communication systems to overcome the above-mentioned technical challenges and other challenges. Summary of the invention

[0005] One aspect provides a method for wireless communication (e.g., by a user equipment (UE)). The method includes: receiving signaling scheduling a physical uplink shared channel (PUSCH) having at least a first transport block (TB) and a second TB, wherein the first TB and the second TB have separate transmission parameters; determining how to multiplex uplink control information (UCI) on the PUSCH; and transmitting the PUSCH with the UCI multiplexed on the PUSCH according to the determination.

[0006] In another aspect, a method for wireless communication by a network entity is provided. The method includes: sending signaling for a UE to schedule a PUSCH having at least a first TB and a second TB, wherein the first TB and the second TB have separate transmission parameters; determining how the UE will multiplex UCI on the PUSCH; and monitoring the PUSCH having the UCI multiplexed on the PUSCH based on the determination.

[0007] Other aspects provide: an apparatus operable to, configured to, or otherwise adapted to perform any one or more of the foregoing methods and / or those described elsewhere herein; a non-transitory computer-readable medium comprising instructions that, when executed by a processor of the apparatus, cause the apparatus to perform the foregoing methods and those described elsewhere herein; a computer program product embodied on a computer-readable storage medium, the computer-readable storage medium comprising code for performing the foregoing methods and those described elsewhere herein; and / or an apparatus comprising components for performing the foregoing methods and those described elsewhere herein. By way of example, an apparatus may include a processing system, a device having a processing system, or a processing system in conjunction with one or more networks.

[0008] For purposes of illustration, the following description and drawings set forth certain features. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] The accompanying drawings depict certain features of the various aspects described herein and should not be considered to limit the scope of the disclosure.

[0010] Figure 1 An example wireless communication network is depicted.

[0011] Figure 2 An example disaggregated base station architecture is depicted.

[0012] Figure 3 Aspects of an example base station and example user equipment are depicted.

[0013] Figure 4A , Figure 4B , Figure 4C and Figure 4D Various example aspects of data structures for a wireless communication network are described.

[0014] Figure 5 is a conceptual diagram illustrating uplink control information (UCI) multiplexed with an uplink data channel in accordance with certain aspects of the present disclosure.

[0015] Figures 6 to 14 Depicted are examples of resource allocation for UCI multiplexed in multiple transport blocks (TBs) of a physical uplink shared channel (PUSCH), in accordance with certain aspects of the present disclosure.

[0016] Fig.15 A method for wireless communication is described.

[0017] Fig.16 A method for wireless communication is described.

[0018] Fig.17Aspects of an example communications device are depicted.

[0019] Fig.18 Aspects of an example communications device are depicted. DETAILED DESCRIPTION

[0020] Aspects of the present disclosure provide apparatus, methods, processing systems, and computer-readable media for multiplexing uplink control information (UCI) on a physical uplink shared channel (PUSCH) transmission.

[0021] UCI multiplexing on PUSCH is a mechanism that allows UCI to be sent on PUSCH resources. UCI multiplexing on PUSCH is supported for various waveforms. In some cases, for frequency-first mapping, when UCI is multiplexed on PUSCH, the UCI resource mapping principle (e.g., mapping around the resources allocated to the RS) is common.

[0022] In the case where a single TB is used for PUSCH, certain types of UCI such as hybrid automatic repeat request (HARQ) acknowledgment feedback and channel state information (CSI) are typically mapped to all layers of the TB on PUSCH. The modulation order of UCI typically follows the modulation order of UL-SCH. For non-periodic CSI on PUSCH triggered by a UL grant without UL-SCH data, the modulation order for PUSCH is typically handled in the same way as when PUSCH is sent with UL-SCH data.

[0023] For UL transmissions with more than one layer, two codewords may be supported in some cases (e.g., NR Release 18), so that two transport blocks (TBs) may be utilized to schedule the PUSCH. In such cases, each TB may have different transmission parameters (e.g., modulation and coding scheme MCS, new data indicator NDI, redundancy version RV, etc.). The possibility of multiple TBs having different transmission parameters creates potential challenges for multiplexing UCI on the PUSCH. For example, one challenge is how to map the UCI content to available resources on different TBs.

[0024] However, aspects of the present disclosure provide various approaches for multiplexing UCI on a PUSCH with multiple TBs. These techniques provide flexible resource allocation and can help improve overall resource utilization and reliable delivery of UCI.

[0025] Introduction to wireless communication networks

[0026] The techniques and methods described herein can be used in various wireless communication networks. 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 also be applicable to other communication systems and standards not explicitly mentioned herein.

[0027] Figure 1 An example of a wireless communication network 100 is depicted in which various aspects described herein may be implemented.

[0028] In general, the wireless communication network 100 includes various network entities (alternatively, network elements or network nodes). A network entity is typically a communication device and / or a communication function performed by a communication device (e.g., user equipment (UE), base station (BS), component of a BS, server, etc.). For example, various functions of a network and various devices associated with and interacting with the network may be considered network entities. In addition, the wireless communication network 100 includes ground aspects, such as ground-based network entities (e.g., BS 102), and non-ground aspects, such as satellites 140 and aircraft 145, which may include airborne network entities (e.g., one or more BSs) capable of communicating with other network elements (e.g., ground BSs) and user equipment.

[0029] In the depicted example, the wireless communication network 100 includes a BS 102, a UE 104, and one or more core networks (such as an evolved packet core (EPC) 160 and a 5G core (5GC) network 190) that interoperate to provide communication services over various communication links (including wired and wireless links).

[0030] Figure 1 Various example UEs 104 are depicted, which may more generally include: a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player, a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, an Internet of Things (IoT) device, an Always-On (AON) device, an edge processing device, or other similar devices. UE 104 may also be more generally referred to as a mobile device, a wireless device, a wireless communication device, a station, a mobile station, a subscriber station, a mobile subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a remote device, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, and others.

[0031] BS 102 wirelessly communicates with (e.g., transmits signals to or receives signals from) UE 104 via communication link 120. Communication link 120 between BS 102 and UE 104 may include uplink (UL) (also referred to as a reverse link) transmissions from UE 104 to BS 102 and / or downlink (DL) (also referred to as a forward link) transmissions from BS 102 to UE 104. In various aspects, communication link 120 may employ multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity.

[0032] BS 102 may generally include: Node B, enhanced Node B (eNB), next generation enhanced Node B (ng-eNB), next generation Node B (gNB or gNodeB), access point, base transceiver station, radio base station, radio transceiver, transceiver function, transmission and reception point, and / or other. Each of BS 102 may provide communication coverage for a corresponding geographic coverage area 110, which may sometimes be referred to as a cell, and may overlap in some cases (e.g., small cell 102' may have a coverage area 110' that overlaps with the coverage area 110 of a macro cell). For example, a BS may provide communication coverage for a macro cell (covering a relatively large geographic area), a pico cell (covering a relatively small geographic area, such as a stadium), a femto cell (relatively small geographic area (e.g., a home)), and / or other types of cells.

[0033] Although BS102 is depicted as a single communication device in various aspects, BS102 can be implemented in various configurations. For example, one or more components of the base station may be decomposed, including a central unit (CU), one or more distributed units (DU), one or more radio units (RU), a near real-time (near RT) RAN intelligent controller (RIC), or a non-real-time (non-RT) RIC, to name a few examples. In another example, various aspects of the base station may be virtualized. More generally, a base station (e.g., BS102) may include components located at a single physical location or components located at various physical locations. In an example in which the base station includes components located at various physical locations, the various components may each perform a function so that the various components together implement functionality similar to that of a base station located at a single physical location. In some aspects, a base station including components located at various physical locations may be referred to as a decomposed radio access network architecture (such as an open RAN (O-RAN) or virtualized RAN (VRAN) architecture). Figure 2 An example decomposed base station architecture is depicted and described.

[0034] Different BSs 102 within the wireless communication network 100 may also be configured to support different radio access technologies (such as 3G, 4G, and / or 5G). For example, a BS 102 configured for 4G LTE (collectively referred to as an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) may interface with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). A BS 102 configured for 5G (e.g., 5G NR or Next Generation RAN (NG-RAN)) may interface with the 5GC 190 via a second backhaul link 184. The BSs 102 may communicate with each other directly or indirectly (e.g., via the EPC 160 or the 5GC 190) over a third backhaul link 134 (e.g., an X2 interface), which may be wired or wireless.

[0035] The wireless communication network 100 may subdivide the electromagnetic spectrum into various categories, frequency bands, channels, or other characteristics. In some aspects, the subdivision is provided based on wavelength and frequency, where frequency may also be referred to as a carrier, subcarrier, channel, tone, or subband. For example, 3GPP currently defines frequency range 1 (FR1) as including 410 MHz-7125 MHz, which is often (interchangeably) referred to as "below 6 GHz". Similarly, 3GPP currently defines frequency range 2 (FR2) as including 24,250 MHz-52,600 MHz, which is sometimes (interchangeably) referred to as "millimeter wave" ("mmW" or "mmWave"). A base station (e.g., a mmWave base station such as BS180) configured to communicate using mmWave / near mmWave radio bands may utilize beamforming (e.g., 182) with a UE (e.g., 104) to improve path loss and range.

[0036] The communication link 120 between the BS 102 and, for example, the UE 104 may be through one or more carriers, which may have different bandwidths (e.g., 5 MHz, 10 MHz, 15 MHz, 20 MHz, 100 MHz, 400 MHz, and / or other MHz) and may be aggregated in various aspects. The carriers may or may not be adjacent to each other. The allocation of carriers may be asymmetric with respect to DL and UL (e.g., more or fewer carriers may be allocated for DL ​​than for UL).

[0037] Communications using higher frequency bands may have higher path loss and shorter range than communications at lower frequencies. Figure 1180) can utilize beamforming 182 with UE 104 to improve path loss and range. For example, BS 180 and UE 104 may each include multiple antennas, such as antenna elements, antenna panels and / or antenna arrays, to facilitate beamforming. In some cases, BS 180 may send beamformed signals to UE 104 in one or more transmit directions 182'. UE 104 may receive beamformed signals from BS 180 in one or more receive directions 182". UE 104 may also send beamformed signals to BS 180 in one or more transmit directions 182". BS 180 may also receive beamformed signals from UE 104 in one or more receive directions 182'. BS 180 and UE 104 may then perform beam training to determine the best receive direction and transmit direction for each of BS 180 and UE 104. It is worth noting that the transmit direction and receive direction of BS 180 may be the same or different. Similarly, the transmit direction and receive direction of UE 104 may be the same or different.

[0038] Wireless communication network 100 also includes Wi-Fi AP 150 that communicates with Wi-Fi stations (STAs) 152 via communication links 154 in, for example, the 2.4 GHz and / or 5 GHz unlicensed spectrum.

[0039] Certain UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), a physical sidelink control channel (PSCCH), and / or a physical sidelink feedback channel (PSFCH).

[0040] The EPC 160 may include various functional components, including: a mobility management entity (MME) 162, other MMEs 164, a serving gateway 166, a multimedia broadcast multicast service (MBMS) gateway 168, a broadcast multicast service center (BM-SC) 170, and / or a packet data network (PDN) gateway 172, such as in the depicted example. The MME 162 may communicate with a home subscriber server (HSS) 174. The MME 162 is a control node that handles signaling between the UE 104 and the EPC 160. In general, the MME 162 provides bearer and connection management.

[0041] Generally speaking, user Internet Protocol (IP) packets are delivered through the Serving Gateway 166, which itself is connected to the PDN Gateway 172. The PDN Gateway 172 provides UE IP address allocation and other functions. The PDN Gateway 172 and the BM-SC 170 are connected to the IP Services 176, which may include, for example, the Internet, an Intranet, an IP Multimedia Subsystem (IMS), a Packet Switched (PS) streaming media service, and / or other IP services.

[0042] The BM-SC 170 may provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 may serve as an entry point for content provider MBMS delivery, may be used to authorize and initiate MBMS bearer services within a public land mobile network (PLMN), and / or may be used to schedule MBMS delivery. The MBMS Gateway 168 may be used to distribute MBMS services to BSs 102 belonging to a multicast broadcast single frequency network (MBSFN) area broadcasting a specific service, and / or may be responsible for session management (start / stop) and for collecting eMBMS related charging information.

[0043] 5GC 190 may include various functional components, including: access and mobility management function (AMF) 192, other AMFs 193, session management function (SMF) 194, and user plane function (UPF) 195. AMF 192 may communicate with unified data management (UDM) 196.

[0044] AMF 192 is a control node that handles signaling between UE 104 and 5GC 190. AMF 192 provides, for example, Quality of Service (QoS) flow and session management.

[0045] Internet Protocol (IP) packets are delivered through UPF 195, which is connected to IP Services 197 and provides IP address allocation for UEs and other functions for 5GC 190. IP Services 197 may include, for example, the Internet, Intranet, IMS, PS streaming services, and / or other IP services.

[0046] In various aspects, a network entity or network node may be implemented as a converged base station, a decomposed base station, a component of a base station, an integrated access and backhaul (IAB) node, a relay node, a sidelink node, to name a few examples.

[0047] Figure 2An example disaggregated base station 200 architecture is depicted. The disaggregated base station 200 architecture may include one or more central units (CUs) 210 that may communicate directly with a core network 220 via a backhaul link, or indirectly with the core network 220 through one or more disaggregated base station units, such as a near real-time (near-RT) RAN intelligent controller (RIC) 225 via an E2 link, or a non-real-time (non-RT) RIC 215 associated with a service management and orchestration (SMO) framework 205, or both. The CU 210 may communicate with one or more distributed units (DUs) 230 via respective midhaul links, such as an F1 interface. The DU 230 may communicate with one or more radio units (RUs) 240 via respective fronthaul links. The RU 240 may communicate with respective UEs 104 via one or more radio frequency (RF) access links. In some implementations, a UE 104 may be served simultaneously by multiple RUs 240.

[0048] Each of the units (e.g., CU 210, DU 230, RU 240, and near-RT RIC 225, non-RT RIC 215, and SMO framework 205) may include or be coupled to one or more interfaces configured to receive or send signals, data, or information (collectively referred to as signals) via a wired or wireless transmission medium. Each of the units or an associated processor or controller that provides instructions to the communication interface of the unit may be configured to communicate with one or more of the other units via a transmission medium. For example, the units may include a wired interface configured to receive or send signals to one or more of the other units via a wired transmission medium. Additionally or alternatively, the unit may include a wireless interface that may include a receiver, transmitter, or transceiver (such as a radio frequency (RF) transceiver) configured to receive or send signals, or both, to one or more of the other units on a wireless transmission medium.

[0049] In some aspects, CU 210 may host one or more higher layer control functions. Such control functions may include radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP), etc. Each control function may be implemented using an interface configured to communicate signals with other control functions hosted by CU 210. CU210 may be configured to handle user plane functionality (e.g., central unit-user plane (CU-UP)), control plane functionality (e.g., central unit-control plane (CU-CP)), or a combination thereof. In some specific implementations, CU 210 may be logically split into one or more CU-UP units and one or more CU-CP units. When implemented in an O-RAN configuration, the CU-UP unit may communicate bidirectionally with the CU-CP unit via an interface (such as an E1 interface). As needed, CU 210 may be implemented to communicate with DU 230 for network control and signaling.

[0050] DU 230 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RUs 240. In some aspects, DU 230 may host one or more of a radio link control (RLC) layer, a medium access control (MAC) layer, and one or more high physical (PHY) layers (such as modules for forward error correction (FEC) encoding and decoding, scrambling, modulation and demodulation, etc.) at least in part according to a functional split such as those defined by the 3rd Generation Partnership Project (3GPP). In some aspects, DU 230 may also host one or more low PHY layers. Each layer (or module) may be implemented using an interface that is configured to communicate signals with other layers (and modules) hosted by DU 230 or with control functions hosted by CU 210.

[0051] The lower layer functionality may be implemented by one or more RUs 240. In some deployments, a RU 240 controlled by a DU 230 may correspond to a logical node that hosts RF processing functions or low PHY layer functions (such as performing Fast Fourier Transform (FFT), Inverse FFT (iFFT), digital beamforming, physical random access channel (PRACH) extraction and filtering, etc.), or both, based at least in part on a functional split (such as a lower layer functional split). In such an architecture, the RU 240 may be implemented to handle over-the-air (OTA) communications with one or more UEs 104. In some implementations, real-time and non-real-time aspects of control plane and user plane communications with the RU 240 may be controlled by the corresponding DU 230. In some scenarios, this configuration may enable the implementation of the DU 230 and the CU 210 in a cloud-based RAN architecture (such as a vRAN architecture).

[0052] The SMO framework 205 may be configured to support RAN deployment and provisioning of non-virtualized network elements and virtualized network elements. For non-virtualized network elements, the SMO framework 205 may be configured to support the deployment of dedicated physical resources for RAN coverage requirements, which may be managed via an operation and maintenance interface (such as an O1 interface). For virtualized network elements, the SMO framework 205 may be configured to interact with a cloud computing platform (such as an open cloud (O-Cloud) 290) to perform network element lifecycle management (such as instantiating virtualized network elements) via a cloud computing platform interface (such as an O2 interface). Such virtualized network elements may include, but are not limited to, CU 210, DU 230, RU 240, and near-RT RIC 225. In some specific implementations, the SMO framework 205 may communicate with hardware aspects of the 4G RAN (such as an open eNB (O-eNB) 211) via the O1 interface. Additionally, in some specific implementations, the SMO framework 205 may communicate directly with one or more RUs 240 via the O1 interface. The SMO framework 205 may also include a non-RT RIC 215 configured to support the functionality of the SMO framework 205 .

[0053] The non-RT RIC 215 may be configured to include logic functions that enable non-real-time control and optimization of RAN elements and resources, artificial intelligence / machine learning (AI / ML) workflows including model training and updating, or policy-based guidance of applications / features in the near-RT RIC 225. The non-RT RIC 215 may be coupled to or in communication with the near-RT RIC 225 (such as via an A1 interface). The near-RT RIC 225 may be configured to include logic functions that enable near-real-time control and optimization of RAN elements and resources via data collection and actions through an interface (such as via an E2 interface) that connects one or more CUs 210, one or more DUs 230, or both, and the O-eNB with the near-RT RIC 225.

[0054] In some implementations, in order to generate an AI / ML model to be deployed in the near-RT RIC 225, the non-RT RIC 215 may receive parameters or external enrichment information from an external server. Such information may be utilized by the near-RT RIC 225 and may be received from a non-network data source or from a network function at the SMO framework 205 or the non-RT RIC 215. In some examples, the non-RT RIC 215 or the near-RT RIC 225 may be configured to tune RAN behavior or performance. For example, the non-RT RIC 215 may monitor long-term trends and patterns of performance and employ AI / ML models to perform corrective actions through the SMO framework 205 (such as via reconfiguration of O1) or via the creation of RAN management policies (such as A1 policies).

[0055] Figure 3 Aspects of an example BS 102 and UE 104 are depicted.

[0056] In general, BS 102 includes various processors (e.g., 320, 330, 338, and 340), antennas 334a-334t (collectively 334), transceivers 332a-332t (collectively 332) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., data source 312) and wireless reception of data (e.g., data sink 339). For example, BS 102 can transmit and receive data between BS 102 and UE 104. BS 102 includes a controller / processor 340 that can be configured to implement various functions described herein related to wireless communication.

[0057] In general, the UE 104 includes various processors (e.g., 358, 364, 366, and 380), antennas 352a-352r (collectively 352), transceivers 354a-354r (collectively 354) including modulators and demodulators, and other aspects that enable wireless transmission of data (e.g., retrieved from a data source 362) and wireless reception of data (e.g., provided to a data sink 360). The UE 104 includes a controller / processor 380 that can be configured to implement various functions described herein related to wireless communications.

[0058] Regarding example downlink transmissions, BS 102 includes a transmit processor 320 that can receive data from a data source 312 and control information from a controller / processor 340. The control information can be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical HARQ indicator channel (PHICH), a physical downlink control channel (PDCCH), a group common PDCCH (GC PDCCH), and / or others. In some examples, the data can be for a physical downlink shared channel (PDSCH).

[0059] The transmit processor 320 may process (e.g., encode and symbol map) data and control information to obtain data symbols and control symbols, respectively. The transmit processor 320 may also generate reference symbols, such as for a primary synchronization signal (PSS), a secondary synchronization signal (SSS), a PBCH demodulation reference signal (DMRS), and a channel state information reference signal (CSI-RS).

[0060] The transmit (TX) multiple-input multiple-output (MIMO) processor 330 may perform spatial processing (e.g., pre-decoding) on ​​data symbols, control symbols, and / or reference symbols, where applicable, and may provide an output symbol stream to a modulator (MOD) in a transceiver 332a-332t. Each modulator in the transceiver 332a-332t may process a corresponding output symbol stream 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 the modulators in the transceivers 332a-332t may be transmitted via antennas 334a-334t, respectively.

[0061] To receive downlink transmissions, UE 104 includes antennas 352a-352r that can receive downlink signals from BS 102 and can provide received signals to demodulators (DEMODs) in transceivers 354a-354r, respectively. Each demodulator in transceivers 354a-354r can condition (e.g., filter, amplify, downconvert, and digitize) a corresponding received signal to obtain input samples. Each demodulator can further process the input samples to obtain received symbols.

[0062] A MIMO detector 356 may obtain received symbols from all demodulators in transceivers 354a-354r, perform MIMO detection on the received symbols if applicable, and provide detected symbols. A receive processor 358 may process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 104 to a data sink 360, and provide decoded control information to a controller / processor 380.

[0063] With respect to example uplink transmissions, the UE 104 also includes a transmit processor 364 that may receive and process data from a data source 362 (e.g., for a PUSCH) and control information from a controller / processor 380 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 364 may also generate reference symbols for reference signals (e.g., a sounding reference signal (SRS)). The symbols from the transmit processor 364 may be pre-decoded by a TX MIMO processor 366, if applicable, further processed by a modulator in the transceivers 354a-354r (e.g., for SC-FDM), and transmitted to the BS 102.

[0064] At BS 102, uplink signals from UE 104 may be received by antennas 334 a-334 t, processed by demodulators in transceivers 332 a-332 t, detected by MIMO detector 336 if applicable, and further processed by receive processor 338 to obtain decoded data and control information transmitted by UE 104. Receive processor 338 may provide decoded data to data sink 339 and decoded control information to controller / processor 340.

[0065] Memories 342 and 382 may store data and program codes for BS 102 and UE 104, respectively.

[0066] Scheduler 344 may schedule UEs for data transmission on the downlink and / or uplink.

[0067] In various aspects, BS 102 may be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 312, a scheduler 344, a memory 342, a transmit processor 320, a controller / processor 340, a TX MIMO processor 330, a transceiver 332a-332t, an antenna 334a-334t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 334a-334t, a transceiver 332a-332t, a RX MIMO detector 336, a controller / processor 340, a receive processor 338, a scheduler 344, a memory 342, and / or other aspects described herein.

[0068] In various aspects, the UE 104 may also be described as sending and receiving various types of data associated with the methods described herein. In these contexts, "sending" may refer to various mechanisms for outputting data, such as outputting data from a data source 362, a memory 382, ​​a transmit processor 364, a controller / processor 380, a TX MIMO processor 366, a transceiver 354a-354t, an antenna 352a-352t, and / or other aspects described herein. Similarly, "receiving" may refer to various mechanisms for obtaining data, such as obtaining data from an antenna 352a-352t, a transceiver 354a-354t, a RX MIMO detector 356, a controller / processor 380, a receive processor 358, a memory 382, ​​and / or other aspects described herein.

[0069] In some aspects, the processor may be configured to perform various operations (such as those associated with the methods described herein) and send (output) data to or receive (obtain) data from another interface configured to send or receive data, respectively.

[0070] Figure 4A , Figure 4B , Figure 4C and Figure 4D Describes a method for use in a wireless communication network such as Figure 1 Various aspects of the data structure of the wireless communication network 100).

[0071] Specifically, Figure 4A is a diagram 400 illustrating an example of a first subframe within a 5G (e.g., 5G NR) frame structure, Figure 4B is a diagram 430 illustrating an example of a DL channel within a 5G subframe, Figure 4C is a diagram 450 illustrating an example of a second subframe within a 5G frame structure, and Figure 4D FIG480 is a diagram illustrating an example of UL channels within a 5G subframe.

[0072] Wireless communication networks can utilize Orthogonal Frequency Division Multiplexing (OFDM) with a Cyclic Prefix (CP) on both the uplink and downlink. Such systems can also support half-duplex operation using Time Division Duplex (TDD). OFDM and Single Carrier Frequency Division Multiplexing (SC-FDM) can be used to maximize the system bandwidth (e.g., Figure 4B and Figure 4D The RF (depicted) is divided into multiple orthogonal subcarriers. Each subcarrier can be modulated with data. Modulation symbols can be transmitted in the frequency domain using OFDM and / or in the time domain using SC-FDM.

[0073] The wireless communication frame structure may be frequency division duplex (FDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to either DL or UL. The wireless communication frame structure may also be time division duplex (TDD), where for a particular set of subcarriers, subframes within the set of subcarriers are dedicated to both DL and UL.

[0074] exist Figure 4A and Figure 4C In the wireless communication frame structure, TDD is used, where D is DL, U is UL, and X is used flexibly between DL / UL. The UE can be configured with a time slot format (dynamically configured by DL control information (DCI) or semi-statically / statically configured by radio resource control (RRC) signaling) through the received time slot format indicator (SFI). In the depicted example, the 10ms frame is divided into 10 equally sized 1ms subframes. Each subframe may include one or more time slots. In some examples, each time slot may include 7 or 14 symbols, depending on the time slot format. The subframe may also include a micro-time slot, which generally has fewer symbols than the entire time slot. Other wireless communication technologies may have different frame structures and / or different channels.

[0075] In certain aspects, the number of time slots within a subframe is based on the time slot configuration and the parameter set. For example, for time slot configuration 0, different parameter sets (μ) 0 to 5 allow for 1, 2, 4, 8, 16, and 32 time slots per subframe, respectively. For time slot configuration 1, different parameter sets 0 to 2 allow for 2, 4, and 8 time slots per subframe, respectively. Thus, for time slot configuration 0 and parameter set μ, there are 14 symbols / time slot and 2μ time slots / subframe. The subcarrier spacing and symbol length / duration are a function of the parameter set. The subcarrier spacing may be equal to 2 μ × 15kHz, where μ is parameter set 0 to 5. Thus, parameter set μ=0 has a subcarrier spacing of 15kHz, while parameter set μ=5 has a subcarrier spacing of 480kHz. The symbol length / duration is inversely related to the subcarrier spacing. Figure 4A , Figure 4B , Figure 4C and Figure 4D An example is provided for slot configuration 0 with 14 symbols per slot and parameter set μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs.

[0076] like Figure 4A , Figure 4B , Figure 4C and Figure 4DAs depicted, a resource grid may be used to represent a frame structure. Each slot includes a resource block (RB) (also referred to as a physical RB (PRB)) extending, for example, over 12 consecutive subcarriers. The resource grid is divided into a plurality of resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.

[0077] like Figure 4A As illustrated, some REs carry data for UEs (e.g. Figure 1 and Figure 3 The RS may include a demodulation RS (DMRS) and / or a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and / or a phase tracking RS (PT-RS).

[0078] Figure 4B Examples of various DL channels within a subframe of a frame are illustrated.The Physical Downlink Control Channel (PDCCH) carries DCI within one or more Control Channel Elements (CCEs), each CCE comprising, for example, nine RE Groups (REGs), each REG comprising, for example, four consecutive REs in an OFDM symbol.

[0079] The primary synchronization signal (PSS) may be in symbol 2 of a particular subframe of a frame. The PSS is transmitted by a UE (e.g., Figure 1 and Figure 3 104) is used to determine subframe / symbol timing and physical layer identification.

[0080] The Secondary Synchronization Signal (SSS) may be within symbol 4 of a particular subframe of a frame. The SSS is used by the UE to determine the physical layer cell identity group number and radio frame timing.

[0081] Based on the physical layer identifier and the physical layer cell identifier group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the location of the aforementioned DMRS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically grouped with the PSS and SSS to form a synchronization signal (SS) / PBCH block. The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information (such as system information blocks (SIBs)) that is not sent via the PBCH, and / or paging messages.

[0082] As in Figure 4CAs illustrated, some REs carry DMRS for channel estimation at the base station (indicated as R for a particular configuration, but other DMRS configurations are possible). The UE may send a DMRS for PUCCH and a DMRS for PUSCH. The PUSCH DMRS may be sent, for example, in the first one or two symbols of the PUSCH. The PUCCH DMRS may be sent in different configurations depending on whether a short PUCCH or a long PUCCH is sent and depending on the specific PUCCH format used. UE 104 may send a sounding reference signal (SRS). The SRS may be sent, for example, in the last symbol of a subframe. The SRS may have a comb structure, and the UE may send the SRS on one of the teeth of the comb. The SRS may be used by the base station for channel quality estimation to achieve frequency-dependent scheduling of the UL.

[0083] Figure 4D Examples of various UL channels within a subframe of a frame are illustrated. The PUCCH may be located at a position as indicated in one configuration. The PUCCH carries uplink control information (UCI), such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and HARQ ACK / NACK feedback. The PUSCH carries data and may additionally be used to carry a buffer status report (BSR), a power headroom report (PHR), and / or UCI.

[0084] Overview of UCI Multiplexing on PUSCH

[0085] As described above, UCI multiplexing on PUSCH is a mechanism that allows UCI to be sent on PUSCH resources. In the case where a single TB is used for PUSCH, certain types of UCI such as hybrid automatic repeat request (HARQ) acknowledgment feedback and channel state information (CSI) are typically mapped to all layers of the TB on PUSCH. The modulation order of UCI typically follows the modulation order of UL-SCH. For non-periodic CSI on PUSCH triggered by a UL grant without UL-SCH data, the modulation order used for PUSCH is typically handled in the same manner as when PUSCH is sent with UL-SCH data.

[0086] Figure 5 is a conceptual diagram illustrating how UCI may be multiplexed with a UL data channel in accordance with certain aspects of the present disclosure. As shown, UCI multiplexing on PUSCH may occur when a physical uplink control channel (PUCCH) scheduled to carry UCI overlaps with PUSCH (e.g., in the time domain). In this case, the PUCCH transmission may be dropped and UCI may be multiplexed on PUSCH such that the PUSCH channel now carries both data and UCI (UL-SCH+UCI).

[0087] How to multiplex UCI may depend on the type and size of the UCI content. For example, for HARQ-ACK multiplexed on PUSCH, if the payload is less than or equal to 2 bits, the PUSCH may be truncated. On the other hand, for HARQ-ACK multiplexed on PUSCH, if the payload is greater than 2 bits, the PUSCH may be rate matched. For periodic CSI reporting configured by RRC and aperiodic CSI reporting triggered by UL grant, UCI may be rate matched with the PUSCH. For CSI multiplexing on PUSCH, CSI may be mapped to distributed REs across RBs allocated to PUSCH. In some cases, it may be supported to split the CSI into two parts by mapping (at least for some CSI). In such cases, the two parts may be mapped differently.

[0088] In some cases, HARQ-ACK content may be mapped to REs around demodulation reference signal (DMRS) symbols. The modulated HARQ-ACK symbol may be mapped starting on the first available non-DMRS symbol after the first DMRS symbol, regardless of the number of DMRS symbols in the PUSCH transmission. Different types of CSI (e.g., CSI part 1 and CSI part 2) may be mapped starting on the first available non-DMRS symbol, regardless of the number of DMRS symbols in the PUSCH.

[0089] If PUSCH is truncated by HARQ-ACK, CSI Part 1 may be mapped starting after a certain amount of reserved HARQ-ACK REs. CSI Part 1 may not be mapped on the reserved HARQ-ACK REs. CSI Part 2 may not be mapped on CSI Part 1 REs. CSI Part 2 and PUSCH may be mapped to the reserved HARQ-ACK REs. If PUSCH is rate matched by HARQ-ACK, HARQ-ACK may be mapped first, followed by CSI Part 1. In such cases, CSI Part 1 may not be mapped on the HARQ-ACK REs, and CSI Part 2 may not be mapped on the HARQ-ACK REs.

[0090] One potential challenge is how to multiplex UCI on simultaneous multi-panel UL transmissions. Multi-panel transmissions may allow higher UL throughput and reliability, especially on certain frequency bands (e.g., on FR2) and multiple transmitter receiver point (mTRP) scenarios, assuming up to 2 TRPs and up to 2 panels. Uplink precoding may be indicated for PUSCH, where no new codebook is introduced for multi-panel simultaneous transmissions.

[0091] In some cases, considering multi-TRP operation based on single DCI and multi-DCI, the total number of layers across all panels can be up to four, and the total number of codewords across all panels can be up to two. In other cases, UL DMRS, SRS, SRI and TPMI (including codebook) can be enhanced to enable 8Tx UL operation to support 4 layers and more per UE in the uplink. And multiple codewords may be required for more than 4 layers in the UL.

[0092] Aspects related to multiplexing of UCI on PUSCH with multiple TBs

[0093] As mentioned above, the possibility of multiple TBs having different transmission parameters creates potential challenges for multiplexing UCI on PUSCH. For example, one challenge is how to map the UCI content to the available resources on different TBs.

[0094] However, aspects of the present disclosure provide various approaches that may help determine how to multiplex UCI on a PUSCH with multiple TBs.

[0095] According to one example aspect, when more than one TB is sent on PUSCH, UCI may be multiplexed across all layers of all TBs on PUSCH regardless of UCI type. This may provide increased robustness for UCI.

[0096] Figure 6 An example mechanism 600 for multiplexing UCI on resource elements (REs) on all layers of all TBs (eg, TB0 and TB1) on PUSCH is illustrated.

[0097] As shown, in this example, the UCI multiplexed on one TB (e.g., a first TB labeled "TB0") may be a copy of the UCI multiplexed on another TB (e.g., a second TB labeled "TB1"). In some aspects, each copy of the UCI may be multiplexed on the same resource elements (REs) across the layers of all TBs. The UCI may include hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) feedback and channel state information (CSI), which may be divided into CSI part 1 and CSI part 2. In some aspects, the same decoded bits before rate matching are rate matched separately and mapped to the layers of the first TB and the second TB, respectively.

[0098] Figure 7 Another example mechanism 700 for multiplexing UCI across all layers of all TBs on PUSCH is illustrated.

[0099] In this example, UCI can be multiplexed on the same RE across the layers of all TBs without repeating (e.g., duplicating) UCI ​​on different TBs. As shown in the figure, in some aspects, the coded bits can be mapped separately to the layers of the first TB and the second TB. For example, the coded UCI bits can be split into a first part 702 and a second part 704 to balance the UCI bits multiplexed on different TBs. In one example, the first part 702 can be multiplexed on TB0 and the second part 704 can be multiplexed on TB1, as shown in the figure. In this case, the UCI bits multiplexed on TB0 can be excluded from the UCI bits multiplexed on TB1.

[0100] According to certain aspects, when more than one TB is sent on PUSCH, UCI may be multiplexed on all layers of one of the TBs on PUSCH. That is, all UCI may be multiplexed on all layers of one TB.

[0101] Figure 8 An example mechanism 800 for multiplexing UCI across all layers of one TB (eg, TB0 or ​​TB1) is illustrated.

[0102] In the example shown, the UE determines to multiplex UCI on TB1. Therefore, all UCI may be multiplexed only on TB1 (and TB0 may be used to send uplink (UL) scheduling (UL-SCH, as shown). The selection of the TB on which the UCI is to be multiplexed may or may not depend on the type of UCI. This may provide increased robustness for the UCI. In some aspects, the UCI may be multiplexed on the TB with the highest modulation and coding scheme (MCS). Therefore, on Figure 8 In the example illustrated in , TB1 may have a higher MCS than TB0. In some aspects, if the MCSs of the two TBs are the same, the UCI may be multiplexed on the first TB in sequence (eg, TB0).

[0103] In some cases, different UCI (e.g., different UCI types) may have different reliability criteria. Thus, according to certain aspects, when more than one TB is sent on the PUSCH, the UCI may be multiplexed across all layers of one or more selected TBs, which may be selected based on the type of UCI to be multiplexed. That is, some UCI may be multiplexed across all layers of two TBs, while other UCI may be multiplexed across all layers of only one TB.

[0104] For example, Fig. 9 Another example mechanism 900 for multiplexing UCIs based on the type of the UCI is illustrated.

[0105] In this case, UCI with a relatively high reliability standard (e.g., HARQ-ACK and / or CG-UCI) may be multiplexed on all layers of two TBs with duplication, while UCI with a relatively low reliability standard (e.g., CSI) may be multiplexed on all layers of a single TB. Fig. 9 In the example of , HARQ-ACK feedback may be multiplexed on both TB0 and TB1, and CSI (parts 1 and 2) may be multiplexed on TB1 (but not on TB0). In some aspects, UCI (e.g., Fig. 9 HARQ-ACK feedback in (HARQ-ACK feedback in) can be multiplexed on the same RE across the layers of all TBs, and the UCI multiplexed on one TB can be a copy of the UCI multiplexed on another TB. In certain other aspects, the UCI can be multiplexed on the same RE across the layers of all TBs without repeating the UCI on different TBs (e.g., the UCI can be split, as discussed above).

[0106] In some cases, different UCIs may have different payload sizes. In this case, for UCIs with relatively large payloads (such as CSI), the UCIs may be multiplexed across all layers of two TBs without duplication, while for UCIs with relatively small payloads (such as HARQ-ACK and / or CG-UCI), the UCIs may be multiplexed across all layers of a single TB.

[0107] For example, Fig.10 An example mechanism 1000 for multiplexing UCI in this manner is illustrated.

[0108] In this example, CSI (parts 1 and 2) may be multiplexed on both TB0 and TB1, and HARQ-ACK feedback may be multiplexed on TB0 (but not on TB1). In certain aspects, UCI included in both TBs (e.g., Fig.10 The CSI in the TB) may be multiplexed on the same RE across the layers of all TBs, and the UCI multiplexed on one TB may be a copy of the UCI multiplexed on another TB. In certain other aspects, the UCI may be multiplexed on the same RE across the layers of all TBs without repeating the UCI on different TBs (e.g., the UCI may be split, as discussed above).

[0109] According to certain aspects, some UCI (e.g., of the first type) may be multiplexed on all layers of one TB, while other UCI (e.g., of the second type) may be mapped to layers of another TB. This may help balance REs used for UCI multiplexing on different TBs.

[0110] For example, Fig.11An example mechanism 1100 for multiplexing UCI in this manner is illustrated. As shown, HARQ-ACK feedback and CSI part 1 may be multiplexed on TB0, while CSI part 2 may be multiplexed on TB1.

[0111] In some aspects (such as Fig.11 Different UCIs (as shown in ) may be multiplexed on different REs across all layers of different TBs. That is, REs in TB1 corresponding to REs in TB0 used to send HARQ-ACK feedback and CSI part 1 may not be used to multiplex CSI part 2.

[0112] Alternatively, if Fig.12 As shown in the example method 1200 in FIG. 1 , different UCI (content) may be multiplexed on the same REs across all layers of different TBs (e.g., when UCI bits are multiplexed on the layers of the second TB, REs of the first TB on which UCI has been multiplexed are not excluded). That is, REs in TB1 corresponding to REs in TB0 used to send HARQ-ACK feedback and CSI part 1 may also be used to multiplex CSI part 2.

[0113] In some examples, one or more types of UCI (e.g., HARQ-ACK feedback, CSI part 1, and / or CG-UCI) may be multiplexed across all layers of a first TB or a TB with the highest MCS, while one or more other types of UCI (e.g., CSI part 1, CSI part 2, and / or CG-UCI) may be multiplexed across all layers of a second TB or a TB with the lowest MCS.

[0114] In any of the above aspects, the modulation order of the UCI may follow the modulation order of the corresponding TB on which the UCI is multiplexed. That is, the UCI multiplexed on the first TB may follow the modulation order of the first TB, and the UCI multiplexed on the second TB may follow the modulation order of the second TB. Additionally, in any of the above aspects in which UCI is multiplexed on more than one TB, the decoded bits of the UCI (e.g., before rate matching) may be rate matched separately and then multiplexed on the first TB and the second TB.

[0115] When UCI is multiplexed on a first set of resource elements (REs) on a first TB, data in a PUSCH may not be mapped to the first set of REs on the first TB.

[0116] However, if Fig.13 As shown in , data in the PUSCH may be mapped to REs in the second TB (eg, TB0 in this case) corresponding to the first set of REs on the first TB (eg, TB1 in this case). Fig.14As shown in , data in the PUSCH may not be mapped to REs in the second TB corresponding to the first group of REs in the first TB.

[0117] Example Operation of User Equipment

[0118] Fig.15 An example of a method 1500 for wireless communication is shown. In some cases, the method 1500 may be performed by a UE (such as, Figure 1 and Figure 3 UE 104) executes.

[0119] Method 1500 begins at step 1505 by receiving signaling for scheduling a PUSCH having at least a first TB and a second TB, wherein the first TB and the second TB have separate transmission parameters. In some cases, the operation of this step refers to or can be referred to as Fig.17 The described circuits for receiving and / or codes for receiving are performed.

[0120] Then, the method 1500 proceeds to step 1510 to determine how to multiplex the UCI on the PUSCH. In some cases, the operation of this step refers to or can be referred to as Fig.17 The described circuits for determining and / or codes for determining are performed.

[0121] Then, the method 1500 proceeds to step 1515, and transmits a PUSCH with UCI multiplexed on the PUSCH according to the determination. In some cases, the operation of this step refers to or can be referred to as Fig.17 The described circuits for sending and / or codes for sending are performed.

[0122] In some aspects, the UCI is multiplexed on one of the first TB or the second TB.

[0123] In some aspects, the UCI is multiplexed on either: a TB with a higher MCS; or the first TB if the MCS of the first TB and the second TB are the same.

[0124] In some aspects, the modulation order of the UCI follows: the modulation order of the first TB multiplexed based on the UCI on the first TB; or the modulation order of the second TB multiplexed based on the UCI on the second TB.

[0125] In some aspects, at least a portion of the UCI is multiplexed on each of the first TB and the second TB.

[0126] In some aspects, the modulation order of the UCI multiplexed on the first TB follows the modulation order of the first TB, and the UCI multiplexed on the second TB follows the modulation order of the second TB.

[0127] In some aspects, the decoded bits of the UCI multiplexed on the first TB are rate matched separately from the decoded bits of the UCI multiplexed on the second TB.

[0128] In some aspects, UCI is multiplexed on the same REs across layers of the first TB and the second TB; and the UCI multiplexed on the first TB is a copy of the UCI multiplexed on the second TB.

[0129] In some aspects, a first set of coded bits of UCI are multiplexed on a first TB; and a second set of coded bits of UCI are multiplexed on a second TB.

[0130] In some aspects, the determination of how to multiplex UCI on PUSCH is based on the type of UCI.

[0131] In some aspects, UCI of the first type is multiplexed on each of the first TB and the second TB; and UCI of the second type is multiplexed on the first TB or the second TB.

[0132] In some aspects, UCI of a first type is multiplexed on a first TB; and UCI of a second type is multiplexed on a second TB.

[0133] In some aspects, UCI is multiplexed across layers of the first TB and the second TB on different REs.

[0134] In some aspects, UCI is multiplexed on the same REs across layers of the first TB and the second TB.

[0135] In some aspects, UCI is multiplexed on a first group of REs on a first TB; data in a PUSCH is not mapped to a first group of REs on the first TB; and data in a PUSCH is mapped to REs in a second TB corresponding to the first group of REs.

[0136] In some aspects, UCI is multiplexed on a first set of REs on a first TB; data in a PUSCH is not mapped to the first set of REs on the first TB; and data in the PUSCH is not mapped to REs in a second TB corresponding to the first set of REs.

[0137] In one aspect, method 1500 or any aspect related thereto may be performed by an apparatus such as Fig.17 The method 1500 is performed by a communication device 1700 that includes various components that are operable, configured, or adapted to perform the method 1500. The communication device 1700 is described in more detail below.

[0138] Please note that Fig.15This is merely one example of a method, and other methods including fewer, additional, or alternative steps may also be consistent with the present disclosure.

[0139] Example Operations of Network Entities

[0140] Fig.16 shows a method for use by network entities such as Figure 1 and Figure 3 BS102 or as relative to Figure 2 An example of a method 1600 of performing wireless communications with a decomposed base station is discussed.

[0141] Method 1600 begins at step 1605 by sending a signaling for a UE to schedule a PUSCH for at least a first TB and a second TB, wherein the first TB and the second TB have separate transmission parameters. In some cases, the operation of this step refers to or can be referred to as Fig.18 The described circuits for sending and / or codes for sending are performed.

[0142] Then, the method 1600 proceeds to step 1610 to determine how the UE will multiplex UCI on the PUSCH. In some cases, the operation of this step refers to or can be referred to as Fig.18 The described circuits for determining and / or codes for determining are performed.

[0143] Then, the method 1600 proceeds to step 1615, monitoring the PUSCH with the UCI multiplexed on the PUSCH based on the determination. In some cases, the operation of this step refers to or can be referred to as Fig.18 The described circuits for monitoring and / or codes for monitoring are implemented.

[0144] In some aspects, the UCI is multiplexed on one of the first TB or the second TB.

[0145] In some aspects, the UCI is multiplexed on either: a TB with a higher MCS; or the first TB if the MCS of the first TB and the second TB are the same.

[0146] In some aspects, the modulation order of the UCI follows: the modulation order of the first TB multiplexed based on the UCI on the first TB; or the modulation order of the second TB multiplexed based on the UCI on the second TB.

[0147] In some aspects, at least a portion of the UCI is multiplexed on each of the first TB and the second TB.

[0148] In some aspects, a modulation order of the portion of UCI multiplexed on a first TB follows a modulation order of the first TB, and a modulation order of the portion of UCI multiplexed on a second TB follows a modulation order of the second TB.

[0149] In some aspects, the decoded bits of the UCI multiplexed on the first TB are rate matched separately from the decoded bits of the UCI multiplexed on the second TB.

[0150] In some aspects, UCI is multiplexed on the same REs across layers of the first TB and the second TB; and the UCI multiplexed on the first TB is a copy of the UCI multiplexed on the second TB.

[0151] In some aspects, a first set of coded bits of UCI are multiplexed on a first TB; and a second set of coded bits of UCI are multiplexed on a second TB.

[0152] In some aspects, the UE's determination of how to multiplex UCI on the PUSCH is based on the type of UCI.

[0153] In some aspects, UCI of the first type is multiplexed on each of the first TB and the second TB; and UCI of the second type is multiplexed on the first TB or the second TB.

[0154] In some aspects, UCI of a first type is multiplexed on a first TB; and UCI of a second type is multiplexed on a second TB.

[0155] In some aspects, UCI is multiplexed across layers of the first TB and the second TB on different REs.

[0156] In some aspects, UCI is multiplexed on the same REs across layers of the first TB and the second TB.

[0157] In some aspects, UCI is multiplexed on a first set of REs on a first TB; and data in a PUSCH is mapped to REs in a second TB corresponding to the first set of REs.

[0158] In some aspects, UCI is multiplexed on a first set of REs on a first TB; and data in a PUSCH is not mapped to REs in a second TB corresponding to the first set of REs.

[0159] In one aspect, method 1600 or any aspect related thereto may be performed by an apparatus such as Fig.18 The method 1600 is performed by a communication device 1800 that includes various components operable to, configured to, or adapted to perform the method 1600. The communication device 1800 is described in more detail below.

[0160] Please note that Fig.16 This is merely one example of a method, and other methods including fewer, additional, or alternative steps may also be consistent with the present disclosure.

[0161] Example Communication Device

[0162] Fig.17 Depicted are aspects of an example communications device 1700. In some examples, communications device 1700 is user equipment, such as described above with respect to Figure 1 and Figure 3 UE 104 is described.

[0163] The communication device 1700 includes a processing system 1705 coupled to a transceiver 1755 (e.g., a transmitter and / or a receiver). The transceiver 1755 is configured to transmit and receive signals for the communication device 1700, such as various signals as described herein, via an antenna 1760. The processing system 1705 may be configured to perform processing functions for the communication device 1700, including processing signals received and / or to be transmitted by the communication device 1700.

[0164] The processing system 1705 includes one or more processors 1710. In various aspects, such as with respect to Figure 3 As depicted, the one or more processors 1710 may represent one or more of the receive processor 358, the transmit processor 364, the TX MIMO processor 366, and / or the controller / processor 380. The one or more processors 1710 are coupled to the computer-readable medium / memory 1730 via the bus 1750. In certain aspects, the computer-readable medium / memory 1730 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1710, cause the one or more processors 1710 to perform operations with respect to the computer-readable medium / memory 1730. Fig.15 The described method 1500 or any aspect related thereto. Note that references to a processor performing a function of the communication device 1700 may include one or more processors 1710 performing that function of the communication device 1700 .

[0165] In the depicted example, computer readable medium / memory 1730 stores code (e.g., executable instructions), such as code for receiving 1735, code for determining 1740, and code for sending 1745. Processing of code for receiving 1735, code for determining 1740, and code for sending 1745 may cause communication device 1700 to perform operations with respect to Fig.15 The described method 1500 or any aspect related thereto.

[0166] The one or more processors 1710 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1730, including circuits such as circuits for receiving 1715, circuits for determining 1720, and circuits for transmitting 1725. Processing using the circuits for receiving 1715, circuits for determining 1720, and circuits for transmitting 1725 may enable the communication device 1700 to perform operations with respect to Fig.15 The described method 1500 or any aspect related thereto.

[0167] The various components of the communication device 1700 may be provided for performing Fig.15 The described means of method 1500 or any aspect thereof. For example, means for sending, transmitting, or outputting for sending may include Figure 3 The transceiver 354 and / or antenna 352 of the exemplary UE 104, and / or Fig.17 The transceiver 1755 and antenna 1760 of the communication device 1700 in FIG. 1 may include Figure 3 The illustrated transceiver 354 and / or antenna 352 of the UE 104, and / or Fig.17 The transceiver 1755 and antenna 1760 of the communication device 1700.

[0168] Fig.18 Aspects of an example communications device 1800 are depicted. In some aspects, communications device 1800 is a network entity such as Figure 1 and Figure 3 BS102 or as relative to Figure 2 The decomposed base station in question.

[0169] The communication device 1800 includes a processing system 1805 coupled to a transceiver 1855 (e.g., a transmitter and / or a receiver) and / or a network interface 1865. The transceiver 1855 is configured to transmit and receive signals for the communication device 1800 via an antenna 1860, such as various signals as described herein. The network interface 1865 is configured to transmit and receive signals for the communication device 1800 via a communication link (e.g., as described herein with respect to Figure 2 The processing system 1805 may be configured to perform the processing functions of the communication device 1800, including processing signals received and / or to be transmitted by the communication device 1800.

[0170] The processing system 1805 includes one or more processors 1810. In various aspects, such as with respect to Figure 3As described, the one or more processors 1810 may represent one or more of the receive processor 338, the transmit processor 320, the TX MIMO processor 330, and / or the controller / processor 340. The one or more processors 1810 are coupled to the computer-readable medium / memory 1830 via the bus 1850. In certain aspects, the computer-readable medium / memory 1830 is configured to store instructions (e.g., computer-executable code) that, when executed by the one or more processors 1810, cause the one or more processors 1810 to perform operations with respect to the computer-readable medium / memory 1830. Fig.16 The described method 1600 or any aspect related thereto. Note that references to a processor of the communication device 1800 that performs a function may include one or more processors 1810 of the communication device 1800 that perform that function.

[0171] In the depicted example, the computer readable medium / memory 1830 stores code (e.g., executable instructions), such as code 1835 for transmitting, code 1840 for determining, and code 1845 for monitoring. Processing of the code 1835 for transmitting, the code 1840 for determining, and the code 1845 for monitoring may cause the communication device 1800 to perform operations relative to Fig.16 The described method 1600 or any aspect related thereto.

[0172] The one or more processors 1810 include circuits configured to implement (e.g., execute) code stored in the computer-readable medium / memory 1830, including circuits such as circuits for transmitting 1815, circuits for determining 1820, and circuits for monitoring 1825. Processing using the circuits for transmitting 1815, the circuits for determining 1820, and the circuits for monitoring 1825 may enable the communication device 1800 to perform operations with respect to Fig.16 The described method 1600 or any aspect related thereto.

[0173] The various components of the communication device 1800 may be provided for performing Fig.16 Means for sending, transmitting, or outputting for sending may include: Figure 3 The illustrated transceiver 332 and / or antenna 334 of the BS 102, and / or Fig.18 The transceiver 1855 and antenna 1860 of the communication device 1800 in FIG. 1 may include Figure 3 The illustrated transceiver 332 and / or antenna 334 of the BS 102, and / or Fig.18 The transceiver 1855 and antenna 1860 of the communication device 1800.

[0174] Sample Clauses

[0175] Specific implementation examples are described in the following numbered clauses:

[0176] Clause 1: A method for wireless communication, the method comprising: receiving signaling for scheduling a PUSCH having at least a first TB and a second TB, wherein the first TB and the second TB have separate transmission parameters; determining how to multiplex UCI on the PUSCH; and transmitting the PUSCH having the UCI multiplexed on the PUSCH based on the determination.

[0177] Clause 2: The method of clause 1, wherein the UCI is multiplexed on one of the first TB or the second TB.

[0178] Clause 3: The method of clause 2, wherein the UCI is multiplexed on either: the TB having a higher MCS; or, if the MCS of the first TB and the second TB are the same, the first TB.

[0179] Clause 4: The method according to clause 2, wherein the modulation order of the UCI follows: the modulation order of the first TB multiplexed on the first TB based on the UCI; or the modulation order of the second TB multiplexed on the second TB based on the UCI.

[0180] Clause 5: The method of any of clauses 1 to 4, wherein: at least a portion of the UCI is multiplexed on each of the first TB and the second TB.

[0181] Clause 6: The method of clause 5, wherein a modulation order of the UCI multiplexed on the first TB follows a modulation order of the first TB, and the UCI multiplexed on the second TB follows a modulation order of the second TB.

[0182] Clause 7: The method of clause 5, wherein the decoded bits of the UCI multiplexed on the first TB are rate matched separately from the decoded bits of the UCI multiplexed on the second TB.

[0183] Clause 8: The method of clause 5, wherein: the UCI is multiplexed on the same REs across layers of the first TB and the second TB; and the UCI multiplexed on the first TB is a copy of the UCI multiplexed on the second TB.

[0184] Clause 9: The method of clause 5, wherein: a first set of decoded bits of the UCI are multiplexed on the first TB; and a second set of decoded bits of the UCI are multiplexed on the second TB.

[0185] Clause 10: A method as set out in any of clauses 1 to 9, wherein the determination of how to multiplex the UCI on the PUSCH is based on a type of the UCI.

[0186] Clause 11: The method of clause 10, wherein: UCI of a first type is multiplexed on each of the first TB and the second TB; and UCI of a second type is multiplexed on the first TB or the second TB.

[0187] Clause 12: The method of clause 10, wherein: UCI of a first type is multiplexed on the first TB; and UCI of a second type is multiplexed on the second TB.

[0188] Clause 13: The method of clause 12, wherein: the UCI is multiplexed on different REs across layers of the first TB and the second TB.

[0189] Clause 14: The method of clause 12, wherein: the UCI is multiplexed on the same RE across layers of the first TB and the second TB.

[0190] Clause 15: A method according to any one of clauses 1 to 14, wherein: the UCI is multiplexed on the first TB on a first group of REs; the data in the PUSCH is not mapped to the first group of REs on the first TB; and the data in the PUSCH is mapped to REs in the second TB corresponding to the first group of REs.

[0191] Clause 16: A method according to any one of clauses 1 to 15, wherein: the UCI is multiplexed on the first TB on a first group of REs; the data in the PUSCH is not mapped to the first group of REs on the first TB; and the data in the PUSCH is not mapped to REs in the second TB corresponding to the first group of REs.

[0192] Clause 17: A method for wireless communications by a network entity, the method comprising: sending signaling for a UE scheduling a PUSCH having at least a first TB and a second TB, wherein the first TB and the second TB have separate transmission parameters; determining how the UE will multiplex UCI on the PUSCH; and monitoring the PUSCH having the UCI multiplexed on the PUSCH based on the determination.

[0193] Clause 18: The method of clause 17, wherein the UCI is multiplexed on one of the first TB or the second TB.

[0194] Clause 19: The method of clause 18, wherein the UCI is multiplexed on either: the TB having a higher MCS; or, if the MCS of the first TB and the second TB are the same, the first TB.

[0195] Clause 20: The method of clause 18, wherein a modulation order of the UCI follows: a modulation order of the first TB multiplexed on the first TB based on the UCI; or a modulation order of the second TB multiplexed on the second TB based on the UCI.

[0196] Clause 21: The method of any of clauses 17 to 20, wherein: at least a portion of the UCI is multiplexed on each of the first TB and the second TB.

[0197] Clause 22: The method of clause 21, wherein the modulation order of the portion of the UCI multiplexed on the first TB follows the modulation order of the first TB, and the portion of the UCI multiplexed on the second TB follows the modulation order of the second TB.

[0198] Clause 23: The method of clause 21, wherein the decoded bits of the UCI multiplexed on the first TB are rate matched separately from the decoded bits of the UCI multiplexed on the second TB.

[0199] Clause 24: The method of clause 21, wherein: the UCI is multiplexed on the same REs across layers of the first TB and the second TB; and the UCI multiplexed on the first TB is a copy of the UCI multiplexed on the second TB.

[0200] Clause 25: The method of clause 21, wherein: a first set of decoded bits of the UCI are multiplexed on the first TB; and a second set of decoded bits of the UCI are multiplexed on the second TB.

[0201] Clause 26: A method as set out in any of clauses 17 to 25, wherein the determination of how the UE is to multiplex the UCI on the PUSCH is based on a type of the UCI.

[0202] Clause 27: The method of clause 26, wherein: UCI of a first type is multiplexed on each of the first TB and the second TB; and UCI of a second type is multiplexed on the first TB or the second TB.

[0203] Clause 28: The method of clause 26, wherein: UCI of a first type is multiplexed on the first TB; and UCI of a second type is multiplexed on the second TB.

[0204] Clause 29: The method of clause 28, wherein: the UCI is multiplexed on different REs across layers of the first TB and the second TB.

[0205] Clause 30: The method of clause 28, wherein: the UCI is multiplexed on the same RE across layers of the first TB and the second TB.

[0206] Clause 31: A method as set forth in any of clauses 17 to 30, wherein: the UCI is multiplexed on a first set of REs on the first TB; and data in the PUSCH is mapped to REs in the second TB corresponding to the first set of REs.

[0207] Clause 32: A method as set forth in any of clauses 17 to 31, wherein: the UCI is multiplexed on a first set of REs on the first TB; and data in the PUSCH is not mapped to REs in the second TB corresponding to the first set of REs.

[0208] Clause 33: An apparatus, the apparatus comprising: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method according to any one of clauses 1 to 32.

[0209] Clause 34: An apparatus comprising means for performing the method of any of clauses 1 to 32.

[0210] Clause 35: A non-transitory computer readable medium comprising executable instructions which, when executed by a processor of an apparatus, cause the apparatus to perform the method of any one of clauses 1 to 32.

[0211] Clause 36: A computer program product embodied on a computer readable storage medium, the computer program product comprising code for performing the method according to any of clauses 1 to 32.

[0212] Additional considerations

[0213] The foregoing description is provided to enable any person skilled in the art to practice the various aspects described herein. The examples discussed herein do not limit the scope, applicability or aspects set forth in the claims. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Each example may ignore, replace or add each process or component as appropriate. For example, the described method may be performed in an order different from the described order, and various actions may be added, omitted or combined. In addition, the features described for 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, functions, or structures and functions that are supplemented or substituted for the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the disclosure disclosed herein may be embodied by one or more elements of the claims.

[0214] The various illustrative logic blocks, modules, and circuits described in conjunction with the present disclosure may be implemented or executed using a general purpose processor, a digital signal processor (DSP), an 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 an 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, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, a system on a chip (SoC), or any other such configuration.

[0215] 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). For 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).

[0216] 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. Moreover, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), and the like. In addition, "determining" may include resolving, selecting, choosing, establishing, and the like.

[0217] The method disclosed herein includes one or more actions for implementing the method. The method actions can be interchangeable with each other without departing from the scope of the claims. In other words, unless a specific order of actions is specified, the order and / or use of specific actions can be modified without departing from the scope of the claims. In addition, the various operations of the method described above can be performed by any appropriate component that can perform the corresponding function. The component may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors.

[0218] The following 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. Within the claims, unless otherwise specified, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specifically stated, the term "some" refers to one or more. Any claim element is not interpreted according to the provisions of 35 U.S.C. § 112 (f) unless the element is explicitly stated using the phrase "member for...". All structural and functional equivalents of the elements of the various aspects described throughout the present disclosure that are known or will be known later to a person of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, regardless of whether such disclosure is explicitly cited in the claims, anything disclosed herein is not intended to be disclosed to the public.

Claims

1. A method for wireless communication, the method include: receiving signaling scheduling a physical uplink shared channel (PUSCH) having at least a first transport block (TB) and a second TB, wherein the first TB and the second TB have separate transmission parameters; determining how to multiplex uplink control information (UCI) on the PUSCH; as well as The PUSCH with the UCI multiplexed on the PUSCH is transmitted according to the determination. 2 . The method of claim 1 , wherein the UCI is multiplexed on one of the first TB or the second TB.

3. The method of claim 2, wherein the UCI is multiplexed on any of: said TB having a higher modulation and coding scheme (MCS); or In the case where the MCS of the first TB and the second TB are the same, then the first TB.

4. The method according to claim 2, wherein the modulation order of the UCI follows: a modulation order of the first TB multiplexed on the first TB based on the UCI; or A modulation order of the second TB multiplexed on the second TB based on the UCI.

5. The method according to claim 1, in: At least a portion of the UCI is multiplexed on each of the first TB and the second TB. 6 . The method of claim 5 , wherein a modulation order of the UCI multiplexed on the first TB follows a modulation order of the first TB, and the UCI multiplexed on the second TB follows a modulation order of the second TB. 7 . The method according to claim 5 , wherein the decoded bits of the UCI multiplexed on the first TB and the decoded bits of the UCI multiplexed on the second TB are rate matched separately.

8. The method according to claim 5, in: The UCI is multiplexed on the same resource element (RE) across layers of the first TB and the second TB; and The UCI multiplexed on the first TB is a copy of the UCI multiplexed on the second TB.

9. The method according to claim 5, in: A first group of decoded bits of the UCI is multiplexed on the first TB; and The second group of decoded bits of the UCI are multiplexed on the second TB.

10. The method of claim 1, wherein the determination of how to multiplex the UCI on the PUSCH is based on a type of the UCI.

11. The method according to claim 10, in: UCI of a first type is multiplexed on each of the first TB and the second TB; and The second type of UCI is multiplexed on the first TB or the second TB.

12. The method according to claim 10, in: UCI of the first type is multiplexed on the first TB; and The second type of UCI is multiplexed on the second TB. 13 . The method of claim 12 , wherein the UCI is multiplexed on different resource elements (REs) across layers of the first TB and the second TB. 14 . The method of claim 12 , wherein the UCI is multiplexed on the same resource element (RE) across layers of the first TB and the second TB.

15. The method according to claim 1, in: The UCI is multiplexed on the first TB on a first set of resource elements (REs); Data in the PUSCH is not mapped to the first group of REs on the first TB; and The data in the PUSCH is mapped to REs corresponding to the first group of REs in the second TB.

16. The method according to claim 1, in: The UCI is multiplexed on the first TB on a first set of resource elements (REs); Data in the PUSCH is not mapped to the first group of REs on the first TB; and The data in the PUSCH is not mapped to REs corresponding to the first group of REs in the second TB.

17. A method for wireless communication by a network entity, the method include: transmitting signaling for a user equipment (UE) scheduling a physical uplink shared channel (PUSCH) for at least a first transport block (TB) and a second TB, wherein the first TB and the second TB have separate transmission parameters; determining how the UE will multiplex uplink control information (UCI) on the PUSCH; as well as The PUSCH on which the UCI is multiplexed is monitored according to the determination. The method of claim 17 , wherein UCI is multiplexed on one of the first TB or the second TB.

19. The method of claim 18, wherein the UCI is multiplexed on any of: said TB having a higher modulation and coding scheme (MCS); or In the case where the MCS of the first TB and the second TB are the same, then the first TB.

20. The method according to claim 18, wherein the modulation order of the UCI follows: a modulation order of the first TB multiplexed on the first TB based on the UCI; or A modulation order of the second TB multiplexed on the second TB based on the UCI.

21. The method according to claim 17, in: At least a portion of the UCI is multiplexed on each of the first TB and the second TB.

22. The method of claim 21, wherein a modulation order of the portion of the UCI multiplexed on the first TB follows a modulation order of the first TB, and the portion of the UCI multiplexed on the second TB follows a modulation order of the second TB. 23 . The method according to claim 21 , wherein the decoded bits of the UCI multiplexed on the first TB and the decoded bits of the UCI multiplexed on the second TB are rate matched separately.

24. The method according to claim 21, in: The UCI is multiplexed on the same resource element (RE) across layers of the first TB and the second TB; and The UCI multiplexed on the first TB is a copy of the UCI multiplexed on the second TB.

25. The method according to claim 21, in: A first group of decoded bits of the UCI is multiplexed on the first TB; and The second group of decoded bits of the UCI are multiplexed on the second TB.

26. The method of claim 17, wherein the determination of how the UE will multiplex the UCI on the PUSCH is based on a type of the UCI.

27. The method according to claim 26, in: UCI of a first type is multiplexed on each of the first TB and the second TB; and The second type of UCI is multiplexed on the first TB or the second TB.

28. The method according to claim 26, in: UCI of the first type is multiplexed on the first TB; and The second type of UCI is multiplexed on the second TB. 29 . The method of claim 28 , wherein the UCI is multiplexed on different resource elements (REs) across layers of the first TB and the second TB.

30. The method of claim 28, wherein the UCI is multiplexed on the same resource element (RE) across layers of the first TB and the second TB.

31. The method according to claim 17, in: The UCI is multiplexed on the first TB on a first set of resource elements (REs); Data in the PUSCH is not mapped to the first group of REs on the first TB; and The data in the PUSCH is mapped to REs corresponding to the first group of REs in the second TB.

32. The method according to claim 17, in: The UCI is multiplexed on the first TB on a first set of resource elements (REs); Data in the PUSCH is not mapped to the first group of REs on the first TB; and The data in the PUSCH is not mapped to REs corresponding to the first group of REs in the second TB.

33. A device, the device include: a memory including executable instructions; and a processor configured to execute the executable instructions and cause the apparatus to perform the method according to any one of claims 1 to 32.

34. An apparatus comprising means for performing the method according to any one of claims 1 to 32.

35. A non-transitory computer readable medium comprising executable instructions which, when executed by a processor of a device, cause the device to perform the method of any one of claims 1 to 32.

36. A computer program product embodied on a computer readable storage medium, the computer program product comprising code for performing the method according to any one of claims 1 to 32.