Single DCI and multi-panel simultaneous PUSCH indication

By using the TDRA and FDRA bit fields in a single DCI in a 5G wireless network to specify resource allocation for multiple PUSCHs, the inefficiency problem of UE multi-panel simultaneous transmission in 5G network is solved, and resource allocation is simplified and efficiency improvement is achieved.

CN119096640APending Publication Date: 2024-12-06APPLE INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202280095437.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2022-04-29
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In 5G wireless networks, it is difficult for the prior art to effectively use a single downlink control information (DCI) to simultaneously send multiple physical uplink shared channels (PUSCH) to multiple user equipment (UE) antenna panels, resulting in resource allocation efficiency Low and complexity increase.

Method used

By configuring a baseband processor in the base station, using the time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA) bit fields in a single DCI to specify resource allocation for multiple PUSCHs, and supports UE's multi-panel transmission at the same time. Specific methods It includes using TDRA or FDRA bit fields to represent airspace or frequency domain resources under SDM or FDM resources, realizing the simultaneous transmission of multiple PUSCHs.

Benefits of technology

It improves resource allocation efficiency, simplifies the UE's multi-panel simultaneous transmission process, reduces system complexity and delay, and improves the resource utilization and user experience of 5G networks.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096640A_ABST
    Figure CN119096640A_ABST
Patent Text Reader

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 configuration information from a base station, where the configuration information includes a single downlink control information (DCI) specifying uplink resource allocations for a plurality of physical uplink shared channels (PUSCHs), where the single downlink control information (DCI) specifies uplink resource allocations for the plurality of physical uplink shared channels (PUSCHs); wherein the uplink resource allocation for the plurality of PUSCHs is specified for each user equipment (UE) antenna panel. Once configured, the baseband processor simultaneously transmits the plurality of PUSCHs via the plurality of antenna panels, where one of the plurality of PUSCHs is transmitted on a different one of the plurality of PUSCHs.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates generally to wireless technologies, and more particularly to using a single downlink control information (DCI) to perform 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 are described 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.

[0004] In some embodiments, a baseband processor is configured to perform operations including the following: receiving configuration information from a base station, wherein the configuration information includes a single downlink control information (DCI), the single downlink control information (DCI) specifying uplink resource allocation for multiple physical uplink shared channels (PUSCHs), wherein the uplink resource allocation for the multiple PUSCHs is specified for each user equipment (UE) antenna panel, when the UE is configured to perform simultaneous multi-panel transmission across spatial domain multiplexing (SDM) resources, one or more time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA) bit fields in the single DCI are used to indicate spatial resources, or when the UE is configured to perform simultaneous multi-panel transmission across frequency domain multiplexing (FDM) resources or across both FDM resources and SDM resources, a time domain resource allocation (TDRA) bit field in the single DCI is used to indicate time domain resource allocation. In some embodiments, the baseband processor also performs operations including: based on the configuration information, configuring the UE to simultaneously send multiple PUSCHs using multiple antenna panels of the UE; and simultaneously sending the multiple PUSCHs via the multiple antenna panels, wherein one PUSCH among the multiple PUSCHs is sent on a different PUSCH among the multiple PUSCHs.

[0005] In some other embodiments, a base station includes a processor (or processing circuit) configured to perform operations including: generating configuration information for configuring a user equipment (UE), wherein the configuration information includes a single downlink control information (DCI), the single downlink control information (DCI) specifies uplink resource allocations for multiple physical uplink shared channels (PUSCHs), wherein the uplink resource allocations for the multiple PUSCHs are specified for each user equipment (UE) antenna panel, when the UE is configured to perform simultaneous multi-panel transmission across spatial domain multiplexing (SDM) resources, one or more time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA) bit fields in the single DCI are used to indicate spatial resources, or when the UE is configured to perform simultaneous multi-panel transmission across frequency domain multiplexing (FDM) resources or across both FDM resources and SDM resources, a time domain resource allocation (TDRA) bit field in the single DCI is used to indicate time domain resource allocation. The base station is also configured to send the single DCI to the UE.

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

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

[0008] Figure 1 An example wireless communication system is illustrated in accordance with some embodiments.

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

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

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

[0012] Figure 5 An example block diagram of a cellular communication circuit according to some embodiments is illustrated.

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

[0014] Figure 6BExamples of PUSCHs completely overlapping in frequency resources allocated to PUSCHs to be simultaneously transmitted, non-overlapping in frequency resources allocated to PUSCHs to be simultaneously transmitted, and partially overlapping in frequency resources allocated to PUSCHs to be simultaneously transmitted are illustrated.

[0015] Figure 7 is a flow chart of some implementations of a process for configuring a UE.

[0016] Figure 8 is a flow chart of one embodiment of a process by which network equipment configures a UE. DETAILED DESCRIPTION

[0017] Methods and apparatus for performing resource allocation for multiple panels of multiple physical uplink shared channels (PUSCHs) simultaneously using a single downlink control information (DCI) are described. In the following description, many 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 practiced without these specific details. In other cases, well-known components, structures, and techniques have not been shown in detail to avoid obscuring the understanding of this description.

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

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

[0020] The processes depicted in the following figures are performed by processing logic that 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 sequentially.

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

[0022] Methods and apparatus for a device that uses a single downlink control information (DCI) to simultaneously transmit multiple panels of multiple physical uplink shared channels (PUSCHs) to perform resource allocation are described. In one embodiment, 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. The device further selects component carriers (CCs) from the wireless link and groups them and determines a virtual CC from a group of selected CCs. The device can also perform physical downlink resource mapping based on an aggregated resource matching pattern of the CC group.

[0023] Figure 1 A simplified example 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.

[0024] As shown, the example 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 of the user equipments may be referred to as a "user equipment" (UE) in this document. Therefore, the user equipment 106 is referred to as a UE or a UE device.

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

[0026] 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), which are 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".

[0027] As shown, base station 102A may also be configured to communicate with network 100 (e.g., a cellular service provider's core network, 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 telecommunication capabilities, such as voice, SMS, and / or data services.

[0028] 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 services to UE 106A to UE 106N and similar devices over a geographic area via one or more cellular communication standards.

[0029] Thus, although base station 102A may function as Figure 1 106A to 106N, 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 to 102N 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 any other variety of other granularity of cells providing service area sizes. For example, in Figure 1 The base stations 102A to 102B illustrated in FIG. 1 may be macro cells, while the base station 102N may be a micro cell. Other configurations are also possible.

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

[0031] It should be noted that the UE 106 is capable of communicating using multiple wireless communication standards. For example, the UE 106 can 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 can 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.

[0032] Figure 2 A user equipment 106 (e.g., one of devices 106A-106N) is illustrated in accordance with some embodiments in communication with base station 102. 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.

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

[0034] 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. In general, 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 parts of a receive chain and / or a transmit chain between multiple wireless communication technologies such as those discussed above.

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

[0036] Figure 3 —UE block diagram

[0037] Figure 3 An example 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 the embodiment, in addition to other devices, the communication device 106 can be a user equipment (UE) device, a mobile device or a mobile station, a wireless device or a wireless station, a desktop computer or a computing device, a mobile computing device (such as a laptop computer, a notebook or a portable computing device), a tablet computer and / or a combination of devices. As shown in the figure, 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), and the system on a chip (SOC) can include parts for various purposes. Alternatively, the group of components 300 can be implemented as a separate component or a group of components for various purposes. This group of components 300 can be (for example, communicatively; directly or indirectly) coupled to various other circuits of the communication device 106.

[0038] 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 TM In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.

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

[0040] 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 radio technologies (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.

[0041] The communication device 106 may also include and / or be configured for use with one or more user interface elements. The user interface element 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.

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

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

[0044] 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 the uplink resource allocations for the multiple PUSCHs are specified for each user equipment (UE) antenna panel. The wireless device may also be configured to send information on the multiple PUSCHs simultaneously via the 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.

[0045] As described herein, the communication device 106 may include hardware and software components for implementing the above-described features for UL data for time division multiplexing NSA NR operation. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium), the processor 302 of the communication device 106 may be configured to implement part or all of the feature parts described herein. Alternatively (or in addition), the processor 302 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 300, 304, 306, 310, 320, 329, 330, 340, 345, 350, 360, the processor 302 of the communication device 106 may be configured to implement part or all of the feature parts described herein.

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

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

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

[0049] Figure 4 An example 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).

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

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

[0052] In some embodiments, base station 102 may be a next generation base station, such as 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.

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

[0054] The base station 102 may be configured to perform wireless communications using multiple wireless communication standards. In some cases, 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 one 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.).

[0055] As further described later herein, BS102 may include hardware and software components for implementing or supporting the specific implementation of the feature parts described herein. The processor 404 of the 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, the 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 thereto), in combination with one or more of the other components 430, 432, 434, 440, 450, 460, 470, the processor 404 of the BS102 may be configured to implement or support a specific implementation of part or all of the feature parts described herein.

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

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

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

[0059] Figure 5 An example 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.

[0060] Cellular communication circuitry 330 may be (eg, communicatively; directly or indirectly) coupled to one or more antennas, such as ( Figure 3 335a to 335b and antenna 336 as shown in FIG. 335b. 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, the cellular communication circuit 330 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT (e.g., such as LTE or LTE-A), and the modem 520 may be configured for communication according to a second RAT (e.g., such as 5GNR).

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

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

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

[0064] As described herein, the modem 510 may include hardware and software components for implementing the above features, or for performing resource allocation for simultaneous transmission of multiple panels for multiple PUSCHs using a single DCI and various other techniques described herein. The processor 512 may be configured to implement part or all of the feature parts 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 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 part or all of the feature parts described herein.

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

[0066] As described herein, the modem 520 may include hardware and software components for implementing the above-described features for performing resource allocation for simultaneous transmission of multiple panels for multiple PUSCHs using a single DCI and various other techniques described herein. The processor 522 may be configured to implement part or all of the feature parts 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 thereto), 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 thereto), 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.

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

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

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

[0070] 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, if scheduled by a single DCI, PDSCH resources associated with different downlink (DL) beams (spatial Rx filters) are transmitted via frequency division multiplexing (FDM). As set out in Section 5.1 of 3GPP TS 38.214, 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 a 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 a non-overlapping frequency domain resource allocation. If multiple DCIs, called multi-DCI (m-DCI), are used for scheduling, the two PDSCH receptions can be full / partial / non-overlapping PDSCHs in the time and frequency domains. In this case, the PDCCHs that schedule the two PDSCHs are associated with different ControlResourceSets with different coresetPoolIndex values.

[0071] In NR Release 17, a UE may 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 used for TDM. In order to send multiple repetitions of the same TB on different UL beams, when the UE is configured to have two sounding reference signal (SRS) resource sets used as codebooks (or two SRS resource sets used as non-codebooks), a beam indication is provided by 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 may have different antenna ports, transmit 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; the repetitions occur in different time slots.

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

[0073] In NR Release 18, one of the goals is to study and specify simultaneous multi-panel UL transmissions when needed, 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.

[0074] In some embodiments, the UE is configured to use multiple antenna panels on the UE to perform multiple PUSCH transmissions simultaneously. 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 the base station.

[0075] In some embodiments, the configuration information is transmitted from the base station to the UE using a single DCI (s-DCI). In some embodiments, the configuration information includes resource information corresponding to the resource allocation to indicate to the UE the resources used for PUSCH transmission. The determination of the resource allocation is performed 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.

[0076] In some embodiments, resource allocation is for multiple different situations in frequency and / or space. For example, in one case, resource allocation specifies resources for sending a single PUSCH opportunity on different panels. In other words, the specified resources are used to send a single TB (i.e., the same data) simultaneously on different UE antenna panels. It should be noted that in some embodiments, sending a single TB on different UE antenna panels involves sending different decoding bits from the same TB on different panels. In some other embodiments, sending a single TB on different UE antenna panels involves sending the same data on different panels. For example, the same data can be modulated in different ways and repeatedly sent, so that one passes through layer 1 and the other 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.

[0077] In another case, the resource allocation specifies resources for repeating the same TB on different panels. In this case, the data sent 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 sending two different codewords.

[0078] Therefore, in some embodiments, a combination of higher layer parameters and a dynamic indication of resource allocation for handling one of the above cases is used to indicate resource allocation 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 will 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.

[0079] After providing resource allocation, the UL beam that the UE will use to send multiple PUSCHs on different panels is determined. Fig. 6A A data flow diagram illustrating some embodiments of a single downlink control information (DCI) resource allocation for supporting multi-panel simultaneous transmission of multiple physical uplink shared channels (PUSCHs) by a UE. Fig. 6A , the base station 601 sends a single DCI to the UE 602. In some embodiments, the single DCI is sent as part of the PDCCH 610. The single DCI contains an uplink resource allocation for resources that the UE 602 will use to send multiple PUSCHs on different panels. In response to the single DCI with the uplink resource allocation, the UE 602 sends user data 611 to the base station 601 using its antenna panel 1, sends user data 612 to the base station 601 using its antenna panel 2, ..., sends user data 613 to the base station 601 using its antenna panel N. In some embodiments, the user data 611 to the user data 613 are sent simultaneously by the UE 602 using the PUSCH. Although Fig. 6A UE 602 is shown using N panels to send up to N PUCSH transmissions 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, one PUCSH is sent to base station 601, and another PUSCH is sent to another base station.

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

[0081] 1.s-DCI: Single DCI

[0082] 2.MPSTx: Multi-panel simultaneous transmission, where multiple PUSCHs are sent simultaneously on multiple UE antenna panels

[0083] 3.sdmMPTx: Multi-panel simultaneous transmission, where spatial multiplexing is used to send multiple PUSCHs simultaneously on multiple UE antenna panels

[0084] 4.fdmMPTx: Multi-panel simultaneous transmission, where frequency domain multiplexing is used to send multiple PUSCHs simultaneously on multiple UE antenna panels

[0085] 5.1sMPTx: Single (no repetition) transmission of a single transport block (TB) with multi-panel simultaneous transmission, where multiple PUSCHs are transmitted simultaneously on multiple UE antenna panels

[0086] 6. ReMPTx: Repetition (in frequency and / or space) of a single TB with multi-panel simultaneous transmission, where multiple PUSCHs are transmitted simultaneously on multiple UE antenna panels

[0087] There are a variety of resource allocation schemes that can be used as part of 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), wherein the uplink resource allocations for the multiple PUSCHs are specified for each user equipment (UE) antenna panel.

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

[0089] 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 sdmMPTx parameter, multi-panel simultaneous transmission is performed across SDM resources. In this case, the TDRA and FDRA bit fields 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 situation is illustrated where PUSCH1 represents time and frequency resources associated with panel 1 and PUSCH2 represents time and frequency resources associated with panel 2, with one opportunity transmitted by panel 1 and one opportunity transmitted by panel 2. Thus, the s-DCI schedules those SDM time and frequency resources for both panels.

[0090] In some embodiments, the uplink resource allocation for the multiple PUSCHs is specified in the following manner: when the UE is configured to perform simultaneous multi-panel transmission across frequency domain multiplexing (FDM) resources or across both FDM resources and SDM resources, a time domain resource allocation (TDRA) bit field in the single DCI is used to indicate the time domain resource allocation.

[0091] 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, multi-panel simultaneous transmission is performed across FDM resources. In this case, for FDM, the s-DCI includes resource allocations with the same time domain resources for two opportunities for simultaneous transmission of two PUSCHs (e.g., multi-panel simultaneous transmission is performed using the same symbol set). In some embodiments, the TDRA bit field in the DCI indicates the time domain resource allocation for all transmissions.

[0092] In some embodiments, when multiple panels are simultaneously transmitted across FDM resources, for both resource allocation type 0 and type 1, a new FDRA field is added in the s-DCI and used for PUSCH scheduling on the second PUSCH.

[0093] In some implementations, resource allocations are specified to the UE in different ways in the s-DCI for resource allocation type 0 and resource allocation type 1. Various implementations for specifying resource allocations for resource allocation type 0 and resource allocation type 1 are given below.

[0094] In order to indicate the resource allocation to the UE, for resource allocation type 0, the resource allocation includes a bitmap indication of the RBG. In this case, there are multiple options available for allocating RBGs. In some embodiments, for resource allocation type 0 in the frequency domain, the uplink resource allocation specified for the multiple PUSCHs in the single DCI 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 even-numbered RBGs allocated to the first PUSCH and odd-numbered RBGs 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 and frequency resources associated with panel 1, and PUSCH2 represents the time and frequency resources associated with panel 2.

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

[0096] In some embodiments, for resource allocation type 0 in the frequency domain, the uplink resource allocation specified in the single DCI for the multiple PUSCHs includes one or more physical resource block (PRB) bundles for each of the multiple PUSCHs, where the physical resource block (PRB) bundle size is set by a PRB bundle parameter. In some embodiments, even-numbered consecutive PRB bundles are assigned to the first PUSCH and odd-numbered consecutive PRB bundles 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 the same as RB 束 In some embodiments, for Figure 6B , the even-numbered RBs in the RBs allocated in the s-DCI 束 Associated with PUSCH1, and an odd RB within the RBs allocated in the s-DCI 束 Associated with PUSCH2. In some embodiments, RB 束 The parameters are indicated via radio resource control (RRC) signaling or dynamic signaling.

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

[0098] In some embodiments, for the uplink resource allocation for the 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 for the multiple PUSCHs in the single DCI 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 for the multiple PUSCHs in the single DCI indicates in the FDRA bit field a resource allocation of contiguous PRBs for a first PUSCH in the multiple PUSCHs, and the resource allocation of the same number of contiguous PRBs for a second PUSCH in the multiple PUSCHs is indicated by an offset, which is derived 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 ceil(N PRB / 2) or alternatively floor(N PRB / 2) is assigned to the first PUSCH ( Figure 6B ), and the remaining RBs belong to the second PUSCH ( Figure 6B ).

[0099] In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates in the FDRA bit field the resource allocation for consecutive PRBs of a first PUSCH of the multiple PUSCHs, including the starting position of the RB and the number of RBs, and the resource allocation for consecutive PRBs of a second PUSCH of the multiple PUSCHs is indicated by an offset modulo the size of a bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH, the offset being relative to the starting position of the RB allocated to 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 determined accordingly, for example, by an offset from the end (or start) of the first resource allocation given by the FDRA bit field, and using the same number of PRBs (in some embodiments) or to the end (start) of the BWP (in other embodiments).

[0100] In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI 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, the offset being derived relative to the end or start of the resource allocation given by the FDRA bit field to the end or start of a bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH. In some embodiments, the existing procedure for intra-slot frequency hopping is reused to determine the starting RB for each PUSCH (rather than frequency hopping), as follows: For PUSCH1:

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

[0102] For PUSCH2:

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

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

[0105] 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 utilizing the same number of PRBs (in some embodiments) and or reusing the previous option of existing procedures 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 is capable of partially overlapping transmissions, and if so, those RBs are used for simultaneous transmissions on the two PUSCHs (partially / fully 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.

[0106] In some embodiments, the uplink resource allocation from the base station for allocating resources for the UE to perform transmission of multiple PUSCHs simultaneously using multiple UE antenna panels (e.g., multiple panels) is specified based on UE capability information possessed by the base station. In some embodiments, the UE capability information is transmitted via the UE and received by the base station via radio resource control (RRC) signaling or via dynamic signaling.

[0107] 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: the number of codewords for each PUSCH transmission opportunity, the number of code blocks for each PUSCH transmission opportunity, the number of transmission layers scheduled for each PUSCH transmission, the number of layers 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 scheduling a predetermined number of transmission layers. In some other embodiments, the UE capability information specifies a combination of the number of code blocks for each PUSCH transmission opportunity when scheduling a predetermined number of transmission layers.

[0108] Figure 7It is a flowchart of some embodiments of the process for configuring a UE. The process is performed by processing logic including hardware (circuitry, dedicated logic, etc.), software (for example, 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, and the processor (or processing circuit) and / or the baseband processor is configured to perform the following operations.

[0109] refer to Figure 7 , the process begins by transmitting UE capability information (processing block 701). In some embodiments, the UE capability information is transmitted via the UE and received by the base station through radio resource control (RRC) signaling or via dynamic signaling. In some embodiments, the UE capability information specifies one or more of the following: the number of codewords for each PUSCH transmission opportunity, the number of code blocks for each PUSCH transmission opportunity, the number of transmission layers scheduled for each PUSCH transmission, the number of layers transmitted when information is transmitted on multiple PUSCHs at the same time, the maximum modulation order, and 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 supported when a predetermined number of transmission layers are scheduled.

[0110] Processing logic receives 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), wherein the uplink resource allocations for the multiple PUSCHs are specified for each user equipment (UE) antenna panel (processing block 702). In some embodiments, the uplink resource allocations are based on UE capability information. In some embodiments, the uplink resource allocations for the multiple PUSCHs are specified by: when the UE is configured to perform simultaneous multi-panel transmission across spatial domain multiplexing (SDM) resources, one or more time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA) bit fields in the single DCI are used to represent spatial resources, or when the UE is configured to perform simultaneous multi-panel transmission across frequency domain multiplexing (FDM) resources or across both FDM resources and SDM resources, a time domain resource allocation (TDRA) bit field in the single DCI is used to represent time domain resource allocation.

[0111] In some embodiments, for resource allocation type 0 in the frequency domain, the uplink resource allocation specified in the single DCI for the multiple PUSCHs allocates a resource block group (RBG) to each of the multiple PUSCHs. In some embodiments, the RBG allocated to each PUSCH includes an even-numbered RBG allocated to a first PUSCH and an odd-numbered RBG allocated to a second PUSCH.

[0112] In some embodiments, for resource allocation type 0 in the frequency domain, the uplink resource allocation specified for the multiple PUSCHs in the single DCI includes one or more physical resource block (PRB) bundles for each of the multiple PUSCHs, wherein the physical resource block (PRB) bundle size is set by a PRB bundle parameter. In some embodiments, even-numbered consecutive PRB bundles are assigned to the first PUSCH and odd-numbered consecutive PRB bundles are assigned to the second PUSCH. In some embodiments, even-numbered consecutive PRB bundles within the allocated resource blocks (RBs) are assigned to the first PUSCH, and odd-numbered consecutive PRB bundles within the allocated RBs are assigned to the second PUSCH.

[0113] In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI specifies the number of RBs allocated in the FDRA bit field, and the first portion of the RBs is assigned to the first PUSCH, and the second portion of the RBs representing the remaining RBs in the RBs is assigned to the second PUSCH. In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates in the FDRA bit field a resource allocation of consecutive PRBs for a first PUSCH in the multiple PUSCHs, and the resource allocation of the same number of consecutive PRBs for a second PUSCH in the multiple PUSCHs is indicated by an offset, which is derived relative to the end or start of the resource allocation given by the FDRA bit field. In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates in the FDRA bit field the resource allocation for consecutive PRBs for a first PUSCH among the multiple PUSCHs, including the starting position of the RB and the number of RBs, and the resource allocation for consecutive PRBs for a second PUSCH among the multiple PUSCHs is indicated by an offset modulo the size of a bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH, and the offset is obtained relative to the starting position of the RB allocated to the first PUSCH.

[0114] In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI 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, the offset being derived relative to the end or start of the resource allocation given by the FDRA bit field to the end or start of a bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH. In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates one or more physical resource block (PRB) bundles for each PUSCH of the multiple PUSCHs, wherein the physical resource block (PRB) bundle size is set by a PRB bundle parameter. In some embodiments, even-numbered consecutive PRB bundles are assigned to a first PUSCH and odd-numbered consecutive PRB bundles are assigned to a second PUSCH, wherein even-numbered consecutive PRB bundles within an allocated resource block (RB) are assigned to the first PUSCH and odd-numbered consecutive PRB bundles within the allocated RB are assigned to the second PUSCH.

[0115] In response to the configuration information, the processing logic configures the UE to use multiple antenna panels of the UE to simultaneously send multiple PUSCHs based on the configuration information (processing box 703), and then the processing logic sends information on the multiple PUSCHs simultaneously via the multiple antenna panels based on the configuration information in the single DCI, wherein one PUSCH among the multiple PUSCHs is sent on a different PUSCH among the multiple PUSCHs (processing box 704).

[0116] Figure 8 It 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 spectrum above 52.6 GHz in 5G New Radio (NR). In some embodiments, the process is performed by a base station, which includes a processor (or processing circuit) configured to perform the following operations.

[0117] refer to Figure 8The process begins by receiving UE capability information (processing block 801). In some embodiments, the UE capability information is transmitted via the UE and received by the base station through radio resource control (RRC) signaling or via dynamic signaling.

[0118] 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 scheduled for each PUSCH transmission, the number of layers 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 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.

[0119] Processing logic generates configuration information for configuring a user equipment (UE), wherein the configuration information includes 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 are specified for each user equipment (UE) antenna panel (processing block 802). In some embodiments, the uplink resource allocations are based on UE capability information. In some embodiments, the uplink resource allocations for the multiple PUSCHs are specified by: when the UE is configured to perform simultaneous multi-panel transmission across spatial domain multiplexing (SDM) resources, one or more time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA) bit fields in the single DCI are used to represent spatial resources, or when the UE is configured to perform simultaneous multi-panel transmission across frequency domain multiplexing (FDM) resources or across both FDM resources and SDM resources, a time domain resource allocation (TDRA) bit field in the single DCI is used to represent time domain resource allocation.

[0120] In some embodiments, for resource allocation type 0 in the frequency domain, the uplink resource allocation specified in the single DCI for the multiple PUSCHs allocates a resource block group (RBG) to each of the multiple PUSCHs. In some embodiments, the RBG allocated to each PUSCH includes an even-numbered RBG allocated to a first PUSCH and an odd-numbered RBG allocated to a second PUSCH.

[0121] In some embodiments, for resource allocation type 0 in the frequency domain, the uplink resource allocation specified for the multiple PUSCHs in the single DCI includes one or more physical resource block (PRB) bundles for each of the multiple PUSCHs, wherein the physical resource block (PRB) bundle size is set by a PRB bundle parameter. In some embodiments, even-numbered consecutive PRB bundles are assigned to the first PUSCH and odd-numbered consecutive PRB bundles are assigned to the second PUSCH. In some embodiments, even-numbered consecutive PRB bundles within the allocated resource blocks (RBs) are assigned to the first PUSCH, and odd-numbered consecutive PRB bundles within the allocated RBs are assigned to the second PUSCH.

[0122] In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI specifies the number of RBs allocated in the FDRA bit field, and the first portion of the RBs is assigned to the first PUSCH, and the second portion of the RBs representing the remaining RBs in the RBs is assigned to the second PUSCH. In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates in the FDRA bit field a resource allocation of consecutive PRBs for a first PUSCH in the multiple PUSCHs, and the resource allocation of the same number of consecutive PRBs for a second PUSCH in the multiple PUSCHs is indicated by an offset, which is derived relative to the end or start of the resource allocation given by the FDRA bit field. In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates in the FDRA bit field the resource allocation for consecutive PRBs for a first PUSCH among the multiple PUSCHs, including the starting position of the RB and the number of RBs, and the resource allocation for consecutive PRBs for a second PUSCH among the multiple PUSCHs is indicated by an offset modulo the size of a bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH, and the offset is obtained relative to the starting position of the RB allocated to the first PUSCH.

[0123] In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI 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, the offset being derived relative to the end or start of the resource allocation given by the FDRA bit field to the end or start of a bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH. In some embodiments, for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates one or more physical resource block (PRB) bundles for each PUSCH of the multiple PUSCHs, wherein the physical resource block (PRB) bundle size is set by a PRB bundle parameter. In some embodiments, even-numbered consecutive PRB bundles are assigned to a first PUSCH and odd-numbered consecutive PRB bundles are assigned to a second PUSCH, wherein even-numbered consecutive PRB bundles within an allocated resource block (RB) are assigned to the first PUSCH and odd-numbered consecutive PRB bundles within the allocated RB are assigned to the second PUSCH.

[0124] After creating the configuration information for the single DCI, processing logic sends the single DCI to the UE (processing block 803). In some implementations, processing logic sends the single DCI to the UE using the PDDCH.

[0125] Subsequently, processing logic simultaneously receives information sent by the UE via its multiple antenna panels on the multiple PUSCHs based on the configuration information in the single DCI, wherein one PUSCH of the multiple PUSCHs is sent on a different PUSCH of the multiple PUSCHs (processing block 804).

[0126] Various example implementations are described herein.

[0127] Embodiment 1 is a method executable by a baseband processor or a UE, wherein the method comprises: receiving configuration information from a base station, wherein the configuration information comprises a single downlink control information (DCI), wherein the single downlink control information (DCI) specifies uplink resource allocation for a plurality of physical uplink shared channels (PUSCHs), wherein the uplink resource allocation for the plurality of PUSCHs is specified for each user equipment (UE) antenna panel, and when the UE is configured to perform simultaneous multi-panel transmission across spatial domain multiplexing (SDM) resources, using one or more time domain resource allocations (TDRA) and frequency domain resource allocations (FDR) in the single DCI A) bit field is used to indicate spatial resources, or when the UE is configured to perform simultaneous multi-panel transmission across frequency domain multiplexing (FDM) resources or across both FDM resources and SDM resources, a time domain resource allocation (TDRA) bit field in the single DCI is used to indicate time domain resource allocation; based on the configuration information, the UE is configured to simultaneously transmit multiple PUSCHs using multiple antenna panels of the UE; and based on the configuration information in the single DCI, information is simultaneously transmitted on the multiple PUSCHs via the multiple antenna panels, wherein one PUSCH among the multiple PUSCHs is transmitted on a different PUSCH among the multiple PUSCHs.

[0128] Embodiment 2 is a method according to embodiment 1, which may optionally include: for resource allocation type 0 in the frequency domain, the uplink resource allocation specified for the multiple PUSCHs in the single DCI allocates a resource block group (RBG) to each PUSCH in the multiple PUSCHs.

[0129] Embodiment 3 is a method according to embodiment 1, and the method may optionally include: the RBG allocated to each PUSCH includes an even-numbered RBG allocated to the first PUSCH and an odd-numbered RBG allocated to the second PUSCH.

[0130] Embodiment 4 is a method according to embodiment 1, and the method may optionally include: the uplink resource allocation specified for the multiple PUSCHs in the single DCI includes one or more physical resource block (PRB) bundles for each PUSCH in the multiple PUSCHs, wherein the physical resource block (PRB) bundle size is set by a PRB bundle parameter, wherein even-numbered consecutive PRB bundles are assigned to the first PUSCH, and odd-numbered consecutive PRB bundles are assigned to the second PUSCH.

[0131] Embodiment 5 is a method according to embodiment 1, which may optionally include: indicating the PRB bundle parameters via radio resource control (RRC) signaling.

[0132] Embodiment 6 is a method according to embodiment 1, which may optionally include: for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI specifies the number of RBs allocated in the FDRA bit field, and the first part of the RBs is assigned to the first PUSCH, and the second part of the RBs representing the remaining RBs in the RBs is assigned to the second PUSCH.

[0133] Embodiment 7 is a method according to embodiment 1, and the method may optionally include: for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates the resource allocation of consecutive PRBs for the first PUSCH among the multiple PUSCHs in the FDRA bit field, and the resource allocation of the same number of consecutive PRBs for the second PUSCH among the multiple PUSCHs is indicated by an offset, and the offset is obtained relative to the end or start of the resource allocation given by the FDRA bit field.

[0134] Embodiment 8 is a method according to embodiment 1, and the method may optionally include: for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates the resource allocation for consecutive PRBs for the first PUSCH among the multiple PUSCHs in the FDRA bit field, including the starting position of the RB and the number of RBs, and the resource allocation for consecutive PRBs for the second PUSCH among the multiple PUSCHs is indicated by an offset modulo operation on the size of the bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH, and the offset is obtained relative to the starting position of the RB allocated to the first PUSCH.

[0135] Embodiment 9 is a method according to embodiment 1, and the method may optionally include: for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates the resource allocation of consecutive PRBs for the first PUSCH among the multiple PUSCHs in the FDRA bit field, and the resource allocation of consecutive PRBs for the second PUSCH among the multiple PUSCHs is indicated by an offset, and the offset is obtained relative to the end or start of the resource allocation given by the FDRA bit field to the end or start of the bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH.

[0136] Embodiment 10 is a method according to embodiment 1, which may optionally include: the uplink resource allocation specified for the multiple PUSCHs in the single DCI includes one or more physical resource block (PRB) bundles for each PUSCH in the multiple PUSCHs, wherein the physical resource block (PRB) bundle size is set by a PRB bundle parameter, wherein even-numbered consecutive PRB bundles are assigned to the first PUSCH, and odd-numbered consecutive PRB bundles are assigned to the second PUSCH.

[0137] Embodiment 11 is a method according to embodiment 1, and the method may optionally include: the uplink resource allocation is based on UE capability information.

[0138] Embodiment 12 is a method according to embodiment 11, which may optionally include: signaling UE capabilities via radio resource control (RRC) signaling or via dynamic signaling.

[0139] Embodiment 13 is a method according to embodiment 11, and the method may optionally include: the UE capability information specifies one or more of the following items: the number of codewords for each PUSCH transmission opportunity, the number of code blocks for each PUSCH transmission opportunity, the number of transmission layers scheduled for each PUSCH transmission, the number of layers transmitted when information is sent on multiple PUSCHs simultaneously, the maximum modulation order, and the transmission scheme.

[0140] Embodiment 14 is a method according to embodiment 13, and the method may optionally include: the UE capability information specifies a combination of the number of code blocks supported when scheduling a predetermined number of transmission layers.

[0141] Embodiment 15 is a method according to embodiment 13, and the method may optionally include: the UE capability information specifies a combination of the number of code blocks for each PUSCH transmission opportunity when a predetermined number of transmission layers are scheduled.

[0142] Embodiment 16 is a baseband processor configured to perform any one of the operations set forth in Embodiments 1 to 15.

[0143] Embodiment 17 is a UE, which is configured to perform any one of the operations described in Embodiments 1 to 15.

[0144] Embodiment 18 is one or more non-transitory computer-readable storage media having stored thereon instructions, which when executed by a UE or a baseband processor, cause any one of the operations set forth in embodiments 1 to 15 to be performed.

[0145] Embodiment 19 is a method performed by a base station, the base station having a processor (or processing circuit), the processor (or processing circuit) being configured to perform operations including: generating configuration information for configuring a user equipment (UE), wherein the configuration information includes a single downlink control information (DCI), the single downlink control information (DCI) specifying uplink resource allocation for multiple physical uplink shared channels (PUSCHs), wherein the uplink resource allocation for the multiple PUSCHs is specified for each user equipment (UE) antenna panel, when the UE is configured to perform simultaneous multi-panel transmission across spatial domain multiplexing (SDM) resources, one or more time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA) bit fields in the single DCI are used to represent spatial resources, or when the UE is configured to perform simultaneous multi-panel transmission across frequency domain multiplexing (FDM) resources or across both FDM resources and SDM resources, one time domain resource allocation (TDRA) bit field in the single DCI is used to represent time domain resource allocation; and sending the single DCI to the UE.

[0146] Embodiment 20 is a method according to embodiment 19, which may optionally include: for resource allocation type 0 in the frequency domain, the uplink resource allocation specified for the multiple PUSCHs in the single DCI allocates a resource block group (RBG) to each PUSCH in the multiple PUSCHs.

[0147] Embodiment 21 is a method according to embodiment 19, which may optionally include: the RBG allocated to each PUSCH includes an even-numbered RBG allocated to the first PUSCH and an odd-numbered RBG allocated to the second PUSCH.

[0148] Embodiment 22 is a method according to embodiment 19, which may optionally include: the uplink resource allocation specified for the multiple PUSCHs in the single DCI includes one or more physical resource block (PRB) bundles for each PUSCH in the multiple PUSCHs, wherein the physical resource block (PRB) bundle size is set by a PRB bundle parameter, wherein even-numbered consecutive PRB bundles are assigned to the first PUSCH, and odd-numbered consecutive PRB bundles are assigned to the second PUSCH.

[0149] Embodiment 23 is a method according to embodiment 19, which may optionally include: indicating the PRB bundle parameters via radio resource control (RRC) signaling.

[0150] Embodiment 24 is a method according to embodiment 19, which may optionally include: for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI specifies the number of RBs allocated in the FDRA bit field, and the first part of the RBs is assigned to the first PUSCH, and the second part of the RBs representing the remaining RBs in the RBs is assigned to the second PUSCH.

[0151] Embodiment 25 is a method according to embodiment 19, which may optionally include: for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates the resource allocation of consecutive PRBs for the first PUSCH among the multiple PUSCHs in the FDRA bit field, and the resource allocation of the same number of consecutive PRBs for the second PUSCH among the multiple PUSCHs is indicated by an offset, and the offset is obtained relative to the end or start of the resource allocation given by the FDRA bit field.

[0152] Embodiment 26 is a method according to embodiment 19, and the method may optionally include: for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates the resource allocation for consecutive PRBs for the first PUSCH among the multiple PUSCHs in the FDRA bit field, including the starting position of the RB and the number of RBs, and the resource allocation for consecutive PRBs for the second PUSCH among the multiple PUSCHs is indicated by an offset modulo operation on the size of the bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH, and the offset is obtained relative to the starting position of the RB allocated to the first PUSCH.

[0153] Embodiment 27 is a method according to embodiment 19, which may optionally include: for resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates the resource allocation of consecutive PRBs for the first PUSCH among the multiple PUSCHs in the FDRA bit field, and the resource allocation of consecutive PRBs for the second PUSCH among the multiple PUSCHs is indicated by an offset, and the offset is obtained relative to the end or start of the resource allocation given by the FDRA bit field to the end or start of the bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH.

[0154] Embodiment 28 is a method according to embodiment 19, which may optionally include: the uplink resource allocation specified for the multiple PUSCHs in the single DCI includes one or more physical resource block (PRB) bundles for each PUSCH in the multiple PUSCHs, wherein the physical resource block (PRB) bundle size is set by a PRB bundle parameter, wherein even-numbered consecutive PRB bundles are assigned to the first PUSCH, and odd-numbered consecutive PRB bundles are assigned to the second PUSCH.

[0155] Embodiment 29 is a method according to embodiment 19, and the method may optionally include: the uplink resource allocation is based on UE capability information.

[0156] Embodiment 30 is a method according to embodiment 29, which may optionally include: signaling UE capabilities via radio resource control (RRC) signaling or via dynamic signaling.

[0157] Embodiment 31 is a method according to embodiment 29, and the method may optionally include: the UE capability information specifies one or more of the following items: the number of codewords for each PUSCH transmission opportunity, the number of code blocks for each PUSCH transmission opportunity, the number of transmission layers scheduled for each PUSCH transmission, the number of layers transmitted when information is sent on multiple PUSCHs simultaneously, the maximum modulation order or the transmission scheme.

[0158] Embodiment 32 is a method according to embodiment 31, and the method may optionally include: the UE capability information specifies a combination of the number of code blocks supported when scheduling a predetermined number of transmission layers.

[0159] Embodiment 33 is a method according to embodiment 31, and the method may optionally include: the UE capability information specifies a combination of the number of code blocks for each PUSCH transmission opportunity when a predetermined number of transmission layers are scheduled.

[0160] Embodiment 34 is a baseband processor of a base station, and the baseband processor is configured to perform any one of the operations set forth in Embodiments 19 to 33.

[0161] Embodiment 35 is a base station configured to perform any one of the operations set forth in Embodiments 19 to 33.

[0162] Embodiment 38 is one or more non-transitory computer-readable storage media of a base station having instructions stored thereon, which, when executed by a UE or a baseband processor, cause any one of the operations set forth in embodiments 19 to 33 to be performed.

[0163] Part of the above content can be realized by utilizing logic circuits such as special logic circuits or utilizing the processing core of microcontroller or other forms of execution program code instructions. Therefore, program code such as machine executable instructions can be utilized to perform the process taught by the above discussion, and the machine executable instructions make the machine execute these instructions to perform certain functions. In this context, "machine" can be a machine that converts intermediate form (or "abstract") instructions into processor-specific instructions (for example, abstract execution environment such as "virtual machine" (for example, Java virtual machine), interpreter, common language runtime, high-level language virtual machine, etc.), and / or an electronic circuit that is arranged on a semiconductor chip (for example, "logic circuit" realized by transistors), and the electronic circuit is designed to execute instructions, and the processor is such as a general-purpose processor and / or a special-purpose processor. The process taught by the above discussion can also be performed by (as a substitute of a machine or in combination with a machine) an electronic circuit, and the electronic circuit is designed to perform a process (or a part thereof) without executing program code.

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

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

[0166] Articles of manufacture may be used to store program code. Articles of manufacture storing program code may be embodied 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 embodied in a propagation medium (e.g., via a communication link (e.g., a network connection)).

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

[0168] 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 computer systems or similar electronic computing devices that manipulate data represented as physical (electronic) quantities in the computer system's registers and memories and convert them 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.

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

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

[0171] 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 configuration information from a base station, wherein the configuration information includes a single downlink control information (DCI) specifying uplink resource allocations for a plurality of physical uplink shared channels (PUSCHs), wherein the uplink resource allocations for the plurality of PUSCHs are specified for each user equipment (UE) antenna panel, When the UE is configured to perform simultaneous multi-panel transmission across spatial domain multiplexing (SDM) resources, one or more time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA) bit fields in the single DCI are used to indicate spatial domain resources, or When the UE is configured to perform simultaneous multi-panel transmission across frequency domain multiplexing (FDM) resources or across both FDM resources and SDM resources, using a time domain resource allocation (TDRA) bit field in the single DCI to indicate time domain resource allocation; Based on the configuration information, configure the UE to simultaneously transmit multiple PUSCHs using multiple antenna panels of the UE; as well as Based on the configuration information in the single DCI, information is simultaneously transmitted on the plurality of PUSCHs via the plurality of antenna panels, wherein one PUSCH among the plurality of PUSCHs is transmitted on a different PUSCH among the plurality of PUSCHs.

2. The baseband processor according to claim 1, wherein: For resource allocation type 0 in the frequency domain, the uplink resource allocation specified for the multiple PUSCHs in the single DCI allocates a resource block group (RBG) to each of the multiple PUSCHs. 3 . The baseband processor of claim 1 , wherein the RBGs allocated to each PUSCH include even-numbered RBGs allocated to a first PUSCH and odd-numbered RBGs allocated to a second PUSCH.

4. The baseband processor of claim 1 , wherein the uplink resource allocation specified for the multiple PUSCHs in the single DCI comprises one or more physical resource block (PRB) bundles for each of the multiple PUSCHs, wherein a physical resource block (PRB) bundle size is set by a PRB bundle parameter, wherein even-numbered consecutive PRB bundles are assigned to a first PUSCH and odd-numbered consecutive PRB bundles are assigned to a second PUSCH, and further wherein the PRB bundle parameters are indicated via radio resource control (RRC) signaling.

5. The baseband processor according to claim 1, wherein: For resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI specifies the number of RBs allocated in the FDRA bit field, and a first portion of the RBs is assigned to a first PUSCH, and a second portion of the RBs representing the remaining RBs in the RBs is assigned to a second PUSCH.

6. The baseband processor according to claim 1, wherein: For resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates the resource allocation of consecutive PRBs for the first PUSCH of the multiple PUSCHs in the FDRA bit field, and the resource allocation of the same number of consecutive PRBs for the second PUSCH of the multiple PUSCHs is indicated by an offset, which is obtained relative to the end or start of the resource allocation given by the FDRA bit field.

7. The baseband processor according to claim 1, wherein: For resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates the resource allocation for consecutive PRBs for a first PUSCH among the multiple PUSCHs in the FDRA bit field, including the starting position of the RBs and the number of RBs, and the resource allocation for consecutive PRBs for a second PUSCH among the multiple PUSCHs is indicated by an offset modulo the size of a bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH, wherein the offset is obtained relative to the starting position of the RB allocated to the first PUSCH.

8. The baseband processor according to claim 1, wherein: For resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI indicates the resource allocation of consecutive PRBs for a first PUSCH among the multiple PUSCHs in the FDRA bit field, and the resource allocation of consecutive PRBs for a second PUSCH among the multiple PUSCHs is indicated by an offset, which is obtained relative to the end or start of the resource allocation given by the FDRA bit field to the end or start of the bandwidth part (BWP) containing the consecutive PRBs allocated to the first PUSCH and the second PUSCH.

9. A baseband processor according to claim 1, wherein the uplink resource allocation specified for the multiple PUSCHs in the single DCI includes one or more physical resource block (PRB) bundles for each of the multiple PUSCHs, wherein the physical resource block (PRB) bundle size is set by a PRB bundle parameter, wherein even-numbered consecutive PRB bundles are assigned to a first PUSCH and odd-numbered consecutive PRB bundles are assigned to a second PUSCH.

10. The baseband processor of claim 1, wherein the uplink resource allocation is based on UE capability information, and wherein the operations further comprise signaling UE capabilities via radio resource control (RRC) signaling or via dynamic signaling.

11. The baseband processor of claim 11, wherein the UE capability information specifies one or more of the following: the number of codewords for each PUSCH transmission opportunity, the number of code blocks for each PUSCH transmission opportunity, the number of transmission layers for each PUSCH transmission scheduling, the number of layers transmitted when information is transmitted on multiple PUSCHs simultaneously, the maximum modulation order, and the transmission scheme. 12 . The baseband processor of claim 13 , wherein the UE capability information specifies a combination of the number of code blocks supported when a predetermined number of transmission layers are scheduled. 13 . The baseband processor of claim 13 , wherein 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.

14. A method performed by a user equipment (UE), the method comprising: receiving configuration information from a base station, wherein the configuration information includes a single downlink control information (DCI) specifying uplink resource allocations for a plurality of physical uplink shared channels (PUSCHs), wherein the uplink resource allocations for the plurality of PUSCHs are specified for each user equipment (UE) antenna panel, When the UE is configured to perform simultaneous multi-panel transmission across spatial domain multiplexing (SDM) resources, one or more time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA) bit fields in the single DCI are used to indicate spatial domain resources, or When the UE is configured to perform simultaneous multi-panel transmission across frequency domain multiplexing (FDM) resources or across both FDM resources and SDM resources, using a time domain resource allocation (TDRA) bit field in the single DCI to indicate time domain resource allocation; Based on the configuration information, configure the UE to simultaneously transmit multiple PUSCHs using multiple antenna panels of the UE; as well as Based on the configuration information in the single DCI, information is simultaneously transmitted on the plurality of PUSCHs via the plurality of antenna panels, wherein one PUSCH among the plurality of PUSCHs is transmitted on a different PUSCH among the plurality of PUSCHs.

15. The method according to claim 14, wherein: For resource allocation type 0 in the frequency domain, the uplink resource allocation specified for the multiple PUSCHs in the single DCI allocates a resource block group (RBG) to each of the multiple PUSCHs.

16. A baseband processor according to claim 1, wherein the uplink resource allocation specified for the multiple PUSCHs in the single DCI includes one or more physical resource block (PRB) bundles for each of the multiple PUSCHs, wherein the physical resource block (PRB) bundle size is set by a PRB bundle parameter, wherein even-numbered consecutive PRB bundles are assigned to a first PUSCH and odd-numbered consecutive PRB bundles are assigned to a second PUSCH, and further wherein the PRB bundle parameters are indicated via radio resource control (RRC) signaling.

17. The method according to claim 14, wherein: For resource allocation type 1 in the frequency domain, the uplink resource allocation for the multiple PUSCHs in the single DCI specifies the number of RBs allocated in the FDRA bit field, and a first portion of the RBs is assigned to a first PUSCH, and a second portion of the RBs representing the remaining RBs in the RBs is assigned to a second PUSCH.

18. A base station, the base station comprising a processor (or a processing circuit), the processor (or a processing circuit) being configured to perform operations including: generating configuration information for configuring a user equipment (UE), wherein the configuration information comprises a single downlink control information (DCI) specifying uplink resource allocations for a plurality of physical uplink shared channels (PUSCHs), wherein the uplink resource allocations for the plurality of PUSCHs are specified for each user equipment (UE) antenna panel, When the UE is configured to perform simultaneous multi-panel transmission across spatial domain multiplexing (SDM) resources, one or more time domain resource allocation (TDRA) and frequency domain resource allocation (FDRA) bit fields in the single DCI are used to indicate spatial domain resources, or When the UE is configured to perform simultaneous multi-panel transmission across frequency domain multiplexing (FDM) resources or across both FDM resources and SDM resources, using a time domain resource allocation (TDRA) bit field in the single DCI to indicate time domain resource allocation; and The single DCI is sent to the UE.

19. The base station according to claim 18, wherein: For resource allocation type 0 in the frequency domain, the uplink resource allocation specified for the multiple PUSCHs in the single DCI allocates a resource block group (RBG) to each of the multiple PUSCHs.

20. The base station of claim 18, wherein the uplink resource allocation specified for the multiple PUSCHs in the single DCI comprises one or more physical resource block (PRB) bundles for each of the multiple PUSCHs, wherein a physical resource block (PRB) bundle size is set by a PRB bundle parameter, wherein even-numbered consecutive PRB bundles are assigned to a first PUSCH and odd-numbered consecutive PRB bundles are assigned to a second PUSCH.