Simultaneous PUSCH transmission to multiple TRPs

Abstract

Disclosed herein are systems and methods for multiple transmit / receive point (TRP) uplink transmission in a cellular communication system. According to one embodiment, a method performed by a wireless communication device includes receiving, from a network node, a configuration of first and second sounding reference signal (SRS) resource sets, each SRS resource set having one or more SRS resources. The method further includes receiving, from the network node, downlink control information (DCI) scheduling a physical uplink channel transmission including a first portion associated with a first SRS resource in the first SRS resource set and a second portion associated with a second SRS resource in the second SRS resource set, the first and second SRS resources being indicated in the DCI. The method further includes transmitting the physical uplink channel transmission in accordance with the DCI.

Description

[Technical field]

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS This application claims the benefit of U.S. Provisional Patent Application No. 63 / 011,707, filed April 17, 2020, the disclosure of which is incorporated herein by reference in its entirety. TECHNICAL FIELD

[0002] The present disclosure relates to uplink transmission to multiple transmission / reception points (TRPs) in a cellular communication system. [Background technology]

[0003] The next generation mobile radio communication system (5G) or New Radio (NR) will support a diverse set of use cases and a diverse set of deployment scenarios, the latter including deployment at both low frequencies (i.e., frequencies below 6 Gigahertz (GHz)) and very high frequencies (i.e., frequencies up to 10 GHz). 1 NR Frame Structure and Resource Grid

[0004] NR uses cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) in both the downlink (DL) (i.e., from the network node (gNB) or base station to the user equipment or UE) and uplink (UL) (i.e., from the UE to the gNB). Discrete Fourier transform (DFT) spread orthogonal frequency division multiplexing (OFDM) is also supported in the uplink. In the time domain, the NR downlink and uplink are organized into equal-sized subframes of 1 millisecond (ms) each. The subframes are further divided into multiple slots of equal duration. The slot length depends on the subcarrier spacing. For a subcarrier spacing of Δf=15 kilohertz (kHz), there is only one slot in a subframe, and each slot consists of 14 OFDM symbols.

[0005] Data scheduling in NR is typically slot-based. An example with a 14-symbol slot for 15 kHz subcarrier spacing is shown in Figure 1, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the rest contain the Physical Shared Data Channel, either the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0006] In NR, different subcarrier spacing values ​​are supported. The supported subcarrier spacings (also called different numerologies) are Δf = (15 × 2 μ ) kHz, where μ∈{0,1,2,3,4}. Δf=15 kHz is the basic subcarrier spacing. The slot durations at different subcarrier spacings are 1 / (2 μ ) ms.

[0007] In the frequency domain, the system bandwidth is divided into resource blocks (RBs), each corresponding to 12 consecutive subcarriers. The RBs are numbered starting with 0 at one end of the system bandwidth. The basic NR physical time-frequency resource grid is shown in Figure 2, where only one RB is shown in a 14-symbol slot. One OFDM subcarrier in one OFDM symbol interval forms one resource element (RE).

[0008] In NR Release 15, UL data transmissions can be dynamically scheduled by an UL grant included in the downlink control information (DCI) carried by the physical downlink control channel (PDCCH). The UE first decodes the uplink grant and then transmits data via a physical uplink shared channel (PUSCH) based on the decoded control information in the UL grant, such as modulation order, coding rate, uplink resource allocation, etc. Three DCI formats are supported in NR Release 16: DCI format 0_0, DCI format 0_1, and DCI format 0_2. Each DCI includes several bit fields, each carrying certain information: Bandwidth indicator ● Time Domain Resource Allocation (TDRA) Frequency Domain Resource Allocation (FDRA) Modulation and Coding Scheme (MCS) Hybrid Automatic Repeat Request (HARQ) process number ●New Data Indicator ● Redundant version (RV) ● Sounding Resource Indicator (SRI) Precoding information and number of layers ●Antenna port ● Sounding Reference Signal (SRS) requirements, etc. ●Channel State Information (CSI) Request Phase Tracking Reference Signal (PTRS)-Demodulation Reference Signal (DMRS) (i.e., PTRS-DMRS) association ●Transmit power control (TPC) commands for scheduled PUSCH

[0009] In addition to dynamic scheduling of PUSCH, there is also the possibility to configure semi-persistent transmission of PUSCH using preconfigured grants (CGs). There are two types of CG-based PUSCH defined in NR Release 15, called CG type 1 and CG type 2. In CG type 1, the periodicity of the PUSCH transmission as well as the start and stop of its transmission are configured by Radio Resource Control (RRC). In CG type 2, the periodicity of the PUSCH transmission is configured by RRC and then the start and stop of its transmission is controlled by DCI, i.e. by PDCCH.

[0010] In NR, it is possible to schedule PUSCH with time repetition via the RRC parameters pusch-AggregationFactor for dynamically scheduled PUSCH and repK for PUSCH with configured UL grant, where PUSCH is scheduled but transmitted in multiple adjacent slots until a number of repetitions determined by the preconfigured RRC parameters have been transmitted.

[0011] In the case of a PUSCH with a configured UL grant, if repetitive transmission is used, the RV sequence used is configured by the repK-RV field. If repetitive transmission is not used for a PUSCH with a configured UL grant, the repK-RV field is not present.

[0012] In NR Release 15, two mapping types applicable for PUSCH transmissions are supported. These two mapping types are called Type A and Type B. Type A PUSCH transmissions are typically called slot-based transmissions, while Type B PUSCH transmissions are sometimes called non-slot-based or minislot-based transmissions. Minislot transmissions can be dynamically scheduled and for NR Release 15: For the downlink, you can specify a length of 7, 4, or 2 symbols, but for the uplink, you can specify any length. Can start and end at any symbol within a slot. Note that minislot transmissions in NR Release 15 must not cross a slot boundary. 2. PUSCH Transmission Method

[0013] In NR, there are two transmission schemes specified for the PUSCH. 2.1 Codebook-based PUSCH

[0014] If a higher layer parameter txConfig is set to codebook, then the codebook-based PUSCH is enabled. For dynamically scheduled PUSCH and configured grant PUSCH type 2, the codebook-based PUSCH transmission scheme can be summarized as follows: The UE transmits SRS in one or two configured SRS resources. One or two SRS resources are configured in an SRS resource set with the upper layer parameter usage set to "CodeBook". Note that only one SRS resource set can be configured with usage set to "Codebook". The NR base station (gNB) determines a preferred precoder (i.e., a transmit precoding matrix indicator (TPMI)) from the codebook and the number of the associated layer corresponding to the SRS received from one of the one or two SRS resources. The gNB indicates the selected SRS resource via a 1-bit "SRS resource indicator" (SRI) field in the DCI for scheduling the PUSCH if two SRS resources are configured in the SRS resource set. If only one SRS resource is configured in the SRS resource set, the "SRS resource indicator" field is not indicated in the DCI. The gNB also indicates the preferred TPMI and the associated number of layers corresponding to the indicated SRS resources (if two SRS resources are used) or configured SRS resources (if one SRS resource is used). The TPMI and number of layers are indicated by the "Precoding information and number of layers" field in DCI formats 0_1 and 0_2. The UE performs PUSCH transmission using the TPMI and the indicated number of layers. If one SRS resource is configured in the associated SRS resource set with the higher layer parameter Usage value "CodeBook", the PUSCH DMRS is spatially related to the latest SRS transmission in this SRS resource. If two SRS resources are configured in the associated SRS resource set with the higher layer parameter Usage value "CodeBook", the PUSCH DMRS is spatially related to the latest SRS transmission in the SRS resource indicated by the "SRS resource indicator" field. ● One (or more) DMRS ports associated with one (or more) layers are indicated in the "antenna port" field in the DCI together with the number of the CDM group, without being multiplexed with PUSCH data. 2.2 Non-Codebook-based PUSCH

[0015] Non-codebook-based UL transmission is also supported in NR, allowing reciprocity-based UL transmission, where SRS precoding is derived at the UE based on the configured DL channel state information reference signal (CSI-RS). By assigning DL CSI-RS to the UE, the UE can measure and estimate appropriate precoder weights for SRS transmission, resulting in one or more (virtual) SRS ports, each corresponding to a spatial layer. The UE may be configured with up to four SRS resources in an SRS resource set, each with a single (virtual) SRS port. The UE may transmit SRS on up to four SRS resources, and the gNB measures the UL channel based on the received SRS and determines the preferred SRS resource (or SRS port). The gNB then indicates the selected SRS resource via an SRS resource indicator (SRI), where the selected SRS resource is:

number

[0016] Spatial relationship is used in NR to refer to the relationship between UL signals or channels, such as PUCCH, PUSCH, and SRS, and another reference signal (RS), which can be either DL RS (e.g., CSI-RS, SSB (synchronization signal block)) or UL RS (e.g., SRS). This is also defined from the UE perspective.

[0017] If a UL signal or channel is spatially related to a DL RS, it means that the UE should transmit the UL signal or channel in the opposite (reverse) direction in which it previously received the DL RS. More precisely, the UE should apply the "same" transmit (TX) spatial filtering configuration to transmit the UL signal or channel as the receive (Rx) spatial filtering configuration it previously used to receive the spatially related DL RS. Here, the term "spatial filtering configuration" may refer to antenna weights applied at either the transmitter or receiver for data or control transmission or reception. The DL RS is also called a spatially filtered reference signal.

[0018] On the other hand, if a first UL signal or channel is spatially related to a second UL RS, the UE should apply the same Tx spatial filtering configuration to the transmission of the first UL signal or channel as the Tx spatial filtering configuration used for previously transmitting the second UL RS.

[0019] In the case of an SRS resource set for a codebook-based PUSCH scheme, it may include at most two SRS resources. Each of the SRS resources may have one, two, or four SRS ports. Each SRS resource may be spatially related to another RS ​​(e.g., SSB, non-zero power (NZP) CSI-RS, or another SRS) via a spatial relationship configuration. The spatial relationship of the PUSCH is given by the spatial transmission characteristics associated with the associated SRS resource.

[0020] For an SRS resource set for a non-codebook-based PUSCH scheme, it may contain up to four SRS resources, each with a single SRS port. Each SRS resource set is associated with a CSI-RS, where the UE derives an SRS precoder for each SRS port. The spatial relationship of the PUSCH is given by the CSI-RS configured for the SRS resource set. 4 TCI States for Uplink

[0021] Several signals can be transmitted from different antenna ports of the same base station antenna, which can have the same large-scale characteristics, for example in terms of Doppler shift / spread, mean delay spread, or mean delay, as measured at the receiver, and these antenna ports are said to be quasi-collocated (QCL).

[0022] The network can then signal to the UE that the two antenna ports are QCL. If the UE knows that the two antenna ports are QCL with respect to a certain parameter (e.g., Doppler spread), the UE can estimate that parameter based on a reference signal transmitted on one of the antenna ports and use that estimate when receiving another reference signal or physical channel. Typically, the first antenna port is represented by a measurement reference signal such as CSI-RS (known as source RS), and the second antenna port is a demodulation reference signal (DMRS) for PDSCH or PDCCH reception (known as target RS).

[0023] NR defines four types of QCL relationships between a transmitted source RS and a transmitted target RS: ●Type A: {Doppler shift, Doppler spread, average delay, delay spread} ●Type B: {Doppler shift, Doppler spread} ●Type C: {average delay, Doppler shift} ● Type D: {Spatial Rx parameters} QCL type D was introduced to facilitate beam management using analog beamforming and is known as spatial QCL. Currently, there is no strict definition of spatial QCL, but it is understood that if two transmitted antenna ports are spatially QCL, the UE can use the same Rx beam to receive them. This is useful for UEs that use analog beamforming to receive signals, because the UE needs to adjust its RX beam in a certain direction before receiving a signal. If the UE knows that a signal is spatially QCL with some other signal that the UE has previously received, the UE can also receive this signal using the same RX beam. Note that for beam management, the following discussion will mainly focus on QCL type D, but it is also necessary to convey the type A QCL relationship for RS to the UE so that all the relevant large-scale parameters can be estimated.

[0024] Information about what assumptions can be made about the QCL is signaled from the network to the UE through a transmission configuration indicator (TCI) state. Each TCI state includes QCL information, i.e., one or two source DL RSs, and each source RS is associated with a QCL type. For example, a TCI state includes a pair of reference signals associated with a QCL type, i.e., two different CSI-RSs {CSI-RS1, CSI-RS2}, respectively, and is set in the TCI state as {qcl-Type1, qcl-Type2} = {Type A, Type D}. This means that the UE can derive the Doppler shift, Doppler spread, mean delay, delay spread from CSI-RS1, and the spatial Rx parameters (i.e., the RX beam to use) from CSI-RS2. In NR, the TCI state is used for downlink channels and signals.

[0025] In NR Release 15, the spatial transmission characteristics are handled differently for PUSCH, PUCCH, and SRS. For PUCCH, the spatial relationship information is configured in the information element PUCCH-SpatialRelationInfo, and for SRS, the spatial relationship information is configured as part of the SRS resource configuration. The spatial transmission characteristics of the PUSCH are given by the spatial transmission characteristics of the associated SRS resource in the SRS resource set configured to "Codebook" or "non-Codebook". Such handling of spatial transmission characteristics is cumbersome and inflexible for uplink multi-panel transmission in NR.

[0026] There has been a proposal to also use the TCI state framework to indicate the spatial characteristics of all UL channels or signals in the uplink (i.e., PUSCH, PUCCH, and SRS). The idea was to use the uplink TCI state to indicate one of multiple uplink panels and the corresponding transmit beam (i.e., transmit characteristics) in the UE for transmitting UL PUSCH / PUCCH / SRS when the UE is equipped with multiple panels. Each TCI state may include one reference signal for spatial relationship indication, one RS for path loss estimation, and possibly a set of power control parameters.

[0027] In general, a list of uplink TCI states may be configured by higher layers (i.e., RRC) for the UE. A subset may be activated by a medium access control (MAC) control element (CE). One of the activated TCI states may be indicated in the DCI for the PUSCH. 5 PUSCH Power Control

[0028] For each SRI, a path loss RS and a set of power control parameters (e.g., a fractional power control factor, P0, a closed-loop index) are preconfigured and signaled to the UE. The PUSCH open-loop transmit power is then derived based on the SRI indicated in the DCI, the associated preconfigured path loss RS, and the set of power control parameters.

[0029] The closed loop power control is performed by sending a transmit power control command (TPC) in the 2-bit "TPC command for scheduled PUSCH" field in the DCI that schedules the PUSCH. The mapping between the precoder value and the power correction is shown in Table 1, where the "Accumulated [dB]" column is used if the UE is configured in accumulation mode, otherwise the "Absolute [dB]" column is used. Table 1: Mapping of TPC command fields in DCI formats scheduling PUSCH transmissions or TPC command fields in DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI or TPC command fields in DCI format 2_3 to absolute and cumulative values ​​or values [Table 1] Summary of the Invention

[0030] Disclosed herein is a system and method for multiple transmit / receive point (TRP) uplink transmission in a cellular communication system. In one embodiment, a method performed by a wireless communication device includes receiving, from a network node, a configuration of two sounding reference signal (SRS) resource sets, a first and a second SRS resource set, each including one or more SRS resources. The method further includes receiving, from the network node, downlink control information (DCI) that schedules a physical uplink channel transmission including a first portion associated with a first SRS resource in the first SRS resource set and a second portion associated with a second SRS resource in the second SRS resource set, the first and second SRS resources being indicated in the DCI. The method further includes transmitting a physical uplink channel transmission signal according to the DCI. In this manner, a robust uplink transmission over multiple TRPs can be provided.

[0031] In one embodiment, the first and second SRS resources are indicated in first and second SRS resource indicator (SRI) fields in the DCI, respectively. In one embodiment, the first and second SRI fields are associated with first and second SRS resource sets, respectively. In one embodiment, the set of possible code points for each of the first and second SRI fields in the DCI has a code point to indicate that the corresponding SRS resource is not selected.

[0032] In one embodiment, the method further includes receiving a configuration of first and second sets of power control parameters associated with the first and second SRS resources, respectively, where each of the first and second sets of power control parameters includes a path loss reference signal, a fractional power control factor, a target received power, a closed loop power control index, or any combination thereof. In one embodiment, the first and second portions of the physical uplink channel transmission are transmitted at first and second transmit powers, respectively, where the first and second transmit powers are calculated based on the first and second sets of power control parameters, respectively.

[0033] In one embodiment, the physical uplink channel transmission is a physical uplink shared channel (PUSCH) transmission.

[0034] In one embodiment, the DCI further indicates first and second transmit power control (TPC) commands for the first and second portions of the physical uplink channel transmission, respectively.

[0035] In one embodiment, the first and second portions of the physical uplink channel transmission are different portions of a single PUSCH transmitted on different frequency domain resources.

[0036] In one embodiment, the first and second parts of the physical uplink channel transmission are first and second PUSCHs carrying different redundancy versions of the same transport block (TB) and transmitted on different frequency domain resources.

[0037] In one embodiment, the first and second portions of the physical uplink channel transmission are first and second layers of a single PUSCH and are transmitted in the same time and frequency domain resources.

[0038] In one embodiment, the first and second SRS resources indicated in the DCI may be replaced with first and second uplink transmission configuration indicator (TCI) states, each of which includes a reference signal index for spatial relationship indication, a path loss reference signal index, a set of power control parameters, or any combination thereof.

[0039] Corresponding wireless communication device embodiments are also disclosed. In one embodiment, the wireless communication device is adapted to receive from a network node a configuration of two SRS resource sets, each having one or more SRS resources. The wireless communication device is further adapted to receive from the network node a DCI scheduling a physical uplink channel transmission including a first portion associated with a first SRS resource in the first SRS resource set and a second portion associated with a second SRS resource in the second SRS resource set, where the first and second SRS resources are indicated in the DCI. The wireless communication device is further configured to transmit a physical uplink channel transmission signal in accordance with the DCI.

[0040] In one embodiment, a wireless communication device has one or more transmitters, one or more receivers, and a processing circuit associated with the one or more transmitters and the one or more receivers. The processing circuit is configured to cause the wireless communication device to receive from a network node a configuration of two SRS resource sets, each including one or more SRS resources. The processing circuit is further configured to cause the wireless communication device to receive from the network node a DCI that schedules a physical uplink channel transmission including a first portion associated with a first SRS resource in the first SRS resource set and a second portion associated with a second SRS resource in the second SRS resource set, where the first and second SRS resources are indicated in the DCI. The processing circuit is further configured to cause the wireless communication device to transmit a physical uplink channel transmission signal according to the DCI.

[0041] An embodiment of a method performed by a network node is also disclosed herein. In one embodiment, the method performed by the network node includes transmitting a configuration of two SRS resource sets, a first and a second SRS resource set, each having one or more SRS resources, to a wireless communication device. The method further includes transmitting a DCI to the wireless communication device that schedules a physical uplink channel transmission including a first portion associated with a first SRS resource in the first SRS resource set and a second portion associated with a second SRS resource in the second SRS resource set, where the first and second SRS resources are indicated in the DCI.

[0042] Corresponding network node embodiments are also disclosed. In one embodiment, the network node is adapted to transmit a configuration of two SRS resource sets, a first and a second SRS resource set, each having one or more SRS resources, to a wireless communication device. The network node is further adapted to send a DCI to the wireless communication device scheduling a physical uplink channel transmission including a first portion associated with a first SRS resource in the first SRS resource set and a second portion associated with a second SRS resource in the second SRS resource set, the first and second SRS resources being indicated in the DCI.

[0043] In one embodiment, the network node has a processing circuit configured to cause the network node to transmit to the wireless communication device a configuration of two SRS resource sets, a first and a second SRS resource set, each having one or more SRS resources, and the processing circuit is further configured to cause the network node to transmit to the wireless communication device a DCI scheduling a physical uplink channel transmission including a first portion associated with a first SRS resource in the first SRS resource set and a second portion associated with a second SRS resource in the second SRS resource set, where the first and second SRS resources are indicated in the DCI.

[0044] In one embodiment, a method performed by a wireless communication device for uplink transmission to a cellular communication network comprises transmitting one or more PUSCHs using two or more Transmission Configuration Indicator (TCI) states in either (a) the same time and frequency domain resources or (b) the same time domain resources but different frequency domain resources, the two or more TCI states being respectively associated with two or more different reference signals.

[0045] In one embodiment, the method further comprises receiving, from the network node, downlink control information scheduling transmission of one or more PUSCHs, where the downlink control information indicates two or more TCI states.

[0046] In one embodiment, the two or more reference signals are two or more downlink reference signals each associated with a particular one of the two or more TCI states, In one embodiment, each of the two or more downlink reference signals is a synchronization signal block (SSB) or a non-zero power (NZP) channel state information reference signal (CSI-RS).

[0047] In one embodiment, each of the two or more reference signals is two or more SRS resources configured with a respective spatial relationship. In one embodiment, the downlink control information includes one or more SRIs indicating the two or more SRS resources. In one embodiment, each of the two or more SRS resources is associated with a respective reference signal via a spatial relationship configuration. In one embodiment, each reference signal is an SSB, an NZP CSI-RS, or another SRS.

[0048] In one embodiment, the two or more SRS resources are associated with two or more respective reference signals, each of the two or more reference signals being associated with two or more respective cell identities. In one embodiment, each of the two or more reference signals is two or more respective SSBs or two or more respective NZP CSI-RS. In one embodiment, each of the two or more reference signals is associated with two or more respective cell identities via a field of the TCI state configuration.

[0049] In one embodiment, each of the two or more reference signals is two or more respective SSBs, and the two or more reference signals are associated with two or more respective cell identities via an SSB configuration.

[0050] In one embodiment, transmitting the one or more PUSCHs includes transmitting a first portion of the one or more PUSCHs using a first TCI state from among the two or more TCI states and transmitting a second portion of the one or more PUSCHs using a second TCI state from among the two or more TCI states. The method further includes receiving an indication of a path loss reference signal and a set of power control parameters associated with each of the two or more TCI states via either: an association between each of the one or more SRIs, one or more path loss reference signals, and one or more sets of power control parameters being signaled to the wireless communication device, or an association between each of the TCI states, one or more path loss reference signals, and one or more sets of power control parameters being signaled to the wireless communication device. In one embodiment, transmitting a first portion of the one or more PUSCHs includes transmitting the first portion of the one or more PUSCHs in accordance with a set of power control parameters associated with a first TCI state, and transmitting a second portion of the one or more PUSCHs includes transmitting the second portion of the one or more PUSCHs in accordance with a set of power control parameters associated with a second TCI state.

[0051] In one embodiment, the method further comprises receiving an indication from the network node to use either a spatial division multiplexing scheme for PUSCH transmission or a frequency division multiplexing scheme for PUSCH transmission. In one embodiment, transmitting the one or more PUSCHs comprises transmitting the one or more PUSCHs on the same time and frequency domain resources if the received indication is an indication to use a spatial division multiplexing scheme for PUSCH transmission, or on the same time domain resources but different frequency domain resources if the received indication is an indication to use a frequency division multiplexing scheme for PUSCH transmission.

[0052] In one embodiment, the one or more PUSCHs include two or more PUSCHs, where each PUSCH of the two or more PUSCHs is scheduled via separate downlink control information. [Brief description of the drawings]

[0053] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate several aspects of the present disclosure and, together with the description, serve to explain the principles of the disclosure.

[0054] [Figure 1] shows an example of a typical slot in New Radio (NR).

[0055] [Diagram 2] FIG. 1 shows the basic NR physical time-frequency resource grid.

[0056] [Diagram 3] 1 illustrates one embodiment of a cellular communication system in which embodiments of the present disclosure may be implemented.

[0057] [Figure 4] 1 illustrates an example of a user equipment (UE) transmitting different layers of a physical uplink shared channel (PUSCH) to two transmission / reception points (TRPs) using spatial domain multiplexing (SDM) in accordance with an embodiment of the present disclosure.

[0058] [Diagram 5] 1 illustrates an example in which a UE transmits two PUSCHs (PUSCH1 and PUSCH2) for the same transport block (TB) to two TRPs (TRP1 and TRP2) in SDM in accordance with an embodiment of the present disclosure.

[0059] [Figure 6] 1 illustrates an example in which a UE transmits a single PUSCH to two TRPs on a portion of the frequency domain resources allocated to each TRP using frequency domain multiplexing (FDM) in accordance with an embodiment of the present disclosure.

[0060] [Figure 7] 4 illustrates an example in which a UE transmits two PUSCHs (PUSCH1 and PUSCH2) for the same TB to two TRPs (TRP1 and TRP2) using FDM according to an embodiment of the present disclosure.

[0061] [Figure 8] 1 illustrates the operation of a wireless communication device (e.g., a UE) and two TRPs in accordance with at least some of the embodiments described in this disclosure.

[0062] [Figure 9A] and [Figure 9B] 1 illustrates the operation of a wireless communication device (e.g., a UE) and two TRPs in accordance with some other embodiments described in this disclosure.

[0063] [Figure 10] and, [Figure 11] and, [Figure 12] FIG. 2 is a schematic block diagram of an exemplary embodiment of a network node.

[0064] [Figure 13] and [Figure 14] 1 is a schematic block diagram of an exemplary embodiment of a wireless communication device.

[0065] [Figure 15] 1 illustrates an exemplary embodiment of a communication system in which embodiments of the present disclosure may be implemented.

[0066] [Figure 16] 16 illustrates an exemplary embodiment of the host computer, base station, and UE of FIG.

[0067] [Figure 17] and [Figure 18]16 is a flow chart illustrating an exemplary embodiment of a method implemented in a communication system such as that of FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0068] The embodiments described below represent information that enables those skilled in the art to implement the embodiments and show the best mode of implementing the embodiments. Upon reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and recognize applications of these concepts not specifically addressed herein. It is to be understood that these concepts and applications are within the scope of the present disclosure.

[0069] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings, in which: However, other embodiments are within the scope of the subject matter disclosed herein, and the disclosed subject matter should not be construed as being limited to only the embodiments described herein, but rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0070] In general, all terms used herein should be interpreted according to their ordinary meaning in the relevant technical field unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the+ element, apparatus, component, means, step, etc. should be openly interpreted as referring to at least one instance of the element, apparatus, component, means, step, etc., unless otherwise specified. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is explicitly described as after or before another step and / or it is implicit that a step must be after or before another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, where appropriate. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the accompanying embodiments will become apparent from the following description.

[0071] Wireless Node: As used herein, a "wireless node" is either a wireless access node or a wireless communication device.

[0072] Radio Access Node: As used herein, a "radio access node" or "radio network node" or "radio access network node" is any node in a radio access network (RAN) of a cellular communications network that operates to transmit and / or receive signals wirelessly. Some examples of radio access nodes include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB)) in a 3rd Generation Partnership Project (3GPP®) fifth generation (5G) NR network, or an enhanced or evolved Node B (eNB) in a 3GPP long term evolution (LTE) network, a high power or macro base station, a low power base station (e.g., a micro base station, a pico base station, a home eNB, etc.), a relay node, a network node implementing some of the functionality of a base station (e.g., a network node implementing a gNB central unit (gNB-CU) or a network node implementing a gNB distributed unit (gNB-DU)), or a network node implementing some of the functionality of some other type of radio access node.

[0073] Core Network Node: As used herein, a "core network node" is a node that implements a core network function or any kind of node in any core network. Examples of core network nodes include a mobility management entity (MME), a packet data network gateway (P-GW), a service capability publication function (SCEF), a home subscriber server (HSS), etc. Some other examples of core network nodes include nodes that implement an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), an authentication server function (AUSF), a network slice selection function (NSSF), a network publication function (NEF), a network function (NF) repository function (NRF), a policy control function (PCF), a unified data management (UDM), etc.

[0074] Communications Device: As used herein, a "communications device" is any type of device that has access to an access network. Some examples of communications devices include, but are not limited to, a mobile phone, a smartphone, a sensor device, a meter, a vehicle, a home appliance, a medical device, a media player, a camera, or any type of consumer electronics, such as, but not limited to, a television, a radio, a lighting fixture, a tablet computer, a laptop, or a personal computer (PC). A communications device may be a portable, handheld, computer-embedded, or vehicle-mounted mobile device that allows for communication of voice and / or data over wireless or wired connections.

[0075] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that accesses (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of wireless communication devices include, but are not limited to, user equipment devices (UEs) in 3GPP networks, machine type communication (MTC) devices, and Internet of Things (IoT) devices. Such wireless communication devices may be or may be integrated into mobile phones, smartphones, sensor devices, meters, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting fixtures, tablet computers, laptops, or PCs. Wireless communication devices may be portable, handheld, computer-embedded, or vehicle-mounted mobile devices that allow for voice and / or data communication over wireless connections.

[0076] Network Node: As used herein, a "network node" is any node that is part of the RAN or in the core network of a cellular communications network / system.

[0077] Transmit / Receive Point (TRP): In some embodiments, a TRP can be either a network node, a radio head, a spatial relationship, or a transmission configuration indicator (TCI) state. A TRP can be represented by a spatial relationship or a TCI state in some embodiments. In some embodiments, a TRP can use multiple TCI states. In some embodiments, a TRP can be part of a gNB that transmits and receives radio signals to and from a UE according to physical layer characteristics and parameters specific to that element. In some embodiments, in multiple TRP (multi-TRP) operation, a serving cell can schedule a UE from two TRPs, providing better physical downlink shared channel (PDSCH) coverage, reliability, and / or data rates. There are two different modes of operation for multi-TRP: single downlink control information (DCI) and multi-DCI. For both modes, control of uplink and downlink operations is done by both the physical layer and the medium access control (MAC). In single DCI mode, the UE is scheduled by the same DCI for both TRPs, whereas in multi-DCI mode, the UE is scheduled by independent DCI from each TRP.

[0078] In some embodiments, a Transmission Point (TP) set is a geographically collocated set of transmitting antennas (e.g., an antenna array (having one or more antenna elements)) for one cell, part of one cell, or one Positioning Reference Signal (PRS)-only TP. A TP may include a base station (eNB) antenna, a remote radio head (RRH), a base station remote antenna, an antenna of a PRS-only TP, etc. A cell may be formed by one or more TPs. In case of homogeneous deployment, each TP may correspond to one cell.

[0079] In some embodiments, a set of TRPs is a geographically collocated set of antennas (e.g., antenna arrays (having one or more antenna elements)) that support TP and / or receiving point (RP) functionality.

[0080] It should be noted that the present specification focuses on 3GPP cellular communication systems and therefore 3GPP terminology or terminology similar to 3GPP terminology is often used, however, the concepts disclosed herein are not limited to 3GPP systems.

[0081] In the description herein, reference may be made to the term "cell", however, it should be noted that, particularly with regard to 5G NR concepts, beams may be used instead of cells, and thus the concepts described herein are equally applicable to both cells and beams.

[0082] Currently, certain one or more problems exist. For dynamically scheduled physical uplink shared channel (PUSCH) and preconfigured grant PUSCH type 2 (i.e., PUSCH transmission), the codebook-based PUSCH in existing NR Release 15 / 16 allows only a single sounding reference signal (SRS) resource to be indicated by the gNB in ​​the downlink control information (DCI), and this single indicated SRS resource is then used to define the spatial relationship for the PUSCH. For non-codebook-based PUSCH schemes, a single channel state information (CSI) reference signal (CSI-RS) is associated with an SRS resource set, and the spatial relationship of the PUSCH is defined by the CSI-RS configured for the corresponding SRS resource set. Thus, the PUSCH in existing NR Release 15 / 16 is only suitable for single transmission / reception point (TRP)-based transmission, such as PUSCH transmission being directed to a single TRP. It is not suitable for transmitting PUSCH toward multiple TRPs. Therefore, the question is how to configure a UE for PUSCH transmissions towards multiple TRPs, and in particular, how to indicate the spatial relationship associated with the TRPs.

[0083] Certain aspects of the present disclosure and embodiments thereof may provide solutions to the above and other problems. Disclosed are systems and methods for supporting simultaneous uplink (UL) PUSCH transmissions towards two or more TRPs by indicating two or more SRS resources in either a single SRS resource set or multiple SRS resource sets, including: Transmitting different layers of PUSCH to different TRPs; Transmitting PUSCH to different TRPs on different frequency resources, and / or ● Transmitting two PUSCHs to different TRPs on different frequency resources.

[0084] Also disclosed herein are systems and methods for per-TRP PUSCH power control and signaling extension in DCI.

[0085] In one embodiment, a method performed by a UE includes transmitting one or more PUSCHs, each associated with a reference signal (RS), to two or more TRPs simultaneously, either on the same time and frequency domain resources (e.g., using a spatial division multiplexing (SDM) scheme) or on the same time domain resources but different frequency domain resources (e.g., using a frequency division multiplexing (FDM) scheme).

[0086] In one embodiment, one or more PUSCHs are scheduled by a single DCI.

[0087] In one embodiment, two or more RSs are indicated in the DCI. In one embodiment, the two or more RSs are two or more SRS resources each configured with a spatial relationship or two or more downlink (DL) RSs each associated with a transmission configuration indicator (TCI) state. In one embodiment, the indication of the two or more SRS resources is via one or more SRS resource indicators (SRIs).

[0088] In one embodiment, the two or more RSs indicated in the DCI are two or more SRS resources, each of which is associated with a reference signal, such as, for example, a synchronization signal block (SSB), a non-zero power (NZP) CSI-RS, or another SRS, via a spatial relationship configuration. In one embodiment, each SSB or NZP CSI-RS is associated with a different physical cell identity (ID), for example, by the SSB configuration or by a field in the TCI state configuration.

[0089] In one embodiment, the indication of the two or more SRS resources is via one or more SRIs, and the UE also receives (e.g., is signaled) a pathloss RS and a set of power control parameters for each of the one or more PUSCHs via the one or more SRIs, and an association between the SRI, the one or more pathloss RS, and the one or more sets of power control parameters is signaled.

[0090] In one embodiment, the two or more SRS resources belong to either the same SRS set or different SRS resource sets.

[0091] In one embodiment, an indication of whether a UE should use an SDM or FDM scheme is signaled semi-statically (e.g., via Radio Resource Control (RRC)) and / or dynamically (e.g., via DCI).

[0092] In one embodiment, each PUSCH is scheduled by a separate DCI.

[0093] In one embodiment, two or more TRPs are indicated in the DCI through an indication of two or more TCI states, each TRP being associated with one TCI state.

[0094] Certain embodiments may provide one or more of the following technical advantages: The proposed solution enables more robust UL data transmission over multiple TRPs with very low latency, and better reliability can be achieved via spatial diversity over multiple TRPs simultaneously.

[0095] FIG. 3 illustrates one embodiment of a cellular communication system 300 in which embodiments of the present invention may be implemented. In the embodiment described herein, the cellular communication system 300 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC). In this example, the RAN includes base stations 302-1 and 302-2, which in 5GS include NR base stations (gNBs) and optional Next Generation eNBs (ng-eNBs) (i.e., LTE RAN nodes connected to 5GC), and control corresponding (macro) cells 304-1 and 304-2. The base stations 302-1 and 302-2 are generally referred to herein collectively as base stations 302, and may be individually referred to as base stations 302. Similarly, the (macro) cells 304-1 and 304-2 are generally referred to herein collectively as (macro) cells 304, and may be individually referred to as (macro) cells 304. The RAN may also include several low power nodes 306-1-306-4 that control corresponding small cells 308-1-308-4. The low power nodes 306-1-306-4 may be small base stations (such as pico or femto base stations) or remote radio heads (RRHs), or the like. Although not specifically shown, one or more of the small cells 308-1-308-4 may alternatively be provided by the base station 302. The low power nodes 306-1-306-4 are generally referred to herein collectively as low power nodes 306 and individually as low power nodes 306. Similarly, the small cells 308-1-308-4 are generally referred to herein collectively as small cells 308 and individually as small cells 308. The cellular communication system 300 also includes a core network 310, which in 5GS is referred to as 5G Core (5GC). The base station 302 (and optionally the low power node 306 ) is connected to a core network 310 .

[0096] The base station 302 and low power node 306 serve wireless communication devices 312-1 through 312-5 in corresponding cells 304 and 308. The wireless communication devices 312-1 through 312-5 are generally referred to herein collectively as wireless communication devices 312 and individually as wireless communication devices 312. In the following description, the wireless communication devices 312 are often UEs and therefore may be referred to herein as UEs 312, although the disclosure is not limited thereto.

[0097] Next, several embodiments of the present disclosure will be described. Simultaneous PUSCH transmission to multiple TRPs using spatial domain multiplexing (SDM)

[0098] In this embodiment, one or more PUSCHs for the same transport block (TB) are transmitted simultaneously to multiple TRPs on the same time and frequency resources or on different frequency resources of different TRPs. Examples of different TRPs are different base stations 302, different low power nodes 306, a mix of one or more base stations 302 and one or more low power nodes 306, etc. It should be noted that these are non-limiting examples of TRPs. Other examples include remote radio heads, multiple panels, etc.

[0099] FIG. 4 illustrates an example of a UE (e.g., UE 312) transmitting different layers of a PUSCH to two TRPs. A PUSCH with two layers is scheduled by DCI, with a first layer (Layer 1) transmitted to TRP1 and a second layer (Layer 2) transmitted to TRP2. The first layer is associated with a first SRS resource and the second layer is associated with a second SRS resource, which means that the layers are transmitted on the SRS ports of the corresponding SRS resources. In Frequency Range 2 (FR2), each SRS resource is spatially associated with either a DL RS (e.g., CSI-RS or SSB) or another SRS via a spatial relationship configuration. In this example, a first DL RS (DL RS #1) is transmitted from TRP1 and a second DL RS (DL RS #2) is transmitted from TRP2. In one example, the two DL RSs belong to two different TCI states and can also have different SSBs as sources of QCL (quasi-collocated) relationships. Therefore, each TRP transmits a different SSB.

[0100] In particular, two SSBs may be possible to be configured with different physical cell IDs even if both are used by the same UE for PUSCH transmission, i.e., two TRPs transmit SSBs belonging to two different cells, and the DL RSs are also transmitted from different cells, since the SSBs are the source of the QCL relationship to the DL RS (target). Alternatively, the TCI state includes a cell ID indicator (i.e., transmitted with different cell IDs from TRPs served by different cells), so that the DL RSs belong to a TCI state and different DL RSs can be configured to belong to different cells.

[0101] One example of a DL RS is a CSI-RS for tracking, ie, a tracking reference signal (TRS).

[0102] The first SRS resource (SRS #1) is spatially associated with the first DL RS, and the second SRS resource (SRS #2) is spatially associated with the second DL RS. And the DCI scheduling the PUSCH is indicated to the UE via the PDCCH (Physical Downlink Control Channel). The two SRS resources are indicated in one or two "SRS Resource Indicator (SRI)" fields of the DCI. Two DMRS ports (i.e., DMRS ports x and y), each associated with one of the two layers in two code division multiplexing (CDM) groups (i.e., CDM groups 1 and 2), are also indicated in the DCI. The first SRS resource is linked to the first DMRS port indicated in the DCI field "Antenna Port", and the second SRS resource is linked to the second DMRS port indicated in the DCI field "Antenna Port". In the case of codebook-based SRS and when there is more than one SRS port per SRS resource, a transmit precoding matrix indicator (TPMI) is also indicated for each SRS resource. In this example, joint decoding by combining the PUSCH signals received from two TRPs is required.

[0103] In an embodiment in which a UE transmits different layers of a single PUSCH to two TRPs (as shown in the example of FIG. 4), the same time and frequency resources are used for transmitting to the two different TRPs.

[0104] In the above exemplary embodiment, two layers of a single PUSCH are covered, but this embodiment can be extended to more than two layers. For example, the above exemplary embodiment can be extended to up to four layers of a single PUSCH, transmitted to up to three TRPs. Example exemplary embodiments are as follows: In one example, a PUSCH with four layers is scheduled by DCI, with the first and second layers (layers 1-2) being transmitted to TRP1, and the third and fourth layers (layers 3-4) being transmitted to TRP2. Layers 1-2 are associated with a first SRS resource, and layers 3-4 are associated with a second SRS resource, and these associations mean that the layers are transmitted on the SRS ports of the corresponding SRS resources. In this case, the "antenna port" field can indicate the DMRS ports corresponding to two CDM groups (one CDM group associated with each TRP). In another example, a PUSCH with three layers is scheduled by DCI, with the first and second layers (Layer 1-2) being transmitted to TRP1 and the third layer (Layer 3) being transmitted to TRP2. Layers 1-2 are associated with a first SRS resource and Layer 3 is associated with a second SRS resource, and these associations mean that the layers are transmitted on the SRS ports of the corresponding SRS resources. In this case, the "antenna port" field can indicate the DMRS ports corresponding to the two CDM groups (one CDM group associated with each TRP). In another example, a PUSCH with four layers is scheduled by DCI, and the first and second layers (Layer 1-2) are transmitted to TRP1, the third layer (Layer 3) is transmitted to TRP2, and the fourth layer is transmitted to TRP3. Layers 1-2 are associated with a first SRS resource, Layer 3 is associated with a second SRS resource, and Layer 4 is associated with a third SRS resource, and these associations mean that the layer is transmitted on the SRS port of the corresponding SRS resource. In this case, the "antenna port" field can indicate the DMRS ports corresponding to the three CDM groups (one CDM group associated with each TRP).

[0105] Alternatively, separate PUSCHs may be transmitted to each TRP for the same or different TBs. Figure 5 shows an example in which a UE transmits two PUSCHs (PUSCH1 and PUSCH2) for the same TB to two TRPs (TRP1 and TRP2). In this case, PUSCH2 can be considered as a retransmission of a TB with the same or different redundancy version. Again, the two SRS resources and DMRSs in the two CDM groups are indicated in the DCI through the SRI and antenna port fields, respectively. In this case, if each of the two PUSCHs is self-decodable, independent decoding can be performed in each TRP. In an embodiment in which a UE transmits two PUSCHs to two TRPs (as shown in the example of Figure 5), the same time-frequency resources are used to transmit to two different TRPs. Although the above embodiment covers two PUSCHs of the same TB transmitted to two TRPs, this embodiment can be extended to N PUSCHs of the same TB with different RVs transmitted to up to N TRPs. Simultaneous PUSCH transmission to multiple TRPs using Frequency Domain Multiplexing (FDM)

[0106] In the above example, the same time-frequency resources were assigned to both TRPs. In this embodiment, different TRPs are assigned different frequency domain resources. Figure 6 shows an example in which a single PUSCH is transmitted to two TRPs using a portion of the frequency domain resources (e.g., a portion of the RBs) assigned to each TRP. In this case, since different resources are used, the same DMRS port may be shared by the two TRPs, and thus a single CDM group may be assigned. Joint decoding by combining the PUSCH signals received from the two TRPs is required.

[0107] Alternatively, separate PUSCHs for the same or different TBs are transmitted to each TRP with different frequency domain resources. Figure 7 shows an example in which a UE transmits two PUSCHs (PUSCH1 and PUSCH2) for the same TB to two TRPs (TRP1 and TRP2). In this case, PUSCH2 can be considered as a retransmission of the same TB with the same or different redundancy version (RV). Again, two SRS resources and one CDM group are indicated in the DCI. In this case, if each of the two PUSCHs is self-decodable, independent decoding can be performed in each TRP.

[0108] A single frequency resource allocation may be signaled, in which case the frequency resource is divided between the two TRPs. In one embodiment, if N RBs are allocated, N / 2 first RBs are allocated to the first TRP and the remaining RBs are allocated to the second TRP. Alternatively, even-numbered RBs (or subcarriers) are allocated to the first TRP and odd-numbered RBs (or subcarriers) are allocated to the second TRP, or vice versa.

[0109] In one embodiment, when two PUSCHs (eg, PUSCH1 and PUSCH2) are used, the TB size is determined based on the number of RBs (or subcarriers) allocated to the first TRP. Configuring the UE to use either the SDM or FDM method

[0110] In some embodiments, the selection of the PUSCH transmission scheme between SDM or FDM scheme and the variations covered above is configured in the UE using higher layer (e.g., RRC) signaling. That is, if the network configures the UE to use the "FDM" scheme, the UE is assumed to use the PUSCH multi-TRP transmission scheme according to the embodiment described above in the "Simultaneous PUSCH Transmission to Multiple TRPs with Frequency Domain Multiplexing (FDM)" section. In another embodiment, whether the UE uses "SDM" or "FDM" multi-TRP PUSCH transmission is jointly indicated by the antenna port field and the SRI field in the UL DCI as follows: ● If the “antenna port” field indicates DMRS ports from two CDM groups and the SRI field indicates two SRS resources, the UE is assumed to use the SDM scheme. ● If the “antenna port” field indicates a DMRS port from one CDM group and the SRI field indicates two SRS resources, the UE is assumed to use the FDM scheme. PUSCH power control

[0111] For codebook-based PUSCH transmission, in one embodiment, a single SRS resource set having two or more SRS resources is configured for the UE. Each of the two or more SRS resources is associated with a TRP via a spatial relationship configuration including a DL RS (or a pathloss RS) for performing pathloss measurement and estimation. A set of PUSCH power control related parameters is also associated with the SRS resource. When one or more PUSCHs transmitted to two TRPs are scheduled by DCI, the two SRS resources are also indicated in the DCI. The transmit power of the PUSCH to each TRP may be calculated based on the pathloss estimation and a set of power control parameters associated with the corresponding SRS resource.

[0112] In another embodiment, two SRS resource sets, each having one or more SRS resources, are configured for the UE. Each of the SRS resource sets is associated with a DL RS for path loss measurement and a set of PUSCH power control related parameters. When one or more PUSCHs transmitted to two TRPs are scheduled by DCI, two SRS resources, one in each SRS resource set, are indicated in the DCI. The transmit power of one or more PUSCHs to each TRP may be calculated based on the estimated path loss and the power control parameters associated with the corresponding SRS resource set.

[0113] For non-codebook-based PUSCH transmission, two SRS resource sets may be configured for the UE. Each of the SRS resource sets is also associated with a DL RS for path loss calculation and a set of power control related parameters. When one or more PUSCHs transmitted to the two TRPs are scheduled by DCI, the SRS resource(s) in each SRS resource set are indicated in the DCI. The transmit power of one or more PUSCHs to each TRP may be calculated based on the estimated path loss and the power control parameters associated with the corresponding SRS resource set.

[0114] For codebook-based PUSCH transmission, one or two SRS resources may be indicated in the DCI for PUSCH transmission to one or two TRPs, respectively. For non-codebook-based transmission, one or two SRS resource sets may be indicated in the DCI for PUSCH transmission to one or two TRPs, respectively. If one SRS resource is indicated, the PUSCH destined for a single TRP is scheduled. On the other hand, if two SRS resources are indicated, one or more PUSCHs are scheduled to two TRPs.

[0115] Two SRI fields, one for each TRP, may be used in the DCI for scheduling the PUSCH. To support dynamic switching between a single TRP and two TRPs, each SRI field may also include a codepoint to indicate that the corresponding SRS resource is not selected.

[0116] To support independent power control of the PUSCH to each TRP, a separate TPC command may be included in the DCI for each TRP. The TPC command field for PUSCH scheduled in DCI 0_1 and DCI 0_2 may be extended from 2 bits to 4 bits, making 2 bits available for each TRP. UCI on PUSCH

[0117] Uplink control information (UCI), such as Hybrid Automatic Repeat Request Acknowledgement (HARQ-Ack), CSI feedback, or Scheduling Request (SR) on PUCCH resources may be present in the same slot as PUSCH. In this case, UCI is carried on PUSCH (instead of PUCCH). There are challenges in how to multiplex UCI and PUSCH.

[0118] In one embodiment, if two PUSCHs, each destined for a different TRP, overlap with a PUCCH in one or more symbols in a slot, and the PUCCH has the same spatial relationship as one of the two PUSCHs, UCI is transmitted on both PUSCHs to both TRPs. Alternatively, UCI is transmitted only on the PUSCH that has the same spatial relationship as the overlapping PUCCH.

[0119] If the UE is provided with control information ACKNACKFeedbackMode=JointFeedback, and if the PUCCH overlaps with the PUSCH in at least one symbol, UCI is transmitted on both PUSCHs.

[0120] In another embodiment, if the UE always multiplexes UCI on the PUSCH regardless of the spatial relationship, then the UE may be provided with higher layer configuration. DCI Indications

[0121] In addition to the "TPC commands for scheduled PUSCH" described above in the "PUSCH power control" section, one or some of the DCI bit fields in DCI formats 0_1 and 0_2 may be extended to have more bits in an existing field (i.e., for joint coding for two TRPs) or to add a new field (for the second TRP) to support two PUSCH transmissions to two TRPs: Precoding information and number of layers ●Antenna port ●SRS request PTRS-DMRS Association DMRS sequence initialization First downlink allocation index Second downlink allocation index

[0122] Although the UE can switch between single-TRP mode and multi-TRP mode based on the received DCI indication, the DCI fields for each format 0_1 ​​and 0_2, as well as the size of each field, should be adjusted to be constant. Either truncation or padding can be applied to adjust each DCI field size to be constant. For example, some most significant bits with value set to "0" are inserted for the bit string of the shorter length (i.e., single-TRP) until the bit lengths of the single-TRP and multi-TRP are the same.

[0123] When PUSCH multi-TRP enablement is configured per CORESET or SearchSpace, each DCI field size is adjusted per CORESET or SearchSpace, and the total DCI payload size of the same format is adjusted to a constant length across all CORESETs and SearchSpaces. Further explanation

[0124] Although the above description focuses on simul-PUSCH transmission to two TRPs for the same TB (e.g., PUSCH1 and PUSCH2), the embodiments can be easily extended to different TBs (e.g., PUSCH1 carries TB1 while PUSCH2 carries TB2). In addition, although single DCI-based scheduling for PUSCH transmissions is described above, the embodiments can also be extended to multi-DCI-based scheduling where the PUSCH to each TRP is scheduled by a separate DCI.

[0125] Furthermore, one or more SRIs are used to indicate the PUSCH transmission direction in the above embodiment. However, in another embodiment, the UL TCI state may be used instead to indicate the PUSCH transmission direction. For example, two UL TCI states may be signaled in the DCI to indicate PUSCH transmission to two TRPs.

[0126] 8 illustrates the operation of a wireless communication device 312 (e.g., a UE) and two TRPs 800-1 and 800-2 according to at least some of the embodiments described above. Note that optional steps are represented by dashed lines or boxes. As shown, in one embodiment, the wireless communication device 312 receives DCI from a network node (e.g., in this case TRP1) that schedules transmission of one or more PUSCHs to TRP1 and TRP2 simultaneously, on the same time and frequency domain resources, or on the same time domain resources but different frequency domain resources (step 806).

[0127] The wireless communication device 312 transmits one or more PUSCHs (e.g., PUSCHs scheduled by the DCI of step 806) to TRP1 and TRP2 on the same time and frequency domain resources or on the same time domain resources but different frequency domain resources (step 808). As described above, each TRP is associated with a different reference signal. The transmission includes a first part (step 808-1) transmitted to TRP1 and a second part (step 808-2) transmitted simultaneously to TRP2. For example, the first part and the second part are different layers of the same PUSCH transmitted on the same time and frequency domain resources (e.g., see FIG. 4). As another example, the first part and the second part are different PUSCH transmissions of different RVs of the same TB transmitted on the same time and frequency domain resources (e.g., see FIG. 5). As another example, the first part and the second part are the same PUSCH transmitted on the same time domain resources but different frequency domain resources (e.g., see FIG. 6). As another example, the first and second parts are separate PUSCH transmissions of different RVs of the same TB transmitted on the same time domain resources but different frequency domain resources (see, for example, FIG. 7).

[0128] The details discussed above regarding the DCI received by the wireless communication device 312 (e.g., a UE) to schedule multi-TRP PUSCH transmissions are applicable to the process of Figure 8. Some of these details are repeated here, but it should be noted that other details not repeated here are also applicable. In one embodiment, the DCI indicates two or more reference signals. In one embodiment, the two or more reference signals are two or more downlink reference signals each associated with a respective TCI state.

[0129] In another embodiment, the two or more reference signals are two or more SRS resources, each configured with a respective spatial relationship. In one embodiment, the DCI includes one or more SRIs indicating the two or more SRS resources. In one embodiment, each of the two or more SRS resources is associated with a respective reference signal via a spatial relationship configuration. In one embodiment, each of the two or more reference signals is an SSB, an NZP CSI-RS, or another SRS. In one embodiment, the two or more SRS resources are associated with each of the two or more reference signals, each of the two or more reference signals being associated with each of the two or more cell IDs (i.e., each reference signal is associated with a different cell ID). In one embodiment, each of the two or more reference signals is two or more respective SSBs or two or more respective NZP CSI-RS. In one embodiment, each of the two or more reference signals is associated with each of the two or more cell IDs via a field of the TCI state configuration. In one embodiment, each of the two or more reference signals is two or more respective SSBs, and the two or more reference signals are associated with each of the two or more cell IDs via an SSB configuration.

[0130] In one embodiment, the wireless communication device 312 further receives an indication from a network node (e.g., TRP1 in this case) indicating one path loss reference signal and a set of power control parameters for each of the one or more PUSCHs via one or more SRIs, and an association between the SRI, the one or more path loss reference signals, and the one or more sets of power control parameters is signaled to the wireless communication device. In this example, the indication indicating the path loss reference signal and the set of power control parameters for each of the one or more PUSCHs is included in the DCI, and more specifically, is provided by the SRI. In other words, in one embodiment, the wireless communication device 312 receives information defining, for each SRI of the set of SRIs, an association between the SRI, the one or more path loss reference signals, and the one or more sets of power control parameters (step 802). In other words, as described above in the section entitled "PUSCH Power Control," the wireless communication device 312 may receive a configuration of a path loss reference signal and a set of power control related parameters for each SRS resource (e.g., in the case of a single SRS resource set) or for each SRS resource set (e.g., in the case of two (or more) SRS resource sets). The wireless communication device 312 then receives an indication via one or more SRIs included in the DCI in step 806 indicating the path loss reference signal and the set of power control parameters for each of the one or more PUSCHs. In one embodiment, in step 808, the wireless communication device 312 transmits the one or more PUSCHs to two or more TRPs according to the indicated set of power control parameters for each of the one or more PUSCHs.

[0131] In one embodiment, the two or more SRS resources belong to either the same SRS resource set or different SRS resource sets.

[0132] In one embodiment, the wireless communication device 312 receives an indication from a network node (e.g., TRP1 in this case) indicating to use either an SDM scheme for multi-TRP PUSCH transmission or an FDM scheme for multi-TRP PUSCH transmission (step 804). In this case, in step 808, the wireless communication device 312 transmits one or more PUSCHs to the TRP on the same time and frequency domain resources if the received indication is an indication to use an SDM scheme for multi-TRP PUSCH transmission, or on the same time domain release but different frequency domain resources if the received indication is an indication to use an FDM scheme for multi-TRP PUSCH transmission.

[0133] In one exemplary alternative embodiment, the one or more PUSCHs comprise two or more PUSCHs, each PUSCH of the two or more PUSCHs being scheduled via separate downlink control information.

[0134] In one embodiment, the TRPs for which the PUSCH is simulcast are indicated in the DCI via an indication of two or more TCI states, with each TRP associated with one TCI state.

[0135] 9A and 9B illustrate the operation of a wireless communication device 312 (e.g., a UE) and two TRPs 800-1 and 800-2 according to at least some of the embodiments described above, particularly those described in the "PUSCH power control" section. As illustrated in FIG. 9A, in an embodiment, the wireless communication device 312 receives a configuration (step 902A) of a single SRS resource set including two or more SRS resources from a network node (e.g., TRP1 in this case). As described above, each of the two or more SRS resources (in the single SRS resource set) is associated with a TRP via a spatial relationship configuration including a DL RS (or path loss RS) for path loss measurement and estimation. A set of PUSCH power control related parameters is also associated with the SRS resource. In other words, each SRS resource in the single SRS resource set is associated with a corresponding path loss RS and a corresponding set of power control related parameters.

[0136] The wireless communication device 312 receives a DCI to transmit one or more PUSCHs to TRP1 900-1 and TRP2 900-2 (step 904A). In other words, the received DCI schedules a PUSCH transmission including a first portion to be transmitted to TRP1 900-1 (e.g., associated with a first SRS resource indicated in the DCI or first TCI state) and a second portion to be transmitted to TRP2 900-2 (e.g., associated with a second SRS resource indicated in the DCI or second TCI state). The DCI indicates two SRS resources (i.e., the first SRS resource and the second SRS resource) selected from a single SRS resource set configured in step 902A. The indication of the first SRS resource in the DCI is also an indication of a set of corresponding path loss RS and PUSCH power control related parameters associated with the first SRS resource. Similarly, an indication of a second SRS resource in the DCI is also an indication of a set of corresponding path loss RS and PUSCH power control related parameters associated with the second SRS resource, and the first SRS resource is associated with TRP1 900-1 (or a first TCI state) and the second SRS resource is associated with TRP2 900-2 (or a second TCI state).

[0137] The wireless communication device 312 transmits one or more PUSCHs in accordance with the DCI (step 906A). More specifically, the PUSCH transmission of step 906A includes a first part (e.g., transmitted using a first TCI state) transmitted to TRP1 900-1 with a transmit power calculated based on a path loss estimated based on a path loss reference signal associated with a first SRS resource indicated by the DCI (step 906A-1). The PUSCH transmission of step 906A also includes a second part (e.g., transmitted using a second TCI state) transmitted to TRP2 900-2 with a transmit power calculated based on a path loss estimate based on a path loss reference signal associated with a second SRS resource indicated by the DCI (step 906A-2). For example, the first part and the second part are different layers for the same PUSCH transmitted. As another example, the first part and the second part are different PUSCH transmissions of different RVs for the same TB.

[0138] As shown in FIG. 9B, in another embodiment, the wireless communication device 312 receives from a network node (e.g., TRP1 900-1 in this example) a configuration of two SRS resource sets, each including one or more SRS resources (step 902B). As explained above, each of the two SRS resource sets is associated with a DL RS (or pathloss RS) for pathloss measurement and estimation and a set of PUSCH power control related parameters. The wireless communication device 312 receives DCI scheduling transmission of one or more PUSCHs to TRP1 900-1 and TRP2 900-2 (step 904B). In other words, the received DCI schedules a PUSCH transmission including a first portion to be transmitted to TRP1 900-1 (e.g., a first SRS resource from a first SRS resource set indicated in the DCI, or a first TCI state) and a second portion to be transmitted to TRP2 900-2 (e.g., a second SRS resource selected from a second SRS resource set, indicated in the DCI or in a second TCI state). The DCI indicates two SRS resources including a first SRS resource from the first SRS resource set (thereby associated with a corresponding pathloss RS and a set of PUSCH power control related parameters associated with the first SRS resource set) and a second SRS resource from the second SRS resource set (thereby associated with a corresponding pathloss RS and a set of PUSCH power control related parameters associated with the second SRS resource set). Additionally, a first SRS resource is associated with TRP1 900-1 (or a first TCI state) and a second SRS resource is associated with TRP2 900-2 (or a second TCI state).

[0139] The wireless communication device 312 transmits one or more PUSCHs in accordance with the DCI (step 906A). More specifically, the PUSCH transmission of step 906A includes a first portion (e.g., transmitted using a first TCI state) transmitted to TRP1 900-1 with a transmit power calculated based on a path loss estimated based on a path loss reference signal associated with a first SRS resource indicated by the DCI (step 906A-1). The PUSCH transmission of step 906A also includes a second portion (e.g., transmitted using a second TCI state) transmitted to TRP2 900-2 with a transmit power calculated based on a path loss estimate based on a path loss reference signal associated with a second SRS resource indicated by the DCI (step 906A-2). For example, the first portion and the second portion are different layers of the same PUSCH transmitted. As another example, the first portion and the second portion are different PUSCH transmissions of different RVs of the same TB.

[0140] As described above, the DCI of step 904A or 904B, in one embodiment, includes two SRI fields, one indicating the SRS resource for each of TRP 900-1 and TRP 900-2. In one embodiment, to support dynamic switching between a single TRP and two TRPs, each SRI field may also include a codepoint to indicate that the corresponding SRS resource is not selected, as described above.

[0141] In one embodiment, to support independent power control of the PUSCH for each TRP, separate TPC commands may be included in the DCI of step 904A or 904B for each of TRP 900-1 and TRP 900-2, as described above. In one embodiment, the "TPC command for scheduled PUSCH" field in DCI 0_1 and DCI 0_2 may be increased by 2 bits for each TRP by expanding it from 2 bits to 4 bits, as described above.

[0142] FIG. 10 is a schematic block diagram of a radio access node 1000 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The radio access node 1000 may be, for example, a TRP as described herein. As shown, the radio access node 1000 has a control system 1002, which has one or more processors 1004 (e.g., a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), etc.), a memory 1006, and a network interface 1008. The one or more processors 1004 are also referred to herein as processing circuits. Additionally, the radio access node 1000 may include one or more radio units 1010, each including one or more transmitters 1012 and one or more receivers 1014 coupled to one or more antennas 1016. The radio units 1010 may be referred to or may be part of a radio interface circuit. According to some embodiments, the radio unit 1010 is external to the control system 1002 and is connected to the control system 1002, for example, via a wired connection (e.g., optical cable). However, according to some other embodiments, the radio unit(s) 1010 and potentially the antenna(s) 1016 are integrated with the control system 1002. The one or more processors 1004 operate to provide one or more functions of the radio access node 1000 described herein (e.g., one or more functions of the TRP described herein). According to an embodiment, the functions are implemented in software, for example stored in the memory 1006 and executed by the one or more processors 1004.

[0143] 11 is a schematic block diagram illustrating a virtualized embodiment of a radio access node 1000 according to some embodiments of the present disclosure. This description is equally applicable to other types of network nodes. Moreover, other types of network nodes may have a similar virtualization architecture. Again, optional functionality is represented by dashed boxes.

[0144] As used herein, a "virtualized" radio access node is an implementation of the radio access node 1000 in which at least a portion of the functionality of the radio access node 1000 is implemented as virtual component(s) (e.g., via virtual machine(s) running on physical processing node(s) in network(s)). As shown, in this illustration, the radio access node 1000 may include a control system 1002 and / or one or more radio units 1010, as described above. The control system 1002 may be connected to the radio units 1010, for example, via optical cables or the like. The radio access node 1000 includes one or more processing nodes 1100 coupled to or included as part of a network(s) 1102. If present, the control system 1002 or radio units are connected to the processing nodes 1100 via the network 1102. Each processing node 1100 has one or more processors 1104 (eg, a CPU, ASIC, FPGA, and / or the like), memory 1106, and a network interface 1108.

[0145] In this illustration, the functions 1110 of the radio access node 1000 described herein (e.g., one or more functions of the TRP) are implemented in one or more processing nodes 1100 or distributed across one or more processing nodes 1100 and the control system 1002 and / or the radio unit 1010 in any desired manner. According to some particular embodiments, some or all of the functions 1110 of the radio access node 1000 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment hosted by the processing node 1100. As will be appreciated by those skilled in the art, additional signaling transfer or communication between the processing node 1100 and the control system 1002 is used to perform at least some of the desired functions 1110. Notably, according to some embodiments, the control system 1002 may not be included, in which case the radio unit 1010 communicates directly with the processing node 1100 via an appropriate network interface.

[0146] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform functions of the radio access node 1000 or a node (e.g., processing node 1100) implementing one or more of the functions 1110 of the radio access node 1000 in a virtual environment according to any of the embodiments described herein. According to some embodiments, a carrier is provided that carries the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0147] 12 is a schematic block diagram of a radio access node 1000 according to some other embodiments of the present disclosure. The radio access node 1000 has one or more modules 1200, each of which is implemented in software. The module(s) 1200 provide the functionality of the radio access node 1000 described herein (e.g., the functionality of the TRP described herein). This description is equally applicable to the processing node 1100 of FIG. 11, where the module 1200 may be implemented in one of the processing nodes 1100 or distributed across multiple processing nodes 1100 and / or distributed across the processing nodes 1100 and the control system 1002.

[0148] 13 is a schematic block diagram of a wireless communication device 1300 according to some embodiments of the present disclosure. The wireless communication device 1300 may be a wireless communication device Q 112 or a UE, as described herein. As shown, the wireless communication device 1300 includes one or more processors 1302 (e.g., CPU, ASIC, FPGA, etc.), a memory 1304, and one or more transceivers 1306, each including one or more transmitters 1308 and one or more receivers 1310 coupled to one or more antennas 1312. The transceiver 1306 includes a radio front-end circuit connected to the antenna 1312 configured to condition signals communicated between the antenna 1312 and the processor 1302, as will be understood by those skilled in the art. The processor 1302 is also referred to herein as a processing circuit. The transceiver 1306 is also referred to herein as a radio circuit. In some embodiments, the functionality of the wireless communication device 1300 described above (e.g., functionality of the wireless communication device 312 or UE described herein) may be implemented fully or partially in software, for example, stored in memory 1304 and executed by processor 1302. It should be noted that the wireless communication device 1300 may include additional components not shown in FIG. 13 , such as, for example, one or more user interface components (e.g., input / output interfaces including a display, buttons, touch screen, microphone, speaker, etc., and / or any other components for enabling input of information into and / or output of information from the wireless communication device 1300, a power supply (e.g., a battery and associated power circuitry), etc.

[0149] In some embodiments, a computer program is provided that includes instructions that, when executed by at least one processor, cause the at least one processor to perform the functions of the wireless communication device 1300 according to any of the embodiments described herein. According to some embodiments, a carrier is provided that carries the aforementioned computer program product. The carrier is one of an electrical signal, an optical signal, a radio signal, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0150] 14 is a schematic block diagram of a wireless communication device 1300 according to some other embodiments of the present disclosure. The wireless communication device 1300 includes one or more modules 1400, each of which is implemented in software. The module(s) 1400 provide the functionality of the wireless communication device 1300 described herein (e.g., the functionality of the wireless communication device 312 or UE described herein).

[0151] With reference to FIG. 15, according to one embodiment, a communication system includes a telecommunications network 1500, such as a 3GPP type cellular network, having an access network 1502, such as a RAN, and a core network 1504. The access network 1502 includes a number of base stations 1506A, 1506B, 1506C, such as Node Bs, eNBs, gNBs, or other types of wireless access points (APs), each defining a corresponding coverage area 1508A, 1508B, 1508C. Each of the base stations 1506a, 1506b, 1506c can be connected to the core network 1504 via a wired or wireless connection 1510. A first UE 1512 located in the coverage area 1508c is configured to be wirelessly connected or paged with the corresponding base station 1506c. A second UE 1514 in the coverage area 1508a can be wirelessly connected to the corresponding base station 1506a. Although multiple UEs 1512, 1514 are shown in this example, the disclosed embodiments are equally applicable to situations where a single UE is present within the coverage area and is connected to a corresponding base station 1506.

[0152] The telecommunications network 1500 is itself connected to a host computer 1516, which may be embodied in hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as processing resources in a server farm. The host computer 1516 may be under the ownership or control of a service provider, or may be operated by or on behalf of the service provider. The connections 1518 and 1520 between the telecommunications network 1500 and the host computer 1516 may extend directly from the core network 1504 to the host computer 1516, or may go through any intermediate network 1522. The intermediate network 1522 may be one or a combination of a public, private, or hosted network, if any, the intermediate network 1522 may be a backbone network or the Internet, and in particular the intermediate network 1522 may include two or more sub-networks (not shown).

[0153] The communication system of FIG. 15 generally provides connectivity between connected UEs 1512, 1514 and a host computer 1516. The connectivity may be described as an over-the-top (OTT) connection 1524. The host computer 1516 and connected UEs 1512, 1514 are configured to communicate data and / or signaling via the OTT connection 1524 using the access network 1502, the core network 1504, any intermediate networks 1522, and further infrastructure (not shown) that may be considered as intermediaries. The OTT connection 1524 may be transparent in the sense that participating communication devices are unaware of the routing of uplink and downlink communications through which the OTT connection 1524 passes. For example, the base station 1506 does not need to be informed about the past routing of incoming downlink communications having data originating from the host computer 1516 to be forwarded (e.g., handed over) to the connected UE 1512. Similarly, the base station 1506 does not need to be aware of the future routing of outgoing uplink communications from the UE 1512 to the host computer 1516.

[0154] Now, with reference to FIG. 16, an exemplary embodiment according to the UE, base station, and host computer embodiments discussed in the previous paragraph will be described. In the communication system 1600, the host computer 1602 has hardware 1604 including a communication interface 1606 configured to set up and maintain a wired or wireless connection with an interface of another communication device of the communication system 1600. The host computer 1602 further has a processing circuit 1608 that may have storage and / or processing capabilities. In particular, the processing circuit 1608 may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The host computer 1602 further has software 1610, which is stored in or accessible to the host computer 1602 and executable by the processing circuit 1608. The software 1610 has a host application 1612. The host application 1612 may be operable to provide services to a remote user, such as the UE 1614, connecting via an OTT connection 1616 terminated at the UE 1614 and the host computer 1602. In providing services to the remote user, the host application 1612 may provide user data that is transmitted using the OTT connection 1616.

[0155] The communication system 1600 further includes a base station 1618 having hardware 1620 disposed within the communication system to enable communication with the host computer 1602 and the UE 1614. The hardware 1620 may include a communication interface 1622 for setting up and maintaining a wired or wireless connection with an interface of another communication device of the communication system 1600, as well as a wireless interface 1624 for setting up and maintaining at least a wireless connection 1626 with a UE 1614 located in a coverage area (not shown in FIG. 16) served by the base station 1618. The communication interface 1622 may be configured to facilitate a connection 1628 to the host computer 1602. The connection 1628 may be direct, may pass through a core network (not shown in FIG. 16) of the communication system, and / or may pass through one or more intermediate networks external to the communication system. According to the illustrated embodiment, the hardware 1620 of the base station 1618 further includes processing circuitry 1630, which may include one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. Additionally, the base station 1618 includes software 1632 stored internally or accessible via an external connection.

[0156] The communication system 1600 further comprises the UE 1614 already mentioned. The hardware 1634 of the UE 1614 may comprise a wireless interface 1636 configured to set up and maintain a wireless connection 1626 with a base station serving the coverage area in which the UE 1614 is currently located. The hardware 1634 of the UE 1614 further comprises a processing circuit 1638 which may comprise one or more programmable processors, ASICs, FPGAs, or combinations thereof (not shown) adapted to execute instructions. The UE 1614 further comprises software 1640 which may be stored or accessible within the UE 1614 and which may be executable by the processing circuit 1638. The software 1640 comprises a client application 1642. The client application 1642, with the support of the host computer 1602, is operable to provide services to a human or non-human user via the UE 1614. In the host computer 1602, an executing host application 1612 may communicate with an executing client application 1642 via an OTT connection 1616 terminating at the UE 1614 and the host computer 1602. In providing services to a user, the client application 1642 may receive request data from the host application 1612 and provide user data in response to the request data. The OTT connection 1616 may carry both the request data and the user data. The client application 1642 may interact with the user and generate the user data provided by the user.

[0157] It should be noted that the host computer 1602, base station 1618, and UE 1614 shown in Figure 16 may be similar to or identical to the host computer 1516, one of the base stations 1506A, 1506B, 1506C, and one of the UEs 1512, 1514 of Figure 15, respectively. That is, the internal operation of these entities may be as shown in Figure 16 or may be independent therefrom, and the surrounding network topology may be that of Figure 15.

[0158] 16, the OTT connection 1616 is depicted abstractly to show communication between the host computer 1602 and the UE 1614 via the base station 1618, and the exact routing of messages through these devices, without explicitly referencing any intermediate devices. The network infrastructure may make routing decisions that may be configured to be hidden from the UE 1614, or from the service provider that operates the host computer 1602, or both. While the OTT connection 1616 is active, the network infrastructure may further make decisions to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0159] The wireless connection 1626 between the UE 1614 and the base station 1618 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 1614 using the OTT connection 1616 of which the wireless connection 1626 forms the final leg.

[0160] Measurement procedures may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve. Additionally, there may be optional network functionality for reconfiguring the OTT connection 1616 between the host computer 1602 and the terminal 1614 in response to variances in the measurement results. The measurement procedures and / or network functionality for reconfiguring the OTT connection 1616 may be implemented in the software 1610 and hardware 1604 of the host computer 1602, or in the software 1640 and hardware 1634 of the UE 1614, or both. In some embodiments, sensors (not shown) may be deployed in or associated with the communication devices through which the OTT connection 1616 passes, and the sensors may participate in the measurement procedures by providing values ​​of the monitored quantities exemplified above, or by providing values ​​of other physical quantities, from which the software 1610, 1640 may calculate or estimate the monitored quantities. Reconfiguration of the OTT connection 1616 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 1618 and may be unknown or imperceptible to the base station 1618. Such procedures and functionality may be known and practiced in the art. According to some embodiments, measurements may have unique UE signaling that facilitates measurements of the host computer 1602 throughput, propagation time, latency, etc. Measurements may be implemented in that the software 1610 and 1640 causes the OTT connection 1616 to send messages, particularly empty or "dummy" messages, while monitoring propagation times, errors, etc.

[0161] FIG. 17 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described in connection with FIG. 15 and FIG. 16. To simplify the disclosure, only drawing references to FIG. 17 are included in this section. In step 1700 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1702, the UE provides user data. In sub-step 1704 (which may be optional) of step 1700, the UE provides the user data by executing a client application. In sub-step 1706 (which may be optional) of step 1702, the UE executes a client application that provides the user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from a user. Regardless of the particular manner in which the user data is provided, the UE begins transmitting the user data to the host computer in sub-step 1708 (which may be optional). In step 1710 of the method, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0162] FIG. 18 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described in connection with FIG. 15 and FIG. 16. To simplify the disclosure, only drawing references to FIG. 18 are included in this section. In step 1800 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. In step 1802 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1804 (which may be optional), the host computer receives the user data carried in a transmission initiated by the base station.

[0163] Any suitable step, method, feature, function, or benefit disclosed herein may be performed via one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may have one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory has program instructions for executing one or more communication and / or data communication protocols, as well as instructions for executing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional units to perform corresponding functions in accordance with one or more embodiments of the present disclosure.

[0164] Although the processes in the figures may indicate a particular order of operations performed by certain embodiments of the present disclosure, it is to be understood that such orders are exemplary (e.g., alternative embodiments may perform operations in different orders, combine certain operations, overlap certain operations, etc.).

[0165] Some exemplary embodiments of the present disclosure are as follows: Group A Embodiments

[0166] Embodiment 1: A method performed by a wireless communication device for uplink transmission to a cellular communication network, the method comprising: transmitting (808) one or more physical uplink shared channels (PUSCHs) to two or more transmission / reception points (TRPs) of the cellular communication network on the same time and frequency domain resources or on the same time domain resources but different frequency domain resources, wherein the two or more TRPs are respectively associated with two or more different reference signals.

[0167] Embodiment 2: The method of embodiment 1, further comprising receiving (806) downlink control information from a network node (e.g., one of two or more TRPs) scheduling transmission of the one or more PUSCHs.

[0168]

[0023] Embodiment 3: The method of embodiment 1 and 2, wherein the downlink control information indicates the two or more reference signals.

[0169] Embodiment 4: The method according to embodiments 1 to 3, wherein the two or more reference signals are two or more downlink reference signals each associated with a TCI state.

[0170] Embodiment 4a: The method of embodiment 4, wherein each of the two or more downlink reference signals is an SSB or NZP CSI-RS.

[0171] Embodiment 5: The method of embodiments 1 to 3, wherein the two or more reference signals are two or more sounding reference signal (SRS) resources that are configured with a spatial relationship with each other.

[0172]

[0023] Embodiment 6: The method of embodiment 5, wherein the downlink control information includes one or more SRS resource indicators SRI indicating the two or more SRS resources.

[0173]

[0023] Embodiment 7: The method of embodiment 6, wherein each of the two or more SRS resources is associated with a respective reference signal via a spatial relationship configuration.

[0174] Embodiment 8: The method of embodiment 7, wherein each of the reference signals is an SSB, an NZP CSI-RS, or another SRS.

[0175] Embodiment 9: The method of embodiment 6, wherein the two or more SRS resources are associated with two or more reference signals, respectively, and the two or more reference signals are associated with two or more cell IDs, respectively (i.e., each of the reference signals is associated with a different cell ID).

[0176] Embodiment 10: The method of embodiment 9, wherein each of the two or more reference signals is each of two or more SSBs or each of two or more NZP CSI-RSs.

[0177]

[0033] Embodiment 11: The method of embodiment 9 or 10, wherein each of the two or more reference signals is associated with each of the two or more cell IDs via a field in a TCI state configuration.

[0178] Embodiment 12: The method of embodiment 9, wherein each of the two or more reference signals is a respective one of two or more SSBs, and the two or more reference signals are associated with each of the two or more cell IDs via an SSB configuration.

[0179] Embodiment 13: A method according to any one of embodiments 1 to 12, further comprising receiving (806) an indication via the one or more SRIs or the one or more TCI states indicating a path loss reference signal and a set of power control parameters for each of the one or more PUSCHs, wherein an association between an SRI or TCI state and one or more path loss reference signals and one or more sets of power control parameters is signaled to the wireless communication device.

[0180] Embodiment 14: A method according to any one of embodiments 6 to 12, further comprising: for each SRI in a set of SRIs including the one or more SRIs, or for each TCI state in a set of TCI states including the one or more TCI states, receiving information defining an association between the SRI or the TCI state and one or more path loss reference signals and one or more sets of power control parameters (802); and receiving an indication via the one or more SRIs or the one or more TCI states indicating a path loss reference signal and a set of power control parameters for each of the one or more PUSCHs (806).

[0181] Embodiment 15: The method of embodiment 13 or 14, wherein transmitting (808) the one or more PUSCHs to the two or more TRPs comprises transmitting (808) the one or more PUSCHs to the two or more TRPs according to the indicated set of power control parameters for each of the one or more PUSCHs.

[0182] Embodiment 16: The method according to any one of embodiments 5 to 15, wherein the two or more SRS resources belong to either the same SRS resource set or different SRS resource sets.

[0183] Embodiment 17: A method according to any one of embodiments 1 to 16, further comprising receiving (804) an indication from a network node (e.g., one of two or more TRPs) indicating the use of either a spatial division multiplexing scheme for multi-TRP PUSCH transmission or a frequency division multiplexing scheme for multi-TRP PUSCH transmission.

[0184] Embodiment 18: The method according to embodiment 17, wherein transmitting (808) the one or more PUSCHs to the two or more TRPs comprises transmitting (808) the one or more PUSCHs to the two or more TRPs on the same time and frequency domain resources if the received indication is an indication indicating the use of a spatial division multiplexing scheme for multi-TRP PUSCH transmission, or on the same time domain resources but different frequency domain resources if the received indication is an indication indicating the use of a frequency division multiplexing scheme for multi-TRP PUSCH transmission.

[0185] Embodiment 19: The method according to embodiment 1, wherein the one or more PUSCHs include two or more PUSCHs, and each PUSCH of the two or more PUSCHs is scheduled via separate downlink control information.

[0186] Embodiment 20: A method according to any one of embodiments 1 to 19, wherein the two or more TRPs are indicated in link control information via indication of two or more TCI states or two or more SRS resources, and each TRP is associated with one TCI state or one SRS resource.

[0187] Embodiment 21: A method of any of the previous embodiments, further comprising providing user data and transferring the user data to a host computer via transmitting one or more PUSCHs to two or more TRPs. Group B Embodiments

[0188] Embodiment 22: A method performed by a TRP, which is a transmission / reception point for a cellular communication network, comprising receiving (808-1) a first portion of a multi-TRP physical uplink shared channel (PUSCH) from a wireless communication device, the multi-TRP PUSCH transmission including one or more PUSCHs to two or more TRPs of the cellular communication network on the same time and frequency domain resources or on the same time domain resources but different frequency domain resources, the two or more TRPs being associated with two or more different reference signals, respectively.

[0189]

[0081] Embodiment 23: The method of embodiment 22, further comprising transmitting (806) downlink control information to the wireless communication device scheduling transmission of the one or more PUSCHs.

[0190] Embodiment 24: The method according to embodiments 22 and 23, wherein the downlink control information indicates the two or more reference signals.

[0191] Embodiment 25: The method according to any one of embodiments 22 to 24, wherein the two or more reference signals are two or more downlink reference signals respectively associated with a TCI state.

[0192] Embodiment 26: The method of any one of embodiments 22 to 24, wherein the two or more reference signals are two or more sounding reference signal (SRS) resources that are configured in a spatial relationship with each other.

[0193] Embodiment 27: The method of embodiment 26, wherein the downlink control information includes one or more SRS resource indicators (SRIs) indicating the two or more SRS resources.

[0194] Embodiment 28: The method of embodiment 27, wherein each of the two or more SRS resources is associated with a respective reference signal via a spatial relationship configuration.

[0195] Embodiment 29: The method according to embodiment 28, wherein the respective reference signals are SSB, NZP CSI-RS, or another SRS.

[0196] Embodiment 30: A method as described in embodiment 27, wherein the two or more SRS resources are associated with two or more reference signals, respectively, and the two or more reference signals are associated with two or more cell IDs, respectively (i.e., each of the reference signals is associated with a different cell ID).

[0197] Embodiment 31: The method of embodiment 30, wherein each of the two or more reference signals is each of two or more SSBs or each of two or more NZP CSI-RSs.

[0198] Embodiment 32: A method as described in embodiment 30 or 31, wherein each of the two or more reference signals is associated with each of the two or more cell IDs via a field in a TCI state configuration.

[0199] Embodiment 33: A method as described in embodiment 30, wherein each of the two or more reference signals is each of two or more SSBs, and the two or more reference signals are associated with each of the two or more cell IDs via an SSB configuration.

[0200] Embodiment 34: A method according to any one of embodiments 27 to 33, further comprising transmitting (806) to the wireless communication device an indication indicating a path loss reference signal and a set of power control parameters for each of the one or more PUSCHs via the one or more SRIs or one or more TCI states, wherein an association between an SRI or TCI state and one or more path loss reference signals and one or more sets of power control parameters is signaled to the wireless communication device.

[0201] Embodiment 35: A method according to any one of embodiments 27 to 33, further comprising: for each SRI of a set of SRIs including the one or more SRIs, or for each TCI state of a set of TCI states including the one or more TCI states, transmitting (802) information to the wireless communication device defining an association between the SRI or the TCI state, one or more path loss reference signals, and one or more sets of power control parameters; and transmitting (806) an indication to the wireless communication device via the one or more SRIs or one or more TCI states, indicating a path loss reference signal and a set of power control parameters for each of the one or more PUSCHs.

[0202] Embodiment 36: The method according to any one of embodiments 26 to 35, wherein the two or more SRS resources belong to either the same SRS resource set or different SRS resource sets.

[0203] Embodiment 37: A method according to any one of embodiments 22 to 36, further comprising transmitting (804) an indication to the wireless communication device indicating the use of either a spatial division multiplexing scheme for multi-TRP PUSCH transmission or a frequency division multiplexing scheme for multi-TRP PUSCH transmission.

[0204] Embodiment 38: The method according to embodiment 22, wherein the one or more PUSCHs include two or more PUSCHs, and each PUSCH of the two or more PUSCHs is scheduled via separate downlink control information.

[0205] Embodiment 39: A method according to any one of embodiments 22 to 38, wherein the two or more TRPs are indicated in the downlink control information via an indication of two or more TCI states or two or more SRS resources, and each TRP is associated with one TCI state or one TCI resource.

[0206] Embodiment 40: A method according to any of the preceding embodiments, further comprising receiving user data from the wireless communication device via the first portion of the multi-TRP PUSCH transmission, and transferring the user data to a host computer. Group C Embodiments

[0207] Embodiment 41: A wireless communication device having a processing circuit configured to perform any of the steps of any of the embodiments of group A and a power supply circuit configured to supply power to the wireless communication device.

[0208] Embodiment 42: A TRP having a processing circuit configured to perform any of the steps of any of the embodiments of group B and a power supply circuit configured to provide power to the TRP.

[0209] Embodiment 43: A user equipment (UE) having an antenna configured to transmit and receive radio signals, a radio front-end circuit connected to the antenna and a processing circuit and configured to condition signals communicated between the antenna and the processing circuit, the processing circuit configured to perform any of the steps of any of the embodiments of Group A, an input interface connected to the processing circuit and configured to enable input of information to the UE to be processed by the processing circuit, an output interface connected to the processing circuit and configured to output information from the UE that has been processed by the processing circuit, and a storage battery connected to the processing circuit and configured to supply power to the UE.

[0210] Embodiment 44: A communications system including a host computer having a communications interface configured to receive user data derived from a multi-TRP PUSCH transmission from a user equipment (UE) to two or more TRPs, the UE having a radio interface and processing circuitry, the processing circuitry of the UE being configured to perform any of the steps of any of the embodiments of Group A.

[0211] Embodiment 45: The communication system of the previous embodiment, further comprising a UE.

[0212] Embodiment 46: The communication system of the two preceding embodiments, further comprising the two or more TRPs, each of the two or more TRPs having a radio interface configured to communicate with the UE and a communication interface configured to transfer user data carried by each portion of the multi-TRP PUSCH transmission from the UE to the TRP to a host computer.

[0213] Embodiment 47: A communication system of the previous three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing the user data.

[0214] Embodiment 48: A communication system of the previous four embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, thereby providing requested data, and the processing circuitry of the UE is configured to execute a client application associated with the host application, thereby providing the user data in response to the requested data.

[0215] Embodiment 49: A method implemented in a communication system including a host computer, two or more TRPs, and a user equipment (UE), the method comprising receiving, at the host computer, user data transmitted from the UE to the two or more TRPs, the UE performing any of the steps of any of the embodiments of Group A.

[0216] Embodiment 50: The method of the previous embodiment, further comprising, in the UE, providing the user data to the two or more TRPs.

[0217] Embodiment 51: The method of the previous two embodiments, further comprising: executing a client application in the UE, thereby providing the user data to be transmitted; and executing a host application associated with the client application in the host computer.

[0218] Embodiment 52: A method of the previous three embodiments, further comprising executing a client application in the UE and receiving input data for the client application in the UE, the input data being provided in the host computer by executing a host application associated with the client application, and the user data to be transmitted being provided by the client application in response to the input data.

[0219] Embodiment 53: A communications system including a host computer having a communications interface configured to receive user data derived from a multi-TRP PUSCH transmission from a user equipment (UE) to two or more TRPs, each of the two or more TRPs having a radio interface and processing circuitry, the processing circuitry of the TRPs configured to perform any of the steps of any of the embodiments of Group B.

[0220] Embodiment 54: A communication system according to the above embodiment, further comprising the TRP.

[0221] Embodiment 55: The communication system of the preceding two embodiments, further comprising the UE, wherein the UE is configured to communicate with the two or more TRPs.

[0222] Embodiment 56: A communication system of the previous three embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and the UE is configured to execute a client application associated with the host application, thereby providing user data to be received by the host computer.

[0223] Embodiment 57: A method implemented in a communication system including a host computer, two or more TRPs, and a user equipment (UE), the method comprising: receiving, at the host computer, user data from the two or more TRPs originating from a multi-TRP PUSCH transmission received by the two or more TRPs from the UE, the UE performing any of the steps of any of the embodiments of Group A.

[0224] Embodiment 58: The method of any preceding embodiment, further comprising receiving the user data from the UE in the two or more TRPs.

[0225] Embodiment 59: The method of the previous two embodiments, further comprising initiating, in the two or more TRPs, transmission of the received user data to the host computer.

[0226] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure, and all such improvements and modifications are deemed to be within the scope of the concepts disclosed herein.

Claims

1. A method performed by a wireless communication device (312), the method comprising: receiving from a network node a configuration of first and second sounding reference signal (SRS) resource sets, each SRS resource set having one or more uplink SRS resources; wherein the first and second SRS resource sets are associated with first and second transmission / reception points (TRPs), respectively; receiving (904B) downlink control information (DCI) from the network node scheduling a first physical uplink channel transmission associated with a first SRS resource in the first SRS resource set and a second physical uplink channel transmission associated with a second SRS resource in the second SRS resource set, where the first and second SRS resources are indicated in the DCI; Transmitting the first and second physical uplink channel transmission signals in accordance with the DCI (906B), where the first and second physical uplink channel transmission signals are transmitted concurrently within the same time domain resource to the first and second TRPs, respectively, and the first and second physical uplink channel transmission signals are (a) (SDM) first and second layers of the same physical uplink channel; (b) (FDM-A) first and second portions of the same physical uplink channel, the first portion being transmitted on resources in a first frequency domain and the second portion being transmitted on resources in a second frequency domain; (c) (FDM-B) first and second physical uplink channels, the first physical uplink channel transmitted on resources of a first frequency domain and the second physical uplink channel transmitted on resources of a second frequency domain; and (d) (retransmission) first and second physical uplink channels associated with the same data transport block, the first physical uplink channel being encoded with a first redundancy version and the second physical uplink channel being encoded with a second redundancy version; How you can become one of them.

2. 2. The method of claim 1, wherein the first and second SRS resources are indicated in first and second SRS resource indicator (SRI) fields, respectively, in the DCI.

3. 3. The method of claim 2, wherein the first and second SRI fields are associated with the first and second SRS resource sets, respectively.

4. 4. The method of claim 1, further comprising receiving configurations of first and second sets of power control parameters associated with the first and second SRS resources, respectively, each of the first and second sets of power control parameters comprising a path loss reference signal, a fractional power control factor, a target received power, a closed loop power control index, or any combination thereof.

5. 5. The method of claim 4, wherein the first and second physical uplink channel transmission signals are transmitted at first and second transmit powers, respectively, the first and second transmit powers being calculated based on the first and second sets of power control parameters, respectively.

6. 6. The method of claim 1, wherein the first and second physical uplink channel transmission signals are Physical Uplink Shared Channel (PUSCH) transmission signals.

7. 3. The method of claim 2, wherein a set of possible code points for each of the first and second SRI fields in the DCI comprises a code point for indicating that a corresponding SRS resource is not selected.

8. 8. The method of claim 1, wherein the DCI further indicates first and second transmit power control (TPC) commands for the first and second physical uplink channel transmission signals, respectively.

9. 9. The method of claim 1, wherein the first and second SRS resources indicated in the DCI may be replaced with first and second uplink transmission configuration indicator (TCI) states, each of the first and second TCI states having a reference signal index for spatial relationship indication, a path loss reference signal index, a set of power control parameters, or any combination thereof.

10. A wireless communication device (312), receiving (902B) from a network node a configuration of first and second sounding reference signal (SRS) resource sets, each SRS resource set having one or more uplink SRS resources, where the first and second SRS resource sets are associated with first and second transmission / reception points (TRPs), respectively; receive (904B) from the network node downlink control information (DCI) scheduling a first physical uplink channel transmission signal associated with a first SRS resource in the first SRS resource set and a second physical uplink channel transmission signal associated with a second SRS resource in the second SRS resource set, where the first and second SRS resources are indicated in the DCI; transmitting the first and second physical uplink channel transmission signals in accordance with the DCI (906B); The first and second physical uplink channel transmission signals are transmitted simultaneously in the same time domain resource to the first and second TRPs, respectively, and the first and second physical uplink channel transmission signals are adapted to: (a) (SDM) first and second layers of the same physical uplink channel; (b) (FDM-A) first and second portions of the same physical uplink channel, the first portion being transmitted on resources in a first frequency domain and the second portion being transmitted on resources in a second frequency domain; (c) (FDM-B) first and second physical uplink channels, the first physical uplink channel transmitted on resources of a first frequency domain and the second physical uplink channel transmitted on resources of a second frequency domain; and (d) (retransmission) first and second physical uplink channels associated with the same data transport block, the first physical uplink channel being encoded with a first redundancy version and the second physical uplink channel being encoded with a second redundancy version; The wireless communication device may be one of:

11. A wireless communication device (312) according to claim 10, wherein said wireless communication device (312) is further adapted to perform the method according to any one of claims 2 to 9.

12. A wireless communication device (312; 1300), one or more transmitters (1308); one or more receivers (1310); a processing circuit (1302) associated with the one or more transmitters (1308) and the one or more receivers (1310), the processing circuit (1302) configured to transmit to the wireless communication device (312; 1300): o receiving (902B) from a network node a configuration of first and second Sounding Reference Signal (SRS) resource sets, each SRS resource set having one or more uplink SRS resources, where the first and second SRS resource sets are associated with first and second Transmission / Reception Points (TRPs), respectively; o receiving from the network node Downlink Control Information (DCI) scheduling a first physical uplink channel transmission associated with a first SRS resource in the first SRS resource set and a second physical uplink channel transmission associated with a second SRS resource in the second SRS resource set (904B), where the first and second SRS resources are indicated in the DCI; o causing (906B) the first and second physical uplink channel transmissions to be transmitted in accordance with the DCI; wherein the first and second physical uplink channel transmission signals are transmitted simultaneously in the same time domain resource to the first TRP and the second TRP, respectively, and the first and second physical uplink channel transmission signals are configured to: (a) (SDM) first and second layers of the same physical uplink channel; (b) (FDM-A) first and second portions of the same physical uplink channel, the first portion being transmitted on resources in a first frequency domain and the second portion being transmitted on resources in a second frequency domain; (c) (FDM-B) first and second physical uplink channels, the first physical uplink channel transmitted on resources of a first frequency domain and the second physical uplink channel transmitted on resources of a second frequency domain; and (d) (retransmission) first and second physical uplink channels associated with the same data transport block, the first physical uplink channel being encoded with a first redundancy version and the second physical uplink channel being encoded with a second redundancy version; The wireless communication device may be one of:

13. 13. The wireless communication device (312; 1300) of claim 12, wherein the first and second SRS resources are indicated in first and second SRS resource indicator (SRI) fields, respectively, in the DCI.

14. 14. The wireless communication device (312; 1300) of claim 13, wherein the first and second SRI fields are associated with the first and second SRS resource sets, respectively.

15. 15. The wireless communication device (312; 1300) of any one of claims 12 to 14, wherein the processing circuitry is further configured to cause the wireless communication device (312; 1300) to receive configurations of first and second sets of power control parameters associated with the first and second SRS resources, respectively, each of the first and second sets of power control parameters having a path loss reference signal, a fractional power control factor, a target received power, a closed loop power control index, or any combination thereof.

16. 16. The wireless communication device (312; 1300) of claim 15, wherein the first and second physical uplink channel transmission signals are transmitted at first and second transmit powers, respectively, and the first and second transmit powers are calculated based on the first and second sets of power control parameters, respectively.

17. 17. A wireless communication device (312; 1300) according to any one of claims 12 to 16, wherein the first and second physical uplink channel transmission signals are Physical Uplink Shared Channel (PUSCH) transmission signals.

18. 14. The wireless communication device (312; 1300) of claim 13, wherein a set of possible code points for each of the first and second SRI fields in the DCI includes a code point for indicating that a corresponding SRS resource is not selected.

19. 19. A wireless communication device (312; 1300) according to any one of claims 12 to 18, wherein the DCI further indicates first and second transmit power control (TPC) commands for the first and second physical uplink channel transmission signals, respectively.

20. 20. A wireless communication device (312; 1300) according to any one of claims 12 to 19, wherein the first and second SRS resources indicated in the DCI are replaced with first and second uplink transmission configuration indicator (TCI) states, each of the first and second TCI states having a reference signal index for spatial relationship indication, a path loss reference signal index, a set of power control parameters, or any combination thereof.

21. 1. A method performed by a network node, the method comprising: transmitting (902B) to a wireless communication device (312) a configuration of two sounding reference signal (SRS) resource sets, first and second SRS resource sets, each having one or more uplink SRS resources, where the first and second SRS resource sets are associated with first and second transmission / reception points (TRPs), respectively; transmitting, to the wireless communication device (312), downlink control information (DCI) scheduling a first physical uplink channel transmission associated with a first SRS resource in the first SRS resource set and a second physical uplink channel transmission associated with a second SRS resource in the second SRS resource set; the first and second SRS resources are indicated in the DCI, and the first and second physical uplink channel transmission signals include (a) (SDM) first and second layers of the same physical uplink channel; (b) (FDM-A) first and second portions of the same physical uplink channel, the first portion being transmitted on resources in a first frequency domain and the second portion being transmitted on resources in a second frequency domain; (c) (FDM-B) first and second physical uplink channels, the first physical uplink channel transmitted on resources of a first frequency domain and the second physical uplink channel transmitted on resources of a second frequency domain; and (d) (retransmission) first and second physical uplink channels associated with the same data transport block, the first physical uplink channel being encoded with a first redundancy version and the second physical uplink channel being encoded with a second redundancy version; How you can become one of them.

22. 22. The method of claim 21, wherein the first and second SRS resources are indicated in first and second SRS resource indicator (SRI) fields, respectively, in the DCI.

23. 23. The method of claim 22, wherein the first and second SRI fields are associated with the first and second SRS resource sets, respectively.

24. 24. The method of any one of claims 21 to 23, further comprising transmitting to the wireless communication device (312) configurations of first and second sets of power control parameters associated with the first and second SRS resources, respectively, the power control parameters comprising a path loss reference signal, a fractional power control factor, a target received power, a closed loop power control index, or any combination thereof.

25. 25. The method of claim 24, wherein the first and second physical uplink channel transmission signals are transmitted at first and second transmit powers, respectively, the first and second transmit powers being calculated based on the first and second sets of power control parameters, respectively.

26. 26. The method of any one of claims 21 to 25, wherein the first and second physical uplink channel transmission signals are physical uplink shared channel (PUSCH) transmission signals.

27. 23. The method of claim 22, wherein a set of possible code points for each of the first and second SRI fields in the DCI includes a code point to indicate that a corresponding SRS resource is not selected.

28. 28. The method of claim 21, wherein the DCI further indicates first and second transmit power control (TPC) commands for the first and second physical uplink channel transmission signals, respectively.

29. 29. The method of any one of claims 21 to 28, wherein the first and second SRS resources indicated in the DCI are replaced with first and second uplink transmission configuration indicator (TCI) states, each of the first and second TCI states including a reference signal index for a spatial relationship indication, a path loss reference signal index, a set of power control parameters, or any combination thereof.

30. A network node, transmitting (902B) to the wireless communication device (312) a configuration of first and second sounding reference signal (SRS) resource sets, each SRS resource set having one or more uplink SRS resources, where the first and second SRS resource sets are associated with first and second transmission / reception points (TRPs), respectively; transmit (904B) downlink control information (DCI) to the wireless communication device (312) scheduling a first physical uplink channel transmission signal associated with a first SRS resource in the first SRS resource set and a second physical uplink channel transmission signal associated with a second SRS resource in the second SRS resource set, where the first and second SRS resources are indicated in the DCI; receiving (906B) the first and second physical uplink channel transmissions from the wireless communication device (312) in accordance with the DCI; wherein the first and second physical uplink channel transmission signals are transmitted concurrently within the same time domain resource to the first and second TRPs, respectively, and the first and second physical uplink channel transmission signals are adapted to: (a) (SDM) first and second layers of the same physical uplink channel; (b) (FDM-A) first and second portions of the same physical uplink channel, the first portion being transmitted on resources in a first frequency domain and the second portion being transmitted on resources in a second frequency domain; (c) (FDM-B) first and second physical uplink channels, the first physical uplink channel transmitted on resources of a first frequency domain and the second physical uplink channel transmitted on resources of a second frequency domain; and (d) (retransmission) first and second physical uplink channels associated with the same data transport block, the first physical uplink channel being encoded with a first redundancy version and the second physical uplink channel being encoded with a second redundancy version; A network node can be one of:

31. 31. A network node according to claim 30, wherein the network node is further adapted to perform a method according to any one of claims 22 to 29.

32. A network node including a processing circuit (1004; 1104), the processing circuit providing the network node with: and causing a wireless communication device (312) to transmit (902B) configurations of first and second sounding reference signal (SRS) resource sets, each SRS resource set having one or more uplink SRS resources, wherein the first and second SRS resource sets are associated with first and second transmission / reception points (TRPs), respectively; transmitting (904B) to the wireless communication device (312) downlink control information (DCI) scheduling a first physical uplink channel transmission signal associated with a first SRS resource in the first SRS resource set and a second physical uplink channel transmission signal associated with a second SRS resource in the second SRS resource set, where the first and second SRS resources are indicated in the DCI; receiving (906B) the first and second physical uplink channel transmissions from the wireless communication device (312) in accordance with the DCI; wherein the first and second physical uplink channel transmission signals are transmitted concurrently within the same time domain resource to the first and second TRPs, respectively, and the first and second physical uplink channel transmission signals are adapted to: (a) (SDM) first and second layers of the same physical uplink channel; (b) (FDM-A) first and second portions of the same physical uplink channel, the first portion being transmitted on resources in a first frequency domain and the second portion being transmitted on resources in a second frequency domain; (c) (FDM-B) first and second physical uplink channels, the first physical uplink channel transmitted on resources of a first frequency domain and the second physical uplink channel transmitted on resources of a second frequency domain; and (d) (retransmission) first and second physical uplink channels associated with the same data transport block, the first physical uplink channel being encoded with a first redundancy version and the second physical uplink channel being encoded with a second redundancy version; A network node can be one of:

33. A network node according to claim 32, wherein the processing circuit (1004; 1104) is further configured to cause the network node to perform a method according to any one of claims 22 to 29.

34. 1. A method performed by a wireless communication device (312) for uplink transmission to a cellular communication network, the method comprising: receiving (806) an indication of a path loss reference signal and a set of power control parameters associated with each of two or more transmission configuration indicator (TCI) states via one or more sounding reference signal (SRS) resource indicators (SRIs) included in downlink control information (DCI) scheduling one or more physical uplink shared channels (PUSCHs); wherein an association between each of the one or more SRIs and the one or more path loss reference signals and one or more sets of power control parameters is signaled to the wireless communication device (312); and transmitting (808) one or more PUSCHs on either (a) the same time and frequency domain resources, or (b) the same time domain resources but different frequency domain resources according to two or more TCI states, wherein transmitting (808) the one or more PUSCHs comprises: transmitting (808-1) a first portion of the one or more PUSCHs to a first transmission / reception point (TRP) using a first TCI state from the two or more TCI states; transmitting a second portion of the one or more PUSCHs to a second TRP using a second TCI state from among the two or more TCI states (808-2); The method, wherein the two or more TCI states are respectively associated with two or more different reference signals.

35. 35. The method of claim 34, further comprising receiving (806) downlink control information from a network node scheduling transmission of the one or more PUSCHs, the downlink control information indicating the two or more TCI states.

36. 35. The method of claim 34, wherein the downlink control information includes one or more SRS resource indicators (SRIs) that indicate two or more uplink SRS resources.

37. 37. The method of claim 36, wherein each of the two or more uplink SRS resources is associated with a particular reference signal via a spatial relationship configuration.

38. 38. The method of claim 37, wherein the particular reference signal is a synchronization signal block (SSB), a non-zero power (NZP) channel state information reference signal (CSI-RS), or another SRS.

39. 37. The method of claim 36, the two or more uplink SRS resources are associated with two or more respective reference signals; each of the two or more reference signals being associated with a respective one of two or more cell identities; method.

40. 40. The method of claim 39, wherein each of the two or more reference signals is a respective one of two or more synchronization signal blocks (SSBs) or a respective one of two or more non-zero power (NZP) channel state information reference signals (CSI-RSs).

41. 41. A method according to claim 39 or 40, wherein each of the two or more reference signals is associated with a respective one of the two or more cell identities via a field in a TCI state configuration.

42. 40. The method of claim 39, wherein each of the two or more reference signals is a respective one of two or more synchronization signal blocks (SSBs), and the two or more reference signals are associated with each of the two or more cell identities via an SSB configuration.

43. 35. The method of claim 34, wherein transmitting (808-1) the first portions of the one or more PUSCHs comprises transmitting (808-1) the first portions of the one or more PUSCHs in accordance with the set of power control parameters associated with the first TCI state, and transmitting (808-2) the second portions of the one or more PUSCHs comprises transmitting (808-2) the second portions of the one or more PUSCHs in accordance with the set of power control parameters associated with the second TCI state.

44. 44. The method according to any one of claims 34 to 43, further comprising receiving (804) an indication from a network node to use either a spatial division multiplexing scheme for PUSCH transmission or a frequency division multiplexing scheme for PUSCH transmission.

45. 45. The method of claim 44, wherein transmitting (808) the one or more PUSCHs comprises transmitting (808) the one or more PUSCHs on a same time and frequency domain resource if the received indication is an indication to use the spatial division multiplexing scheme for PUSCH transmission, and on a same time domain resource but different frequency domain resource if the received indication is an indication to use the frequency division multiplexing scheme for PUSCH transmission.

46. 35. The method of claim 34, wherein the one or more PUSCHs include two or more PUSCHs, each PUSCH of the two or more PUSCHs being scheduled via separate downlink control information.

Images