Simultaneous PUSCH transmission based on multiple DCI

Abstract

The invention relates to simultaneous PUSCH transmission based on multiple DCI. The network device may be configured to: generate a plurality of downlink control information (DCI) for scheduling simultaneous transmission of a plurality of physical uplink shared channels (PUSCHs) of the wireless device; and transmitting the plurality of DCIs to the wireless device, wherein the simultaneous transmission is configured by the plurality of DCIs such that the plurality of PUSCHs to be transmitted by the wireless device at least partially overlap in the time domain.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems, including uplink transmissions. 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) (commonly referred to within industry organizations 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) to perform communications 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 herein as 5G RAT, 5G NR RAT, or NR). 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 (sometimes also referred to as a gNodeB or gNB).

[0006] The RAN provides 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) and NG-RAN may utilize the 5G Core Network (5GC). Summary of the invention

[0007] Recently, simultaneous uplink transmissions that can be supported by using a multi-panel structure of a wireless device are being discussed. Specifically, the wireless device may include multiple antenna panels, each antenna panel including one or more antenna arrays. The antenna panels may be arranged at different positions of the wireless device, for example, one antenna panel is arranged at the top side of the wireless device and a further antenna panel is arranged at the bottom side of the wireless device. By providing multiple antenna panels, simultaneous transmission of multiple physical uplink shared channels (PUSCHs) from the multiple antenna panels can be achieved (for example, one antenna panel transmits one PUSCH). This helps to increase uplink transmission throughput and reliability.

[0008] In case of simultaneous PUSCH transmission, the scheduling of the simultaneously transmitted PUSCHs may need to be discussed and designed.In the present disclosure, it is proposed to use multiple downlink control information (DCI) to schedule multiple simultaneously transmitted PUSCHs.

[0009] A network device according to some embodiments of the present disclosure may be configured to generate multiple DCIs for scheduling simultaneous transmission of multiple PUSCHs of a wireless device, and may be configured to transmit the multiple DCIs to the wireless device. The simultaneous transmission may be configured by the multiple DCIs so that the multiple PUSCHs to be transmitted by the wireless device at least partially overlap in the time domain.

[0010] A wireless device according to some embodiments of the present disclosure may be configured to report a capability of simultaneous transmission of multiple PUSCHs to a network device, and may be configured to receive multiple DCIs for scheduling the simultaneous transmission of the multiple PUSCHs from the network device. The capability of simultaneous transmission of the multiple PUSCHs may include at least one of the following: the multiple PUSCHs are completely non-overlapping in the frequency domain but at least partially overlapping in the time domain; the multiple PUSCHs are completely overlapping in both the time domain and the frequency domain; and the multiple PUSCHs are partially overlapping in both the time domain and the frequency domain.

[0011] A method for a network device according to some embodiments of the present disclosure may include: generating a plurality of downlink control information (DCI) for scheduling simultaneous transmission of a plurality of physical uplink shared channels (PUSCH) of a wireless device; and transmitting the plurality of DCI to the wireless device. The simultaneous transmission is configured by the plurality of DCIs so that the plurality of PUSCHs to be transmitted by the wireless device at least partially overlap in the time domain.

[0012] A method for a wireless device according to some embodiments of the present disclosure may include: reporting to a network device a capability of simultaneous transmission of multiple physical uplink shared channels (PUSCHs); and receiving from the network device a plurality of downlink control information (DCI) for scheduling the simultaneous transmission of the multiple PUSCHs. The capability of simultaneous transmission of the multiple PUSCHs includes at least one of the following: the multiple PUSCHs are completely non-overlapping in the frequency domain but at least partially overlapping in the time domain; the multiple PUSCHs are completely overlapping in both the time domain and the frequency domain; and the multiple PUSCHs are partially overlapping in both the time domain and the frequency domain.

[0013] The techniques described herein may be implemented in and / or used with a number of different types of devices, including, but not limited to, any of cellular telephones, tablet computers, wearable computing devices, portable media players, and a variety of other computing devices.

[0014] This summary 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

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

[0016] Figure 1 An example architecture of a wireless communication system according to embodiments disclosed herein is illustrated.

[0017] Figure 2 A system for performing signaling between a wireless device and a network device according to embodiments disclosed herein is illustrated.

[0018] Figure 3 An example method of a network device for scheduling simultaneous PUSCH transmissions based on multiple DCIs according to some embodiments disclosed herein is illustrated.

[0019] Figure 4 An example multi-panel structure of a wireless device according to some embodiments disclosed herein is illustrated.

[0020] Figure 5 Example time-frequency resource diagrams of spatial domain multiplexing (SDM) and frequency domain multiplexing (FDM) according to some embodiments disclosed herein are illustrated.

[0021] Figure 6 An example method of a wireless device for performing simultaneous PUSCH transmission based on multiple DCIs according to some embodiments disclosed herein is illustrated.

[0022] Figure 7 An example time-frequency resource diagram for a simultaneous PUSCH transmission scenario according to some embodiments disclosed herein is illustrated.

[0023] Figure 8 An example signaling diagram between a network device and a wireless device for simultaneous PUSCH transmission based on multiple DCIs according to some embodiments disclosed herein is illustrated. DETAILED DESCRIPTION

[0024] Various embodiments are described with respect 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 suitable electronic component.

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

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

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

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

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

[0030] 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 on 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 uplink communication or ProSe or sidelink communication) or single carrier frequency division multiple access (SC-FDMA) communication techniques (e.g., for uplink and ProSe or sidelink communication), but the scope of the embodiment is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0031] 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 an 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 the EPC and / or between two eNBs connected to the EPC. In an embodiment where wireless communication system 100 is an NR system (e.g., when CN 124 is a 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 a 5GC, between a base station 112 (e.g., a gNB) and an eNB connected to a 5GC, and / or between two eNBs connected to a 5GC (e.g., CN 124).

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

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

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

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

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

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

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

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

[0040] 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 resource. This behavior may be referred to as, for example, multiple-input multiple-output (MIMO) behavior (referring to 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).

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

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

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

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

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

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

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

[0048] Reference now Figure 3 , an example method 300 of a network device for scheduling simultaneous PUSCH transmissions based on multiple DCIs according to some embodiments disclosed herein will be described.

[0049] In 302, the network device generates a plurality of downlink control information DCIs for scheduling simultaneous transmission of a plurality of PUSCHs of the wireless device. The network device may correspond to Figure 1 Base stations 112, 114 or Figure 2 Any of the network devices 218 described in. The wireless device may correspond to Figure 1 UE 102, 104 or Figure 2 Any of the wireless devices 202 described in .

[0050] The simultaneous transmission is configured by the network device using multiple DCIs such that multiple PUSCHs to be transmitted by the wireless device at least partially overlap in the time domain. In some embodiments, each of the multiple DCIs may be used by the wireless device to configure a corresponding PUSCH of the multiple PUSCHs.

[0051] In the present disclosure, simultaneous transmission of multiple PUSCHs means that the multiple PUSCHs at least partially overlap in the time domain when being transmitted. In some embodiments, simultaneous transmission of multiple PUSCHs may be achieved through a multi-panel structure of a wireless device.

[0052] Figure 4 An example multi-panel structure of a wireless device is illustrated. The wireless device 402 includes two antenna panels, namely Panel 1 and Panel 2. There are two PUSCHs to be sent simultaneously to the network device 404, namely, Figure 4 By using the multi-panel structure of the wireless device 402, each of the two PUSCHs can be sent by a corresponding antenna panel of the wireless device to achieve simultaneous transmission. Figure 4 As shown, PUSCH 1 may be transmitted by panel 1, and PUSCH 2 may be transmitted by panel 2.

[0053] In 304, the network device transmits a plurality of DCIs to the wireless device to configure the wireless device to perform simultaneous PUSCH transmissions.

[0054] According to the present disclosure, simultaneous PUSCH transmission based on multiple DCIs may be achieved, which may help increase uplink transmission throughput and reliability.

[0055] The present disclosure can be applied to simultaneous PUSCH transmission, where multiple PUSCHs are at least partially overlapped in the time domain, and there is no restriction on the overlap of multiple PUSCHs in the frequency domain. There are mainly two ways to achieve simultaneous PUSCH transmission, one is spatial domain multiplexing (SDM) and the other is frequency domain multiplexing (FDM). Figure 5 An example time-frequency resource diagram for SDM and FDM is illustrated, where the horizontal axis represents the time domain and the vertical axis represents the frequency domain. Assuming that PUSCH 1 and PUSCH 2 are to be transmitted simultaneously, for SDM, PUSCH 1 and PUSCH 2 are to be distinguished in the spatial domain (e.g., transmitted in different antenna beams), so they may occupy the same time-frequency resources. For FDM, PUSCH 1 and PUSCH 2 are to be distinguished in the frequency domain (e.g., transmitted in different frequency bands), and so they may occupy the same time resources.

[0056] When scheduling simultaneous transmission of multiple PUSCHs, some restrictions may be considered from the perspective of reducing power control complexity, reducing system overhead, reducing heating and / or saving costs, etc. Some exemplary restrictions are described in detail below.

[0057] Limitation of PUSCH overlap in time and / or frequency domain

[0058] In some embodiments, some restrictions on the overlap of multiple PUSCHs in the time domain and / or frequency domain may be considered.

[0059] For the limitation in the time domain, in some embodiments, the simultaneous transmission can be configured by the network device using multiple DCIs so that multiple PUSCHs completely overlap in the time domain. For example, since multiple PUSCHs are limited to completely overlap in the time domain, the power control complexity at the wireless device side can be reduced.

[0060] For the limitation in the frequency domain, as option 1, in some embodiments, simultaneous transmission can be configured by the network device using multiple DCIs so that multiple PUSCHs do not overlap in the frequency domain. In this way, frequency domain multiplexing (FDM) is applied to multiple PUSCHs. Since multiple PUSCHs do not overlap in the frequency domain, they will not interfere with each other even if they overlap in the time domain.

[0061] For the limitation in the frequency domain, as option 2, in some embodiments, simultaneous transmission can be configured by the network device using multiple DCIs so that multiple PUSCHs completely overlap in the frequency domain. In this case, multiple PUSCHs overlap in both the frequency domain and the time domain, and further spatial domain multiplexing (SDM) can be applied to avoid interference.

[0062] For restrictions in the frequency domain, as option 3, as a combination of the above two options, in some embodiments, simultaneous transmission may be configured by the network device using multiple DCIs such that multiple PUSCHs do not overlap in the frequency domain or completely overlap in the frequency domain.

[0063] In some embodiments, the network device may generate multiple DCIs to configure the wireless device to perform simultaneous PUSCH transmissions taking into account the above restrictions. For example, the network device may select one option from options 1 to 3 above to configure the overlap of multiple PUSCHs in the frequency domain.

[0064] It should be noted that although three options of frequency domain overlap are described, other options may be designed according to actual practice. For example, an additional option may be that multiple PUSCHs partially overlap in the frequency domain.

[0065] Limitation of PUSCH priority

[0066] PUSCH transmissions may be associated with different priorities. For example, the priority of a PUSCH may include a high priority and a low priority. In the case of network congestion or low channel quality, a PUSCH with a low priority may be discarded, while a PUSCH with a high priority may be maintained as much as possible. For example, the DCI may include a one-bit field indicating the priority of the PUSCH to be scheduled.

[0067] In some embodiments, simultaneous transmission can be configured by a network device using multiple DCIs so that multiple PUSCHs have the same priority. For example, all simultaneously transmitted PUSCHs can be configured to have a high priority, or all simultaneously transmitted PUSCHs can be configured to have a low priority. By configuring multiple PUSCHs to have the same priority, the processing complexity of the wireless device can be reduced.

[0068] In some other embodiments, simultaneous transmission may be configured by the network device using multiple DCIs so that different priorities may be allowed for multiple PUSCHs in the simultaneous transmission in order to meet different requirements in PUSCH transmission.

[0069] Limitation of PUSCH Timing Advance (TA)

[0070] Timing advance is a medium access control-control element (MAC-CE) used to control the timing of uplink signal (such as PUSCH) transmission. The network device may keep measuring the time difference between PUSCH reception and subframe time, and may transmit a TA command to the wireless device to change the PUSCH transmission to better align it with the subframe timing at the network device side. If the PUSCH arrives at the network device too early, the network device may transmit a TA command to the wireless device with a smaller timing advance. If the PUSCH arrives at the network device too late, the network device may transmit a TA command to the wireless device with a larger timing advance.

[0071] In some embodiments, simultaneous transmission can be configured by a network device using multiple DCIs so that multiple PUSCHs have the same TA. This ensures that the PUSCHs transmitted simultaneously are aligned at the time of initial transmission to reduce interference that may occur between the simultaneous transmissions of these PUSCHs. Further, if the same TA is configured, the processing complexity of the wireless device can be reduced. Further, even if two simultaneously transmitted PUSCHs are to be received by different network devices, the difference between the propagation delay of one PUSCH and the propagation delay of another PUSCH can also be considered small enough to be ignored. Therefore, in the case where the simultaneously transmitted PUSCHs have the same TA, there may be little impact on the receiver (e.g., different network devices).

[0072] Restrictions on uplink operation modes of PUSCH

[0073] The uplink operation mode may include a codebook-based uplink operation mode and a non-codebook-based uplink operation mode. For the codebook-based uplink operation mode, the PUSCH is sent based on a single SRS (sounding reference signal) resource with multiple antenna ports, and the network device schedules the PUSCH by indicating the transmit precoding matrix (TPMI) and the rank indication (RI). For the non-codebook-based uplink operation mode, the PUSCH is sent based on multiple SRS resources, each SRS resource has a single antenna port, and the network device schedules the PUSCH by indicating the SRS resource selection.

[0074] In some embodiments, simultaneous transmission can be configured by a network device using multiple DCIs so that multiple PUSCHs are in the same uplink operation mode. For example, all multiple PUSCHs can be configured in a codebook-based uplink operation mode. Alternatively, all multiple PUSCHs can be configured in a non-codebook-based uplink operation mode. This can reduce the processing complexity of the wireless device.

[0075] In some embodiments, in the case where multiple PUSCHs are configured in a codebook-based uplink operation mode, the simultaneous transmission may be further configured by a network device using multiple DCIs so that the multiple PUSCHs follow the same coherence configuration. The coherence configuration indicates a sub-mode in a codebook-based uplink operation mode, and may include a fully coherent configuration, a partially coherent configuration, and a non-coherent configuration. The fully coherent configuration is compatible with the partial and non-coherent configuration, and may be referred to as "fullyAndPartialAndNonCoherent". The partially coherent configuration is compatible with the non-coherent configuration, and may be referred to as "partialAndNonCoherent". Further, the non-coherent configuration may be referred to as "nonCoherent". By configuring multiple PUSCHs to follow the same coherence configuration, the processing complexity of the wireless device may be further reduced.

[0076] Limitation on the number of PUSCHs transmitted simultaneously

[0077] In some embodiments, multiple PUSCHs scheduled in simultaneous transmission may be limited to include at most two PUSCHs from the perspective of cost saving, power consumption, processing complexity, heating issues, etc. That is, in simultaneous transmission, two PUSCHs are scheduled to be transmitted simultaneously.

[0078] Limitations on PUSCH Demodulation Reference Signal (DMRS)

[0079] DMRS symbols are carried in each PUSCH and can be used for uplink channel estimation. Specifically, DMRS symbols with a specific pattern can be carried by PUSCH and sent from a wireless device to a network device. The network device can estimate the uplink channel using the received DMRS symbols with a specific pattern known in advance by the network device. In the following description, the design of a specific pattern of DMRS symbols for multiple simultaneously transmitted PUSCHs will be described.

[0080] For the case where multiple PUSCHs are configured by the network device using multiple DCIs to be non-overlapping in the frequency domain (such as the overlapping option 1 in the frequency domain described above), interference between multiple PUSCHs in the frequency domain will not occur. Therefore, in this case, the DMRS pattern of multiple PUSCHs can be designed arbitrarily.

[0081] For the case where multiple PUSCHs are configured by a network device using multiple DCIs to at least partially overlap in the frequency domain, it is possible that the DMRS symbol of one PUSCH is interfered with by the uplink data carried by another PUSCH. To avoid such interference, in some embodiments, the network device may use multiple DCIs to configure the DMRS symbols in different PUSCHs to align with each other. Alignment may be achieved by following at least one of the designs described below.

[0082] Specifically, for the first design, multiple PUSCHs may have the same number of front-loading DMRS symbols (e.g., one DMRS symbol per PUSCH, or two DMRS symbols per PUSCH). The number of front-loading DMRS symbols may be defined differently in a resource block (RB). The first design limits the actual number of front-loading DMRS symbols used for each of the multiple PUSCHs to be the same.

[0083] In a second design, multiple PUSCHs may have the same number of additional DMRS symbols. Additional DMRS symbols may be configured in an RB to facilitate more accurate channel estimation. The combination of this second design with the first design may ensure that the total number of DMRS symbols used for each of the PUSCHs is the same.

[0084] In a third design, multiple PUSCHs may have the same DMRS symbol position. Depending on different mapping types of DMRS symbols, the DMRS symbol position (front-loaded DMRS symbol or additional DMRS symbol in an RB in the time domain) may be different. Therefore, the third design may ensure that the DMRS symbol in each of the multiple PUSCHs is aligned in the same position of the RB.

[0085] In a fourth design, multiple PUSCHs may have the same DMRS configuration type. There are mainly two DMRS configuration types 1 and 2, which define different mappings of DMRS in resource elements in the frequency domain. By further configuring the same DMRS configuration type for each of the multiple PUSCHs, the DMRS symbols may be aligned more accurately.

[0086] In the present disclosure, by aligning DMRS symbols in simultaneously transmitted PUSCHs, a receiver (eg, a network device) can more easily distinguish DMRS symbols from uplink data carried by each PUSCH, so as to simplify a reception algorithm in the receiver.

[0087] Constraints on the Orthogonal Frequency Division Multiplexing (OFDM) Waveform of PUSCH

[0088] The OFDM waveform may include DFT-s-OFDM (Discrete Fourier Transform (DFT)-Spread-OFDM) with transform precoding enabled and CP-OFDM (Cyclic Prefix-OFDM) with transform precoding disabled.

[0089] In some embodiments, simultaneous transmission may be configured by the network device using multiple DCIs such that multiple PUSCHs are to be transmitted by the same OFDM waveform.

[0090] Limitation on the maximum number of PUSCH Hybrid Automatic Repeat Request (HARQ) processes

[0091] In some embodiments, simultaneous transmission may be configured by the network device using multiple DCIs such that the maximum number of PUSCH HARQ processes for multiple PUSCHs is the same as the maximum number of legacy PUSCH HARQ processes.

[0092] It should be noted that the term “legacy” described herein means any existing solution prior to the present disclosure, including but not limited to any solution related to the LTE system standard and / or the 5G or NR system standard as provided by the 3GPP technical specifications.

[0093] For example, the maximum number of legacy PUSCH HARQ processes may be 16, and the maximum number of PUSCH HARQ processes for multiple PUSCHs may also be set to 16 so as not to increase any storage burden compared to legacy devices.

[0094] In some embodiments, the network may support more than 16 PUSCH HARQ processes, such as 32 PUSCH HARQ processes, etc. In this case, the network device may receive an additional capability report from the wireless device, which shows the maximum capability of the wireless device to support PUSCH HARQ processes (e.g., 32 supported HARQ processes). The network device may determine the maximum number of PUSCH HARQ processes for multiple PUSCHs based on the received additional capability report.

[0095] In the above description, several restrictions are discussed when scheduling simultaneous PUSCH transmissions. Note that the restrictions described herein may be applied individually, or multiple restrictions may be applied together.

[0096] Reference now Figure 6 , an example method 600 for a wireless device for performing simultaneous PUSCH transmission based on multiple DCIs according to some embodiments disclosed herein will be described.

[0097] In 602, the wireless device reports to the network device the capability of simultaneously transmitting multiple PUSCHs. The network device may correspond to Figure 1 Base stations 112, 114 or Figure 2 Any of the network devices 218 described in. The wireless device may correspond to Figure 1 UE 102, 104 or Figure 2 Any of the wireless devices 202 described in .

[0098] In some embodiments, the ability to simultaneously transmit multiple PUSCHs may include at least one of the following: (1) multiple PUSCHs are completely non-overlapping in the frequency domain but at least partially overlapping in the time domain; (2) multiple PUSCHs completely overlap in both the time domain and the frequency domain; and (3) multiple PUSCHs at least partially overlap in both the time domain and the frequency domain.

[0099] Figure 7 An example time-frequency resource diagram is illustrated for a simultaneous PUSCH transmission scenario according to some embodiments disclosed herein, where the horizontal axis represents the time domain and the vertical axis represents the frequency domain. Figure 7 The scenario shown in may correspond to the above-mentioned capabilities (1) to (3).

[0100] Specifically, Figure 7 Scenario 1 in FIG. 1 corresponds to a first capability in which multiple PUSCHs are completely non-overlapping in the frequency domain but at least partially overlapping in the time domain. The left side of scenario 1 shows that PUSCHs 1 and 2 are completely non-overlapping in the frequency domain and completely overlapping in the time domain. The right side of scenario 1 shows that PUSCHs 1 and 2 are completely non-overlapping in the frequency domain and partially overlapping in the time domain.

[0101] Figure 7 Scenario 2 in corresponds to multiple PUSCHs (corresponding to Figure 7 The second capability of PUSCH 1 and 2) shown in FIG. 1 completely overlaps in both time and frequency domains.

[0102] Figure 7 Scenario 3 in corresponds to a third capability that multiple PUSCHs overlap at least partially in both the time domain and the frequency domain. The left side of scenario 3 shows that PUSCH 1 and PUSCH 2 overlap partially in the frequency domain and partially in the time domain. The middle of scenario 3 shows that PUSCH 1 and PUSCH 2 overlap completely in the frequency domain and partially in the time domain. The right side of scenario 3 shows that PUSCH 1 and PUSCH 2 overlap partially in both the frequency domain and the time domain.

[0103] At 604, the wireless device receives multiple DCIs for scheduling simultaneous transmission of multiple PUSCHs from the network device. The multiple DCIs may be determined by the network device based on the capability of simultaneous transmission of multiple PUSCHs reported by the wireless device, so as to configure the wireless device to perform supportable simultaneous transmission.

[0104] In legacy PUSCH transmission, the maximum number of PUSCH layers that the wireless device can support is reported from the wireless device to the network device. The maximum number of PUSCH layers indicates the maximum number of layers that can transmit one PUSCH from the wireless device.

[0105] Depending on different band combinations, different frequency bands, and different component carriers, the maximum number of PUSCH layers may be different. The maximum number of PUSCH layers that a wireless device may support may be reported per feature set per component carrier (FSPC), i.e., per band per component carrier per band combination. In legacy systems, for codebook-based PUSCH operation, the maximum number of PUSCH layers is reported in "maxNumberMIMO-LayersCB-PUSCH". For non-codebook-based PUSCH operation, the maximum number of PUSCH layers is reported in "maxNumberMIMO-LayersNonCB-PUSCH".

[0106] In the case where multiple PUSCHs are configured by the network device using multiple DCIs to be non-overlapping in the frequency domain (such as the above-mentioned overlapping option 1 in the frequency domain), the above legacy reporting of the maximum number of PUSCH layers may still work because different PUSCHs do not share any resource elements in the frequency domain.

[0107] However, in the case where multiple PUSCHs are configured by a network device using multiple DCIs to partially overlap in the frequency domain (e.g., at least two PUSCHs share at least one resource element in the frequency domain), the legacy reporting of “maxNumberMIMO-LayersCB-PUSCH” or “maxNumberMIMO-LayersNonCB-PUSCH” may not be applicable because the maximum number of PUSCH layers supportable per FSPC may change when there is partial overlap in the frequency domain.

[0108] In some embodiments, instead of reporting "maxNumberMIMO-LayersCB-PUSCH" or "maxNumberMIMO-LayersNonCB-PUSCH", the wireless device may report to the network device a set of maximum number of layers for multiple PUSCHs that the wireless device can support. For example, when two PUSCHs are scheduled to be sent simultaneously and the PUSCH operation mode is configured as "codebook-based uplink operation mode", the wireless device may report to the network device a set (pair) of (maxNumberMIMO-LayersCB-PUSCH1, maxNumberMIMO-LayersCB-PUSCH2). In this pair, "maxNumberMIMO-LayersCB-PUSCH1" indicates the maximum number of layers for the first PUSCH, and "maxNumberMIMO-LayersCB-PUSCH2" indicates the maximum number of layers for the second PUSCH. Similarly, in the case where two simultaneously transmitted PUSCHs are configured as "non-codebook based uplink operation mode", the wireless device may report a set (pair) of (maxNumberMIMO-LayersNonCB-PUSCH1, maxNumberMIMO-LayersNonCB-PUSCH2) to the network device.

[0109] In some embodiments, instead of reporting only one set of maximum number of layers, the wireless device may alternatively report multiple sets of maximum number of layers that each PUSCH can support. For example, the wireless device may report two sets (maxNumberMIMO-LayersCB-PUSCH1=2, maxNumberMIMO-LayersCB-PUSCH2=1) and (maxNumberMIMO-LayersCB-PUSCH1=1, maxNumberMIMO-LayersCB-PUSCH2=2). When the network device receives the reports of the two sets, it may select one set and generate multiple DCIs based on the selected set. Further, similar to the legacy transmission, one or more sets of maximum number of layers may be reported according to FSPC.

[0110] In some embodiments, the old maximum number of PUSCH layers L may be reused to report the maximum number of layers of multiple simultaneously transmitted PUSCHs.

[0111] In the case where multiple PUSCHs are configured by the network device using multiple DCIs to be non-overlapping in the frequency domain (such as the above-mentioned overlapping option 1 in the frequency domain), the old maximum number L can be directly applied because different PUSCHs do not share any resource elements in the frequency domain.

[0112] However, in the case where multiple PUSCHs are configured by a network device using multiple DCIs to partially overlap in the frequency domain (e.g., at least two PUSCHs share at least one resource element in the frequency domain), the old maximum number L may not be directly applied. Some interpretations may be made to the old maximum number L so that the number can be reused to indicate the maximum number of layers of multiple simultaneously transmitted PUSCHs.

[0113] In some embodiments, the legacy maximum number L may be interpreted as L being an upper limit of the sum of the number of layers of multiple PUSCHs. For example, as shown in Table 1 below, assuming that the number of layers of PUSCH1 is R1 and the number of layers of PUSCH2 is R2, when the legacy maximum number L (e.g., maxNumberMIMO-LayersCB-PUSCH=L or maxNumberMIMO-LayersNonCB-PUSCH=L) is reported by the wireless device, this means that "R1+R2≤L" should be satisfied.

[0114] In some embodiments, the legacy maximum number L may be interpreted as L being an upper limit on the number of layers of each of the plurality of PUSCHs. For example, as shown in Table 1 below, this interpretation of L means that "R1≤L and R2≤L" should be satisfied.

[0115] In some embodiments, the old maximum number L can be interpreted as a lower limit of L / 2 being an upper limit on the number of layers of each of the multiple PUSCHs. For example, as shown in Table 1 below, this interpretation of L means that "R1 ≤ lower limit (L / 2) and R2 ≤ lower limit (L / 2)" should be satisfied.

[0116] In some embodiments, the old maximum number L can be interpreted as an upper limit of L / 2 being an upper limit of the number of layers of each of the multiple PUSCHs and L being an upper limit of the sum of the number of layers of the multiple PUSCHs. For example, as shown in Table 1 below, the interpretation of L means that "R1 ≤ upper limit (L / 2) and R2 ≤ upper limit (L / 2), and R1+R1 ≤ L" should be satisfied.

[0117] [Table 1]

[0118]

[0119] In some embodiments, the wireless device may report to the network device which interpretation of the legacy maximum number L was used. For example, for a total of four interpretations as shown in Table 1, two bits of information may be used to indicate the interpretation number and transmitted to the network device.

[0120] When scheduling simultaneous transmission of multiple PUSCHs, the spatial transmission filters (spatial Tx filters, or referred to as "analog Tx beams") used to transmit the multiple PUSCHs can be appropriately determined. Due to the multi-panel structure of a wireless device for supporting simultaneous transmission, for each antenna panel used for simultaneous transmission of one PUSCH, not all spatial filters can be used, but only a part of the spatial filters can be used by one antenna panel. In this case, the wireless device should report to the network device which spatial filters can be used for which antenna panel.

[0121] In some implementations, the plurality of spatial Tx filters may be identical to the spatial receive filters (spatial Rx filters).

[0122] For downlink reception of one or more physical downlink shared channels (PDSCHs), the wireless device may transmit a downlink receive beam measurement report to the network device, which may include one or more sets of spatial Rx filters that can be used by the wireless device for simultaneous downlink reception.

[0123] For example, in order to receive two PDSCHs simultaneously, a set (pair) of spatial Rx filters (1, 7) may be included in the downlink receive beam measurement report, which means that spatial Rx filters No. 1 and No. 7 may be used to receive the two PDSCHs simultaneously. The set of spatial Rx filters may be spatial filters for receiving the set of QCL (quasi co-located) reference signals. Further, multiple sets of spatial RX filters (such as (1, 7), (2, 10), (3, 11)) may be included in the report indicating the candidate set of spatial Rx filters.

[0124] For uplink transmission of multiple PUSCHs, the network device may determine multiple spatial Tx filters based on the downlink receive beam measurement report. For example, if spatial Rx filters No. 1 and No. 7 are reported in the downlink receive beam measurement report, spatial Tx filters No. 1 and No. 7 may be determined by the network device as spatial Tx filters. Further, if multiple groups of spatial Rx filters (such as (1,7), (2,10), (3,11)) are reported, the network device may determine one group from the multiple groups as the group of spatial Tx filters.

[0125] However, in some cases, such as for the purpose of saving power and saving processing complexity, the number of antenna panels for downlink and uplink may be different, and the number of downlink panels may exceed the number of uplink panels. In these cases, the spatial Rx filter for simultaneous downlink reception may not be similarly applied to the spatial Tx filter for simultaneous uplink transmission. Therefore, a separate uplink transmit beam measurement report and corresponding signaling between the network device and the wireless device may be designed. This will refer to Figure 8 Describe in detail.

[0126] Figure 8 An example signaling diagram between a network device and a wireless device for simultaneous PUSCH transmission based on multiple DCIs according to some embodiments disclosed herein is illustrated. The network device may correspond to Figure 1 Base stations 112, 114 or Figure 2 Any of the network devices 218 described in. The wireless device may correspond to Figure 1 UE 102, 104 or Figure 2 Any of the wireless devices 202 described in .

[0127] In 800, the wireless device may generate an uplink transmit beam measurement report. The uplink transmit beam measurement report may include one or more sets of spatial Tx filters that can be used by the wireless device to simultaneously transmit multiple PUSCHs. For example, the report may include multiple sets of spatial Tx filters (1, 8), (2, 9), (3, 11) that can be used to simultaneously transmit two PUSCHs.

[0128] In 802, the wireless device may transmit an uplink transmit beam measurement report to a network device.

[0129] In 804, the network device may receive an uplink transmit beam measurement report and determine a plurality of spatial Tx filters based on the received report. For example, the network device may determine a set of spatial Tx filters from a plurality of sets (1, 8), (2, 9), (3, 11) included in the report. The network device may then generate a plurality of DCIs based on the determined set of spatial Tx filters and transmit the plurality of DCIs to the wireless device for scheduling simultaneous transmission of two PUSCHs.

[0130] Embodiments contemplated herein include an apparatus comprising a component for performing Figure 3 and Figure 6 58 or one or more elements of the method illustrated in , or one or more elements of the signaling illustrated in FIG. 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) or 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 Figure 3 and Figure 6 One or more elements of the method illustrated in, or Figure 8The 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) or 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 logic components, modules, or circuits for performing Figure 3 and Figure 6 One or more elements of the method illustrated in, or Figure 8 The apparatus may be, for example, an apparatus of a base station (such as the network apparatus 218 as a base station, as described herein) or an apparatus of a UE (such as the wireless apparatus 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 Figure 3 and Figure 6 One or more elements of the method illustrated in, or Figure 8 The apparatus may be, for example, an apparatus of a base station (such as the network apparatus 218 as a base station, as described herein) or an apparatus of a UE (such as the wireless apparatus 202 as a UE, as described herein).

[0134] Embodiments contemplated herein include a signal such as Figure 3 and Figure 6 One or more elements of the method exemplified in or with Figure 3 and Figure 6 or Figure 8 One or more elements of the signaling illustrated in .

[0135] 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 an execution Figure 3 and Figure 6 One or more elements of the method illustrated in, or Figure 8The processor may be a processor of a base station (such as processor 220 of network device 218 as a base station, as described herein). For example, these instructions may be located in a processor and / or on a memory of a base station (such as memory 222 of network device 218 as a base station, as described herein). The processor may be a processor of a UE (such as processor 204 of wireless device 202 as a UE, as described herein). These instructions may be located, for example, in a processor and / or on a memory of a UE (such as memory 206 of wireless device 202 as a UE, as described herein).

[0136] 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 described 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, a circuit system 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.

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

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

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

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

[0141] 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 to implement 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 network device, comprising: A memory storing instructions; and at least one processor configured to execute the instructions stored in the memory to cause the network device to: generating a plurality of downlink control information (DCI) for simultaneous transmission of a plurality of physical uplink shared channels (PUSCH) for scheduling wireless devices; and transmitting the plurality of DCIs to the wireless device, The simultaneous transmission is configured by the plurality of DCIs such that the plurality of PUSCHs to be transmitted by the wireless device at least partially overlap in the time domain.

2. The network device according to claim 1, wherein the simultaneous transmission is configured by the multiple DCIs such that The multiple PUSCHs do not overlap in the frequency domain; The multiple PUSCHs completely overlap in the frequency domain; or The multiple PUSCHs do not overlap in the frequency domain or completely overlap in the frequency domain. 3 . The network device according to claim 1 , wherein the simultaneous transmission is configured by the multiple DCIs so that the multiple PUSCHs completely overlap in the time domain.

4. The network device according to claim 1, wherein the plurality of DCIs configure a plurality of spatial transmit filters for the wireless device to transmit the plurality of PUSCHs, and the at least one processor is further configured to execute the instructions stored in the memory so that the network device: The plurality of spatial transmit filters is determined based on a downlink receive beam measurement report from the wireless device, wherein the downlink receive beam measurement report contains one or more sets of spatial receive filters that can be used by the wireless device for simultaneous downlink reception.

5. The network device of claim 1 , wherein the plurality of DCIs configure a plurality of spatial transmit filters for the wireless device to transmit the plurality of PUSCHs, and the at least one processor is further configured to execute the instructions stored in the memory to cause the wireless device to: receiving an uplink transmit beam measurement report from the wireless device, wherein the uplink transmit beam measurement report comprises one or more sets of spatial transmit filters that can be used by the wireless device to simultaneously transmit the plurality of PUSCHs; and The plurality of spatial transmit filters are determined based on the received uplink transmit beam measurement reports. The network device according to claim 1 , wherein the simultaneous transmission is configured by the plurality of DCIs so that the plurality of PUSCHs have the same priority. 7 . The network device according to claim 1 , wherein the simultaneous transmission is configured by the plurality of DCIs so that the plurality of PUSCHs have different priorities. 8 . The network device according to claim 1 , wherein the simultaneous transmission is configured by the plurality of DCIs so that the plurality of PUSCHs have the same timing advance (TA).

9. The network device according to claim 1, wherein the simultaneous transmission is configured by the multiple DCIs so that the multiple PUSCHs are in the same uplink operation mode, wherein the uplink operation mode includes a codebook-based uplink operation mode and a non-codebook-based uplink operation mode.

10. The network device according to claim 9, wherein, when the multiple PUSCHs are configured in the codebook-based uplink operation mode, the simultaneous transmission is further configured by the multiple DCIs so that the multiple PUSCHs follow the same coherence configuration, wherein the coherence configuration includes a full coherence configuration, a partial coherence configuration, and a non-coherence configuration.

11. The network device of claim 1, wherein the plurality of PUSCHs scheduled in the simultaneous transmission comprises at most two PUSCHs.

12. The network device according to claim 1, wherein, in a case where the plurality of PUSCHs are configured to at least partially overlap in the frequency domain, the simultaneous transmission is further configured by the plurality of DCIs such that at least one of the following is satisfied: The plurality of PUSCHs have the same number of front-loaded demodulation reference signal (DMRS) symbols; The multiple PUSCHs have the same number of additional DMRS symbols; The multiple PUSCHs have the same DMRS symbol position; and The multiple PUSCHs have the same DMRS configuration type.

13. The network device of claim 1, wherein the simultaneous transmission is configured by the plurality of DCIs such that the plurality of PUSCHs are to be transmitted by the same Orthogonal Frequency Division Multiplexing (OFDM) waveform.

14. The network device of claim 1, wherein the simultaneous transmission is configured by the plurality of DCIs such that a maximum number of PUSCH hybrid automatic repeat request (HARQ) processes for the plurality of PUSCHs is the same as a maximum number of legacy PUSCH HARQ processes.

15. The network device of claim 1, wherein the simultaneous transmission is configured by the plurality of DCIs such that a maximum number of PUSCH HARQ processes for the plurality of PUSCHs is determined based on an additional capability report from the wireless device.

16. The network device of claim 1, wherein the at least one processor is further configured to execute the instructions stored in the memory to cause the wireless device to: receiving a capability report for simultaneous transmission of the plurality of PUSCHs from the wireless device; and The plurality of DCIs are generated based on the capability report.

17. A wireless device, comprising: A memory storing instructions; and at least one processor configured to execute the instructions stored in the memory to cause the wireless device to: The ability to report to network equipment the simultaneous transmission of multiple physical uplink shared channels (PUSCH); as well as receiving a plurality of downlink control information (DCI) for scheduling the simultaneous transmission of the plurality of PUSCHs from the network device, The capability of simultaneously transmitting the plurality of PUSCHs comprises at least one of the following: The multiple PUSCHs are completely non-overlapping in the frequency domain but at least partially overlapping in the time domain; The multiple PUSCHs completely overlap in both the time domain and the frequency domain; and The multiple PUSCHs at least partially overlap in both the time domain and the frequency domain.

18. The wireless device of claim 17, wherein the at least one processor is further configured to execute the instructions stored in the memory to An uplink transmit beam measurement report is transmitted to the network device, wherein the uplink transmit beam measurement report includes one or more sets of spatial transmit filters that can be used by the wireless device to simultaneously transmit the multiple PUSCHs.

19. The wireless device of claim 17, wherein, in a case where the plurality of PUSCHs are configured by the plurality of DCIs to at least partially overlap in the frequency domain, the at least one processor is further configured to execute the instructions stored in the memory to One or more sets of maximum number of layers for the plurality of PUSCHs that the wireless device can support are reported to the network device.

20. The wireless device of claim 17, wherein, in a case where the plurality of PUSCHs are configured by the plurality of DCIs to at least partially overlap in the frequency domain, the at least one processor is further configured to execute the instructions stored in the memory to reporting, to the network device, a legacy maximum number L of PUSCH layers supported by the wireless device, wherein the legacy maximum number L is interpreted as one of: L is an upper limit of the sum of the number of layers of the plurality of PUSCHs; L is an upper limit on the number of layers of each of the plurality of PUSCHs; The lower limit of L / 2 is the upper limit of the number of layers of each of the plurality of PUSCHs; and An upper limit of L / 2 is an upper limit of the number of layers of each of the plurality of PUSCHs, and L is an upper limit of a sum of the number of layers of the plurality of PUSCHs.

21. The wireless device of claim 20, wherein the at least one processor is further configured to execute the instructions stored in the memory to An explanation of the legacy maximum number L is reported to the network device.

22. A method for a network device, the method comprising: generating a plurality of downlink control information (DCI) for simultaneous transmission of a plurality of physical uplink shared channels (PUSCH) for scheduling wireless devices; as well as transmitting the plurality of DCIs to the wireless device, The simultaneous transmission is configured by the plurality of DCIs such that the plurality of PUSCHs to be transmitted by the wireless device at least partially overlap in the time domain.

23. A method for a wireless device, the method comprising: The ability to report to network equipment the simultaneous transmission of multiple physical uplink shared channels (PUSCH); as well as receiving a plurality of downlink control information (DCI) for scheduling the simultaneous transmission of the plurality of PUSCHs from the network device, The capability of simultaneously transmitting the plurality of PUSCHs comprises at least one of the following: The multiple PUSCHs are completely non-overlapping in the frequency domain but at least partially overlapping in the time domain; The multiple PUSCHs completely overlap in both the time domain and the frequency domain; and The multiple PUSCHs at least partially overlap in both the time domain and the frequency domain.

24. A non-transitory computer-readable memory medium storing program instructions, wherein the program instructions, when executed by a computer system, cause the computer system to perform the method according to claim 22 or 23.

25. A computer program product comprising program instructions which, when executed by a computer, cause the computer to perform the method according to claim 22 or 23.

Images