Method and apparatus for supporting multi-panel simultaneous PUSCH transmission

Abstract

An apparatus of a user equipment (UE), the apparatus comprising a processor and a memory storing instructions that, when executed by the processor, configure the apparatus to: receive, from a base station, scheduling information for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in a time domain; and in response to the scheduling information, performing the first PUSCH transmission through the first antenna panel and the second PUSCH transmission through the second antenna panel by using mutually different frequency domain resources.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems including support for multi-panel simultaneous physical uplink shared channel (PUSCH) transmission for frequency domain multiplexing (FDM). Background Art

[0002] Wireless mobile communication technologies use various standards and protocols to send data between base stations and wireless communication devices. Wireless communication system standards and protocols may include, for example, the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) (e.g., 4G), 3GPP New Radio (NR) (e.g., 5G), and the IEEE 802.11 standard for wireless local area networks (WLANs) (often referred to by industry groups as WLANs). ).

[0003] As envisioned by 3GPP, different wireless communication system standards and protocols may use various radio access networks (RANs) to communicate between base stations of the RAN (which may also sometimes be referred to as RAN nodes, network nodes, or simply nodes) and wireless communication devices referred to as user equipment (UE). 3GPP RANs may include, for example, Global System for Mobile Communications (GSM), Enhanced Data Rates for GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), Evolved Universal Terrestrial Radio Access Network (E-UTRAN), and / or Next Generation Radio Access Network (NG-RAN).

[0004] Each RAN may use one or more radio access technologies (RATs) for communication between base stations and UEs. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT (sometimes referred to as LTE), and NG-RAN implements NR RAT (sometimes referred to as 5G RAT, 5G NR RAT, or simply NR in this document). In some deployments, E-UTRAN may also implement NR RAT. In some deployments, NG-RAN may also implement LTE RAT.

[0005] The base stations used by the RAN may correspond to the RAN. An example of an E-UTRAN base station is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as an evolved Node B, enhanced Node B, eNodeB, or eNB). An example of an NG-RAN base station is a Next Generation Node B (also sometimes referred to as a gNodeB or gNB).

[0006] The RAN provides its communication services together with external entities through its connection with the Core Network (CN). For example, E-UTRAN may utilize the Evolved Packet Core (EPC) while NG-RAN may utilize the 5G Core Network (5GC).

[0007] LTE and NR have defined the Physical Uplink Shared Channel (PUSCH) as an uplink (UL) channel shared by all devices (also called user equipment, UE) in a radio cell to send user data to the network. Scheduling for all UEs is under the control of the LTE or NR base station (eNB or gNB). The base station uses the UL scheduling grant to inform the UE about resource allocation, modulation and coding scheme, precoding information, UL power control, etc. In addition to user data, the PUSCH may also carry any control information or reference signals (RS) necessary for decoding the data. Summary of the invention

[0008] In one aspect, a device of a user equipment (UE) is provided, comprising: a processor; and a memory storing instructions, which, when executed by the processor, configure the device to: receive scheduling information from a base station for scheduling a first physical uplink shared channel (PUSCH) and a second PUSCH transmission that at least partially overlap in the time domain; and in response to the scheduling information, perform a first PUSCH transmission through a first antenna panel and a second PUSCH transmission through a second antenna panel by using mutually different frequency domain resources.

[0009] On the other hand, a base station device is provided, comprising: a processor; and a memory storing instructions, which, when executed by the processor, configure the device to: send scheduling information to a user equipment (UE) for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that partially overlap in the time domain; and in response to the scheduling information, receive a first PUSCH transmission and a second PUSCH transmission performed by the UE using mutually different frequency domain resources, wherein the first PUSCH transmission and the second PUSCH transmission are respectively from a first antenna panel and a second antenna panel of the UE.

[0010] On the other hand, a method is provided, the method comprising: receiving scheduling information from a base station for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in the time domain; and in response to the scheduling information, performing a first PUSCH transmission through a first antenna panel and a second PUSCH transmission through a second antenna panel by using mutually different frequency domain resources.

[0011] On the other hand, a method is provided, comprising: sending scheduling information to a user equipment (UE) for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that partially overlap in the time domain; and in response to the scheduling information, receiving a first PUSCH transmission and a second PUSCH transmission performed by the UE using mutually different frequency domain resources, wherein the first PUSCH transmission and the second PUSCH transmission are from a first antenna panel and a second antenna panel of the UE, respectively.

[0012] This disclosure is intended to provide a brief overview of some of the topics described in this document. Therefore, it should be understood that the above features are only examples and should not be construed as narrowing the scope or essence of the topics described herein in any way. Other features, aspects, and advantages of the topics described herein will become apparent through the following detailed description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] To easily identify the discussion of any particular element or action, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

[0014] Figure 1 An example architecture of a wireless communication system according to some aspects of the present disclosure is shown.

[0015] Figure 2 A system for performing signaling between a wireless device and a network device according to some aspects of the present disclosure is shown.

[0016] Figure 3 An example scenario of simultaneous multi-panel PUSCH transmission according to some aspects of the present disclosure is shown.

[0017] Figure 4 is a flow chart illustrating an example method for supporting simultaneous multi-panel PUSCH transmissions according to some aspects of the present disclosure.

[0018] Figure 5 is a flow chart illustrating an example method for supporting simultaneous multi-panel PUSCH transmissions according to some aspects of the present disclosure.

[0019] Figure 6 A diagram showing the frame structure in 5G NR.

[0020] Figure 7 Two FDM modes are shown in accordance with some aspects of the present application.

[0021] Figure 8 A configuration of a single-port phase tracking reference signal (PTRS) according to some aspects of the present disclosure is shown.

[0022] Figures 9a to 9c An example TB configuration according to some aspects of the present application is shown. DETAILED DESCRIPTION

[0023] Various exemplary embodiments of the present application will be described below with reference to the accompanying drawings. For the sake of clarity and brevity, not all features are described in the specification. However, it should be noted that when practicing the embodiments of the present disclosure, many settings specific to a specific implementation may be made. In addition, it should be noted that, in order to avoid blurring the description, some of the accompanying drawings only show the steps of the process and / or parts of the device that are closely related to the technical solution of the present application, while in some other drawings, well-known process steps and / or device structures are shown only for a better understanding of the present application.

[0024] For ease of explanation, various aspects of the present application will be described below in the context of 5G NR. However, it should be noted that this is not a limitation on the scope of application of the present application, and one or more aspects of the present application may also be applied to wireless communication systems that are already commonly used (such as 4G LTE / LTE-A) or various wireless communication systems to be developed in the future. Equivalents of the architectures, entities, functions, processes, etc. described in the following description may be found in these communication systems.

[0025] Various embodiments are described with reference to UE. However, reference to UE is provided for illustrative purposes only. The example embodiments may be used with any electronic component that can establish a connection with a network and is configured with hardware, software and / or firmware for exchanging information and data with the network. Therefore, UE as described herein is used to represent any appropriate electronic component. Examples of UE may include mobile devices, personal digital assistants (PDAs), tablet computers, laptop computers, personal computers, Internet of Things (IoT) devices, or machine type communication (MTC) devices, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0026] In addition, various embodiments are described with reference to a "base station". However, reference to a base station is provided for illustrative purposes only. The term "base station" as used in this application is an example of a control device in a wireless communication system, which has the full breadth of its ordinary meaning. For example, in addition to the gNB specified in 5G NR, a "base station" may also be, for example, an eNB in ​​an LTE communication system, a remote radio head, a wireless access point, a relay node, a drone control tower, or any communication device or element thereof for performing similar control functions.

[0027] System Overview

[0028] Figure 1An example architecture of a wireless communication system 100 is illustrated in accordance with an embodiment disclosed herein. The description provided below is for an example wireless communication system 100 operating in conjunction with the LTE system standard and / or the 5G or NR system standard provided in the 3GPP technical specifications.

[0029] like Figure 1 As shown, wireless communication system 100 includes UE 102 and UE 104 (although any number of UEs may be used). In this example, UE 102 and UE 104 are illustrated as smartphones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device configured for wireless communication.

[0030] UE 102 and UE 104 may be configured to be communicatively coupled to RAN 106. In an embodiment, RAN 106 may be NG-RAN, E-UTRAN, etc. UE 102 and UE 104 utilize connections (or channels) (shown as connection 108 and connection 110, respectively) with RAN 106, where each connection (or channel) includes a physical communication interface. RAN 106 may include one or more base stations, such as base station 112 and base station 114, to implement connection 108 and connection 110.

[0031] In this example, connection 108 and connection 110 are air interfaces that enable such communicative coupling and may conform to the RAT used by RAN 106 , such as, for example, LTE and / or NR.

[0032] In some embodiments, UE 102 and UE 104 may also directly exchange communication data via side link interface 116. UE 104 is shown as being configured to access an access point (shown as AP 118) via connection 120. By way of example, connection 120 may include a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, wherein AP 118 may include In this example, AP 118 may be connected to another network (eg, the Internet) without going through CN 124.

[0033] In an embodiment, UE 102 and UE 104 may be configured to communicate with each other or with base station 112 and / or base station 114 over a multi-carrier communication channel using orthogonal frequency division multiplexing (OFDM) communication signals according to various communication techniques, such as but not limited to orthogonal frequency division multiple access (OFDMA) communication techniques (e.g., for downlink communication) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communication), although the scope of the embodiment is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0034] In some embodiments, all or part of base station 112 or base station 114 may be implemented as one or more software entities running on a server computer as part of a virtual network. In addition, or in other embodiments, base station 112 or base station 114 may be configured to communicate with each other via interface 122. In an embodiment where wireless communication system 100 is an LTE system (e.g., when CN124 is EPC), interface 122 may be an X2 interface. The X2 interface may be defined between two or more base stations (e.g., two or more eNBs, etc.) connected to EPC and / or between two eNBs connected to EPC. In an embodiment where wireless communication system 100 is an NR system (e.g., when CN 124 is 5GC), interface 122 may be an Xn interface. The Xn interface is defined between two or more base stations (e.g., two or more gNBs, etc.) connected to 5GC, between base station 112 (e.g., gNB) and eNB connected to 5GC, and / or between two eNBs connected to 5GC (e.g., CN 124).

[0035] The RAN 106 is shown as being communicatively coupled to the CN 124. The CN 124 may include one or more network elements 126 configured to provide various data and telecommunication services to customers / subscribers (e.g., UE 102 and users of UE 104) connected to the CN 124 via the RAN 106. The components of the CN 124 may be implemented in one physical device or separate physical devices including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium).

[0036] In an embodiment, CN 124 may be an EPC, and RAN 106 may be connected to CN 124 via an S1 interface 128. In an embodiment, S1 interface 128 may be divided into two parts: an S1 user plane (S1-U) interface that carries traffic data between base station 112 or base station 114 and a serving gateway (S-GW); and an S1-MME interface that is a signaling interface between base station 112 or base station 114 and a mobility management entity (MME).

[0037] In an embodiment, CN 124 may be a 5GC, and RAN 106 may be connected to CN 124 via an NG interface 128. In an embodiment, NG interface 128 may be divided into two parts: an NG user plane (NG-U) interface that carries service data between base station 112 or base station 114 and a user plane function (UPF); and an S1 control plane (NG-C) interface that is a signaling interface between base station 112 or base station 114 and an access and mobility management function (AMF).

[0038] Generally speaking, application server 130 may be an element that provides applications (e.g., packet-switched data services) that use Internet Protocol (IP) bearer resources with CN 124. Application server 130 may also be configured to support one or more communication services (e.g., VoIP sessions, group communication sessions, etc.) for UE 102 and UE 104 via CN 124. Application server 130 may communicate with CN 124 via IP communication interface 132.

[0039] Figure 2 A system 200 for performing signaling 234 between a wireless device 202 and a network device 218 according to embodiments disclosed herein is shown. The system 200 may be part of a wireless communication system as described herein. The wireless device 202 may be, for example, a UE of a wireless communication system. The network device 218 may be, for example, a base station (e.g., an eNB or a gNB) of a wireless communication system.

[0040] The wireless device 202 may include one or more processors 204. The processor 204 may execute instructions to perform various operations of the wireless device 202, as described herein. The processor 204 may include one or more baseband processors implemented using, for example, a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0041] The wireless device 202 may include a memory 206. The memory 206 may be a non-transitory computer-readable storage medium that stores instructions 208 (which may include, for example, instructions executed by the processor 204). The instructions 208 may also be referred to as program code or a computer program. The memory 206 may also store data used by the processor 204 and results calculated by the processor.

[0042] The wireless device 202 may include one or more transceivers 210 that may use radio frequency (RF) transmitter and / or receiver circuitry that uses an antenna 212 of the wireless device 202 to facilitate signaling (e.g., signaling 234) to and / or from the wireless device 202 with other devices (e.g., network device 218) according to a corresponding RAT.

[0043] The wireless device 202 may include one or more antennas 212 (e.g., one, two, four, or more). For embodiments with multiple antennas 212, the wireless device 202 may utilize the spatial diversity of such multiple antennas 212 to transmit and / or receive multiple different data streams on the same time-frequency resources. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to the multiple antennas used at each of the transmitting device and the receiving device to implement this aspect). MIMO transmission by the wireless device 202 may be implemented based on precoding (or digital beamforming) applied at the wireless device 202, which multiplexes the data streams across the antennas 212 based on known or assumed channel characteristics, so that each data stream is received at an appropriate signal strength relative to the other streams and at a desired location in the spatial domain (e.g., the location of the receiver associated with the data stream). Certain embodiments may use a single-user MIMO (SU-MIMO) approach (where the data streams are all directed to a single receiver) and / or a multi-user MIMO (MU-MIMO) approach (where separate data streams may be directed to separate (different) receivers in different locations in the spatial domain).

[0044] In certain embodiments with multiple antennas, the wireless device 202 may implement analog beamforming techniques whereby the phases of signals transmitted by the antennas 212 are relatively adjusted so that the (joint) transmissions of the antennas 212 can be directed (this is sometimes referred to as beam steering).

[0045] The wireless device 202 may include one or more interfaces 214. The interfaces 214 may be used to provide input to the wireless device 202 or output from the wireless device. For example, a wireless device 202 that is a UE may include an interface 214, such as a microphone, a speaker, a touch screen, buttons, etc., to allow a user of the UE to input and / or output to the UE. Other interfaces of such a UE may be composed of transmitters, receivers, and other circuits that allow communication between the UE and other devices (e.g., in addition to the transceiver 210 / antenna 212 described above), and may be based on known protocols (e.g., etc.) to perform the operation.

[0046] The network device 218 may include one or more processors 220. The processor 220 may execute instructions to perform various operations of the network device 218, as described herein. The processor 204 may include one or more baseband processors implemented using, for example, a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein.

[0047] The network device 218 may include a memory 222. The memory 222 may be a non-transitory computer-readable storage medium that stores instructions 224 (which may include, for example, instructions executed by the processor 220). The instructions 224 may also be referred to as program code or a computer program. The memory 222 may also store data used by the processor 220 and results calculated by the processor.

[0048] The network device 218 may include one or more transceivers 226, which may include RF transmitter and / or receiver circuits that use an antenna 228 of the network device 218 to facilitate signaling (e.g., signaling 234) to and / or from the network device 218 with other devices (e.g., wireless device 202) according to a corresponding RAT.

[0049] The network device 218 may include one or more antennas 228 (eg, one, two, four, or more). In embodiments with multiple antennas 228, the network device 218 may perform MIMO, digital beamforming, analog beamforming, beamsteering, etc. as described.

[0050] The network device 218 may include one or more interfaces 230. The interface 230 may be used to provide input to or output from the network device 218. For example, the network device 218 as a base station may include an interface 230 composed of a transmitter, a receiver, and other circuits (e.g., in addition to the transceiver 226 / antenna 228 described above), which enables the base station to communicate with other equipment in the core network and / or enables the base station to communicate with external networks, computers, databases, etc., in order to achieve the purpose of performing operations, management, and maintenance of the base station or other equipment operably connected to the base station.

[0051] Simultaneous PUSCH transmission on multiple panels

[0052] New cellular communication technologies are constantly being developed to increase coverage, better meet various needs and use cases, and for various other reasons. One technology currently under development may include support for multiple panels to transmit simultaneously, for example, for the purpose of higher throughput or reliability.

[0053] However, there is no clear specification agreement to date to support simultaneous multi-panel uplink (UL) transmissions. Although several enhancements have been introduced to support multi-panel PUSCH operation, they are generally limited to time domain multiplexing (TDM) repetition, in which multiple antenna panels can be switched to send UL data alternately in the time domain, but there is no period when they perform PUSCH transmissions simultaneously.

[0054] Figure 3 An example scenario of simultaneous multi-panel PUSCH transmission according to some aspects of the present disclosure is shown. Figure 3 In the figure, two antenna panels (panel 1 and panel 2) of a UE (eg, a mobile phone) are shown for explanation purposes, but the number of panels is not particularly limited. The UE may be provided with more than two antenna panels, such as three, four or even more antenna panels.

[0055] As used herein, an "antenna panel" (also simply referred to as a "panel") is a collection of antennas, such as Figure 2 Antenna 212 depicted in . Antennas that radiate electromagnetic waves according to their own amplitude parameters and phase parameters are arranged into one or more antenna arrays in the form of a matrix. Antenna arrays may be composed of entire rows, entire columns, multiple rows, and multiple columns of antennas. Each antenna array actually constitutes an independently configurable transceiver unit (TXRU). The TXRU antenna pattern is adjusted by configuring the amplitude parameters and / or phase parameters of the antennas that constitute the TXRU, and the electromagnetic wave radiation emitted by all antennas forms a narrow beam pointing to a specific spatial direction, that is, beamforming is achieved. Physically, an antenna panel may include one or more antenna arrays, and if the antenna arrays operate with the same pattern, they can be regarded as a single larger array. That is, in some cases, the panel as used herein may be equivalent to a so-called antenna array.

[0056] like Figure 3 As shown, the UE may activate and utilize its panel 1 and panel 2 to perform PUSCH transmissions simultaneously (e.g., PUSCH 1 and PUSCH 2 as shown). It should be understood that PUSCH 1 and PUSCH 2 are only used to identify PUSCH transmissions from panel 1 and PUSCH transmissions from panel 2, respectively, but this does not mean that they must be essentially distinguished from each other. PUSCH 1 and PUSCH 2 may be sent to the same transmit receive point (TRP) or different TRPs. PUSCH 1 and PUSCH 2 may serve the same hybrid automatic repeat request (HARQ) process or different HARQ processes. PUSCH 1 and PUSCH 2 may be scheduled in the same UL grant or different UL grants, i.e., based on a single downlink control information (DCI) or based on multiple DCIs.

[0057] According to some aspects of the present disclosure, simultaneous PUSCH transmissions from multiple panels (such as Figure 3 PUSCH 1 and PUSCH 2 in the 4G LTE CAN bus are supported by frequency domain multiplexing (FDM). In other words, multiple panels perform their own PUSCH operations by using different frequency domain resources.

[0058] Figure 4 1 is a flow chart illustrating an example method for supporting simultaneous multi-panel PUSCH transmission according to some aspects of the present disclosure. The method may be performed at a UE.

[0059] At 401, the UE receives scheduling information for scheduling a first PUSCH transmission and a second PUSCH transmission from a base station (e.g., a gNB), wherein the first PUSCH transmission and the second PUSCH transmission at least partially overlap in the time domain, i.e., the first PUSCH transmission and the second PUSCH transmission are not necessarily aligned in the time domain, but may result in at least one time domain scheduling unit during which they are simultaneously transmitted.

[0060] At 402, in response to the received scheduling information, the UE performs a first PUSCH transmission through a first antenna panel of the UE and performs a second PUSCH transmission through a second antenna panel of the UE. The scheduling information may allocate or activate different frequency domain resources for the first PUSCH transmission and the second PUSCH transmission, thereby enabling PUSCH transmissions from the first panel and the second panel to be performed simultaneously through FDM.

[0061] Figure 5 1 is a flow chart illustrating an example method for supporting simultaneous multi-panel PUSCH transmissions according to some aspects of the present application. The method may be performed by a base station such as a gNB.

[0062] At 501, the base station may send scheduling information for scheduling a first PUSCH transmission and a second PUSCH transmission to the UE, wherein the first PUSCH transmission and the second PUSCH transmission at least partially overlap in the time domain, that is, both of them are scheduled in at least one time domain scheduling unit. The scheduling information may allocate or activate different frequency domain resources for FDM of the first PUSCH transmission and the second PUSCH transmission.

[0063] At 502, the base station may receive a first PUSCH transmission and a second PUSCH transmission from a UE on mutually different frequency domain resources. The first PUSCH transmission may be from a first antenna panel of the UE, and the second PUSCH transmission may be from a second antenna panel of the UE. Subsequently, Figure 5 Not shown in the figure, the base station may decode the first PUSCH transmission and the second PUSCH transmission individually or jointly to obtain the user data carried thereon.

[0064] Hereinafter, some additional aspects of the present application will be described for better understanding of the present application.

[0065] Frequency Domain Resource Allocation (FDRA)

[0066] In 5G NR, both downlink and uplink transmissions are organized into frames. Figure 6 Figure 2 shows the frame structure in 5G NR. As a fixed frame compatible with LTE / LTE-A, the frame in NR also has a length of 10ms and includes 10 subframes of equal size, each subframe having a length of 1ms. Unlike LTE / LTE-A, the frame structure in NR has a flexible structure depending on the supported transmission parameter sets. Figure 6 As shown, each subframe has a configurable number of time slots, such as 1, 2, 4, 8, or 16. Each time slot also has a configurable number of OFDM symbols. For a normal cyclic prefix, each time slot includes 14 consecutive OFDM symbols, and for an extended cyclic prefix, each time slot includes 12 consecutive OFDM symbols. In the frequency domain dimension, each time slot includes several resource blocks (RBs), and each resource block may include 12 consecutive subcarriers in the frequency domain. Therefore, a resource grid can be used to represent a resource element (RE) in a time slot.

[0067] The resource blocks that can be used for uplink transmission can be divided into a data part and a control part. The resource elements in the control part can be allocated to the UE for the transmission of control information. The data part may include all resource elements not included in the control part. The resource elements in the data part may also be allocated to the UE for sending data to the base station.

[0068] When there is data to be sent, the UE may send a scheduling request (SR) and / or a buffer status report (BSR) to the base station to request time-frequency resources for sending user data. In resource scheduling based on dynamic grants, the base station may use DCI containing resource allocation information to dynamically schedule PUSCH. In resource scheduling based on configured grants, the base station may pre-configure available time-frequency resources for the UE through RRC layer signaling, so that the UE can directly use the pre-configured time-frequency resources for PUSCH transmission without requiring the base station to send UL grants each time.

[0069] According to one aspect of the present application, PUSCH transmissions from different panels may be scheduled in mutually different frequency domain resource sets. Typically, two scheduling modes may be used, namely, interleaved FDM and non-interleaved FDM, such as Figure 7 shown.

[0070] References Figure 6In the example of the two panels shown, in interleaved FDM, the frequency domain resources for PUSCH 1 and the frequency domain resources for PUSCH 2 may be interleaved based on an interleaving unit. The interleaving unit may be an RE, a physical resource block (PRB), or a plurality of PRBs. For example, with respect to an interleaving unit of one PRB, an even PRB may be allocated to PUSCH 1, and an odd PRB may be allocated to PUSCH 2, and vice versa.

[0071] To schedule such staggered FDM, a single FDRA is indicated in the scheduling information for both PUSCH 1 and PUSCH 2. For example, FDRA can be implemented by a "frequency domain resource allocation" field in a DCI for scheduling PUSCH, such as DCI format 0_0 or 0_1 or 0_2. The frequency domain resources scheduled by FDRA are divided between PUSCH 1 and PUSCH 2 and are interleaved based on an interleaving unit. Examples of interleaving units include one or more REs, one or more PRBs, and the like. The interleaving unit may be hard-coded in the protocol specification, or may be configured by RRC layer signaling such as ConfiguredGrantConfig or PUSCH-Config information element (IE), or by MAC layer signaling such as a medium access control (MAC) control element (CE), or by a physical layer DCI such as a DCI including FDRA. In this way, the resources indicated by FDRA actually include two frequency domain resource sets, each for one PUSCH (further for one panel).

[0072] In non-interleaved FDM, the frequency domain resources for PUSCH 1 and the frequency domain resources for PUSCH 2 may be separated by a number X>=0 of frequency domain resources (eg, REs or PRBs), such as Figure 7 Although Figure 7 The resources used for each of PUSCH 1 and PUSCH 2 are depicted as uninterrupted blocks, but they may or may not be discontinuous. In addition, the resources used for PUSCH 1 and the resources used for PUSCH 2 may be adjacent in the frequency domain (i.e., X=0) or may not be adjacent in the frequency domain (i.e., X>0).

[0073] To support non-interleaved FDM, in one example, a single FDRA is indicated in the scheduling information for one of PUSCH 1 and PUSCH 2 (e.g., for PUSCH 1), and the frequency domain resources for the other (e.g., for PUSCH 2) may be determined by the FDRA and a frequency offset specifying the offset of the resources for PUSCH 2 relative to the resources for PUSCH 1, both of which may span the same number of RBs in the frequency domain. The frequency offset may be defined from the end of the frequency domain resources for PUSCH 1, or from the beginning of the frequency domain resources for PUSCH 1. Examples of frequency offsets may include zero or more REs, zero or more PRBs, etc. The frequency offset may be configured by RRC layer signaling, by MAC CE, or by DCI (such as a DCI including the FDRA).

[0074] In another example, independent FDRAs are indicated in the scheduling information for PUSCH 1 and PUSCH 2. For example, two "frequency domain resource allocation" fields may be introduced in the DCI, each for one PUSCH (further for one panel). Upon receiving such a DCI, the UE may determine the corresponding FDRA for each of PUSCH 1 and PUSCH 2 from the two "frequency domain resource allocation" fields. In this example, PUSCH 1 and PUSCH 2 may be allocated with different RBs.

[0075] In addition, according to one aspect of the present application, the same resource allocation type applies to PUSCH transmissions sent simultaneously by all panels. The resource allocation type specifies how RBs are allocated to UEs. For a configured grant, the resource allocation type is configured in the RRC parameter resourceAllocation of ConfiguredGrantConfig, for example as follows:

[0076]

[0077]

[0078] For dynamic authorization, the resource allocation type is configured in the RRC parameter resourceAllocation of PUSCH-Config as follows:

[0079]

[0080] There are generally two resource allocation types, including resource allocation type 0 and resource allocation type 1. PUSCH 1 and PUSCH 2 may be configured with the RRC parameter resourceAllocation set to "resourceAllocationType0" so that their frequency domain resource allocation follows resource allocation type 0, or configured with the RRC parameter resourceAllocation set to "resourceAllocationType1" so that their frequency domain resource allocation follows resource allocation type 1. When the RRC parameter resourceAllocation is configured to "dynamicSwitch", both PUSCH 1 and PUSCH 2 will be dynamically indicated, always having the same resource allocation type, either resource allocation type 0 or resource allocation type 1.

[0081] Time Domain Resource Allocation (TDRA)

[0082] As used herein, "simultaneous" PUSCH transmissions mean that there is a period of time in which two or more panels are performing PUSCH operations. In the time domain, a PUSCH transmission from one panel may or may not be completely aligned with a PUSCH transmission from another panel, but they at least partially overlap.

[0083] According to the present application, as a result of supporting simultaneous multi-panel PUSCH transmissions, the base station can schedule PUSCH transmissions in an overlapping manner. Figure 3 An example situation of two panels is shown to describe TDRA.

[0084] In one aspect, a single TDRA is indicated in the scheduling information for both PUSCH 1 and PUSCH 2, assuming that they have the same time domain resources. For example, TDRA can be implemented by the "Time Domain Resource Allocation" field in the DCI used to schedule PUSCH, such as DCI format 0_0 or 0_1 or 0_2. Examples of time domain scheduling units include one or more time slots, or even several OFDM symbols in a time slot, called mini-slots. Upon receiving such DCI, the UE can apply the time domain resources to the PUSCH transmissions to be sent from panel 1 and panel 2. This scheduling approach is particularly applicable when the PUSCH transmissions serve the same HARQ process.

[0085] In another aspect, independent TDRAs are indicated in the scheduling information for PUSCH 1 and PUSCH 2. For example, two "time domain resource allocation" fields may be introduced in the DCI, one for each PUSCH (and further for one panel). Upon receiving such a DCI, the UE may determine the corresponding TDRA for each of PUSCH 1 and PUSCH 2 from the two "time domain resource allocation" fields. In this example, PUSCH 1 and PUSCH 2 may be independently allocated, e.g., with different numbers of time slots, which may be applicable when the PUSCH transmissions serve different HARQ processes.

[0086] For multiple "time domain resource allocation" fields, TDRA indications for different PUSCH transmissions may refer to the same TDRA table. The TDRA table is a table configured by RRC signaling, such as pusch-TimeDomainAllocationList or its variants, including pusch-TimeDomainAllocationListDCI-0-1, pusch-TimeDomainAllocationListDCI-0-2 or pusch-TimeDomainAllocationListForMultiPUSCH as defined in 3GPP Release 16, or pusch-TimeDomainResourceAllocationListForMultiPUSCH as defined in 3GPP Release 17. The TDRA table has a list of entries, each of which maps a "TDRA" index to a corresponding time domain resource allocation. Each entry of the TDRA table may be configured with the same time domain resource allocation for two panels, or with different time domain resource allocations for each panel.

[0087] Alternatively, TDRA indications for different PUSCH transmissions may refer to different TDRA tables configured separately by RRC signaling. Therefore, PUSCH 1 to be transmitted from panel 1 and PUSCH 2 to be transmitted from panel 2 may be scheduled according to different time domain resource allocation types.

[0088] Precoding Indicator

[0089] Precoding techniques can be used to improve system performance. Generally speaking, there is digital precoding for baseband signals, analog precoding for radio frequency (RF) signals, or a combination thereof, such as hybrid precoding.

[0090] Based on the use of codebooks in digital precoding, NR supports two PUSCH transmission schemes, codebook-based transmission or non-codebook-based transmission, and supports up to 4 layers. When the higher layer parameter txConfig is set to "Codebook", the UE is configured with codebook-based transmission, and when the higher layer parameter txConfig is set to "nonCodebook", the UE is configured with non-codebook-based transmission.

[0091] For codebook-based UL transmission, the UE sends a sounding reference signal (SRS) resource to the base station in an SRS resource set with multiple ports, and the base station performs uplink channel detection and determines the precoder (precoding matrix) to be used based on the codebook and the number of layers. The base station schedules PUSCH transmission by indicating an SRS resource indicator (SRI) identifying an SRS resource corresponding to the selected precoding matrix, a transmit precoding matrix indicator (TPMI) identifying the selected precoding matrix, and a rank indication (RI) indicating the number of layers.

[0092] For non-codebook based transmission, the UE detects a downlink reference signal, such as a channel state information RS (CSI-RS), and calculates an uplink candidate SRS precoder based on the channel reciprocity of the uplink and downlink channels. The UE precodes multiple SRS resources using the candidate SRS precoder and sends the precoded SRS resources, each with a single port, to the base station. The base station receives the SRS resources and selects one or more appropriate SRS resources based on the uplink channel conditions. The base station schedules PUSCH transmission by indicating one or more selected SRS resources / ports using SRI, and indicates the number of layers by the number of selected SRS resources.

[0093] Analog precoding is also known as analog beamforming or beamforming, which is used to form a directional beam by applying phase adjustment to the RF signal at the antenna in the antenna array. The UE is configured with a set of beams, and the best pair of transmit and receive beams is determined through a process of beam training. For example, UL beam training may include: 1) beam scanning, the UE sends SRS resources to the base station in the SRS resource set; 2) beam measurement, the base station measures the received SRS and determines the SRS resource with the best beam gain; and 3) beam indication, the base station indicates the selected SRS resource to the UE so that the UE can use the beam corresponding to the SRS resource for UL transmission. Beam indication can be implemented by an SRI that identifies the selected SRS resource. Alternatively, a unified transmission configuration indication (TCI) state including information identifying the uplink spatial filter can be used for UL beam indication.

[0094] According to one aspect of the present application, various precoding information including SRI, TPMI, RI and unified TCI states may be indicated to the UE, for example, together with FDRA and TDRA, to support simultaneous multi-panel PUSCH transmission. DCI, such as format 0_1 ​​or 0_2, may be used to carry one or more of the "SRS resource indicator" field for indicating SRI, which may be used for digital precoding and / or analog precoding; "precoding information and number of layers" field, which is used to indicate TPMI and RI that may be used in digital precoding for codebook-based PUSCH transmission; or "transmission configuration indication" field, which is used to indicate the TCI state that may be used for analog precoding.

[0095] In one example, independent precoding information may be indicated for different PUSCH transmissions (and further for different panels). Figure 3 For example, in the case of two panels, two "SRS resource indicator" fields may be introduced in the DCI, each field being used for one panel, and the UE may determine the corresponding uplink transmit precoding matrix and / or uplink beam for each of PUSCH 1 and PUSCH 2; and / or two "precoding information and number of layers" fields may be introduced in the DCI, each field being used for one panel, and the UE may determine the corresponding uplink transmit precoding matrix for each of PUSCH 1 and PUSCH 2; and / or two "transmission configuration indication" fields may be introduced in the DCI, each field being used for one panel, and the UE may determine the corresponding uplink beam for each of PUSCH 1 and PUSCH 2.

[0096] In another example, a single piece of precoding information may be indicated for simultaneous PUSCH transmissions assuming the same SRI / TPMI / RI / unified TCI state.

[0097] According to one aspect of the present application, the same number of layers (ranks), for example, 2 layers per panel, are scheduled for all PUSCH transmissions from multiple panels. The same antenna port configuration is assumed for all PUSCH transmissions from multiple panels.

[0098] In the example case where a maximum of two layers per panel are used for PUSCH transmission, only one bit of the "PTRS-DMRS Association" field may be introduced in the DCI to indicate the association between the phase tracking reference signal (PTRS) and the demodulation reference signal (DMRS). For example, if the field is set to "0", the PTRS is mapped to the first DMRS port, and if the field is set to "0", the PTRS is mapped to the second DMRS port.

[0099] In one aspect, a 1-port PTRS may be shared between PUSCH transmissions from different panels.PTRS are typically distributed with low density in the frequency domain and with high density in the time domain. Figure 8 The application of PTRS in time-frequency resources is shown (for example, Figure 3 The PTRS of one port is used for phase noise estimation of both PUSCH 1 from panel 1 and PUSCH 2 from panel 2.

[0100] Transport Block (TB) Configuration

[0101] For PUSCH transmission, user data from the medium access control (MAC) layer will be processed into TBs, which need to go through a series of uplink physical layer processing in order to be mapped to the transmission channel in the physical layer. The uplink physical layer processing generally includes:

[0102] - Cyclic Redundancy Check (CRC) addition to transport blocks;

[0103] - Code block segmentation and code block CRC addition;

[0104] - channel coding;

[0105] - Physical layer HARQ processing;

[0106] -Rate matching;

[0107] - scrambling;

[0108] -modulation;

[0109] - Layer mapping, transform precoding and precoding;

[0110] - Mapping to allocated resources and antenna ports, etc.

[0111] Through various signal processing functions of the physical layer, the bit stream as user data is encoded and modulated into OFDM symbols and sent to the base station by the corresponding antenna array / panel using the allocated time-frequency resources. The base station receiving the signal receives the user data and decodes the user data through the inverse process of the above signal processing.

[0112] As described above, PUSCH transmissions from different panels may be used in a flexible manner. According to one aspect of the present application, one or more of the following use cases may be supported.

[0113] Case 1: TB is jointly encoded and sent from all panels. Figure 9aAs shown exemplarily, for the TB to be transmitted, the available number of REs is the union of the REs used for PUSCH 1 from panel 1 and PUSCH 2 from panel 2, as indicated in FDRA and TDRA. The base station may determine a modulation and coding scheme (MCS) based on the total REs used for PUSCH 1 and PUSCH 2 and the size of the TB for which PUSCH transmission is requested, and may indicate the determined MCS to the UE, for example, via a single "Modulation and Coding Scheme" field in the DCI.

[0114] In case 1, PUSCH transmissions from multiple panels are used for one HARQ process, and a single "New Data Indicator (NDI)" field is required in the DCI to indicate whether the PUSCH transmission is a retransmission or an initial transmission for a TB.

[0115] Case 2: TB is encoded individually and sent repeatedly from all panels. Figure 9b As shown exemplarily, for the TB to be transmitted, the available number of REs is the REs for each of PUSCH 1 from panel 1 and PUSCH 2 from panel 2. The base station may determine the MCS based on the total REs and TB size for PUSCH 1 or PUSCH 2, and may indicate the determined MCS to the UE, for example, via a single "Modulation and Coding Scheme" field in the DCI. In addition, the UE may use the PUSCH transmission for one HARQ process with a single "New Data Indicator" field in the DCI.

[0116] For PUSCH 1 and PUSCH 2, the same or different redundancy versions (RVs) may be applied to the corresponding TBs according to the RV sequence. The RV determines the rate matching of the coded TBs and may also be indicated in the DCI, i.e., in the "Redundancy Version" field. Figure 9b As shown, RV 0 is applied to TB 1 to be transmitted by PUSCH 1, and the same RV0 or a different RV2 is applied to TB 1 to be transmitted by PUSCH 2.

[0117] Case 3: Different TBs are encoded and sent from different panels. Fig.9c As exemplarily shown, TB 1 will be transmitted by PUSCH 1 from panel 1, and TB 2 will be transmitted by PUSCH 2 from panel 2. Therefore, the available number of REs for TB 1 is the REs for PUSCH 1, and the available number of REs for TB 2 is the REs for PUSCH 2. For PUSCH 1 and PUSCH 2, different or the same redundancy versions may be applied to the corresponding TBs according to the RV sequence.

[0118] The base station may determine the MCS for each of PUSCH 1 and PUSCH 2 based on the available REs and the size of the corresponding TB. If the same MCS is used, the base station may indicate the common MCS to the UE, for example, via a single "Modulation and Coding Scheme" field in the DCI. Alternatively, separate "Modulation and Coding Scheme" fields may be introduced in the DCI, each for one PUSCH (and further for one panel).

[0119] In case 3, the UE may use PUSCH transmissions from multiple panels to send different TBs in one HARQ process, or may use them to send different TBs in different HARQ processes. In addition, a common "new data indicator" field or an independent "new data indicator" field may be indicated in the DCI.

[0120] Although three example cases are described above, simultaneous multi-panel PUSCH transmission may be used for any other possible purposes, which will fall within the scope of the present application.

[0121] Uplink Power Control

[0122] According to one aspect of the present application, various uplink power control strategies may be used for simultaneous multi-panel PUSCH transmissions.

[0123] In one example, the base station may schedule PUSCH transmissions from multiple panels so as to ensure the same power spectral density (PSD). For open-loop power control (OLPC), when multiple path loss reference signals (such as SSB) each for one panel are configured, the path loss from only one reference signal is used by the UE. For example, the UE may compensate for the maximum path loss in a "quality first" consideration, or may compensate for the minimum path loss in a "energy saving first" consideration. For closed-loop power control (CLPC), the base station may perform transmit power control (TPC) for PUSCH transmissions, for example, via the "TPC command for scheduled PUSCH" field in the DCI.

[0124] The base station may send a single TPC command for all PUSCH transmissions to the UE, and the UE adjusts the corresponding transmit power from each of its panels. Alternatively, the base station may send independent TPC commands to the UE, each for one PUSCH transmission (further for one panel). In this case, multiple "TPC command for scheduled PUSCH" fields may be introduced in the DCI. When receiving a TPC command, the UE makes only one TPC decision, for example, "or down" or "or up".

[0125] In another example, each of the PUSCH transmissions from multiple panels may have its own different transmit power. Specifically, the base station may send independent TPC commands for PUSCH transmissions to the UE, for example, via multiple "TPC command for scheduled PUSCH" fields in the DCI. The UE sets the corresponding transmit power for each of the PUSCH transmissions based on these TPC commands.

[0126] Simultaneous PUSCH transmissions from multiple panels may face requirements for maximum permitted exposure. For example, the Federal Communications Commission has proposed a limit on equivalent isotropic radiated power (EIRP), such as 1mW / cm 2 Another consideration relates to energy saving, especially if the UE is an energy-constrained device powered by a battery. If two or more panels are transmitting, this places a limit on their total transmit power. Therefore, it may be necessary to adjust the transmit power of the PUSCH transmissions to below a total threshold.

[0127] In one example, the transmit power of each of the PUSCH transmissions is scaled by the same factor (eg, -3dB, etc.) so that the total transmit power does not exceed the associated requirement.

[0128] In another example, the adjustment of the transmit power of PUSCH transmissions may be based on priority or ranking. PUSCH with low priority is scaled first. For example, referring to Figure 3 In the case of two panels, assuming that PUSCH 1 has a higher priority than PUSCH 2, the UE may apply less adjustment or no adjustment at all to the transmit power of PUSCH 1, while the UE may apply more adjustment to the transmit power of PUSCH 2. This may ensure the quality of service of PUSCH 1. The priority may be based on the order of the panels. The panels may correspond to a logical ID, such as an SRS resource ID, and the base station may control the adjustment of PUSCH transmissions from the panels via the logical ID.

[0129] The correspondence between PUSCH and physical panels may be agnostic to the base station. The base station schedules two resource sets for two PUSCH transmissions, but may not decide which panel sends a specific PUSCH. This decision may depend on the specific implementation at the UE, especially when the UE is equipped with more than two panels. However, the base station may specify the desired panel selection, for example via the logical ID of the panel. That is, there is a possibility that the base station may be able to control a specific panel of the UE to perform PUSCH operation after the UE has reported its panel configuration as a UE capability.

[0130] Embodiments contemplated herein include an apparatus comprising a device for performing Figure 4A means for one or more elements of the illustrated method. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 202 as a UE, as described herein).

[0131] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the following operations: Figure 4 One or more elements of the method shown. The non-transitory computer-readable medium may be, for example, a memory of a UE (such as the memory 206 of the wireless device 202 as a UE, as described herein).

[0132] Embodiments contemplated herein include an apparatus comprising a device for performing Figure 4 Logic, modules or circuits of one or more elements of the illustrated method. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 202 as a UE, as described herein).

[0133] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the following operations: Figure 4 One or more elements of the method shown. The apparatus may be, for example, an apparatus of a UE (such as the wireless device 202 as a UE, as described herein).

[0134] Embodiments contemplated herein include a signal such as Figure 4 The invention may be described in or relating to one or more elements of the method shown.

[0135] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processor causes the processor to perform the following: Figure 4 One or more elements of the method shown. The processor may be a processor of a UE (such as the processor 204 of the wireless device 202 as a UE, as described herein). These instructions may be located, for example, in the processor and / or on a memory of the UE (such as the memory 206 of the wireless device 202 as a UE, as described herein).

[0136] Embodiments contemplated herein include an apparatus comprising a device for performing Figure 5 A means for one or more elements of the illustrated method. The apparatus may be, for example, an apparatus of a base station (such as network device 218 as a base station, as described herein).

[0137] Embodiments contemplated herein include one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform the following operations: Figure 5 One or more elements of the method shown. The non-transitory computer-readable medium may be, for example, a memory of a base station (such as the memory 222 of the network device 218 as a base station, as described herein).

[0138] Embodiments contemplated herein include an apparatus comprising a device for performing Figure 5 Logic, modules or circuits of one or more elements of the illustrated method. The apparatus may be, for example, an apparatus of a base station (such as the network device 218 as a base station, as described herein).

[0139] Embodiments contemplated herein include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the following operations: Figure 5 One or more elements of the method shown. The apparatus may be, for example, an apparatus of a base station (such as network device 218 as a base station, as described herein).

[0140] Embodiments contemplated herein include a signal such as Figure 5 The invention may be described in or relating to one or more elements of the method shown.

[0141] Embodiments contemplated herein include a computer program or computer program product comprising instructions, wherein execution of the program by a processing element causes the processing element to perform the following steps: Figure 5 One or more elements of the method shown. The processor may be a processor of a base station (such as processor 220 of network device 218 as a base station, as described herein). These instructions may, for example, be located in the processor and / or in a memory of the UE (such as memory 222 of network device 218 as a base station, as described herein).

[0142] For one or more embodiments, at least one of the components set forth in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes and / or methods as set forth herein. For example, a baseband processor as described herein in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein. For another example, circuits associated with a UE, a base station, a network element, etc. as described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples set forth herein.

[0143] Examples

[0144] The following examples relate to additional embodiments.

[0145] Embodiment 1 may include a user equipment (UE) device, comprising: a processor; and a memory storing instructions, wherein the instructions, when executed by the processor, configure the device to: receive scheduling information from a base station for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in the time domain; and in response to the scheduling information, perform the first PUSCH transmission through a first antenna panel and the second PUSCH transmission through a second antenna panel by using mutually different frequency domain resources.

[0146] Embodiment 2 may include the apparatus of embodiment 1, wherein the frequency domain resources used for the first PUSCH transmission are interleaved with the frequency domain resources used for the second PUSCH transmission.

[0147] Embodiment 3 may include an apparatus according to embodiment 2, wherein the scheduling information includes a frequency domain resource allocation (FDRA), and the frequency domain resources indicated by the FDRA are divided and interleaved based on an interleaving unit used for the first PUSCH transmission and the second PUSCH transmission, and wherein the interleaving unit is a resource element (RE), a physical resource block (PRB), or one of multiple PRBs.

[0148] Embodiment 4 may include the apparatus of embodiment 1, wherein the frequency domain resources used for the first PUSCH transmission are separate from the frequency domain resources used for the second PUSCH transmission.

[0149] Embodiment 5 may include an apparatus according to embodiment 4, wherein the scheduling information includes one of the following items: a frequency domain resource allocation (FDRA) for the first PUSCH transmission, wherein the frequency domain resources for the second PUSCH transmission are determined by a frequency offset from the frequency domain resources used for the first PUSCH transmission, the frequency offset comprising 0 or more resource elements (REs) or physical resource blocks (PRBs), or corresponding FDRAs for the first PUSCH transmission and the second PUSCH transmission.

[0150] Embodiment 6 may include the apparatus of embodiment 1, wherein the same resource allocation type is configured for the first PUSCH transmission and the second PUSCH transmission.

[0151] Embodiment 7 may include the apparatus of embodiment 1, wherein the scheduling information includes a time domain resource allocation (TDRA) for both the first PUSCH transmission and the second PUSCH transmission.

[0152] Embodiment 8 may include the apparatus of embodiment 1, wherein the scheduling information includes respective time domain resource allocations (TDRAs) for the first PUSCH transmission and the second PUSCH transmission.

[0153] Embodiment 9 may include an apparatus as in Embodiment 8, wherein the TDRAs reference the same TDRA table, or wherein the TDRAs reference different TDRA tables.

[0154] Embodiment 10 may include an apparatus according to embodiment 1, wherein the scheduling information includes one of the following items: precoding information common to the first PUSCH transmission and the second PUSCH transmission, or corresponding precoding information for the first PUSCH transmission and the second PUSCH transmission, wherein the precoding information includes at least one of a sounding reference signal (SRS) resource indicator (SRI), a transmission configuration indication (TCI) status, and a transmit precoding matrix indicator (TPMI).

[0155] Embodiment 11 may include the apparatus of embodiment 1, wherein the first PUSCH transmission and the second PUSCH transmission have the same number of layers; and / or

[0156] The first PUSCH transmission and the second PUSCH transmission have the same antenna port configuration.

[0157] Embodiment 12 may include an apparatus according to embodiment 11, wherein the scheduling information includes PTRS-DMRS association information common to the first PUSCH transmission and the second PUSCH transmission, and / or wherein the first PUSCH transmission and the second PUSCH transmission share the same single-port PTRS.

[0158] Embodiment 12 may include an apparatus according to embodiment 1, wherein at least one of the following items is supported: a transport block (TB) is jointly encoded for the first PUSCH transmission and the second PUSCH transmission and is sent by the first PUSCH transmission and the second PUSCH transmission; or a TB is repeatedly sent by the first PUSCH transmission and the second PUSCH transmission; or different TBs are sent by the first PUSCH transmission and the second PUSCH transmission.

[0159] Embodiment 14 may include the apparatus of embodiment 1, wherein the scheduling information includes a modulation and coding scheme (MSC) and / or a new data indicator (NDI) and / or a redundancy version (RV) common to the first PUSCH transmission and the second PUSCH transmission; or

[0160] The scheduling information includes corresponding MSC and / or NDI and / or RV for the first PUSCH transmission and the second PUSCH transmission.

[0161] Embodiment 15 may include an apparatus according to embodiment 1, wherein the scheduling information includes uplink power control information so that the same power spectral density (PSD) is ensured for both the first PUSCH transmission and the second PUSCH transmission, or the first PUSCH transmission and the second PUSCH transmission have their own different transmission powers.

[0162] Embodiment 16 may include the apparatus of embodiment 15, wherein the transmit power of each of the first PUSCH transmission and the second PUSCH transmission is scaled by the same factor or based on priority.

[0163] Embodiment 17 may include a base station device, the device comprising: a processor; and a memory storing instructions, the instructions, when executed by the processor, configuring the device to: send scheduling information to a user equipment (UE) for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that partially overlap in the time domain; and in response to the scheduling information, receive the first PUSCH transmission and the second PUSCH transmission performed by the UE using mutually different frequency domain resources, wherein the first PUSCH transmission and the second PUSCH transmission are respectively from a first antenna panel and a second antenna panel of the UE.

[0164] Embodiment 18 may include the apparatus of embodiment 17, wherein the frequency domain resources used for the first PUSCH transmission are interleaved with the frequency domain resources used for the second PUSCH transmission.

[0165] Embodiment 19 may include an apparatus according to embodiment 18, wherein the scheduling information includes a frequency domain resource allocation (FDRA), and the frequency domain resources indicated by the FDRA are divided and interleaved based on an interleaving unit used for the first PUSCH transmission and the second PUSCH transmission, and wherein the interleaving unit is a resource element (RE), a physical resource block (PRB), or one of multiple PRBs.

[0166] Embodiment 20 may include the apparatus of embodiment 17, wherein the frequency domain resources used for the first PUSCH transmission are separate from the frequency domain resources used for the second PUSCH transmission.

[0167] Embodiment 21 may include an apparatus according to embodiment 20, wherein the scheduling information includes one of the following items: a frequency domain resource allocation (FDRA) for the first PUSCH transmission, wherein the frequency domain resources for the second PUSCH transmission are determined by a frequency offset from the frequency domain resources used for the first PUSCH transmission, the frequency offset comprising 0 or more resource elements (REs) or physical resource blocks (PRBs), or corresponding FDRAs for the first PUSCH transmission and the second PUSCH transmission.

[0168] Embodiment 22 may include the apparatus of embodiment 17, wherein the scheduling information includes time domain resource allocation (TDRA) for both the first PUSCH transmission and the second PUSCH transmission, or wherein the scheduling information includes corresponding time domain resource allocation (TDRA) for the first PUSCH transmission and the second PUSCH transmission.

[0169] Embodiment 23 may include an apparatus according to embodiment 17, wherein the scheduling information includes one of the following items: precoding information common to the first PUSCH transmission and the second PUSCH transmission, or corresponding precoding information for the first PUSCH transmission and the second PUSCH transmission, wherein the precoding information includes at least one of a sounding reference signal (SRS) resource indicator (SRI), a transmission configuration indication (TCI) status, and a transmit precoding matrix indicator (TPMI).

[0170] Embodiment 24 may include an apparatus according to embodiment 17, wherein the first PUSCH transmission and the second PUSCH transmission have the same number of layers; and / or wherein the first PUSCH transmission and the second PUSCH transmission have the same antenna port configuration.

[0171] Embodiment 25 may include an apparatus according to embodiment 24, wherein the scheduling information includes PTRS-DMRS association information common to the first PUSCH transmission and the second PUSCH transmission, and / or wherein the first PUSCH transmission and the second PUSCH transmission share the same single-port PTRS.

[0172] Embodiment 26 may include an apparatus according to embodiment 17, wherein at least one of the following items is supported: a transport block (TB) is jointly encoded for the first PUSCH transmission and the second PUSCH transmission and is sent by the first PUSCH transmission and the second PUSCH transmission; or a TB is repeatedly sent by the first PUSCH transmission and the second PUSCH transmission; or different TBs are sent by the first PUSCH transmission and the second PUSCH transmission.

[0173] Embodiment 27 may include the apparatus of embodiment 17, wherein the scheduling information includes a modulation and coding scheme (MSC) and / or a new data indicator (NDI) and / or a redundancy version (RV) common to the first PUSCH transmission and the second PUSCH transmission; or

[0174] The scheduling information includes corresponding MSC and / or NDI and / or RV for the first PUSCH transmission and the second PUSCH transmission.

[0175] Embodiment 28 may include an apparatus according to embodiment 17, wherein the scheduling information includes uplink power control information so that the same power spectral density (PSD) is ensured for both the first PUSCH transmission and the second PUSCH transmission, or the first PUSCH transmission and the second PUSCH transmission have their own different transmission powers.

[0176] Embodiment 29 may include a method comprising: receiving scheduling information from a base station for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in the time domain; and in response to the scheduling information, performing the first PUSCH transmission through a first antenna panel and the second PUSCH transmission through a second antenna panel by using mutually different frequency domain resources.

[0177] Embodiment 30 may include a method comprising: sending scheduling information to a user equipment (UE) for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that partially overlap in the time domain; and in response to the scheduling information, receiving the first PUSCH transmission and the second PUSCH transmission performed by the UE using mutually different frequency domain resources, wherein the first PUSCH transmission and the second PUSCH transmission are respectively from a first antenna panel and a second antenna panel of the UE.

[0178] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise form disclosed. In view of the above teachings, modifications and variations are possible, or can be obtained from the practice of various embodiments.

[0179] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations; or may include a combination of hardware, software, and / or firmware.

[0180] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially combined into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of another embodiment may be used in one embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless expressly stated herein.

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

[0182] Although the foregoing has been described in considerable detail for the sake of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles of the invention. It should be noted that there are many alternative ways of implementing both the processes and the apparatus described herein. Therefore, the embodiments of the present invention should be regarded as illustrative rather than restrictive, and the specification is not limited to the details given herein, but may be modified within the scope and equivalents of the appended claims.

Claims

1. A device of a user equipment (UE), the device comprising: processor; and a memory storing instructions that, when executed by the processor, configure the apparatus to: receiving, from a base station, scheduling information for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in a time domain; and In response to the scheduling information, the first PUSCH transmission through the first antenna panel and the second PUSCH transmission through the second antenna panel are performed by using frequency domain resources different from each other.

2. The apparatus according to claim 1, wherein the frequency domain resources used for the first PUSCH transmission are interleaved with the frequency domain resources used for the second PUSCH transmission.

3. The apparatus of claim 2, wherein the scheduling information comprises a frequency domain resource allocation (FDRA), and the frequency domain resources indicated by the FDRA are divided and interleaved based on an interleaving unit used for the first PUSCH transmission and the second PUSCH transmission, and wherein the interleaving unit is one of a resource element (RE), a physical resource block (PRB), or a plurality of PRBs. 4 . The apparatus of claim 1 , wherein the frequency domain resources used for the first PUSCH transmission are separated from the frequency domain resources used for the second PUSCH transmission.

5. The apparatus according to claim 4, wherein the scheduling information comprises one of the following: a frequency domain resource allocation (FDRA) for the first PUSCH transmission, wherein the frequency domain resources for the second PUSCH transmission are determined by a frequency offset from the frequency domain resources for the first PUSCH transmission, the frequency offset comprising zero or more resource elements (REs) or physical resource blocks (PRBs), or Respective FDRAs for the first PUSCH transmission and the second PUSCH transmission.

6. The apparatus of claim 1, wherein the same resource allocation type is configured for the first PUSCH transmission and the second PUSCH transmission.

7. The apparatus of claim 1, wherein the scheduling information comprises a time domain resource allocation (TDRA) for both the first PUSCH transmission and the second PUSCH transmission.

8. The apparatus of claim 1, wherein the scheduling information comprises respective time domain resource allocations (TDRAs) for the first PUSCH transmission and the second PUSCH transmission.

9. The apparatus of claim 8, wherein the TDRAs reference the same TDRA table, or wherein the TDRAs reference different TDRA tables.

10. The apparatus of claim 1, wherein the scheduling information comprises one of the following: precoding information common to the first PUSCH transmission and the second PUSCH transmission, or corresponding precoding information for the first PUSCH transmission and the second PUSCH transmission, The precoding information includes at least one of a sounding reference signal (SRS) resource indicator (SRI), a transmission configuration indication (TCI) state, and a transmit precoding matrix indicator (TPMI).

11. The apparatus of claim 1 , wherein the first PUSCH transmission and the second PUSCH transmission have the same number of layers; and / or The first PUSCH transmission and the second PUSCH transmission have the same antenna port configuration.

12. The apparatus according to claim 11, wherein the scheduling information comprises PTRS-DMRS association information common to the first PUSCH transmission and the second PUSCH transmission, and / or The first PUSCH transmission and the second PUSCH transmission share the same single-port PTRS.

13. The apparatus of claim 1, wherein at least one of the following is supported: A transport block (TB) is jointly coded for the first PUSCH transmission and the second PUSCH transmission and is transmitted by the first PUSCH transmission and the second PUSCH transmission; or A TB is repeatedly transmitted by the first PUSCH transmission and the second PUSCH transmission; or Different TBs are sent by the first PUSCH transmission and the second PUSCH transmission.

14. The apparatus according to claim 1, wherein the scheduling information comprises a modulation and coding scheme (MSC) and / or a new data indicator (NDI) and / or a redundancy version (RV) common to the first PUSCH transmission and the second PUSCH transmission; or The scheduling information includes corresponding MSC and / or NDI and / or RV for the first PUSCH transmission and the second PUSCH transmission.

15. The apparatus according to claim 1, wherein the scheduling information includes uplink power control information so that the same power spectral density (PSD) is ensured for both the first PUSCH transmission and the second PUSCH transmission, or the first PUSCH transmission and the second PUSCH transmission have their own different transmission powers.

16. The apparatus of claim 15, wherein the transmit power of each of the first PUSCH transmission and the second PUSCH transmission is scaled by a same factor or based on a priority.

17. A base station device, the device comprising: processor; and a memory storing instructions that, when executed by the processor, configure the apparatus to: transmitting, to a user equipment (UE), scheduling information for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that partially overlap in a time domain; and In response to the scheduling information, the first PUSCH transmission and the second PUSCH transmission performed by the UE using different frequency domain resources are received, wherein the first PUSCH transmission and the second PUSCH transmission are from a first antenna panel and a second antenna panel of the UE, respectively.

18. The apparatus of claim 17, wherein the frequency domain resources used for the first PUSCH transmission are interleaved with the frequency domain resources used for the second PUSCH transmission.

19. The apparatus of claim 18, wherein the scheduling information comprises a frequency domain resource allocation (FDRA), and the frequency domain resources indicated by the FDRA are divided and interleaved based on an interleaving unit used for the first PUSCH transmission and the second PUSCH transmission, and wherein the interleaving unit is one of a resource element (RE), a physical resource block (PRB), or a plurality of PRBs.

20. The apparatus of claim 17, wherein the frequency domain resources used for the first PUSCH transmission are separated from the frequency domain resources used for the second PUSCH transmission.

21. The apparatus of claim 20, wherein the scheduling information comprises one of the following: a frequency domain resource allocation (FDRA) for the first PUSCH transmission, wherein the frequency domain resources for the second PUSCH transmission are determined by a frequency offset from the frequency domain resources for the first PUSCH transmission, the frequency offset comprising zero or more resource elements (REs) or physical resource blocks (PRBs), or Respective FDRAs for the first PUSCH transmission and the second PUSCH transmission.

22. The apparatus of claim 17, wherein the scheduling information comprises a time domain resource allocation (TDRA) for both the first PUSCH transmission and the second PUSCH transmission, or The scheduling information includes corresponding time domain resource allocation (TDRA) for the first PUSCH transmission and the second PUSCH transmission.

23. The apparatus of claim 17, wherein the scheduling information comprises one of the following: precoding information common to the first PUSCH transmission and the second PUSCH transmission, or corresponding precoding information for the first PUSCH transmission and the second PUSCH transmission, The precoding information includes at least one of a sounding reference signal (SRS) resource indicator (SRI), a transmission configuration indication (TCI) state, and a transmit precoding matrix indicator (TPMI).

24. The apparatus of claim 17, wherein the first PUSCH transmission and the second PUSCH transmission have the same number of layers; and / or The first PUSCH transmission and the second PUSCH transmission have the same antenna port configuration.

25. The apparatus according to claim 24, wherein the scheduling information comprises PTRS-DMRS association information common to the first PUSCH transmission and the second PUSCH transmission, and / or The first PUSCH transmission and the second PUSCH transmission share the same single-port PTRS.

26. The apparatus of claim 17, wherein at least one of the following is supported: A transport block (TB) is jointly coded for the first PUSCH transmission and the second PUSCH transmission and is transmitted by the first PUSCH transmission and the second PUSCH transmission; or A TB is repeatedly transmitted by the first PUSCH transmission and the second PUSCH transmission; or Different TBs are sent by the first PUSCH transmission and the second PUSCH transmission.

27. The apparatus of claim 17, wherein the scheduling information comprises a modulation and coding scheme (MSC) and / or a new data indicator (NDI) and / or a redundancy version (RV) common to the first PUSCH transmission and the second PUSCH transmission; or The scheduling information includes corresponding MSC and / or NDI and / or RV for the first PUSCH transmission and the second PUSCH transmission.

28. The apparatus according to claim 17, wherein the scheduling information includes uplink power control information so that the same power spectral density (PSD) is ensured for both the first PUSCH transmission and the second PUSCH transmission, or the first PUSCH transmission and the second PUSCH transmission have their own different transmission powers.

29. A method comprising: receiving, from a base station, scheduling information for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that at least partially overlap in a time domain; as well as In response to the scheduling information, the first PUSCH transmission through the first antenna panel and the second PUSCH transmission through the second antenna panel are performed by using frequency domain resources different from each other.

30. A method comprising: Sending scheduling information to a user equipment (UE) for scheduling a first physical uplink shared channel (PUSCH) transmission and a second PUSCH transmission that partially overlap in a time domain; as well as In response to the scheduling information, the first PUSCH transmission and the second PUSCH transmission performed by the UE using different frequency domain resources are received, wherein the first PUSCH transmission and the second PUSCH transmission are from a first antenna panel and a second antenna panel of the UE, respectively.

Images