Resource allocation for multi-panel simultaneous PUSCH transmission

Abstract

Methods and apparatus for using a single downlink control information (DCI) and supporting simultaneous transmission of a simultaneous physical uplink shared channel (PUSCH) using multiple user equipment (UE) antenna panels are described. In some embodiments, a baseband processor is configured to perform operations including receiving RRC configuration information from a base station, where the RRC configuration information includes an uplink transmission scheme using a plurality of antenna panels for simultaneously transmitting a plurality of PUSCHs using a plurality of UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes transmission of a single transport block (TB) without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on user equipment (UE) capabilities; receiving a single downlink control information (DCI) specifying an uplink resource allocation for a plurality of physical uplink shared channels (PUSCHs); and transmitting the plurality of PUSCHs.

Description

Technical Field

[0001] The present invention relates generally to wireless technologies, and more particularly to performing resource allocation for multi-panel simultaneous transmission of multiple physical uplink shared channels (PUSCHs). Background Art

[0002] The fifth generation of mobile networks (5G) is a wireless standard that aims to improve data transmission speed, reliability, availability, etc. This standard, while still under development, includes many details related to various aspects of wireless communications, such as NR and NR in spectrum greater than 52.6 GHz. Summary of the invention

[0003] Methods and apparatus for using a single downlink control information (DCI) and supporting simultaneous transmission of a simultaneous physical uplink shared channel (PUSCH) using multiple user equipment (UE) antenna panels are described. In some embodiments, a baseband processor is configured to perform operations including: receiving RRC configuration information from a base station, wherein the RRC configuration information includes an uplink transmission scheme using multiple antenna panels for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes transmission of a single transport block (TB) without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on user equipment (UE) capabilities; receiving a single downlink control information (DCI) specifying uplink resource allocations for multiple physical uplink shared channels (PUSCHs); and transmitting the multiple PUSCHs.

[0004] In some embodiments, a base station includes a processor (or processing circuit) configured to perform operations, the operations including: transmitting RRC configuration information, wherein the RRC configuration information includes an uplink transmission scheme using multiple antenna panels for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes transmission of a single transport block (TB) without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on user equipment (UE) capabilities; generating a single downlink control information (DCI) specifying uplink resource allocation for multiple physical uplink shared channels (PUSCHs); and sending the single DCI to the UE.

[0005] Other methods and apparatus are also described. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] The present invention is illustrated by way of example and not limitation in the figures of the accompanying drawings in which like references indicate similar elements.

[0007] Figure 1 An exemplary wireless communication system according to some embodiments is illustrated.

[0008] Figure 2 A base station (BS) in communication with a user equipment (UE) device is illustrated according to some embodiments.

[0009] Figure 3 An exemplary block diagram of a UE according to some embodiments is illustrated.

[0010] Figure 4 An exemplary block diagram of a BS according to some embodiments is illustrated.

[0011] Figure 5 An exemplary block diagram of cellular communication circuitry according to some embodiments is illustrated.

[0012] Fig. 6A A data flow diagram illustrating some embodiments for supporting single downlink control information (DCI) resource allocation for simultaneous transmission by multiple panels of multiple physical uplink shared channels (PUSCHs) of a UE.

[0013] Figure 6B Examples of PUSCHs having completely overlapping frequency resources allocated to PUSCHs to be simultaneously transmitted, non-overlapping frequency resources allocated to PUSCHs to be simultaneously transmitted, and partially overlapping frequency resources allocated to PUSCHs to be simultaneously transmitted are illustrated.

[0014] Fig. 7A and Figure 7B An example of a PUSCH used for the first transmission scheme is illustrated.

[0015] Fig. 8A and Figure 8B An example of the second transmission scheme is illustrated.

[0016] Fig.9A and Fig. 9B An example of the third transmission scheme is illustrated.

[0017] Fig. 10A An example of a mapping scheme for a third transmission scheme is illustrated, and Fig. 10B An example of a mapping scheme for the third transmission scheme is illustrated.

[0018] Fig.11A and Fig. 11B An example of PUSCH mapping for each repetition when two PUSCH transmissions (eg, PUSCH1 and PUSCH2) of the same TB are simultaneously transmitted on a multi-panel is illustrated.

[0019] Fig. 12A and Fig. 12BAn example of PUSCH mapping for each repetition when two PUSCH transmission chains for two PUSCHs (eg, PUSCH1 and PUSCH2) for the same TB are simultaneously transmitted on multiple UE antenna panels is illustrated.

[0020] Fig.13 An example of frequency hopping for multi-panel simultaneous transmission involving transmission of a single TB with repetitions is illustrated.

[0021] Fig.14 is a flow chart of some implementations of a process for configuring a UE.

[0022] Fig.15 is a flow chart of some embodiments of a process by which network equipment configures a UE. DETAILED DESCRIPTION

[0023] Methods and apparatus for performing resource allocation for multiple panels of multiple physical uplink shared channels (PUSCHs) simultaneously transmitted using a single downlink control information (DCI) are described. In the following description, numerous specific details are set forth to provide a thorough explanation of the embodiments of the present invention. However, it is apparent to those skilled in the art that the embodiments of the present invention may be implemented without these specific details. In other instances, well-known components, structures, and techniques have not been shown in detail to avoid obscuring the understanding of this description.

[0024] Reference to "one embodiment" or "embodiment" in this specification means that a particular feature, structure or characteristic described in conjunction with the embodiment can be included in at least one embodiment of the present invention. The phrase "in one embodiment" appearing in various places in this specification does not necessarily refer to the same embodiment.

[0025] In the following description and claims, the terms "coupled" and "connected" and their derivatives may be used. It should be understood that these terms are not intended to be synonymous with each other. "Coupled" is used to indicate that two or more elements that may or may not be in direct physical or electrical contact with each other cooperate or interact with each other. "Connected" is used to indicate the establishment of communication between two or more elements that are coupled to each other.

[0026] The processes shown in the following figures are performed by processing logic, which includes hardware (e.g., circuits, dedicated logic, etc.), software (such as software running on a general-purpose computer system or a dedicated machine), or a combination of both. Although the following describes these processes as certain sequential operations, it should be understood that certain operations described may be performed in a different order. In addition, certain operations may also be performed in parallel rather than in sequence.

[0027] The terms "server," "client," and "device" are intended to refer generally to data processing systems rather than specifically to a particular form factor of a server, client, and / or device.

[0028] Methods and apparatus for devices that perform resource allocation for multi-panel simultaneous transmission of multiple physical uplink shared channels (PUSCHs) using a single downlink control information (DCI) are described. In some embodiments, the device is a user equipment device having a wireless link with a base station. In one embodiment, the wireless link is a fifth generation (5G) link.

[0029] Figure 1 A simplified exemplary wireless communication system according to some embodiments is illustrated. Note that Figure 1 The system is only one example of possible systems, and features of the present disclosure may be implemented in any of a variety of systems as desired.

[0030] As shown, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipment 106A, user equipment 106B to user equipment 106N, etc. through a transmission medium. Each user equipment in the user equipment may be referred to as a "user equipment" (UE) in this document. Therefore, user equipment 106 is referred to as a UE or UE device.

[0031] The base station (BS) 102A may be a base transceiver station (BTS) or a cell site ("cellular base station"), and may include hardware that enables wireless communications with the UEs 106A-106N.

[0032] The communication area (or coverage area) of a base station may be referred to as a "cell". The base station 102A and the UE 106 may be configured to communicate over a transmission medium using any of a variety of radio access technologies (RATs), also referred to as wireless communication technologies or telecommunication standards, such as GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, Advanced LTE (LTE-A), 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), and the like. Note that if the base station 102A is implemented in the context of LTE, it may alternatively be referred to as an "eNodeB" or "eNB". Note that if the base station 102A is implemented in the context of 5G NR, it may alternatively be referred to as a "gNodeB" or "gNB".

[0033] As shown, base station 102A may also be configured to communicate with network 100 (e.g., a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN), and / or the Internet, among other possibilities). Thus, base station 102A may facilitate communications between user devices and / or between user devices and network 100. Specifically, cellular base station 102A may provide UE 106 with various communication capabilities, such as voice, SMS, and / or data services.

[0034] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore provide a network as a cell that can provide continuous or nearly continuous overlapping service to UEs 106A-N and similar devices over a geographic area via one or more cellular communication standards.

[0035] Thus, although base station 102A may function as Figure 1 106A-N, but each UE 106 may also be able to receive signals from (and possibly be within communication range of) one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells". Such cells may also be able to facilitate communications between user devices and / or between user devices and network 100. Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells of any various other granularity of service area size. For example, in Figure 1 The base stations 102A-B illustrated in FIG. 1 may be macro cells, while the base station 102N may be a micro cell. Other configurations are also possible.

[0036] In some embodiments, base station 102A may be a next generation base station, e.g., a 5G New Radio (5G NR) base station or "gNB". In some embodiments, a gNB may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. In addition, a gNB cell may include one or more transition and reception points (TRPs). In addition, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0037] Note that the UE 106 is capable of communicating using multiple wireless communication standards. For example, the UE 106 may be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). If desired, the UE 106 may also or alternatively be configured to communicate using one or more global navigation satellite systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcast standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocols. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.

[0038] Figure 2 A user equipment 106 (eg, one of devices 106A-106N) is illustrated in accordance with some embodiments in communication with a base station 102. The UE 106 may be a device with cellular communication capabilities, such as a mobile phone, handheld device, computer or tablet computer, or virtually any type of wireless device.

[0039] UE 106 may include a processor configured to execute program instructions stored in a memory. UE 106 may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or in addition, UE 106 may include a programmable hardware element, such as a field programmable gate array (FPGA) configured to perform any of the method embodiments described herein or any part of any of the method embodiments described herein.

[0040] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT, 1xEV-DO, HRPD, eHRPD) or LTE using a single shared radio component and / or GSM or LTE using a single shared radio component. The shared radio component may be coupled to a single antenna, or may be coupled to multiple antennas (e.g., for MIMO) for performing wireless communications. Typically, the radio component may include any combination of a baseband processor, an analog RF signal processing circuit (e.g., including filters, mixers, oscillators, amplifiers, etc.), or a digital processing circuit (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of a receive chain and / or a transmit chain between multiple wireless communication technologies such as those discussed above.

[0041] In some embodiments, UE 106 may include a separate transmit chain and / or receive chain (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate with it. As another possibility, UE 106 may include one or more radio components shared between multiple wireless communication protocols, and one or more radio components used uniquely by a single wireless communication protocol. For example, UE 106 may include a shared radio component for communicating using either LTE or 5GNR (or LTE or 1xRTT, or LTE or GSM), and a separate radio component for communicating using each of Wi-Fi and Bluetooth. Other configurations are also possible.

[0042] Figure 3 —UE block diagram

[0043] Figure 3 An exemplary simplified block diagram of a communication device 106 according to some embodiments is illustrated. Note that Figure 3The block diagram of the communication device is only an example of a possible communication device. According to an embodiment, the communication device 106 can be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, a notebook or a portable computing device), a tablet computer and / or a combination of devices, in addition to other devices. As shown, the communication device 106 may include a group of components 300 configured to perform core functions. For example, the group of components can be implemented as a system on a chip (SOC), which can include parts for various purposes. Alternatively, the group of components 300 can be implemented as a separate component or group of components for various purposes. This group of components 300 can be coupled to various other circuits of the communication device 106 (e.g., communicatively; directly or indirectly).

[0044] For example, the communication device 106 may include various types of memory (e.g., including NAND flash memory 310), input / output interfaces such as a connector I / F 320 (e.g., for connecting to a computer system; a docking station; a charging station; an input device such as a microphone, a camera, a keyboard; an output device such as a speaker; etc.), a display 360 that may be integrated with the communication device 106 or external to the communication device, and cellular communication circuits 330 such as for 5G NR, LTE, GSM, etc., and short-range to medium-range wireless communication circuits 329 (e.g., Bluetooth ™ and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

[0045] Cellular communication circuitry 330 may be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 335 and 336 as shown. Short-range to medium-range wireless communication circuitry 329 may also be (e.g., communicatively; directly or indirectly) coupled to one or more antennas, such as antennas 337 and 338 as shown. Alternatively, short-range to medium-range wireless communication circuitry 329 may be (e.g., communicatively; directly or indirectly) coupled to antennas 335 and 336 in addition to or in lieu of being (e.g., communicatively; directly or indirectly) coupled to antennas 337 and 338. Short-range to medium-range wireless communication circuitry 329 and / or cellular communication circuitry 330 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration.

[0046] In some embodiments, as further described below, the cellular communication circuit 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). In addition, in some embodiments, the cellular communication circuit 330 may include a single transmit chain that can switch between radio components dedicated to specific RATs. For example, a first radio component can be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with an additional radio component, such as a second radio component that can be dedicated to a second RAT (e.g., 5G NR) and can communicate with the dedicated receive chain and the shared transmit chain.

[0047] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface elements may include various elements such as a display 360 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of a touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other elements capable of providing information to a user and / or receiving or interpreting user input.

[0048] The communication device 106 may also include one or more smart cards 345 having SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (Universal Integrated Circuit Cards) 345 .

[0049] As shown, the SOC 300 may include a processor 302 that may execute program instructions for the communication device 106 and a display circuit 304 that may perform graphics processing and provide display signals to a display 360. The processor 302 may also be coupled to a memory management unit (MMU) 340 (which may be configured to receive addresses from the processor 302 and convert those addresses to locations in a memory (e.g., memory 306, read-only memory (ROM) 350, NAND flash memory 310)) and / or to other circuits or devices (such as display circuit 304, short-range wireless communication circuit 229, cellular communication circuit 330, connector I / F 320, and / or display 360). The MMU 340 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 340 may be included as part of the processor 302.

[0050] As described above, the communication device 106 may be configured to communicate using wireless and / or wired communication circuits. The communication device 106 may be configured to receive configuration information from a base station, wherein the configuration information includes a single downlink control information (DCI) that specifies uplink resource allocations for multiple physical uplink shared channels (PUSCHs), and each user equipment (UE) antenna panel specifies uplink resource allocations for multiple PUSCHs. The wireless device may also be configured to simultaneously send information about multiple PUSCHs via multiple antenna panels based on the configuration information in the single DCI, wherein one of the multiple PUSCHs is sent on a different PUSCH in the multiple PUSCHs.

[0051] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features for time-division multiplexing UL data for NSA NR operation. The processor 302 of the communication device 106 may be configured to implement some or all of the features described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively (or in addition), the processor 302 may be configured as a programmable hardware element, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement some or all of the features described herein.

[0052] In addition, as described in the present invention, the processor 302 may include one or more processing elements. Therefore, the processor 302 may include one or more integrated circuits (ICs) configured to perform the functions of the processor 302. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 302.

[0053] In addition, as described herein, both the cellular communication circuit 330 and the short-range wireless communication circuit 329 may include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 330, and similarly, one or more processing elements may be included in the short-range wireless communication circuit 329. Therefore, the cellular communication circuit 330 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 330. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 230. Similarly, the short-range wireless communication circuit 329 may include one or more ICs configured to perform the functions of the short-range wireless communication circuit 32. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-range wireless communication circuit 329.

[0054] Figure 4 —Block diagram of a base station

[0055] Figure 4 An exemplary block diagram of a base station 102 according to some embodiments is illustrated. Note that Figure 4 The base station of is only one example of a possible base station. As shown, the base station 102 may include a processor 404 that may execute program instructions for the base station 102. The processor 404 may also be coupled to a memory management unit (MMU) 440 or other circuit or device, which may be configured to receive addresses from the processor 404 and convert these addresses to locations in memory (e.g., memory 460 and read-only memory (ROM) 450).

[0056] Base station 102 may include at least one network port 470. Network port 470 may be configured to couple to a telephone network and provide access to the telephone network described above. Figure 1 and Figure 2 Multiple devices of the telephone network described in, such as UE device 106.

[0057] The network port 470 (or an additional network port) may also or alternatively be configured to couple to a cellular network, such as a core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as the UE device 106. In some cases, the network port 470 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).

[0058] In some embodiments, base station 102 may be a next generation base station, e.g., a 5G New Radio (5G NR) base station, or "gNB". In such embodiments, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and reception points (TRPs). Furthermore, a UE capable of operating in accordance with 5G NR may be connected to one or more TRPs within one or more gNBs.

[0059] The base station 102 may include at least one antenna 434 and possibly multiple antennas. The at least one antenna 434 may be configured to function as a wireless transceiver and may be further configured to communicate with the UE device 106 via the radio component 430. The antenna 434 communicates with the radio component 430 via a communication chain 432. The communication chain 432 may be a receive chain, a transmit chain, or both. The radio component 430 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, and the like.

[0060] The base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some instances, the base station 102 may include multiple radio components that enable the base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station 102 may include an LTE radio component for performing communications according to LTE and a 5G NR radio component for performing communications according to 5G NR. In this case, the base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, the base station 102 may include a multimode radio component that can perform communications according to any of a plurality of wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

[0061] As further described later herein, BS 102 may include hardware and software components for implementing or supporting a specific implementation of the features described herein. The processor 404 of base station 102 may be configured to implement or support a specific implementation of part or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 404 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit) or a combination thereof. Alternatively (or in addition), in combination with one or more of other components 430, component 432, component 434, component 440, component 450, component 460, component 470, processor 404 of BS 102 may be configured to implement or support a specific implementation of part or all of the features described herein.

[0062] In addition, as described herein, processor 404 may be composed of one or more processing elements. In other words, one or more processing elements may be included in processor 404. Therefore, processor 404 may include one or more integrated circuits (ICs) configured to perform the functions of processor 404. In addition, each integrated circuit may include circuits (e.g., first circuits, second circuits, etc.) configured to perform the functions of one or more processors 404.

[0063] Additionally, as described herein, radio 430 may be comprised of one or more processing elements. In other words, one or more processing elements may be included in radio 430. Thus, radio 430 may include one or more integrated circuits (ICs) configured to perform the functions of radio 430. Furthermore, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio 430.

[0064] Figure 5 : Block diagram of a cellular communication circuit

[0065] Figure 5 An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is illustrated. Note that Figure 5 The block diagram of the cellular communication circuitry of is only one example of possible cellular communication circuitry. According to an embodiment, the cellular communication circuitry 330 may be included in a communication device such as the communication device 106 described above. As described above, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of devices, among other devices.

[0066] Cellular communication circuitry 330 may be (eg, communicatively; directly or indirectly) coupled to one or more antennas, such as ( Figure 3 In some embodiments, the cellular communication circuit 330 may include dedicated receive chains (including and / or coupled to (e.g., communicatively; directly or indirectly) dedicated processors and / or radio components) for multiple RATs (e.g., a first receive chain for LTE and a second receive chain for 5G NR). For example, Figure 5 As shown, cellular communication circuitry 330 may include modem 510 and modem 520. Modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and modem 520 may be configured for communication according to a second RAT (e.g., such as 5G NR).

[0067] As shown, the modem 510 may include one or more processors 512 and a memory 516 in communication with the processor 512. The modem 510 may communicate with a radio frequency (RF) front end 530. The RF front end 530 may include circuits for sending and receiving radio signals. For example, the RF front end 530 may include a receiving circuit (RX) 532 and a transmitting circuit (TX) 534. In some embodiments, the receiving circuit 532 may communicate with a downlink (DL) front end 550, which may include circuits for receiving radio signals via an antenna 335a.

[0068] Similarly, the modem 520 may include one or more processors 522 and a memory 526 in communication with the processor 522. The modem 520 may communicate with the RF front end 540. The RF front end 540 may include circuits for sending and receiving radio signals. For example, the RF front end 540 may include a receiving circuit 542 and a transmitting circuit 544. In some embodiments, the receiving circuit 542 may communicate with the DL front end 560, which may include circuits for receiving radio signals via the antenna 335b.

[0069] In some embodiments, the switch 570 may couple the transmit circuit 534 to an uplink (UL) front end 572. In addition, the switch 570 may couple the transmit circuit 544 to the UL front end 572. The UL front end 572 may include circuitry for transmitting radio signals via the antenna 336. Thus, when the cellular communication circuit 330 receives an instruction to transmit according to a first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572) supported by the modem 510, the switch 570 may be switched to a first state that allows the modem 510 to transmit signals according to the first RAT (e.g., via a transmit chain including the transmit circuit 534 and the UL front end 572). Similarly, when the cellular communication circuit 330 receives an instruction to transmit according to a second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572) supported by the modem 520, the switch 570 may be switched to a second state that allows the modem 520 to transmit signals according to the second RAT (e.g., via a transmit chain including the transmit circuit 544 and the UL front end 572).

[0070] As described herein, the modem 510 may include hardware components and software components for implementing the above-described features or for performing resource allocation for multi-panel simultaneous transmission of multiple PUSCHs using a single DCI, as well as various other techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 512 may be configured to implement some or all of the features described herein. Alternatively (or in addition), the processor 512 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 530, 532, 534, 550, 570, 572, 335, and 336, the processor 512 may be configured to implement some or all of the feature parts described herein.

[0071] In addition, as described herein, processor 512 may include one or more processing elements. Thus, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. In addition, each integrated circuit may include circuits (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.

[0072] As described herein, the modem 520 may include hardware components and software components for implementing the above-described features for performing resource allocation for multi-panel simultaneous transmission of multiple PUSCHs using a single DCI, as well as various other techniques described herein. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 522 may be configured to implement part or all of the feature parts described herein. Alternatively (or in addition), the processor 522 may be configured as a programmable hardware element such as an FPGA (field programmable gate array), or as an ASIC (application-specific integrated circuit). Alternatively (or in addition), in combination with one or more of the other components 540, 542, 544, 550, 570, 572, 335, and 336, the processor 522 may be configured to implement part or all of the feature parts described herein.

[0073] In addition, as described herein, the processor 522 may include one or more processing elements. Thus, the processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of the processor 522. In addition, each integrated circuit may include a circuit (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the processor 522.

[0074] Single DCI and indication of simultaneous transmission of multiple panels for PUSCH

[0075] In some embodiments, the techniques described herein are used to perform resource allocation to signal resources to a UE to enable the UE to transmit multiple PUSCHs simultaneously using multiple antenna panels of the UE. In some embodiments, resource allocation is performed by a base station (e.g., a gNB) using a single DCI.

[0076] In NR Release 16, the NR standard specifies simultaneous physical downlink shared channel (PDSCH) reception for multiple transmit and receive points (TRPs). In this case, PDSCH resources associated with different downlink (DL) beams (spatial Rx filters) are transmitted via frequency division multiplexing (FDM) if scheduled by a single DCI. As stated in 3GPP TS 38.214 Section 5.1, the UE is indicated using two transmit configuration indication (TCI) states in the code point of the DCI field "Transmit Configuration Indication" and a demodulation reference signal (DM-RS) port within one code division multiplexing (CDM) group in the DCI field "Antenna Port". When the UE is set to "fdmSchemeA", the UE shall receive a single PDSCH transmission opportunity for a transport block (TB), where each TCI state is associated with a non-overlapping frequency domain resource allocation. When the UE is set to "fdmSchemeB", the UE shall receive two PDSCH transmission opportunities for the same TB, where each TCI state is associated with a PDSCH transmission opportunity with non-overlapping frequency domain resource allocation. If multiple DCIs called multi-DCI (m-DCI) are used for scheduling, the two PDSCH receptions can be fully overlapping / partially overlapping / non-overlapping PDSCHs in the time domain and frequency domain. In this case, the PDCCH scheduling the two PDSCHs is associated with different ControlResourceSets with different coresetPoolIndex values.

[0077] In NR Release 17, a UE can send multiple repetitions of the same TB on different uplink (UL) beams, where the repetitions are sent using time division multiplexing (TDM). That is, there is beam hopping, but the beam hopping is for TDM. In order to send multiple repetitions of the same TB on different UL beams, when the UE is configured for two sounding reference signal (SRS) resource sets used as codebook (or two SRS resource sets used as non-codebook), a beam indication is provided through an extended status report indication (SRI) bit field (done by the UE). In addition, when multiple repetitions are sent on different UL beams, all repetitions have the same rank (number of layers), although the repetitions on different beams can have different antenna ports, transmitted precoding matrix indicators (TPMI) (for code block (CB) based transmissions), transmit power control (TPC), etc. In other words, the repetitions do not occur in time; they occur in different time slots.

[0078] In NR Release 16 and Release 17, simultaneous PUSCH transmission is not supported (neither spatial division multiplexing (SDM) nor frequency division multiplexing (FDM).

[0079] In NR Release 18, one of the goals is to study and, if necessary, specify simultaneous multi-panel UL transmissions, including considering the use of multi-TRP operation based on single DCI and multiple DCI to provide UL precoding indication for PUSCH and considering the use of multi-TRP operation based on single DCI and multiple DCI to provide UL beam indication for PUCCH / PUSCH.

[0080] In some embodiments, the UE is configured to perform transmission of multiple PUSCHs simultaneously using multiple antenna panels on the UE. This is referred to herein as multi-panel simultaneous PUSCH. In some embodiments, the multiple PUSCH transmissions include two PUSCH transmissions, one PUSCH from one antenna on the UE and another PUSCH from another antenna on the UE, where both UE antennas are part of a multi-panel antenna. Configuration information for configuring the UE to perform multi-panel simultaneous transmission of multiple PUSCHs is transmitted from a base station.

[0081] In some embodiments, information is transmitted from the base station to the UE using a single DCI (s-DCI) that specifies the transmission scheme to be used by the UE. In some embodiments, the single DCI includes resource information corresponding to the resource allocation to indicate to the UE the resources to be used for PUSCH transmission. The determination of the resource allocation is made by the base station. In some embodiments, the base station determines the resource allocation based on the UE capabilities. The UE capabilities may be provided by the UE.

[0082] In some embodiments, resource allocation is performed in frequency and / or space for multiple different situations. For example, in one case, resource allocation specifies resources for sending a single PUSCH opportunity on different panels. In other words, resources are designated for sending a single TB (i.e., the same data) simultaneously on different UE antenna panels. Note that in some embodiments, the transmission of a single TB on different UE antenna panels involves sending different encoded bits from the same TB on different panels. In some other embodiments, the transmission of a single TB on different UE antenna panels involves sending the same data on different panels. For example, the same data can be modulated differently and its transmission is repeated so that one data passes through layer 1 and the other data passes through layer 2, where layer 1 is sent by the first antenna panel and layer 2 is sent by the second antenna panel. Such transmission will improve diversity.

[0083] In another case, the resource allocation specifies resources for performing repetition of the same TB on different panels. In this instance, the data transmitted by each antenna panel is different. In a third case, the resource allocation specifies resources for performing simultaneous PUSCH transmission of two different TBs. In some embodiments, this involves transmitting two different codewords.

[0084] Therefore, in some embodiments, a combination of higher layer parameters and dynamically indicating resource allocations for handling one of the above cases is used to indicate resource allocations to the UE via a single DCI. In some embodiments, the base station first determines the transmission scheme (e.g., SDM, FDM, etc.) that the UE wants to use for multiple PUSCH transmissions, and then after determining the transmission scheme (e.g., SDM, FDM, etc.), the base station determines whether the multiple simultaneous PUSCH transmissions are for transmitting a single TB, multiple TBs, or repeated. These resources can be determined by the base station based on the UE capabilities.

[0085] After providing resource allocation, a determination is made as to the UL beam to be used by the UE for transmission of multiple PUSCHs on different panels. Fig. 6A A data flow diagram illustrating some embodiments for supporting a single downlink control information (DCI) resource allocation for simultaneous transmission of multiple panels of multiple physical uplink shared channels (PUSCHs) by a UE. Fig. 6A , base station 601 sends a single DCI to UE 602. In some embodiments, the single DCI is sent as part of PDCCH 610. The single DCI contains uplink resource allocations for resources to be used by UE 602 to send multiple PUSCHs on different panels. In response to the single DCI with the uplink resource allocations, UE 602 sends user data 611 to base station 601 using its antenna panel 1, sends user data 612 to base station 601 using its antenna panel 2, ..., sends user data 613 to base station 601 using its antenna panel N. In some embodiments, user data 611-613 are sent simultaneously by UE 602 using PUSCH. Although Fig. 6A It is shown that N panels are used by UE 602 to send PUCSH simultaneously, but in some embodiments, UE 602 uses only two antenna panels to send two PUSCHs simultaneously. In addition, in some other embodiments, multiple PUCSCHs are sent to two base stations simultaneously, where one PUCSH is sent to base station 601 and another PUSCH is sent to another base station.

[0086] In the following descriptions, the following terms may be used:

[0087] 1.s-DCI: Single DCI

[0088] 2.MPSTx: Multi-panel simultaneous transmission, where the UE transmits on multiple antenna panels in its antenna panel

[0089] 3.sdmMPTx: Multi-panel simultaneous transmission, where the UE transmits on multiple antenna panels in its antenna panel using spatial domain multiplexing

[0090] 4.fdmMPTx: Multi-panel simultaneous transmission, where the UE uses frequency domain multiplexing to transmit on multiple antenna panels in its antenna panel

[0091] 5.1sMPTx: Single (no repetition) transmission of a single transport block (TB) transmitted simultaneously over multiple panels (e.g., a UE transmits one TB without repetition over multiple antenna panels in its antenna panel)

[0092] 6. ReMPTx: Repetition (in frequency and / or space) of a single TB transmitted simultaneously by multiple panels (e.g., a UE transmits a single TB repeatedly on multiple antenna panels in its antenna panels)

[0093] There are a variety of resource allocation schemes that can be used as part of a multi-panel simultaneous transmission for simultaneously transmitting multiple PUSCHs using multiple antenna panels of a UE. Examples of such resource allocation schemes for multi-panel simultaneous transmission are disclosed below. In some embodiments, each of these resource allocation schemes involves allocating resources using a single DCI that specifies uplink resource allocations for multiple physical uplink shared channels (PUSCHs), where the uplink resource allocations for multiple PUSCHs are specified per user equipment (UE) antenna panel.

[0094] In some embodiments, when the UE is configured to perform simultaneous multi-panel transmission on spatial domain multiplexing (SDM) resources, uplink resource allocations for multiple PUSCHs are specified using one or more time domain resource allocation (TDRA) bit fields and frequency domain resource allocation (FDRA) bit fields in a single DCI to represent spatial domain resources.

[0095] More specifically, in some embodiments, for s-DCI, based on or subject to UE capabilities (e.g., the UE indicates its capabilities regarding SDM, FDM, or a combination of the two), if the UE is configured with sdmMPTx parameters (via, for example, RRC configuration information), multi-panel simultaneous transmission is on SDM resources. In this case, the TDRA bit field and the FDRA bit field indicate the resources for each panel, where for SDM multi-panel simultaneous transmission, full resource overlap in time and frequency is assumed. Figure 6B This case is illustrated, where PUSCH1 represents the time resources and frequency resources associated with panel 1, and PUSCH2 represents the time resources and frequency resources associated with panel 2, where one opportunity is sent by panel 1 and one opportunity is sent by panel 2. Therefore, the s-DCI schedules those SDM time resources and frequency resources for both panels.

[0096] In some embodiments, when the UE is configured to perform simultaneous multi-panel transmission on frequency domain multiplexing (FDM) resources or on both FDM resources and SDM resources, uplink resource allocations for multiple PUSCHs are specified using one or more time domain resource allocation (TDRA) bit fields in a single DCI to indicate the time domain resource allocation.

[0097] More specifically, in some embodiments, for s-DCI, based on or subject to UE capabilities (e.g., the UE indicates its capabilities regarding SDM, FDM, or a combination of the two), if the UE is configured with the fdmMPTx parameter (via, for example, RRC configuration information), the multi-panel simultaneous transmission is on FDM resources. In this case, for FDM, the s-DCI includes resource allocations with the same time domain resources for both occasions where two PUSCHs are transmitted simultaneously (e.g., the multi-panel simultaneous transmission is on the same symbol set). In some embodiments, the TDRA bit field in the DCI indicates the time domain resource allocation for all transmissions.

[0098] In some embodiments, when multi-panel simultaneous transmission is on FDM resources, for both resource allocation type 0 and type 1, a new FDRA field in s-DCI is added and used for PUSCH scheduling on the second PUSCH.

[0099] In some embodiments, for resource allocation type 0 and resource allocation type 1 The resource allocation is specified to the UE in the s-DCI differently. Various implementations for specifying resource allocation of resource allocation type 0 and resource allocation type 1 are given below.

[0100] To indicate resource allocation to the UE, for resource allocation type 0 , the resource allocation includes a bitmap indication of RBGs. In this case, there are multiple options that can be used to allocate RBGs. In some embodiments, for resource allocation type 0 in the frequency domain, the uplink resource allocation specified in a single DCI for multiple PUSCHs allocates non-contiguous resource block groups (RBGs) to each of the multiple PUSCHs. In some embodiments, the non-contiguous RBGs allocated to each PUSCH include an even RBG allocated to the first PUSCH and an odd RBG allocated to the second PUSCH. In some embodiments, in the case of a resource allocation consisting of only one RBG (special case), the first half of the RB belongs to PUSCH1 and the second half belongs to PUSCH2, where PUSCH1 represents the time resources and frequency resources associated with panel 1, and PUSCH2 represents the time resources and frequency resources associated with panel 2.

[0101] As another option, in some embodiments, for resource allocation type 0 in the frequency domain, the uplink resource allocation specified in a single DCI for multiple PUSCHs includes a resource block (RB) parameter that indicates the size of consecutive physical resource blocks (PRBs) within the allocated RB assigned to each of the multiple PUSCHs (e.g., PUSCH1, PUSCH2, etc.). In some embodiments, an even-numbered consecutive PRB group within the allocated resource block (RB) is assigned to the first PUSCH, and an odd-numbered consecutive PRB group within the allocated RB is assigned to the second PUSCH.

[0102] In some embodiments, for resource allocation type 0 in the frequency domain, the uplink resource allocation specified in a single DCI for multiple PUSCHs includes a resource block (RB) parameter that indicates the size of consecutive physical resource blocks (PRBs) within the allocated RB assigned to each of the multiple PUSCHs. In some embodiments, an even number of consecutive PRB groups within the allocated resource block (RB) are assigned to the first PUSCH, and an odd number of consecutive PRB groups within the allocated RB are assigned to the second PUSCH. To this end, in some embodiments, a new RRC parameter RB is used in the s-DCI. 束 , which is based on which bandwidth part (BWP) is divided into RBs of size 束 Note that the first and last bundle sizes can be different from RB 束 In some embodiments, for Figure 6B , the even-numbered RBs in the RBs allocated in s-DCI 束 Associated with PUSCH1 and an odd RB within the RBs allocated in s-DCI 束 Associated with PUSCH2

[0103] Note that if the UE indicates that it has both SDM and FDM capabilities, then in some embodiments both the sdmMPTx parameters and the fdmMPTx parameters will be configured and only one configuration will be used.

[0104] In some embodiments, in an uplink resource allocation in a single DCI for multiple PUSCHs for resource allocation type 1 in the frequency domain, the s-DCI specifies an allocation of contiguous PRBs for each PUSCH in the PUSCHs. In some embodiments, for resource allocation type 1, the uplink resource allocation in a single DCI for multiple PUSCHs specifies the number of RBs allocated in the FDRA bit field, and the first half of the RBs are assigned to the first PUSCH and the second half of the RBs are assigned to the second PUSCH. In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation in a single DCI for multiple PUSCHs indicates a resource allocation of contiguous PRBs for a first PUSCH in the multiple PUSCHs in the FDRA bit field, and a resource allocation of the same number of contiguous PRBs for a second PUSCH in the multiple PUSCHs is indicated by an offset relative to the end or start of the resource allocation given by the FDRA bit field. In some embodiments, the FDRA bit field indicates N PRB RBs allocated, where N is rounded up to an integer. PRB / 2) or alternatively round down (N PRB / 2) is assigned to the first PUSCH ( Figure 6B ) and the rest of the RBs belong to the second PUSCH ( Figure 6B ).

[0105] In some embodiments, for resource allocation type 1 in the frequency domain, an uplink resource allocation in a single DCI for multiple PUSCHs indicates a resource allocation of consecutive PRBs for a first PUSCH of the multiple PUSCHs with an RB start position and a number of RBs in a FDRA bit field, and a resource allocation of consecutive PRBs for a second PUSCH of the multiple PUSCHs is indicated by modulo the size of a bandwidth part (BWP) containing consecutive PRBs allocated to the first PUSCH and the second PUSCH relative to an offset from the RB start position allocated for the first PUSCH. In some embodiments, the FDRA bit field indicates the resource allocation associated with the first PUSCH, and the resource allocation for the second PUSCH is correspondingly determined, for example, by an offset from the end (or start) of the first resource allocation given by the FDRA bit field and having the same number of PRBs (in some embodiments) or to the end (or start) of the BWP (in other embodiments).

[0106] In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation in a single DCI for multiple PUSCHs indicates in the FDRA bit field a resource allocation for consecutive PRBs for a first PUSCH of the multiple PUSCHs, and the resource allocation for consecutive PRBs for a second PUSCH of the multiple PUSCHs is indicated by an offset from the end or start of the resource allocation given in the FDRA bit field to the end or start of a bandwidth part (BWP) containing consecutive PRBs allocated to the first PUSCH and the second PUSCH. In some embodiments, the existing process for intra-slot frequency hopping is reused to determine the starting RB for each PUSCH (rather than frequency hopping), as follows: For PUSCH1:

[0107] RB 开始 and L are given by the FDRA bit field, and

[0108] For PUSCH2:

[0109] RB 开始 = (RB 开始 + RB 偏移 ) mod BWP 大小 .

[0110] In some embodiments, for resource allocation type 1 in the frequency domain, an uplink resource allocation in a single DCI for multiple PUSCHs indicates a resource allocation for consecutive PRBs of a first PUSCH of the multiple PUSCHs includes a resource block (RB) parameter indicating a size of consecutive physical resource blocks (PRBs) within the allocated RB assigned to each of the multiple PUSCHs, wherein an even number of consecutive PRBs within the allocated resource block (RB) is assigned to the first PUSCH, and an odd number of consecutive PRBs within the allocated RB is assigned to the second PUSCH. This is the same as the second option of type 0 FDRA.

[0111] Alternatively, in the option where the FDRA bit field indicates the resource allocation associated with the first PUSCH and the resource allocation for the second PUSCH is determined accordingly, for example, by offsetting from the end (or start) of the first resource allocation given by the FDRA bit field, and having the same number of PRBs (in some embodiments) and / or reusing the previous option of the existing process for intra-slot frequency hopping, there are multiple alternatives for those RBs that may overlap in frequency on the two PUSCHs. In some embodiments, the first alternative is that the RBs that overlap in frequency on the two PUSCHs are not available for both PUSCHs (i.e., are discarded). In some other embodiments, the second alternative is that the RBs that overlap in frequency on the two PUSCHs are only used for transmissions by PUSCH1. In some other embodiments, the third alternative is that the RBs that overlap in frequency on the two PUSCHs are based on whether the UE indicates that it can partially overlap transmissions, and if so, those RBs are used for simultaneous transmissions on the two PUSCHs (partially / completely overlapping in frequency). Figure 6B It also shows a situation where there is a partial overlap in the frequency resources allocated to both PUSCH1 and PUSCH2.

[0112] In some embodiments, the uplink resource allocation from the base station is specified based on the UE capability information that the base station has, and the base station is used to allocate resources to the UE to perform the transmission of multiple PUSCHs simultaneously using multiple UE antenna panels (e.g., multiple panels). In some embodiments, the UE capability information is sent via the UE and received by the base station through radio resource control (RRC) signaling or via dynamic signaling. In some embodiments, the base station uses RRC signaling to indicate to the UE the transmission scheme it is to use (e.g., Scheme A, Scheme B, Scheme C, etc.). In some embodiments, the base station uses RRC signaling to indicate to the UE multiple transmission schemes that it can use (e.g., Scheme A, Scheme B, Scheme C, etc.), and then uses DCI to dynamically indicate which of the multiple schemes it is to use at a specific time.

[0113] In some embodiments, the UE capability information used by the base station when allocating uplink resources for multi-panel multi-PUSCH simultaneous transmission specifies one or more of the following items: the number of codewords per PUSCH transmission opportunity, the number of code blocks per PUSCH transmission opportunity, the number of transmission layers scheduled per PUSCH transmission, the number of layers being transmitted when information is transmitted on multiple PUSCHs simultaneously, the maximum modulation order, and the transmission scheme. In some embodiments, the UE capability information specifies a combination of two or more of the above information. For example, in some embodiments, the UE capability information specifies a combination of the number of code blocks supported when a predetermined number of transmission layers are scheduled. In some other embodiments, when a predetermined number of transmission layers are scheduled, the UE capability information specifies a combination of the number of code blocks per PUSCH transmission opportunity.

[0114] As part of the resource allocation scheme described herein, in some embodiments, uplink resource allocation specifies TB calculation and PUSCH mapping of the encoded bits to resources (e.g., resource elements) via a single DCI. In some embodiments, TB calculation and PUSCH mapping are based on the transmission scheme used when multiple PUSCHs are transmitted simultaneously using multiple UE antenna panels. In some embodiments, one of three transmission schemes is used at any one time. These may include transmission schemes in which a single transport block (TB) is transmitted without repetition, a single TB is transmitted with repetition, and multiple TBs are transmitted. In some embodiments, the scheme is selected based on the capabilities of the UE. In some embodiments, the UE indicates their capabilities through a combination of radio resource control (RRC) and / or dynamic signaling.

[0115] In some embodiments, an uplink resource allocation is transmitted by a base station to a UE using a single DCI that specifies an uplink resource allocation for multiple PUSCHs and includes uplink resources for each PUSCH, the uplink resources including resources for simultaneously sending a single transport block (TB) without repetition using multiple UE antenna panels, simultaneously sending a single TB with repetition (in one or both of frequency and space) using multiple UE antenna panels, or simultaneously sending multiple TBs using multiple UE antenna panels based on UE capabilities provided by the UE to the base station. The UE uses the uplink resource allocation to configure itself to simultaneously send multiple PUSCHs using multiple UE antenna panels. After being configured, the UE uses multiple UE antenna panels via multiple antenna panels to send a single TB without repetition, send a single TB with repetition, or send multiple TBs, wherein each of the multiple PUSCHs is sent on a different UE antenna panel.

[0116] In some embodiments, if the UE is configured with parameters that indicate that the UE uses multiple simultaneous transmissions of a single TB on multiple UE antenna panels simultaneously (e.g., 1sMPTx parameters, referred to herein as Scheme A), the UE transmits a single PUSCH transmission of the TB on all entire allocated resources including multiple PUSCHs (e.g., PUSCH1 and PUSCH2). In some embodiments, multiple PUSCHs (e.g., PUSCH1, PUSCH2, etc.) are associated with different beams and panels via signaling from a base station.

[0117] When the UE's transmission scheme is to transmit a single TB simultaneously on multiple UE antenna panels (Scheme A), the uplink resource allocation indicates that a single TB is calculated on all frequency division multiplexing (FDM) resources and spatial division multiplexing (SDM) resources of the uplink resource allocation to be used to transmit a single TB using multiple UE antenna panels, assuming that the same modulation and coding scheme (MCS) and the same number of layers for transmitting a single TB as specified in a single DCI are applied to all beams and UE antenna panels. In some embodiments, the uplink resource allocation includes an indication of the MCS and number of layers for each UE antenna panel. An example process for TB calculation for this transmission scheme (Scheme A) is described in more detail below.

[0118] In some embodiments, when a single TB is transmitted simultaneously on multiple UE antenna panels (Scheme A), the uplink resource allocation for the UE specifies a slot-based repetition with a redundancy version (RV) index for each repetition opportunity for the UE for beam hopping on the time domain repetition using multiple UE antenna panels. In other words, in some embodiments, the UE can still use slot-based (Type A) or sub-slot-based (Type B) repetition for indication, but for each repetition opportunity, all resources on multiple panels are assumed to be a single opportunity. In some embodiments, the RV indication follows the traditional revision 15 / 16in, where the RV field in the DCI indicates the first RV index, and the RV for the next TD opportunity is determined by the mod operation as given in Table 6.1.2.1-2 of Section 6.1.4.2 of 3GPP TS 38.214.

[0119] In some embodiments, the beam for PUSCH may hop in time domain repetition, similar to the pattern described in NR Revision 17. In this case, both cyclic and sequential may be supported, and beam hopping may be used. Fig. 7A and Figure 7B An example of a PUSCH used for the first transmission scheme is illustrated (scheme A). Fig. 7A The first transmission scheme of simultaneously transmitting two PUSCHs on two UE antenna panels without time domain (TD) repetition is illustrated. Fig. 7A, during time slot #n, a single TB is transmitted without repetition using PUSCH1 on a first UE antenna panel associated with a first beam and using PUSCH2 on a different second UE antenna panel associated with a second beam. Figure 7B The first transmission scheme of simultaneously transmitting two PUSCHs on two UE antenna panels with TD repetition is illustrated. Figure 7B , during time slot #n, PUSCH1 is transmitted on a first UE antenna panel associated with a first beam, and PUSCH2 is transmitted on a different second UE antenna panel associated with a second beam, both with an RV equal to 0. In time slot #n+1, PUSCH1 is transmitted on the second UE antenna panel using the second beam, and PUSCH2 is transmitted on the first UE antenna panel using the first beam, both with an RV equal to 2.

[0120] In some other embodiments, the UE does not expect to receive any additional indication from the base station to perform TDM repetition. In some other embodiments, the transmission of a single TB using multiple time slots (TBoMS) is also possible. In this case, the resources are repeated at different times and the TB is calculated over all resources.

[0121] When the UE's transmission scheme is to transmit a single TB repeatedly on multiple UE antenna panels at the same time (Scheme B), the uplink resource allocation indicates that a single TB is transmitted repeatedly in frequency and / or space. In some embodiments, the resource allocation indicates resources for transmitting two PUSCHs (i.e., two repetitions) with the same TB simultaneously using two different UE antenna panels. In some embodiments, the TB is determined based on the resources, MCS, and number of layers associated with the PUSCH, and the same resources (e.g., FDRA and TDRA) are used for two PUSCHs. In some embodiments, using this transmission scheme (Scheme B), the uplink resource allocation provides an indication of the MCS and number of layers used for a single TB. The indication can be provided for each PUSCH of each beam using different code rates per repetition. In some embodiments, multiple PUSCHs (e.g., PUSCH1, PUSCH2, etc.) are associated with different beams and panels via signaling from a base station.

[0122] In some embodiments, for this transmission scheme (scheme B), uplink resource allocation specifies slot-based repetition with a redundancy version (RV) index without time domain repetition for repetition of each PUSCH in multiple PUSCHs. For two PUSCH repetitions, the RV is determined by Table 6.1.2.1-2 of 3GPP TS 38.214, where n=0,1 is applied to the first PUSCH and the second PUSCH, respectively (or vice versa). In this case, the UE does not expect to receive additional information from the base station to perform time domain repetition.

[0123] In some other embodiments, for this transmission scheme (Scheme B), the uplink resource allocation specifies a slot-based repetition with a redundancy version (RV) index for the UE per repetition opportunity for beam hopping on a time domain repetition using multiple UE antenna panels. In this case, the first RV for the PUSCH repetition associated with the first UE antenna panel is based on the count of PUSCH transmission opportunities associated with the first UE antenna panel, and the second RV associated with the second UE antenna panel is based on the first RV and the offset. That is, the UE can also be indicated by a slot-based (Type A) or sub-slot-based (Type B) repetition, where the RV indication follows the traditional revision 17 of NR by counting n separately for the repetition opportunity associated with each PUSCH. For all PUSCH repetitions associated with the first UE antenna panel, the RV is derived according to Table 6.1.2.1-2 of 3GPP TS 38.214, where only PUSCH transmission opportunities associated with the first panel are counted. In some embodiments, for all PUSCH repetitions associated with the second UE antenna panel, the RV is derived according to Table 6.1.2.1-3 of 3GPP TS 38.214, where only PUSCH transmission opportunities associated with the second panel are counted, and an additional shift operation for each redundant version is applied through the RRC parameter sequenceOffsetforRV.

[0124] Fig. 8A and Figure 8B An example of the second transmission scheme (scheme B) including using sequenceOffsetforRV=3 is illustrated. Fig. 8A A second transmission scheme of simultaneously transmitting two PUSCHs on two UE antenna panels without time domain (TD) repetition is illustrated. Fig. 8A, during time slot #n, a single TB is transmitted repeatedly using PUSCH1 (one repetition) on a first UE antenna panel associated with a first beam and using PUSCH2 (one repetition) on a different second UE antenna panel associated with a second beam. Each of PUSCH1 and PUSCH2 has a different RV (i.e., PUSCH1 with RV=0, PUSCH2 with RV=2). Figure 8B The second transmission scheme of simultaneously transmitting two PUSCHs on two UE antenna panels with TD repetition is illustrated. Figure 8B , during time slot #n, PUSCH1 is transmitted on a first UE antenna panel associated with a first beam, and PUSCH2 is transmitted on a different second UE antenna panel associated with a second beam. In this case, PUSCH1 has an RV equal to 0. sequenceOffsetforRV is set to 3 as an offset. Therefore, the RV for PUSCH2 is 3. In time slot #n+1, PUSCH1 is transmitted on a second UE antenna panel associated with a second beam, and PUSCH2 is transmitted on a first UE antenna panel associated with the first beam. In this case, the RV for PUSCH1 becomes 2, and the RV for PUSCH2 becomes 1 (e.g., 2(RV for PUSCH1) + 3(RV offset) modulo 4 equals 1). Therefore, Figure 8B It shows how the beams rotate on different PUSCHs in time and frequency / space.

[0125] Note that for this transmission scheme (Scheme B), the UE does not expect to receive any additional indication from the base station to perform TB over multiple time slots (TBoMS).

[0126] When the UE's transmission scheme is to transmit multiple TBs on multiple UE antenna panels simultaneously (Scheme C), the uplink resource allocation indicates which TB of the multiple TBs is associated with which PUSCH of the multiple PUSCHs. For example, in some embodiments, if the UE is configured with maxNrofCodeWordsScheduledByDCI having a value of 2, the UE may transmit two PUSCHs of separate TBs, where the first TB is associated with PUSCH1 and the second TB is associated with PUSCH2.

[0127] In some embodiments, for this transmission scheme (Scheme C), the resource allocation indicates the MCS and number of layers used for each TB (each TB has its own MCS and its own number of layers). If both TBs are enabled, TB1 and TB2 are determined based on the resources associated with PUSCH1 and PUSCH2 and the MCS and number of layers associated with PUSCH1 and PUSCH2. In some embodiments, the uplink resource allocation includes a downlink control information (DCI) bit field to specify one or more of the MCS, NDI, and RV associated with each of a plurality of codewords transmitted simultaneously using multiple UE antenna panels. For example, in the case where two TBs are transmitted simultaneously using PUSCH1 and PUSCH2 using two UE antenna panels, a new bit field is used to indicate the MCS, new data indicator (NDI), and RV associated with the second CW. Thus, this indication is provided per codeword.

[0128] In some embodiments, for this transmission scheme (scheme C), the uplink allocation specifies slot-based repetition with a redundancy version (RV) flag for the repetition opportunities associated with each UE antenna panel for multiple PUSCHs. In some embodiments, the RV indication follows the legacy Revision 17 of NR by counting n separately for the repetition opportunities associated with each beam / panel. Repetition in the time domain (TD) is performed similarly to Revision 16 of NR, but with beam hopping (both cyclic and sequential modes).

[0129] Fig.9A and Fig. 9B An example of this transmission scheme (scheme C) is illustrated. Fig.9A A third transmission scheme of simultaneously transmitting two PUSCHs with two TBs on two UE antenna panels without time domain (TD) repetition is illustrated. Fig.9A , during time slot #n, a first TB for a first codeword is transmitted using PUSCH1 on a first UE antenna panel associated with a first beam, and a second TB for a second codeword is transmitted using PUSCH2 on a different second UE antenna panel associated with a second beam (one repetition). Each of PUSCH1 and PUSCH2 has a different RV (i.e., PUSCH1 with RV=0, PUSCH2 with RV=1). Fig. 9B The second transmission scheme of simultaneously transmitting two PUSCHs on two UE antenna panels is illustrated. Fig. 9B, during time slot #n, PUSCH1 with codeword 0 (CW0) is transmitted on a first UE antenna panel associated with a first beam, and PUSCH2 with codeword 1 (CW1) is transmitted on a different second UE antenna panel associated with a second beam. In this case, PUSCH1 and CW0 have an RV equal to 0, while PUSCH2 and CW1 have an RV equal to 1. In time slot #n+1, CW0 is transmitted on a second UE antenna panel associated with a second beam, and CW1 is transmitted on a first UE antenna panel associated with the first beam. In this case, the RV of CW0 becomes 2, and the RV of CW1 is 0. Therefore, codewords CW0 and CW1 jump to other panels, so that the same codeword is transmitted using different beams when changing time slots.

[0130] Note that for this transmission scheme (Scheme C), the UE does not expect to receive any additional indication from the base station to perform TB over multiple time slots (TBoMS).

[0131] In some embodiments, the UE receives an indication from the base station that specifies whether the uplink resource allocation has resources for simultaneously sending a single TB without repetition using multiple UE antenna panels, simultaneously sending a single TB with repetition using multiple UE antenna panels, or simultaneously sending multiple TBs using multiple UE antenna panels (e.g., transmission scheme A, transmission scheme B, transmission scheme C). In some embodiments, the configuration is subject to the UE capabilities. If the UE is capable of multiple schemes, only one scheme is signaled to the UE by the base station. In some embodiments, the signaling is performed via RRC. In some other embodiments, the transmission scheme is dynamically indicated by the base station via a scheduling DCI format to support fast adaptation. For example, such signaling can be performed based on the type of service associated with the PUSCH (e.g., URLLC vs. eMBB).

[0132] When the UE's transmission scheme is to use multiple UE antenna panels to transmit a single PUSCH transmission of the TB on multiple panels simultaneously without duplication (Scheme A), the TB calculation and PUSCH construction are as follows. If a single MCS bit field and number of layers are applied to the UE antenna panels (e.g., two UE antenna panels when two UE antenna panels are used), the single PUSCH transmission of the TB is calculated according to 3GPP TS 38.214 Section 6.1.4.2, where n PRB is the total number of PRBs allocated across all UE antenna panels in the UE antenna panel. Overlapped RBs may be counted once or twice.

[0133] In some embodiments, in the case of a single PUSCH transmission without repeated TBs, the PUSCH configuration is performed according to the PUSCH configuration set forth in Section 6.3.1 of 3GPP TS 38.211, except that different beams and / or precodings are applied to the PUSCHs. For example, when two PUSCHs (such as PUSCH1 and PUSCH2) are transmitted simultaneously, these PUSCHs are applied to different beams and / or have different precodings. Note that this applies to both FDM and SDM.

[0134] In some embodiments, when a single MCS bit field and number of layers are applied to the UE antenna panel, the mapping of the encoded bits to resources can be performed in a variety of different ways. In some embodiments, when two PUSCH transmissions are to occur (e.g., PUSCH1 and PUSCH2), the mapping starts with the first allocated symbol and the encoded symbols are first mapped to all resource elements (REs) associated with PUSCH1 in frequency and then mapped to resource elements (REs) associated with PUSCH2. The mapping then moves to the next symbol. In some other embodiments, the mapping starts with PUSCH1, where the encoded bits are mapped in all frequency and time REs associated with PUSCH1 (the next frequency), and the mapping moves to the next PUSCH, such as PUSCH2. In some other embodiments, for FDM, the mapping starts with the first allocated symbol and the encoded symbols are mapped to all REs in frequency (which belong to PUSCH1 and PUSCH2) and then subsequently mapped to the next symbol, and so on. Fig. 10A An example of the PUSCH mapping scheme for the transmission scheme (scheme A) is illustrated.

[0135] refer to Fig. 10A, the transmit chain first determines the TB (1001). In some embodiments, the determination of the TB is performed according to Section 6.1.4.2 of 3GPP TS 38.214. Next, multiplexing and channel coding are performed (1002). In some embodiments, multiplexing and channel coding are performed according to Section 6.2 of 3GPP TS 38.212. Thereafter, the encoded bits are concatenated after rate matching for codeword 0 (CW0). After concatenation, scrambling and modulation (1004) followed by layer mapping (1005) and transform precoding (1006) are performed. In some embodiments, scrambling and modulation are performed according to Sections 6.3.1.1 and 6.3.1.2 of 3GPP TS 38.211. In some embodiments, layer mapping is performed according to Section 6.3.3 of 3GPP TS 38.211. In some embodiments, transform precoding is performed in accordance with 3GPP TS 38.211 Section 6.3.1.4. Once transform precoding is completed, precoding is performed (1007). In some embodiments, precoding is performed in accordance with 3GPP TS 38.211 Section 6.3.1.5, except that if the uplink is codebook based, the codebook is applied to the layer associated with the PUSCH (per PUSCH). After precoding, the coded symbols are mapped to all REs in frequency (FDM) belonging to the PUSCH (e.g., PUSCH1 and PUSCH2 for the case of two simultaneously transmitted PUSCHs) (1008). Therefore, for this transmission scheme, precoding (1007) and mapping to REs (1008) are performed differently than traditional PUSCH mapping.

[0136] In some other embodiments, if the MCS and / or number of layers are indicated for each panel / beam separately, the TB calculation and PUSCH construction for this transmission scheme (scheme A) are performed in a different manner. In this case, for TB calculation, a single TB calculation is performed according to 3GPP TS 38.214 Section 6.1.4.2 based on a separate TB calculation for each UE antenna panel in the plurality of UE antenna panels using the number of allocated PRBs associated with each UE antenna panel in the plurality of UE antenna panels. That is, for TB calculation: TB = TB1 + TB2, both TB1 and TB2 are determined using 38.214 Section 6.1.4.2, where n for TB1 PRBTB2 is the total number of allocated PRBs associated with the first PUSCH (PUSCH1), TB3 is the total number of allocated PRBs associated with the second PUSCH (PUSCH2), and so on. In addition, the PUSCH mapping to resource elements is determined by the assigned PRBs corresponding to each beam used for its corresponding PUSCH in multiple PUSCHs. In the case of two PUSCHs being transmitted simultaneously, the PUSCH transmission is decomposed into two transmissions, each associated with one of the panels / beams, where each transmission follows 38.211 section 6.3.1 for a given modulation order and number of layers. Fig. 10B An example of this mapping scheme for this transmission scheme (scheme A) is illustrated.

[0137] Fig. 10B An example of the PUSCH mapping scheme for the transmission scheme (scheme A) is illustrated. Fig. 10B In this alternative, the transmit chain first determines TB (1011). In some embodiments, the determination of TB is performed according to 3GPP TS 38.214 Section 6.1.4.2. As discussed above, in this alternative, for TB calculation, TB is equal to TB1+TB2, and 38.214 Section 6.1.4.2 is used to determine both TB1 and TB2, where n for TB1 is PRBTB1 is the total number of allocated PRBs associated with the first PUSCH (PUSCH1), TB2 is the total number of allocated PRBs associated with the second PUSCH (PUSCH2), and so on. Next, multiplexing and channel coding are performed (1012). In some embodiments, multiplexing and channel coding are performed in accordance with 3GPP TS 38.212 Section 6.2. Thereafter, the encoded bits are concatenated after rate matching for codeword 0 (CW0). After concatenation, scrambling and modulation are performed (1014) followed by layer mapping (1015) and transform precoding (1016). In some embodiments, scrambling and modulation are performed in accordance with 3GPP TS 38.211 Sections 6.3.1.1 and 6.3.1.2. In some embodiments, layer mapping is performed in accordance with 3GPP TS 38.211 Section 6.3.3, where PUSCH transmissions are each associated with one of the panels / beams and have a given modulation order and number of layers. In some embodiments, transform precoding is performed in accordance with 3GPP TS 38.211 Section 6.3.1.4. Once transform precoding is completed, precoding is performed (1017). In some embodiments, precoding is performed in accordance with 3GPP TS 38.211 Section 6.3.1.5, except that if the uplink is codebook based, the codebook is applied to the layer associated with the PUSCH (per PUSCH). After precoding, the coded symbols are mapped to all REs in frequency (FDM) belonging to the PUSCH (e.g., PUSCH1 and PUSCH2 for the case of two simultaneously transmitted PUSCHs) (1018). Therefore, for this transmission scheme, TB determination (1011), layer mapping (1015), precoding (1017), and mapping to REs (1018) are performed differently from conventional PUSCH mapping.

[0138] When the UE's transmission scheme is to transmit multiple PUSCH transmissions (e.g., two PUSCH transmissions) of the same TB simultaneously on multiple UE antenna panels (scheme B), the TB calculation and PUSCH construction are as follows. In some embodiments, the TB calculation is based on the resource elements (REs), MCS, and number of layers associated with each beam to be transmitted by the UE antenna panel, or based on the TB with the maximum transport block size (TBS) of the TB calculated for each beam / panel (e.g., when two PUSCHs are transmitted simultaneously using two UE antenna panels, the TB is the maximum TBS for the first panel and the second panel), or based on the TB with the minimum TBS of the TB calculated for each beam / panel (e.g., when two PUSCHs are transmitted simultaneously using two UE antenna panels, the TB is the minimum TBS for the first panel and the second panel). For example, for the case where two PUSCHs with the same TB are transmitted simultaneously, when performing TB calculation, the TB for the first UE antenna panel is determined based on the RE, MCS and number of layers associated with the first beam of the first UE antenna panel as given in Section 6.1.4.2 of 3GPP TS 38.214, and the TB for the second UE antenna panel is determined based on the RE, MCS and number of layers associated with the second beam of the second UE antenna panel as given in Section 6.1.4.2 of 3GPP TS 38.214, or the TB with the maximum value of the two TBs calculated for each beam / panel or the minimum value of the two TBs calculated for each beam / panel.

[0139] In some embodiments, when multiple PUSCH transmissions (e.g., two PUSCH transmissions) of the same TB are transmitted simultaneously on multiple UE antenna panels (scheme B), for PUSCH construction, the PUSCH mapping to resource elements is determined by assigning a PRB corresponding to each beam used for its corresponding PUSCH. For example, when performing PUSCH construction, the construction of each PUSCH repetition is in accordance with 3GPP TS 38.211 Section 6.3.1, where the mapping to resource elements is determined by the assigned PRB corresponding to each beam. Note that this is the same for FDM and SDM (no change in PUSCH RE mapping). Fig.11A and Fig. 11B An example of PUSCH mapping for each repetition is illustrated when two PUSCH transmissions (e.g., PUSCH1 and PUSCH2) of the same TB are transmitted simultaneously on multiple UE antenna panels (scheme B). Fig.11A, the transmission chain of the first TB repetition initially determines the TB based on PUSCH1 (1101). In some embodiments, the determination of the TB is performed according to Section 6.1.4.2 of 3GPP TS 38.214. Next, multiplexing and channel coding (1102) are performed. In some embodiments, multiplexing and channel coding are performed according to Section 6.2 of 3GPP TS 38.212. Thereafter, the encoded bits are concatenated after rate matching for codeword 0 (CW0). After concatenation, scrambling and modulation (1104) are performed followed by layer mapping (1105) and transform precoding (1106). In some embodiments, scrambling and modulation are performed according to Sections 6.3.1.1 and 6.3.1.2 of 3GPP TS 38.211. In some embodiments, layer mapping is performed according to Section 6.3.3 of 3GPP TS 38.211. In some embodiments, transform precoding is performed according to 3GPP TS 38.211 Section 6.3.1.4. Once transform precoding is completed, precoding is performed (1107). In some embodiments, precoding is performed according to 3GPP TS 38.211 Section 6.3.1.5. After precoding, the coded symbols are mapped to all REs associated with PUSCH1 (1108). Therefore, for this transmission scheme, TB determination (1101) and precoding (1107) are performed differently from the traditional PUSCH mapping.

[0140] refer to Fig. 11B, the transmission chain of the second TB repetition initially determines the TB based on PUSCH2 (1111). In some embodiments, the determination of the TB is performed according to Section 6.1.4.2 of 3GPP TS 38.214. Next, multiplexing and channel coding (1112) are performed. In some embodiments, multiplexing and channel coding are performed according to Section 6.2 of 3GPP TS 38.212. Thereafter, the encoded bits are concatenated after rate matching for codeword 1 (CW1). After concatenation, scrambling and modulation (1114) are performed followed by layer mapping (1115) and transform precoding (1116). In some embodiments, scrambling and modulation are performed according to Sections 6.3.1.1 and 6.3.1.2 of 3GPP TS 38.211. In some embodiments, layer mapping is performed according to Section 6.3.3 of 3GPP TS 38.211. In some embodiments, transform precoding is performed in accordance with 3GPP TS 38.211 Section 6.3.1.4. Once transform precoding is completed, precoding is performed (1117). In some embodiments, precoding is performed in accordance with 3GPP TS 38.211 Section 6.3.1.5. After precoding, the coded symbols are mapped to all REs associated with PUSCH2 (1118). Therefore, for this transmission scheme, TB determination (1111) and precoding (1117) are performed differently from the traditional PUSCH mapping.

[0141] When the UE's transmission scheme is multiple PUSCH transmissions (e.g., two PUSCH transmissions) that will use multiple UE antenna panels to simultaneously transmit multiple TBs (e.g., two TBs) (Scheme C), the TB calculation and PUSCH construction are as follows. In some embodiments, for this transmission scheme, the MCS and / or number of layers are indicated separately for each panel / beam. In some embodiments, for TB calculation, a single TB calculation is based on a separate TB for each UE antenna panel in the UE antenna panels, and the calculation is in accordance with Section 6.1.4.2 of 3GPP TS 38.214. For example, in some embodiments, when two PUSCHs are transmitted simultaneously using two UE antenna panels, TB1 for the first UE antenna panel is calculated in accordance with 3GPP TS 38.214, and TB2 for the second UE antenna panel is calculated in accordance with 3GPP TS 38.214. In these cases, the nPRBs calculated for each individual TB for each UE antenna panel is the number of allocated PRBs associated with said each UE antenna panel, and the code rate, modulation order and rank calculated for said each individual TB are obtained by calculating the indicated MCS and number of layers for said each individual TB. Thus, the TB calculations for determining TB1 and TB2 are determined according to 3GPP TS 38.214 Section 6.1.4.2, where nPRBs for TB1 and TB2 arePRB The total number of allocated PRBs associated with the first and second panels, respectively, and used for R&Q m & v (Code rate, modulation order, rank) are obtained by MCS and the number of layers used for TB1 and TB2 respectively.

[0142] In some embodiments, in the case of multiple PUSCH transmissions (e.g., two PUSCH transmissions) of multiple TBs (e.g., two TBs) being transmitted simultaneously using multiple UE antenna panels (Scheme C), for the PUSCH construction, the PUSCH transmissions are decomposed into different transmissions (e.g., two transmissions for PUSCH1 and PUSCH2), where each transmission is associated with one of the panels / beams, where each transmission is for a given modulation order and number of layers in accordance with 3GPP TS 38.211 Section 6.3.1. Fig. 12A and Fig. 12B An example of PUSCH mapping for two codewords when two PUSCHs (eg, PUSCH1 and PUSCH2) are transmitted simultaneously on multiple UE antenna panels (scheme C) is illustrated. Note that the same operation is performed for FDM and SDM.

[0143] refer to Fig. 12A, the transmission chain for the first codeword transmission initially determines the TB for codeword 0 (CW0) (1201). In some embodiments, the determination of the TB is performed in accordance with 3GPP TS 38.214 Section 6.1.4.2. Next, multiplexing and channel coding are performed (1202). In some embodiments, multiplexing and channel coding are performed in accordance with 3GPP TS 38.212 Section 6.2. Thereafter, the encoded bits are concatenated after rate matching for CW0. After concatenation, scrambling and modulation are performed (1204) followed by layer mapping (1205) and transform precoding (1206). In some embodiments, scrambling and modulation are performed in accordance with 3GPP TS 38.211 Sections 6.3.1.1 and 6.3.1.2. In some embodiments, layer mapping is performed in accordance with 3GPP TS 38.211 Section 6.3.3, where the transmission of CW0 is for a given modulation order and number of layers. In some embodiments, transform precoding is performed in accordance with 3GPP TS 38.211 Section 6.3.1.4. Once transform precoding is completed, precoding is performed (1207). In some embodiments, precoding is performed in accordance with 3GPP TS 38.211 Section 6.3.1.5, except that it is applied per PUSCH (e.g., if the uplink is codebook based, the codebook is applied to the layers associated with the PUSCH). After precoding, the coded symbols are mapped to REs associated with CW0 (1208). Therefore, for this transmission scheme, TB determination (1201), layer mapping (1205), precoding (1107), and mapping to REs (1208) are performed differently from conventional PUSCH mapping because they are performed for one TB among multiple TBs that are simultaneously transmitted using multiple antenna panels of a UE.

[0144] refer to Fig. 12B, the transmission chain for the first codeword transmission initially determines the TB for codeword 1 (CW1) (1211). In some embodiments, the determination of the TB is performed in accordance with 3GPP TS 38.214 Section 6.1.4.2. Next, multiplexing and channel coding are performed (1212). In some embodiments, multiplexing and channel coding are performed in accordance with 3GPP TS 38.212 Section 6.2. Thereafter, the encoded bits are concatenated after rate matching for CW1. After concatenation, scrambling and modulation are performed (1214) followed by layer mapping (1215) and transform precoding (1216). In some embodiments, scrambling and modulation are performed in accordance with 3GPP TS 38.211 Sections 6.3.1.1 and 6.3.1.2. In some embodiments, layer mapping is performed in accordance with 3GPP TS 38.211 Section 6.3.3, where the transmission of CW1 is for a given modulation order and number of layers. In some embodiments, transform precoding is performed in accordance with 3GPP TS 38.211 Section 6.3.1.4. Once transform precoding is completed, precoding is performed (1217). In some embodiments, precoding is performed in accordance with 3GPP TS 38.211 Section 6.3.1.5, except that the application is applied per PUSCH (e.g., if the uplink is codebook based, the codebook is applied to the layers associated with the PUSCH). After precoding, the coded symbols are mapped to REs associated with CW1 (1218). Therefore, for this transmission scheme, TB determination (1211), layer mapping (1215), precoding (1217), and mapping to REs (1218) are performed differently from conventional PUSCH mapping because they are performed for TBs of each codeword (of multiple TBs) transmitted simultaneously using multiple antenna panels of a UE.

[0145] In some embodiments, regardless of whether one of the three transmission schemes described above is used (e.g., Scheme A, Scheme B, Scheme C), if the UE has indicated that it is capable of performing multi-panel simultaneous transmission, the UE only supports inter-slot frequency hopping, subject to the UE capabilities. For example, in some embodiments, when multiple PUSCHs are transmitted, each PUSCH is transmitted on a different UE antenna panel, and the transmission on multiple time slots occurs in frequency hopping. The frequency hopping can be inter-slot frequency hopping. In some other embodiments, inter-slot (and / or intra-slot) frequency hopping is supported only if the UE is configured with parameters indicating the performance of FDM and (e.g., setting the fdmMPTx parameter) in combination with a single (non-repetitive) simultaneous transmission of a single TB with multiple UE antenna panels.

[0146] Fig.13 An example of frequency hopping for multi-panel simultaneous transmission involving the transmission of a single TB with repetition as described above (scheme B) is illustrated. Fig.13 , during time slot #n, PUSCH1 and PUSCH2 are shown as being transmitted from different panels using different beams, while in time slot #n+1, PUSCH1 and PUSCH2 have undergone beam hopping and frequency hopping such that they are transmitted from different panels.

[0147] In some other implementations, the UE supports neither intra-slot frequency nor inter-slot frequency.

[0148] In some embodiments, the baseband processor (or UE) is configured to perform operations including: receiving RRC configuration information from a base station, wherein the RRC configuration information includes an uplink transmission scheme using multiple antenna panels for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes transmission of a single TB without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on user equipment (UE) capabilities. In some embodiments, the baseband processor also receives a single downlink control information (DCI) specifying uplink resource allocation for multiple PUSCHs and transmits the multiple PUSCHs.

[0149] Fig.14 Flowcharts of some embodiments of a process for configuring a UE. The process is performed by processing logic including hardware (circuitry, dedicated logic, etc.), software (e.g., software running on a chip, software running on a general-purpose computer system or a dedicated machine, etc.), firmware, or a combination of the three. In one embodiment, the operations in the process are performed by a UE in a 5G NR communication system. In some embodiments, the process is performed by a UE in a 5G NR communication system, and the UE includes a processor (or processing circuit) and / or a baseband processor in the 5G NR communication system configured to perform the following operations.

[0150] refer to Fig.14 The process begins by transmitting UE capability information (processing block 1401). In some embodiments, the UE capability information is sent via the UE and received by the base station through radio resource control (RRC) signaling or via dynamic signaling.

[0151] In some embodiments, where the UE is capable of using multiple transmission schemes such as those described herein (e.g., Scheme A, Scheme B, Scheme C, etc.), the UE may receive an indication from a base station specifying whether an uplink resource allocation has resources for simultaneously transmitting a single TB without repetition using multiple UE antenna panels, simultaneously transmitting a single TB with repetition using multiple UE antenna panels, or simultaneously transmitting multiple TBs using multiple UE antenna panels. In some embodiments, the UE receives the indication via radio resource control (RRC) signaling. In some embodiments, the UE may receive a dynamic DCI indication from a base station specifying whether an uplink resource allocation has resources for simultaneously transmitting a single TB without repetition using multiple UE antenna panels, simultaneously transmitting a single TB with repetition using multiple UE antenna panels, or simultaneously transmitting multiple TBs using multiple UE antenna panels.

[0152] In some embodiments, the UE capability information specifies one or more of the following: the number of codewords per PUSCH transmission opportunity, the number of code blocks per PUSCH transmission opportunity, the number of transmission layers per PUSCH transmission scheduling, the number of layers being transmitted when information is transmitted on multiple PUSCHs simultaneously, the maximum modulation order, the transmission scheme. In some embodiments, the UE capability information specifies a combination of the number of code blocks supported when a predetermined number of transmission layers are scheduled. In some embodiments, the UE capability information specifies a combination of the number of code blocks per PUSCH transmission opportunity when a predetermined number of transmission layers are scheduled.

[0153] Processing logic receives RRC configuration information from a base station, wherein the RRC configuration information includes an uplink transmission scheme using multiple antenna panels for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes transmission of a single transport block (TB) without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on user equipment (UE) capabilities. Processing logic also receives a single downlink control information (DCI) specifying uplink resource allocation for multiple physical uplink shared channels (PUSCHs) (processing block 1402). In some embodiments, based on the user equipment (UE) capabilities, the transmission scheme is for multiple PUSCHs for simultaneously transmitting a single transport block (TB) without repetition using multiple UE antenna panels, simultaneously transmitting a single TB with repetition using multiple UE antenna panels in one or both of frequency and space, or simultaneously transmitting multiple TBs using multiple UE antenna panels.

[0154] In some embodiments, if the RRC configuration information includes an uplink transmission scheme (e.g., Scheme A) for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels including transmission of a single transport block (TB) without repetition, then the single TB is calculated over all frequency division multiplexing (FDM) resources and spatial division multiplexing (SDM) resources of the uplink resource allocation to be used for transmitting the single TB using the multiple UE antenna panels and the single TB indicates the same modulation and coding scheme (MCS) and the same number of layers for transmitting the single TB using the multiple UE antenna panels. In some embodiments, the uplink resource allocation specifies a slot-based repetition with a redundancy version (RV) index for the UE per repetition opportunity for beam hopping over time domain repetition using the multiple UE antenna panels. In some embodiments, if the RRC configuration information includes an uplink transmission scheme (e.g., Scheme A) for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels including transmission of a single TB without repetition, then the single TB is calculated over all frequency division multiplexing (FDM) resources and spatial division multiplexing (SDM) resources of the uplink resource allocation to be used for transmitting the single TB using multiple UE antenna panels and the single TB indicates the same modulation and coding scheme (MCS) and the same number of layers for each UE antenna panel for transmitting the single TB using multiple UE antenna panels.

[0155] In some embodiments, in a transmission scheme similar to Scheme A, when a single MCS bit field and number of layers are applied to multiple UE antenna panels, a single TB is calculated using the total number of PRBs allocated on all UE antenna panels in the multiple UE antenna panels in accordance with Section 6.1.4.2 of 3GPP TS 38.214. In some embodiments, when the MCS and number of layers are indicated separately for each UE antenna panel in the multiple UE antenna panels, the single TB calculation is calculated based on a separate TB for each UE antenna panel in the UE antenna panels using the number of allocated PRBs associated with each UE antenna panel in the multiple UE antenna panels in accordance with Section 6.1.4.2 of 3GPP TS 38.214. In some embodiments, in a transmission scheme similar to Scheme A, the PUSCH mapping to resource elements is determined by the assigned PRBs corresponding to each beam for its corresponding PUSCH in the multiple PUSCHs.

[0156] In some embodiments, in a transmission scheme similar to scheme A, transmitting multiple PUSCHs is performed as part of transmitting multiple TBs using multiple time slots with inter-slot hopping, where each of the multiple PUSCHs is transmitted on a different UE antenna panel.

[0157] In some embodiments, in a transmission scheme similar to Scheme B, if the RRC configuration information includes an uplink transmission scheme for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels including transmission of a single TB with repetitions, the transmission occurs in one or both of frequency and space. In some embodiments, in a transmission scheme similar to Scheme B, the RRC configuration information includes an uplink transmission scheme for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels including transmission of a single TB with repetitions, the uplink resource allocation specifies the same resources, MCS, and number of layers using different code rates per repetition for a single TB for each PUSCH per beam. In some embodiments, the uplink resource allocation specifies slot-based repetitions with a redundancy version (RV) index for the repetitions of each PUSCH in the multiple PUSCHs without time domain repetitions. In some embodiments, uplink resource allocation specifies a slot-based repetition with a redundancy version (RV) index for a UE per repetition opportunity for beam hopping on a time domain repetition using multiple UE antenna panels, wherein a first RV for a PUSCH repetition associated with a first UE antenna panel is based on a count of PUSCH transmission opportunities associated with the first UE antenna panel, and a second RV associated with a second UE antenna panel is based on the first RV and an offset.

[0158] In some embodiments, in a transmission scheme similar to scheme B, the calculation of the TB is based on the RE, MCS and number of layers associated with each of the beams to be transmitted by multiple UE antenna panels or a TB with a maximum transport block size (TBS) among the TBs calculated for each beam / panel, or a TB with a minimum TBS among the TBs calculated for each beam / panel. In some embodiments, the PUSCH mapping to resource elements is determined by the assigned PRBs corresponding to each beam for its corresponding PUSCH among multiple PUSCHs.

[0159] In some embodiments, in a transmission scheme similar to scheme C, the RRC configuration information includes an uplink transmission scheme for simultaneously transmitting multiple PUCSCHs using multiple UE antenna panels, and includes the transmission of multiple TBs, then the uplink resource allocation specifies which TB of the multiple TBs is associated with which PUSCH of the multiple PUSCHs, including indicating the MCS and the number of layers used for the TBs. In some embodiments, the uplink resource allocation includes a downlink control information (DCI) bit field to specify one or more of the MCS, NDI, and RV associated with each of the multiple codewords. In some embodiments, the uplink resource allocation specifies a slot-based repetition with a redundancy version (RV) index for a repetition opportunity associated with each UE antenna panel for the multiple PUSCHs.

[0160] In some embodiments, in a transmission scheme similar to scheme C, the single TB calculation is based on calculations of separate TB calculations for each of the UE antenna panels according to 3GPP TS 38.214 Section 6.1.4.2, where n is calculated for each separate TB calculation for each UE antenna panel. PRB is the number of allocated PRBs associated with each UE antenna panel, and the code rate, modulation order and rank calculated for each individual TB are obtained by the MCS and number of layers calculated for each individual TB.

[0161] In response to the configuration information, processing logic configures the UE to transmit multiple PUSCHs simultaneously using multiple UE antenna panels (processing block 1403), and thereafter transmit multiple PUSCHs with a single TB without duplication, transmit multiple PUSCHs with a single TB with duplication, or transmit multiple PUSCHs with multiple TBs on multiple UE antenna panels, wherein each of the multiple PUSCHs is transmitted on a different UE antenna panel. (processing block 1404).

[0162] In some embodiments, transmitting multiple PUSCH resources is performed as part of transmitting multiple TBs using multiple time slots with inter-slot frequency hopping, wherein each PUSCH of the multiple PUSCHs is transmitted on a different UE antenna panel.

[0163] In some embodiments, a base station includes a processor (or processing circuit) configured to perform operations, the operations including: generating and transmitting RRC configuration information, wherein the RRC configuration information includes an uplink transmission scheme using multiple antenna panels for simultaneously transmitting multiple physical uplink shared channels (PUSCHs) using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes transmission of a single transport block (TB) without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on user equipment (UE) capabilities. In some embodiments, the base station also generates a single DCI specifying uplink resource allocation for multiple PUSCHs, and transmits the single DCI to the UE.

[0164] Fig.15It is a flowchart of one embodiment of a process by which network equipment configures a UE. The process is performed by processing logic including hardware (circuitry, dedicated logic, etc.), software (e.g., software running on a chip, software running on a general-purpose computer system or a dedicated machine, etc.), firmware, or a combination of the three. In one embodiment, the operations in the process are performed by network equipment operating in a 5G new radio in a spectrum above 52.6 GHz in a 5G new air interface (NR). In some embodiments, the process is performed by a base station including a processor (or processing circuit) configured to perform the following operations.

[0165] refer to Fig.15 The process begins by receiving UE capability information (processing block 1501). In some embodiments, the UE capability information is sent via the UE and received by the base station through radio resource control (RRC) signaling or via dynamic signaling.

[0166] In some embodiments, where the UE is capable of using multiple transmission schemes such as those described herein (e.g., Scheme A, Scheme B, Scheme C, etc.), the base station may transmit an indication to the UE that specifies whether the uplink resource allocation has resources for simultaneously transmitting a single TB without repetition using multiple UE antenna panels, simultaneously transmitting a single TB with repetition using multiple UE antenna panels, or simultaneously transmitting multiple TBs using multiple UE antenna panels. In some embodiments, the UE receives the indication via radio resource control (RRC) signaling. In some embodiments, the UE may receive a dynamic DCI indication from the base station that specifies whether the uplink resource allocation has resources for simultaneously transmitting a single TB without repetition using multiple UE antenna panels, simultaneously transmitting a single TB with repetition using multiple UE antenna panels, or simultaneously transmitting multiple TBs using multiple UE antenna panels.

[0167] In some embodiments, the UE capability information specifies one or more of the following: the number of codewords per PUSCH transmission opportunity, the number of code blocks per PUSCH transmission opportunity, the number of transmission layers per PUSCH transmission scheduling, the number of layers being transmitted when information is transmitted on multiple PUSCHs simultaneously, the maximum modulation order, the transmission scheme. In some embodiments, the UE capability information specifies a combination of the number of code blocks supported when a predetermined number of transmission layers are scheduled. In some embodiments, the UE capability information specifies a combination of the number of code blocks per PUSCH transmission opportunity when a predetermined number of transmission layers are scheduled.

[0168] The processing logic generates configuration information for configuring a user equipment (UE). In some embodiments, the configuration includes RRC configuration information. The RRC configuration information may specify an uplink transmission scheme using multiple antenna panels for simultaneously transmitting multiple physical uplink shared channels (PUSCHs) using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes transmission of a single transport block (TB) without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on the user equipment (UE) capability.

[0169] In some embodiments, the processing logic also generates a single downlink control information (DCI) that specifies uplink resource allocations for multiple physical uplink shared channels (PUSCHs), wherein the uplink resource allocations for the multiple PUSCHs include uplink resources for each PUSCH, including resources for simultaneously transmitting multiple PUSCHs with a single transport block (TB) without duplication using multiple UE antenna panels, simultaneously transmitting multiple PUSCHs with a single TB with duplication in one or both of frequency and space using multiple UE antenna panels, or simultaneously transmitting multiple PUSCHs with multiple TBs using multiple UE antenna panels (processing block 1502). In some embodiments, the uplink resource allocations are based on user equipment (UE) capabilities.

[0170] In some embodiments, if the RRC configuration information includes an uplink transmission scheme (e.g., Scheme A) for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels including transmission of a single TB without repetition, then the single TB is calculated over all frequency division multiplexing (FDM) resources and spatial division multiplexing (SDM) resources of the uplink resource allocation to be used for transmitting the single TB using multiple UE antenna panels and the single TB indicates the same modulation and coding scheme (MCS) and the same number of layers for transmitting the single TB using multiple UE antenna panels. In some embodiments, the uplink resource allocation specifies a slot-based repetition with a redundancy version (RV) index for the UE per repetition opportunity for beam hopping over time domain repetition using multiple UE antenna panels. In some embodiments, if the RRC configuration information includes an uplink transmission scheme (e.g., Scheme A) for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels including transmission of a single TB without repetition, then the single TB is calculated over all frequency division multiplexing (FDM) resources and spatial division multiplexing (SDM) resources of the uplink resource allocation to be used for transmitting the single TB using multiple UE antenna panels and the single TB indicates the same modulation and coding scheme (MCS) and the same number of layers for each UE antenna panel for transmitting the single TB using multiple UE antenna panels.

[0171] In some embodiments, in a transmission scheme similar to Scheme A, when a single MCS bit field and number of layers are applied to multiple UE antenna panels, a single TB is calculated using the total number of PRBs allocated on all UE antenna panels in the multiple UE antenna panels in accordance with Section 6.1.4.2 of 3GPP TS 38.214. In some embodiments, when the MCS and number of layers are indicated separately for each UE antenna panel in the multiple UE antenna panels, the single TB calculation is calculated based on a separate TB for each UE antenna panel in the UE antenna panels using the number of allocated PRBs associated with each UE antenna panel in the multiple UE antenna panels in accordance with Section 6.1.4.2 of 3GPP TS 38.214. In some embodiments, in a transmission scheme similar to Scheme A, the PUSCH mapping to resource elements is determined by the assigned PRBs corresponding to each beam for its corresponding PUSCH in the multiple PUSCHs.

[0172] In some embodiments, in a transmission scheme similar to scheme A, transmitting multiple PUSCHs is performed as part of transmitting multiple TBs using multiple time slots with inter-slot hopping, where each of the multiple PUSCHs is transmitted on a different UE antenna panel.

[0173] In some embodiments, in a transmission scheme similar to Scheme B, if the RRC configuration information includes an uplink transmission scheme for transmitting a single TB including repetitions for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels, the single TB is transmitted with repetitions in one or both of frequency and space. In some embodiments, in a transmission scheme similar to Scheme B, if the RRC configuration information includes an uplink transmission scheme for transmitting a single TB including repetitions for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels, the uplink resource allocation specifies the same resources, MCS, and number of layers for each repetition using different code rates for a single TB for each PUSCH per beam. In some embodiments, the uplink resource allocation specifies slot-based repetitions with a redundancy version (RV) index for the repetitions of each PUSCH in the multiple PUSCHs without time domain repetitions. In some embodiments, uplink resource allocation specifies a slot-based repetition with a redundancy version (RV) index for a UE per repetition opportunity for beam hopping on a time domain repetition using multiple UE antenna panels, wherein a first RV for a PUSCH repetition associated with a first UE antenna panel is based on a count of PUSCH transmission opportunities associated with the first UE antenna panel, and a second RV associated with a second UE antenna panel is based on the first RV and an offset.

[0174] In some embodiments, in a transmission scheme similar to scheme B, the calculation of the TB is based on the resources, MCS and number of layers associated with each of the beams to be transmitted by multiple UE antenna panels or a TB with a maximum transport block size (TBS) among the TBs calculated for each beam / panel, or a TB with a minimum TBS among the TBs calculated for each beam / panel. In some embodiments, the PUSCH mapping to resource elements is determined by the assigned PRBs corresponding to each beam for its corresponding PUSCH among multiple PUSCHs.

[0175] In some embodiments, in a transmission scheme similar to scheme C, if the RRC configuration information includes an uplink transmission scheme for simultaneously transmitting multiple PUCSCHs using multiple UE antenna panels, including the transmission of multiple transport blocks (TBs), then the uplink resource allocation specifies which TB of the multiple TBs is associated with which PUCSCH of the multiple PUSCHs, including indicating the MCS and number of layers used for the TBs. In some embodiments, the uplink resource allocation includes a downlink control information (DCI) bit field to specify one or more of the MCS, NDI, and RV associated with each of the multiple codewords. In some embodiments, the uplink resource allocation specifies a slot-based repetition with a redundancy version (RV) index for a repetition opportunity associated with each UE antenna panel for the multiple PUSCHs.

[0176] In some embodiments, in a transmission scheme similar to scheme C, the single TB calculation is based on calculations of separate TB calculations for each of the UE antenna panels according to 3GPP TS 38.214 Section 6.1.4.2, where n is calculated for each separate TB calculation for each UE antenna panel. PRB is the number of allocated PRBs associated with each UE antenna panel, and the code rate, modulation order and rank calculated for each individual TB are obtained by the MCS and number of layers calculated for each individual TB.

[0177] After generating the single DCI, processing logic sends the single DCI to the UE (processing block 1503).

[0178] Various example implementations are described herein.

[0179] Embodiment 1 is a method that can be performed by a baseband processor or a UE, wherein the method includes: receiving RRC configuration information from a base station, wherein the RRC configuration information includes an uplink transmission scheme using multiple antenna panels for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes the transmission of a single transport block (TB) without repetition, the transmission of a single TB with repetition, or the transmission of multiple TBs based on user equipment (UE) capabilities; receiving a single downlink control information (DCI) specifying uplink resource allocation for multiple physical uplink shared channels (PUSCHs); and transmitting the multiple PUSCHs.

[0180] Embodiment 2 is a method according to embodiment 1, which may optionally include: if the RRC configuration information includes an uplink transmission scheme for simultaneously sending multiple PUSCHs using the multiple UE antenna panels, including the transmission of the single transport block (TB) without repetition, then the single DCI indication is used to calculate the resources of the single TB on all frequency division multiplexing (FDM) resources and spatial division multiplexing (SDM) resources of the uplink resource allocation to be used for sending the single TB using the multiple UE antenna panels, including an indication of the same modulation and coding scheme (MCS) and the same number of layers used for the single TB.

[0181] Embodiment 3 is a method according to embodiment 2, which may optionally include: the uplink resource allocation specifies a time slot-based repetition with a redundant version (RV) index for the UE per repetition opportunity for beam hopping on time domain repetition using the multiple UE antenna panels.

[0182] Embodiment 4 is a method according to embodiment 2, which may optionally include: if the RRC configuration information includes an uplink transmission scheme for simultaneously sending multiple PUSCHs using the multiple UE antenna panels, including the transmission of the single transport block (TB) without repetition, then the single DCI indication is used to calculate the resources of the single TB on all frequency division multiplexing (FDM) resources and spatial division multiplexing (SDM) resources of the uplink resource allocation to be used for sending the single TB using the multiple UE antenna panels, including an indication of the same modulation and coding scheme (MCS) and the same number of layers used for the single TB.

[0183] Embodiment 5 is a method according to embodiment 1 or 2, which may optionally include: when a single MCS bit field and number of layers are applied to the multiple UE antenna panels, calculating the single TB using the total number of PRBs allocated on all UE antenna panels among the multiple UE antenna panels.

[0184] Embodiment 6 is a method according to embodiment 2, and the method may optionally include: when the MCS and the number of layers are indicated separately for each of the multiple UE antenna panels, the single TB calculation is based on a separate TB calculation for each of the multiple UE antenna panels using the number of allocated PRBs associated with each of the multiple UE antenna panels.

[0185] Embodiment 7 is a method according to embodiment 2, which may optionally include: PUSCH mapping to resource elements is determined by the assigned PRB corresponding to each beam of its corresponding PUSCH in the multiple PUSCHs.

[0186] Embodiment 8 is a method according to embodiment 2, which may optionally include: sending information on the multiple PUSCH resources is performed as part of sending multiple TBs using multiple time slots with inter-slot hopping, wherein each PUSCH of the multiple PUSCHs is sent on a different UE antenna panel.

[0187] Embodiment 9 is a method according to embodiment 1, which may optionally include: if the RRC configuration information includes an uplink transmission scheme including the transmission of the single TB for simultaneously transmitting multiple PUSCHs using the multiple UE antenna panels, then the single TB is repeatedly transmitted in one or both of frequency and space.

[0188] Embodiment 10 is a method according to embodiment 9, which may optionally include: if the RRC configuration information includes an uplink transmission scheme for simultaneously sending multiple PUSCHs using the multiple UE antenna panels, including the transmission of a repeated single TB, wherein the uplink resource allocation specifies the same resources, MCS and number of layers for each repetition using a different code rate for the single TB for each PUSCH per beam.

[0189] Embodiment 11 is a method according to embodiment 10, which may optionally include: the uplink resource allocation specifies a slot-based repetition with a redundancy version (RV) index without time domain repetition for the repetition of each PUSCH in the multiple PUSCHs.

[0190] Embodiment 12 is a method according to embodiment 10, which may optionally include: the uplink resource allocation specifies a time slot-based repetition with a redundant version (RV) index for the UE per repetition opportunity for beam hopping on a time domain repetition using the multiple UE antenna panels, wherein a first RV for a PUSCH repetition associated with a first UE antenna panel is based on a count of PUSCH transmission opportunities associated with the first UE antenna panel, and a second RV associated with a second UE antenna panel is based on the first RV and an offset.

[0191] Embodiment 13 is a method according to embodiment 1 or 9, which may optionally include: the calculation of the TB indicated by the single DCI is based on the RE, MCS and number of layers associated with each beam in the beams to be transmitted by the multiple UE antenna panels or the TB with the maximum transport block size (TBS) in the TB calculated for each UE antenna panel, or the TB with the minimum TBS in the TB calculated for each UE antenna panel.

[0192] Embodiment 14 is a method according to embodiment 9, which may optionally include: PUSCH mapping to resource elements is determined by the assigned PRB corresponding to each beam of its corresponding PUSCH in the multiple PUSCHs.

[0193] Embodiment 15 is a method according to embodiment 1, which may optionally include: if the RRC configuration information includes an uplink transmission scheme including TBs for simultaneously sending multiple PUSCHs using the multiple UE antenna panels, then the uplink resource allocation indicates which TB among the multiple TBs is associated with which PUSCH among the multiple PUSCHs, including indicating the MCS and number of layers used for the TBs.

[0194] Embodiment 16 is a method according to embodiment 15, which may optionally include: the uplink resource allocation includes a downlink control information (DCI) bit field to specify one or more of the MCS, NDI and RV associated with each of the multiple codewords.

[0195] Embodiment 17 is a method according to embodiment 15, which may optionally include: the uplink resource allocation specifies a slot-based repetition with a redundancy version (RV) index for a repetition opportunity associated with each UE antenna panel for the plurality of PUSCHs.

[0196] Embodiment 18 is a method according to embodiment 1 or 15, which may optionally include: the single TB calculation is based on the calculation of a separate TB calculation for each UE antenna panel in the UE antenna panel, wherein n of each TB is calculated separately for each UE antenna panel. PRB is the number of allocated PRBs associated with each UE antenna panel, and the code rate, modulation order and rank used to calculate each TB are obtained by the MCS and number of layers calculated for each individual TB.

[0197] Embodiment 19 is a method according to embodiment 1, which may optionally include: the RRC configuration information includes an uplink transmission scheme specifying multiple transmission schemes, and further wherein the single DCI includes an indication of one of the multiple transmission schemes.

[0198] Embodiment 20 is a method according to embodiment 1, which may optionally include: sending information on the multiple PUSCH resources is performed as part of sending multiple TBs using multiple time slots with inter-slot hopping, wherein each PUSCH of the multiple PUSCHs is sent on a different UE antenna panel.

[0199] Embodiment 21 is a baseband processor configured to perform any one of the operations described in Embodiments 1 to 20.

[0200] Embodiment 22 is a UE, which is configured to perform any one of the operations described in embodiments 1 to 20.

[0201] Embodiment 23 is one or more non-transitory computer-readable storage media, which have instructions stored thereon, and when the instructions are executed by a UE or a baseband processor, any one of the operations described in embodiments 1 to 20 is performed.

[0202] Embodiment 24 is a method performed by a base station, the base station comprising a processor (or processing circuit) configured to perform operations, the operations comprising: transmitting RRC configuration information, wherein the RRC configuration information comprises an uplink transmission scheme using multiple antenna panels for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels comprises transmission of a single transport block (TB) without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on user equipment (UE) capabilities; transmitting a single downlink control information (DCI) specifying uplink resource allocation for multiple physical uplink shared channels (PUSCHs); and sending the single DCI to the UE.

[0203] Embodiment 25 is a method according to embodiment 24, which may optionally include: if the RRC configuration information includes an uplink transmission scheme for simultaneously sending multiple PUSCHs using the multiple UE antenna panels, including the transmission of the single TB without repetition, then the single DCI indication is used to calculate the resources of the single TB on all frequency division multiplexing (FDM) resources and spatial division multiplexing (SDM) resources of the uplink resource allocation to be used for sending the single TB using the multiple UE antenna panels, including an indication of the same modulation and coding scheme (MCS) and the same number of layers used for the single TB.

[0204] Embodiment 26 is a method according to embodiment 25, which may optionally include: the uplink resource allocation specifies a time slot-based repetition with a redundant version (RV) index for the UE per repetition opportunity for beam hopping on time domain repetition using the multiple UE antenna panels.

[0205] Embodiment 27 is a method according to embodiment 25, which may optionally include: if the RRC configuration information includes an uplink transmission scheme for simultaneously sending multiple PUSCHs using the multiple UE antenna panels, including the transmission of the single TB without repetition, then the single DCI indication is used to calculate the resources of the single TB on all frequency division multiplexing (FDM) resources and spatial division multiplexing (SDM) resources of the uplink resource allocation to be used for sending the single TB using the multiple UE antenna panels, including an indication of the modulation and coding scheme (MCS) and number of layers for each UE antenna panel for the single TB.

[0206] Embodiment 28 is a method according to embodiment 24 or 25, which may optionally include: when a single MCS bit field and number of layers are applied to the multiple UE antenna panels, calculating the single TB using the total number of PRBs allocated on all UE antenna panels among the multiple UE antenna panels.

[0207] Embodiment 29 is a method according to embodiment 26, which may optionally include: when the MCS and the number of layers are indicated separately for each of the multiple UE antenna panels, the single TB calculation is based on a separate TB calculation for each of the multiple UE antenna panels using the number of allocated PRBs associated with each of the multiple UE antenna panels.

[0208] Embodiment 30 is a method according to embodiment 24, which may optionally include: PUSCH mapping to resource elements is determined by the assigned PRB corresponding to each beam used for its corresponding PUSCH in the multiple PUSCHs.

[0209] Embodiment 31 is a method according to embodiment 25, which may optionally include: wherein sending information on the multiple PUSCH resources is performed as part of sending multiple TBs using multiple time slots with inter-slot hopping, wherein each PUSCH of the multiple PUSCHs is sent on a different UE antenna panel.

[0210] Embodiment 32 is a method according to embodiment 24, which may optionally include: if the RRC configuration information includes an uplink transmission scheme including the transmission of the single TB for simultaneously transmitting multiple PUSCHs using the multiple UE antenna panels, then the single TB is repeatedly transmitted in one or both of frequency and space.

[0211] Embodiment 33 is a method according to embodiment 32, which may optionally include: if the RRC configuration information includes an uplink transmission scheme for simultaneously sending multiple PUSCHs using the multiple UE antenna panels including the transmission of a repeated single transport block (TB), then the uplink resource allocation specifies the same resources, MCS and number of layers using different code rates for each repetition of the single TB for each PUSCH per beam.

[0212] Embodiment 34 is a method according to embodiment 33, which may optionally include: the uplink resource allocation specifies a slot-based repetition with a redundant version (RV) index without time domain repetition for the repetition of each PUSCH in the multiple PUSCHs.

[0213] Embodiment 35 is a method according to embodiment 33, which may optionally include: the uplink resource allocation specifies a time slot-based repetition with a redundant version (RV) index for the UE per repetition opportunity for beam hopping on a time domain repetition using the multiple UE antenna panels, wherein a first RV for a PUSCH repetition associated with a first UE antenna panel is based on a count of PUSCH transmission opportunities associated with the first UE antenna panel, and a second RV associated with a second UE antenna panel is based on the first RV and an offset.

[0214] Embodiment 36 is a method according to embodiment 24 or 32, the method may optionally include: the single DCI indicating that the calculation of the TB is based on the RE, MCS and number of layers associated with each of the beams to be transmitted by the plurality of UE antenna panels, the TB with the maximum transport block size (TBS) in the TB calculated for each UE antenna panel, or the TB with the minimum TBS in the TB calculated for each UE antenna panel. .

[0215] Embodiment 37 is a method according to embodiment 32, which may optionally include: PUSCH mapping to resource elements is determined by the assigned PRB corresponding to each beam of its corresponding PUSCH in the multiple PUSCHs.

[0216] Embodiment 38 is a method according to embodiment 24, which may optionally include: if the RRC configuration information includes an uplink transmission scheme including the transmission of multiple TBs for simultaneously sending multiple PUSCHs using the multiple UE antenna panels, then the uplink resource allocation indicates which TB of the multiple TBs is associated with which PUSCH of the multiple PUSCHs, including indicating the MCS and number of layers used for the TBs.

[0217] Embodiment 39 is a method according to embodiment 38, which may optionally include: the uplink resource allocation includes a downlink control information (DCI) bit field to specify one or more of the MCS, NDI and RV associated with each of the multiple codewords.

[0218] Embodiment 40 is a method according to embodiment 38, which may optionally include: the uplink resource allocation specifies a time slot-based repetition with a redundancy version (RV) index for a repetition opportunity associated with each UE antenna panel for the plurality of PUSCHs.

[0219] Embodiment 41 is a method according to embodiment 24 or 38, which method may optionally include: the single TB calculation is based on the calculation of the individual TB calculation for each UE antenna panel in the UE antenna panel, wherein n for each individual TB calculation for each UE antenna panel is PRB is the number of allocated PRBs associated with each UE antenna panel, and the code rate, modulation order and rank calculated for each individual TB are obtained by the MCS and number of layers calculated for each individual TB.

[0220] Embodiment 42 is a method according to embodiment 24, which may optionally include: the RRC configuration information includes an uplink transmission scheme specifying multiple transmission schemes, and further wherein the single DCI includes an indication of one of the multiple transmission schemes.

[0221] Embodiment 43 is a baseband processor of a base station, and the baseband processor is configured to perform any one of the operations described in embodiments 24 to 42.

[0222] Embodiment 44 is a base station, which is configured to perform any one of the operations described in Embodiments 24 to 42.

[0223] Embodiment 45 is one or more non-transitory computer-readable storage media of a base station, wherein the one or more non-transitory computer-readable storage media have instructions stored thereon, which, when executed by a UE or a baseband processor, cause any one of the operations described in embodiments 24 to 42 to be performed.

[0224] Part of the above content can be realized by using logic circuits such as dedicated logic circuits or by using a microcontroller or other forms of processing cores for executing program code instructions. Thus, the process taught by the above discussion can be performed using program code such as machine executable instructions, which enable the machine to execute these instructions to perform certain functions. In this context, a "machine" can be a machine that converts intermediate form (or "abstract") instructions into processor-specific instructions (e.g., abstract execution environments such as "virtual machines" (e.g., Java virtual machines), interpreters, common language runtimes, high-level language virtual machines, etc.), and / or an electronic circuit that is set on a semiconductor chip (e.g., a "logic circuit" implemented using transistors), which is designed to execute instructions, and the processor is such as a general-purpose processor and / or a dedicated processor. The process taught by the above discussion can also be performed by (as a substitute for a machine or in combination with a machine) an electronic circuit that is designed to execute a process (or a part thereof) without executing program code.

[0225] The present invention also relates to an apparatus for performing the operations described herein. The apparatus may be specially constructed for the required purposes, or may include a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as but not limited to any type of disk, including floppy disks, optical disks, CD-ROMs and magneto-optical disks, read-only memories (ROMs), RAMs, EPROMs, EEPROMs, magnetic or optical cards, or any type of medium suitable for storing electronic instructions, and each is coupled to a computer system bus.

[0226] A machine-readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, machine-readable media include read-only memory ("ROM"); random access memory ("RAM"); magnetic disk storage media; optical storage media; flash memory devices; and the like.

[0227] Articles of manufacture may be used to store program code. Articles of manufacture storing program code may be implemented as, but not limited to, one or more memories (e.g., one or more flash memories, random access memories (static, dynamic, or other)), optical disks, CD-ROMs, DVD ROMs, EPROMs, EEPROMs, magnetic or optical cards, or other types of machine-readable media suitable for storing electronic instructions. Program code may also be downloaded from a remote computer (e.g., a server) to a requesting computer (e.g., a client) by means of a data signal contained in a propagation medium (e.g., via a communication link (e.g., a network connection)).

[0228] The foregoing detailed description has been presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are tools used by those skilled in the art of data processing, and these tools can also most effectively convey the substance of their work to other technicians in the field. An algorithm is here and generally refers to a self-consistent sequence of operations leading to a desired result. These operations are those that require physical manipulation of physical quantities. Typically, but not necessarily, these quantities are in the form of electrical or magnetic signals that can be stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc., primarily for general reasons.

[0229] It should be borne in mind, however, that all of these and similar terms are associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless otherwise specifically stated, it will be apparent from the above discussion that discussions throughout this specification using terms such as "select," "determine," "receive," "form," "group," "aggregate," "generate," "remove," etc., will be understood to refer to actions and processes on a computer system or similar electronic computing device that manipulates data represented as physical (electronic) quantities in the computer system's registers and memories and converts it into other data similarly represented as physical quantities in the computer system's memories or registers or other such information storage, transmission, or display devices.

[0230] The process presented herein and display are not inherently relevant to any particular computer or other device. According to the teaching content of this paper, various general-purpose systems can be used together with programs, or it can be proved that it is convenient to construct a more special-purpose device for performing the operation. According to the description below, the required structure for various these systems will be apparent. In addition, the present invention is not described with reference to any specific programming language. It should be appreciated that multiple programming languages ​​can be used to realize the teaching content of the present invention as described herein.

[0231] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of the authorized use should be clearly stated to users.

[0232] The foregoing discussion describes only some exemplary embodiments of the present invention. Those skilled in the art will readily recognize from these discussions, drawings and claims that various modifications can be made without departing from the spirit and scope of the present invention.

Claims

1. A baseband processor, the baseband processor being configured to perform operations including: receiving RRC configuration information from a base station, wherein the RRC configuration information includes an uplink transmission scheme using multiple antenna panels, the uplink transmission scheme for simultaneously transmitting multiple physical uplink shared channels (PUSCHs) using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes transmission of a single transport block (TB) without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on user equipment (UE) capabilities; receiving a single downlink control information (DCI) specifying uplink resource allocations for a plurality of PUSCHs; and The multiple PUSCHs are sent.

2. The baseband processor according to claim 1, in, If the RRC configuration information includes an uplink transmission scheme for simultaneously transmitting multiple PUSCHs using the multiple UE antenna panels, including the transmission of the single transport block (TB) without repetition, the single DCI indicates the following resources, which are used to calculate the single TB on all frequency division multiplexing (FDM) resources and spatial division multiplexing (SDM) resources of the uplink resource allocation to be used for transmitting the single TB using the multiple UE antenna panels, including an indication of the same modulation and coding scheme (MCS) and the same number of layers used for the single TB.

3. The baseband processor according to claim 1 or 2, in, When a single MCS bit field and number of layers are applied to the multiple UE antenna panels, the single TB is calculated using the total number of PRBs allocated on all UE antenna panels in the multiple UE antenna panels, and wherein the PUSCH mapping to resource elements is determined based on the assigned PRBs corresponding to each beam used for its corresponding PUSCH in the multiple PUSCHs.

4. The baseband processor according to claim 1, in, If the RRC configuration information includes an uplink transmission scheme for transmitting the single TB including multiple PUSCHs simultaneously using the multiple UE antenna panels, the single transport block TB is transmitted with repetitions in one or both of frequency and space, and wherein, if the uplink resource allocation includes resources for transmitting the single transport block (TB) simultaneously with repetitions using multiple UE antenna panels, wherein the uplink resource allocation specifies the same resources, MCS and number of layers for the single TB for each PUSCH per beam, wherein a different code rate is used for each repetition.

5. The baseband processor of claim 10, wherein the uplink resource allocation specifies a slot-based repetition with a redundant version (RV) index for repetition of each of the multiple PUSCHs without time domain repetition, or specifies the slot-based repetition with the RV index for the UE per repetition opportunity for beam hopping on time domain repetition using the multiple UE antenna panels, wherein a first RV for a PUSCH repetition associated with a first UE antenna panel is based on a count of PUSCH transmission opportunities associated with the first UE antenna panel, and a second RV associated with a second UE antenna panel is based on the first RV and an offset.

6. A baseband processor according to claim 1 or 4, wherein the calculation of the single DCI indicating the TB is based on the RE, MCS and number of layers associated with each of the beams to be transmitted by the multiple UE antenna panels or a TB with a maximum transport block size (TBS) in the TB calculated for each UE antenna panel, or a TB with the minimum TBS in the TB calculated for each UE antenna panel.

7. The baseband processor according to claim 4, in, The PUSCH mapping to resource elements is determined according to the assigned PRBs corresponding to each beam for its corresponding PUSCH among the plurality of PUSCHs.

8. The baseband processor according to claim 1, in, If the RRC configuration information includes an uplink transmission scheme including transmission of the multiple transport blocks (TBs) for simultaneously transmitting multiple PUSCHs using the multiple UE antenna panels, the uplink resource allocation indicates which of the multiple TBs is associated with which of the multiple PUSCHs, including indicating the MCS and number of layers used for the TBs.

9. The baseband processor of claim 8, wherein the uplink resource allocation comprises a downlink control information (DCI) bit field to specify one or more of an MCS, an NDI, and a RV associated with each of a plurality of codewords.

10. The baseband processor of claim 8, wherein the uplink resource allocation specifies slot-based repetition with a redundancy version (RV) index for repetition opportunities associated with each UE antenna panel for the plurality of PUSCHs.

11. The baseband processor of claim 1 or 8, wherein the single TB calculation is based on calculation of a separate TB calculation for each of the UE antenna panels, wherein n of each TB is calculated separately for each UE antenna panel. PRB is the number of allocated PRBs associated with each UE antenna panel, and the code rate, modulation order and rank used to calculate each TB are obtained by the MCS and number of layers calculated for each individual TB.

12. The baseband processor of claim 1, wherein the RRC configuration information includes an uplink transmission scheme specifying a plurality of transmission schemes, and further wherein the single DCI includes an indication of one of the plurality of transmission schemes.

13. The baseband processor of claim 1, wherein sending information on the plurality of PUSCH resources is performed as part of sending a plurality of TBs using a plurality of time slots with inter-slot frequency hopping, wherein each of the plurality of PUSCHs is sent on a different UE antenna panel.

14. A method performed by a UE, the method include: receiving RRC configuration information from a base station, wherein the RRC configuration information includes an uplink transmission scheme using multiple antenna panels, the uplink transmission scheme for simultaneously transmitting multiple PUSCHs using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes transmission of a single transport block (TB) without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on user equipment (UE) capabilities; receiving a single downlink control information (DCI) specifying uplink resource allocations for a plurality of physical uplink shared channels (PUSCHs); and The multiple PUSCHs are sent.

15. The method according to claim 14, in, If the RRC configuration information includes an uplink transmission scheme including transmission of multiple transport blocks (TBs) for simultaneously transmitting multiple PUSCHs using the multiple UE antenna panels, the uplink resource allocation indicates which of the multiple TBs is associated with which of the multiple PUSCHs, including indicating the MCS and number of layers used for the TBs.

16. The method of claim 14, wherein the single TB calculation is based on calculation of a separate TB calculation for each of the UE antenna panels according to 3GPP TS 38.214 Section 6.1.4.2, wherein n of each TB is calculated separately for each UE antenna panel. PRB is the number of allocated PRBs associated with each UE antenna panel, and the code rate, modulation order and rank used to calculate each TB are obtained by the MCS and number of layers calculated for each individual TB.

17. The method according to claim 14, in, When a single MCS bit field and number of layers are applied to the multiple UE antenna panels, the single TB is calculated according to Section 6.1.4.2 of 3GPP TS 38.214 using the total number of PRBs allocated on all UE antenna panels in the multiple UE antenna panels, and wherein the PUSCH mapping to resource elements is determined by the assigned PRBs corresponding to each beam for its corresponding PUSCH in the multiple PUSCHs.

18. A base station, the base station comprising a processor (or processing circuit) configured to perform an operation, the operation include: transmitting RRC configuration information, wherein the RRC configuration information includes an uplink transmission scheme using multiple antenna panels for simultaneously transmitting multiple physical uplink shared channels (PUSCHs) using multiple UE antenna panels, wherein the uplink transmission scheme using multiple antenna panels includes transmission of a single transport block (TB) without repetition, transmission of a single TB with repetition, or transmission of multiple TBs based on user equipment (UE) capabilities; generating a single downlink control information (DCI) specifying uplink resource allocations for a plurality of PUSCHs; and The single DCI is sent to the UE.

19. The base station according to claim 18, in, If the RRC configuration information includes an uplink transmission scheme for simultaneously transmitting multiple PUSCHs using the multiple UE antenna panels, including the transmission of the multiple transport blocks (TBs), the uplink resource allocation indicates which of the multiple TBs is associated with which of the multiple PUSCHs, including indicating the MCS and the number of layers used for the TBs, and wherein the uplink resource allocation includes a downlink control information (DCI) bit field to specify one or more of the MCS, NDI and RV associated with each of the multiple codewords.

20. The base station of claim 18 or 19, wherein the single TB calculation is based on calculation of a separate TB calculation for each of the UE antenna panels according to 3GPP TS 38.214 Section 6.1.4.2, wherein n of each TB is calculated separately for each UE antenna panel. PRB is the number of allocated PRBs associated with each UE antenna panel, and the code rate, modulation order and rank used to calculate each TB are obtained by the MCS and number of layers calculated for each individual TB.

Images