Method and apparatus for simultaneous transmission to multiple transmission and reception points (TRPs)

Abstract

Disclosed herein are systems and methods related to multi-transmission / reception point (TRP) uplink transmissions in a cellular communications system. In one embodiment, a method performed by a wireless communications 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 SRS resource set including one or more SRS resources. The method further includes receiving, from the network node, a downlink control information (DCI) that schedules a physical uplink channel transmission, the physical uplink channel transmission including a first portion associated to a first SRS resource in the first SRS resource set and a second portion associated to a second SRS resource in the second SRS resource set, where the first and second SRS resources are indicated in the DCI. The method further includes transmitting the physical uplink channel transmission in accordance with the DCI.

Description

[0001] Related applications

[0002] This application claims the benefit of provisional patent application serial number 63 / 011,707, filed on April 17, 2020, the disclosure of which is hereby incorporated herein by reference in its entirety. Technical Field

[0003] This disclosure relates to uplink transmissions at multiple transmit and receive points (TRPs) in a cellular communication system. Background Technology

[0004] The next generation of mobile wireless communication systems (5G), or New Radio (NR), will support a wide range of use cases and deployment scenarios. The latter includes deployments at low frequencies (i.e., frequencies below 6 GHz) and very high frequencies (i.e., frequencies up to tens of GHz).

[0005] 1NR framework structure and resource grid

[0006] 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 the uplink (UL) (i.e., from the UE to the gNB). Discrete Fourier Transform (DFT) Extended Orthogonal Frequency Division Multiplexing (OFDM) is also supported in the uplink. In the time domain, NR downlink and uplink are organized into equal-sized subframes of 1 millisecond (ms). These subframes are further divided into multiple time slots of equal duration. The time slot length depends on the subcarrier spacing. For Δ... f = 15 kHz subcarrier spacing, with only one time slot per subframe, and each time slot consists of 14 OFDM symbols.

[0007] In NR, data scheduling is typically based on time slots. Figure 1 The example shown is a 14-symbol time slot for a 15 kHz subcarrier spacing, where the first two symbols contain the Physical Downlink Control Channel (PDCCH) and the remaining symbols contain the Physical Shared Data Channel, i.e., the Physical Downlink Shared Channel (PDSCH) or the Physical Uplink Shared Channel (PUSCH).

[0008] NR supports different subcarrier spacing values. The supported subcarrier spacing values ​​(also known as different parameter sets) are determined by... Given, where . This is the basic subcarrier spacing. The time slot duration for different subcarrier spacings is determined by... ms is given.

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

[0010] In NR Release 15, UL data transmission can be dynamically scheduled via UL grants contained 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 the Physical Uplink Shared Channel (PUSCH) based on the control information decoded in the UL grant (such as modulation order, coding rate, uplink resource allocation, etc.). NR Release 16 supports three DCI formats: DCI format 0_0, DCI format 0_1, and DCI format 0_2. Each DCI contains multiple bit fields, each conveying certain information, including:

[0011] • Bandwidth indicator

[0012] • Time-Domain Resource Allocation (TDRA)

[0013] • Frequency Domain Resource Allocation (FDRA)

[0014] • Modulation and coding scheme (MCS)

[0015] • Hybrid Automatic Repeat Request (HARQ) process number

[0016] • New data indicator

[0017] • Redundant Version (RV)

[0018] • Detect Resource Indicator (SRI)

[0019] • Precoding information and number of layers

[0020] • Antenna port

[0021] • Detection Reference Signal (SRS) request, etc.

[0022] • Channel State Information (CSI) Request

[0023] • Phase Tracking Reference Signal (PTRS) - Demodulation Reference Signal (DMRS) Correlation (i.e., PTRS-DMRS)

[0024] • Transmission Power Control (TPC) command for scheduled PUSCH

[0025] In addition to dynamic scheduling of PUSCH, it is also possible to configure semi-persistent PUSCH transmissions using configured permission (CG). Two types of CG-based PUSCH exist, defined in NR Release 15, referred to as CG Type 1 and CG Type 2. In CG Type 1, the periodicity of PUSCH transmissions, as well as the start and stop of such transmissions, are configured by Radio Resource Control (RRC). In CG Type 2, the periodicity of PUSCH transmissions is configured by RRC, and then the start and stop of such transmissions are controlled by DCI (i.e., using PDCCH).

[0026] In NR, it is possible to schedule PUSCHs using time repetition via the RRC parameter pusch-AggregationFactor for dynamically scheduled PUSCHs and via repK for permitted PUSCHs with UL configuration. In this case, the PUSCH is scheduled but transmitted in multiple adjacent time slots until the number of repetitions determined by the configured RRC parameters has been transmitted.

[0027] In the case of a permitted PUSCH with UL configuration, when used repeatedly, by repK-RV The field configures the RV sequence to be used. If no duplicates are used for permitted PUSCHs with UL configuration, then... repK-RV The field does not exist.

[0028] In NR Release 15, two mapping types are supported for PUSCH transports. These two mapping types are referred to as Type A and Type B. Type A PUSCH transports are generally referred to as slot-based transports, while Type B PUSCH transports can be referred to as non-slot-based transports or mini-slot-based transports. Mini-slot transports can be dynamically scheduled, and for NR Release 15:

[0029] • Downlinks can have lengths of 7, 4, or 2 symbols, while uplinks can have any length, and

[0030] • It can start and end at any symbol within a time slot.

[0031] Note that mini-slot transmissions in NR version 15 do not need to cross slot boundaries.

[0032] 2PUSCH transmission scheme

[0033] In NR, there are two transmission schemes specified for PUSCH.

[0034] 2.1 Codebook-based PUSCH

[0035] If higher-level parameters txConfig = codebook If so, codebook-based PUSCH is enabled. For dynamically scheduled PUSCH and configured permitted PUSCH type 2, the codebook-based PUSCH transmission scheme can be summarized as follows:

[0036] • The UE transmits SRS in one or two configured SRS resources. (This refers to the transmission of higher-layer parameters.) use 'Set as' CodeBook In the case of ', configure one or two SRS resources in the SRS resource set. Note that when ' use Set to " CodeBook In the case of "", only a single SRS resource set can be configured.

[0037] • The NR base station (gNB) determines the preferred precoder (i.e., the transmission precoder matrix indicator (TPMI)) from the codebook and the associated layer number corresponding to the SRS received from one or two SRS resources.

[0038] • If two SRS resources are configured in the SRS resource set, the gNB will use the 1-bit ' in the DCI of the scheduling PUSCH. SRS resource indicator The (SRI) field is used to indicate the selected SRS resource. If only one SRS resource is configured in the SRS resource set, it is not indicated in the DCI. SRS resource indicator 'Field'.

[0039] • The gNB also indicates the preferred TPMI corresponding to the indicated SRS resource (in the case of using two SRS resources) or the configured SRS resource (in the case of using one SRS resource), and the associated number of layers. The TPMI and the number of layers are specified in DCI formats 0_1 and 0_2. Precoding information and number of layers 'Field indication.'

[0040] • The UE uses the indicated TPMI and layer number to perform PUSCH transports. If an SRS resource is configured in the SRS resource set associated with the higher layer parameter 'Use' of the value 'CodeBook', then the PUSCH DMRS is spatially associated with the latest SRS transport in that SRS resource. If two SRS resources are configured in the SRS resource set associated with the higher layer parameter 'Use' of the value 'CodeBook', then the PUSCH DMRS is spatially associated with the latest SRS transport in that SRS resource. SRS resource indicator 'Related to the latest SRS transmission in the SRS resource indicated by the field.'

[0041] • The “Antenna Port” field in DCI indicates one or more DMRS ports associated with one or more layers and multiple CDM groups that are not multiplexed with PUSCH data.

[0042] 2.2 Non-codebook-based PUSCH

[0043] NR also supports non-codebook-based UL transmission to enable reciprocal UL transmission, where SRS precoding is derived at the UE based on the configured DL Channel State Information Reference Signal (CSI-RS). By assigning the DL CSI-RS to the UE, it can measure and infer appropriate precoder weights for SRS transmission to generate one or more (virtual) SRS ports, each corresponding to a spatial layer. The UE can be configured with up to four SRS resources in the SRS resource set, each with a single (virtual) SRS port. The UE can transmit SRS in these up to four SRS resources, and the gNB measures the UL channel based on the received SRS and determines one or more preferred SRS resources (or one or more SRS ports). Subsequently, the gNB indicates the selected SRS resource via an SRS Resource Indicator (SRI), where... The units digit is used to jointly encode the selected SRS resource, where Indicates the number of SRS resources configured, and This is the maximum number of layers supported by PUSCH. Note that only a single SRS resource set can be configured with a "non-codebook".

[0044] 3. Definition of Spatial Relationships

[0045] In NR, spatial relationships are used to refer to the relationship between UL signals or channels (such as PUCCH, PUSCH) and SRS and another reference signal (RS), which can be DL RS (e.g., CSI-RS, SSB (Synchronization Signal Block)) or ULRS (e.g., SRS). This is also defined from the UE's perspective.

[0046] If the UL signal or channel is spatially correlated with the DL RS, this means that the UE should transmit the UL signal or channel in the opposite (reciprocal) direction to the direction in which it previously received the DL RS. More precisely, the UE should apply the same transmit (TX) spatial filtering configuration as the receive (Rx) spatial filtering configuration it previously used to receive spatially correlated DL RS for transmitting the UL signal or channel. Here, the term 'spatial filtering configuration' can refer to the antenna weights applied at the transmitter or receiver for data / control transmission / reception. The DL RS is also known as the spatial filtering reference signal.

[0047] On the other hand, if the first UL signal or channel is spatially associated with the second UL RS, the UE should apply the same Tx spatial filtering configuration as it previously used to transmit the second UL RS for transmitting the first UL signal or channel.

[0048] For a codebook-based PUSCH scheme, the SRS resource set can contain up to two SRS resources. Each SRS resource can have 1, 2, or 4 SRS ports. Each SRS resource can be spatially associated with another RS ​​(e.g., an SSB, a non-zero power (NZP) CSI-RS, or another SRS) through spatial relationships. The spatial relationships of the PUSCH are given by the spatial transmission characteristics associated with the associated SRS resources.

[0049] For a non-codebook-based PUSCH scheme, an SRS resource set can contain up to four SRS resources, each with a single SRS port. Each SRS resource set is associated with a CSI-RS, through which the UE derives the SRS precoder for each SRS port. The spatial relationships of the PUSCH are given by the CSI-RS configured for the SRS resource set.

[0050] 4. Uplink TCI status

[0051] Several signals can be transmitted from different antenna ports of the same base station antenna. These signals can have the same large-scale properties, such as Doppler shift / spread, average delay spread, or average delay, when measured at the receiver. These antenna ports are thus called quasi-co-location (QCL).

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

[0053] In NR, four types of QCL relationships are defined between the source RS and the destination RS of a transmission:

[0054] • Type A: {Doppler shift, Doppler spread, mean delay, delay spread}

[0055] • Type B: {Doppler shift, Doppler extension}

[0056] • Type C: {mean delay, Doppler shift}

[0057] • Type D: {spatial Rx parameter}

[0058] QCL type D is introduced to facilitate beam management using analog beamforming, and it is called spatial QCL. Currently, there is no strict definition of spatial QCL, but the understanding is that if two transmitting antenna ports are in spatial QCL, the UE can use the same Rx beam to receive them. This helps the UE 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 the signal is in spatial QCL with some other signal it has previously received, then it can also safely use the same RX beam to receive that signal. Note that for beam management, the discussion mainly revolves around QCL type D, but it is also necessary to communicate the RS type A QCL relationship to the UE so that it can estimate all relevant large-scale parameters.

[0059] The network signals the UE to the UE via Transmit Configuration Indicator (TCI) states, informing them of what assumptions can be made regarding QCL. Each TCI state contains QCL information, namely one or two source DL RSs, each associated with a QCL type. For example, a TCI state may contain a pair of reference signals, each associated with a QCL type. For instance, in a TCI state, two distinct CSI-RSs {CSI-RS1, CSI-RS2} might be configured as {qcl-Type1, qcl-Type2} = {Type A, Type D}. This means the UE can derive Doppler shift, Doppler spread, average delay, and delay spread from CSI-RS1, and spatial Rx parameters (i.e., the Rx beam to be used) from CSI-RS2. In NR, TCI states are used for downlink channels and signaling.

[0060] In NR version 15, the handling of spatial transmission characteristics differs for PUSCH, PUCCH, and SRS. For PUCCH, the handling of spatial transmission characteristics differs in the information element. PUCCH - SpatialRelationInfo Spatial relationship information is configured in the configuration, and the spatial relationship information of the SRS 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(one or more) resources in the SRS resource set configured with 'Codebook' or 'non-Codebook'. This handling of spatial transmission characteristics is cumbersome and inflexible when it comes to uplink multi-panel transmissions in NR.

[0061] There are also suggestions to use a TCI state framework to indicate the spatial characteristics of all UL channels or signals (i.e., PUSCH, PUCCH, and SRS) in the uplink. The idea is that when the UE is equipped with multiple panels, the uplink TCI state is used to indicate one of the multiple uplink panels, and the corresponding transmission beam (i.e., transmission characteristics) is used at the UE to transmit the ULPUSCH / PUCCH / SRS. Each TCI state may contain a reference signal for spatial relationship indication, an RS for path loss estimation, and may contain a set of power control parameters.

[0062] Generally, the list of uplink TCI states can be configured for the UE by a higher layer (i.e., RRC). A subset can be activated by the Media Access Control (MAC) control element (CE). One of the active TCI states can be indicated for PUSCH in the DCI.

[0063] 5PUSCH power control

[0064] For each SRI, a pre-configured set of path loss RS and power control parameters (e.g., fractional power control coefficients, P0, closed-loop exponent) is sent to the UE. The PUSCH open-loop transmission power is then derived based on the SRI indicated in the DCI and the associated pre-configured set of path loss RS and power control parameters.

[0065] Closed-loop power control is performed by sending a Transmit Power Control Command (TPC) in the 2-bit "TPC Command for Scheduled PUSCH" field of the DCI that schedules the PUSCH. Table 1 shows the mapping between TPC values ​​and power correction, where the "Cumulative [dB]" column is used if the UE is configured with a cumulative mode, and the "Absolute" column is used otherwise.

[0066] Table 1: Mapping of TPC command fields to absolute and cumulative values ​​for DCI formats using scheduled PUSCH transmission, or DCI format 2_2 with CRC scrambled via TPC-PUSCH-RNTI, or DCI format 2_3.

[0067] TPC command fields Cumulative [dB] Absolutely [dB] 0 -1 -4 1 0 -1 2 1 1 3 3 4 Summary of the Invention

[0068] This document discloses systems and methods related to uplink transmission over multiple transmit / receive points (TRPs) in cellular communication systems. In one embodiment, a method performed by a wireless communication device includes receiving from a network node the configuration of two sounding reference signal (SRS) resource sets, namely first and second SRS resource sets, each SRS resource set including one or more SRS resources. The method further includes receiving from the network node downlink control information (DCI) scheduling physical uplink channel transmission, the 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, wherein the first and second SRS resources are indicated in the DCI. The method further includes transmitting the physical uplink channel transmission according to the DCI. In this way, robust uplink transmission can be provided over multiple TRPs.

[0069] In one embodiment, the first and second SRS resources are indicated in the first and second SRS Resource Indicator (SRI) fields of the DCI, respectively. In one embodiment, the first and second SRI fields are associated with the first and second SRS resource sets, respectively. In one embodiment, the possible set of code points for each SRI field in the first and second SRI fields of the DCI includes code points used to indicate that no corresponding SRS resource has been selected.

[0070] In one embodiment, the method further includes receiving configurations of first and second power control parameter sets respectively associated with first and second SRS resources, wherein each power control parameter set in the first and second power control parameter sets 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, first and second portions of a physical uplink channel transmission are transmitted using first and second transmit powers respectively, wherein the first and second transmit powers are calculated based on the first and second power control parameter sets respectively.

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

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

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

[0074] In one embodiment, the first and second portions of the physical uplink channel transmission are first and second PUSCHs that carry different redundant versions of the same transport block (TB) and are transmitted in different frequency domain resources.

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

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

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

[0078] In one embodiment, a wireless communication device includes one or more transmitters, one or more receivers, and processing circuitry associated with the one or more transmitters and one or more receivers. The processing circuitry is configured to cause the wireless communication device to receive from a network node a configuration of two SRS resource sets, each SRS resource set including one or more SRS resources. The processing circuitry is further configured to cause the wireless communication device to receive a Direct Access Control (DCI) from the network node, the DCI scheduling a physical uplink channel transmission including a first portion of a first SRS resource associated with a first SRS resource set and a second portion of a second SRS resource associated with a second SRS resource set, wherein the first and second SRS resources are indicated in the DCI. The processing circuitry is further configured to cause the wireless communication device to transmit the physical uplink channel transmission according to the DCI.

[0079] This document also discloses an embodiment of a method performed by a network node. In one embodiment, a method performed by a network node includes sending to a wireless communication device the configuration of two SRS resource sets, namely first and second SRS resource sets, each SRS resource set including one or more SRS resources. The method further includes sending to the wireless communication device a DCI that schedules physical uplink channel transmissions, the physical uplink channel transmissions including a first portion of first SRS resources associated with the first SRS resource set and a second portion of second SRS resources associated with the second SRS resource set, wherein the first and second SRS resources are indicated in the DCI.

[0080] A corresponding embodiment of a network node is also disclosed. In one embodiment, the network node is adapted to send to a wireless communication device a configuration of two SRS resource sets, namely first and second SRS resource sets, each SRS resource set including one or more SRS resources. The network node is further adapted to send to the wireless communication device a DCI that schedules physical uplink channel transmission, the physical uplink channel transmission including a first portion associated with the first SRS resources in the first SRS resource set and a second portion associated with the second SRS resources in the second SRS resource set, wherein the first and second SRS resources are indicated in the DCI.

[0081] In one embodiment, a network node includes processing circuitry configured to send configurations of two SRS resource sets, namely first and second SRS resource sets, to a wireless communication device, each SRS resource set including one or more SRS resources. The processing circuitry is further configured to send a DCI to the wireless communication device, the DCI scheduling physical uplink channel transmissions including a first portion of first SRS resources associated with the first SRS resource set and a second portion of second SRS resources associated with the second SRS resource set, wherein the first and second SRS resources are indicated in the DCI.

[0082] In one embodiment, a method performed by a wireless communication device for uplink transmission to a cellular communication network includes transmitting one or more PUSCHs using two or more Transmission Configuration Indicator (TCI) states on any of the following resources: (a) the same time-domain and frequency-domain resources; or (b) the same time-domain resources but different frequency-domain resources. The two or more TCI states are each associated with two or more different reference signals.

[0083] In one embodiment, the method further includes receiving downlink control information from a network node that schedules transmissions of one or more PUSCHs, wherein the downlink control information indicates two or more TCI states.

[0084] In one embodiment, the two or more reference signals are two or more downlink reference signals, each associated with a corresponding TCI state among 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).

[0085] In one embodiment, the two or more reference signals are two or more SRS resources each configured with a corresponding 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 corresponding reference signal through a spatial relationship configuration. In one embodiment, the corresponding reference signal is an SSB, an NZP CSI-RS, or another SRS.

[0086] In one embodiment, two or more SRS resources are associated with two or more corresponding reference signals, and the two or more corresponding reference signals are associated with two or more corresponding cell identifiers. In one embodiment, the two or more corresponding reference signals are two or more corresponding SSBs or two or more corresponding NZP CSI-RSs. In one embodiment, the two or more corresponding reference signals are associated with two or more corresponding cell identifiers via fields in the TCI state configuration.

[0087] In one embodiment, two or more corresponding reference signals are two or more corresponding SSBs, and the two or more reference signals are associated with two or more corresponding cell identifiers via SSB configuration.

[0088] In one embodiment, transmitting one or more PUSCHs includes: transmitting a first portion of the one or more PUSCHs using a first TCI state from two or more TCI states; and transmitting a second portion of the one or more PUSCHs using a second TCI state from the two or more TCI states. The method further includes receiving an indication of a path loss reference signal and a power control parameter set associated with each of the two or more TCI states via either: one or more SRIs in downlink control information scheduling one or more PUSCHs, wherein a signal is sent to a wireless communication device notifying each of the one or more SRIs of the association with one or more path loss reference signals and one or more power control parameter sets; or the two or more TCI states, wherein a signal is sent to a wireless communication device notifying each of the TCI states of the association with one or more path loss reference signals and one or more power control parameter sets. In one embodiment, transmitting a first portion of one or more PUSCHs includes transmitting a first portion of the one or more PUSCHs according to a power control parameter set associated with a first TCI state, and transmitting a second portion of the one or more PUSCHs includes transmitting a second portion of the one or more PUSCHs according to a power control parameter set associated with a second TCI state.

[0089] In one embodiment, the method further includes receiving from a network node an indication of using a spatial multiplexing scheme or a frequency multiplexing scheme for PUSCH transmission. In one embodiment, transmitting one or more PUSCHs includes: if the received indication is an indication of using a spatial multiplexing scheme for PUSCH transmission, transmitting the one or more PUSCHs on the same time and frequency domain resources; or if the received indication is an indication of using a frequency multiplexing scheme for PUSCH transmission, transmitting the one or more PUSCHs on the same time domain resources but on different frequency domain resources.

[0090] In one embodiment, one or more PUSCHs include two or more PUSCHs, and each of the two or more PUSCHs is scheduled via separate downlink control information. Attached Figure Description

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

[0092] Figure 1 An example of a typical time slot in the New Radio (NR) is shown;

[0093] Figure 2 The basic NR physical time-frequency resource grid is shown;

[0094] Figure 3 An example of a cellular communication system in which embodiments of the present disclosure may be implemented is shown;

[0095] Figure 4 An example is shown of a user equipment (UE) according to an embodiment of the present disclosure using spatial multiplexing (SDM) to transmit different layers of the physical uplink shared channel (PUSCH) to two transmit and receive points (TRPs);

[0096] Figure 5 An example of an embodiment according to this disclosure is shown, wherein the UE uses SDM to transmit two PUSCHs (PUSCH1 and PUSCH2) of the same transport block (TB) to two TRPs (TRP1 and TRP2).

[0097] Figure 6 An example of an embodiment according to this disclosure is shown, wherein the UE utilizes frequency domain multiplexing (FDM) to transmit a single PUSCH to two TRPs while allocating a portion of the frequency domain resources to each TRP;

[0098] Figure 7 An example of an embodiment according to this disclosure is shown, wherein the UE uses FDM to transmit two PUSCHs (PUSCH1 and PUSCH2) of the same TB to two TRPs (TRP1 and TRP2).

[0099] Figure 8 The operation of a wireless communication device (e.g., a UE) and two TRPs is illustrated according to at least some embodiments described herein;

[0100] Figure 9A and Figure 9B The operation of a wireless communication device (e.g., a UE) and two TRPs according to some other embodiments described herein is illustrated;

[0101] Figure 10 , Figure 11 and Figure 12 This is a schematic block diagram of an example embodiment of a network node;

[0102] Figure 13 and Figure 14 This is a schematic block diagram of an example embodiment of a wireless communication device;

[0103] Figure 15 Example embodiments of a communication system in which embodiments of the present disclosure may be implemented are shown;

[0104] Figure 16 Show Figure 15Example embodiments of the host computer, base station, and UE; and

[0105] Figure 17 and Figure 18 It is shown in such as Figure 15 A flowchart of an example embodiment of a method implemented in a communication system such as a communication system. Detailed Implementation

[0106] The embodiments described below represent information enabling those skilled in the art to practice the embodiments and illustrate the best mode for practicing the embodiments. Those skilled in the art will understand the concepts of this disclosure and recognize the application of these concepts unless specifically mentioned herein when reading the following description in conjunction with the accompanying drawings. It should be understood that these concepts and applications fall within the scope of this disclosure.

[0107] Some embodiments of the ideas contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the subject matter disclosed herein and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0108] Generally, unless a different meaning is explicitly given and / or implied in the context of the use of the term, all terms used herein shall be interpreted in accordance with their ordinary meaning in the relevant art. Unless otherwise expressly stated, all references to a (a / an) / element, device, component, part, step, etc. shall be openly interpreted as referring to at least one instance of an element, device, component, part, step, etc. Unless a step is explicitly described as occurring after or before another step and / or implied that a step must occur after or before another step, the steps of any method disclosed herein need not be performed in the exact order disclosed. Where appropriate, any feature of any embodiment of the embodiments disclosed herein may be applied to any other embodiment. Similarly, any advantage of any embodiment of the described embodiments may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the appended embodiments will become apparent from the following description.

[0109] Radio node: As used in this article, a “radio node” is a radio access node or wireless communication device.

[0110] Radio Access Node: As used herein, a “radio access node,” “radio network node,” or “radio access network node” is any node operating in the radio access network (RAN) of a cellular communication network to wirelessly transmit and / or receive signals. Some examples of radio access nodes include, but are not limited to: base stations (e.g., New Radio (NR) base stations (gNBs) in 3GPP 5G NR networks or enhanced or evolved Node Bs (eNBs) in 3GPP LTE networks), high-power or macro base stations, low-power base stations (e.g., micro base stations, pico base stations, home eNBs, or the like), relay nodes, network nodes that implement the functional part of a base station (e.g., network nodes that implement the gNB central unit (gNB-CU) or the gNB distributed unit (gNB-DU), or network nodes that implement the functional part of some other type of radio access node.

[0111] Core Network Node: As used herein, a “core network node” is any type of node in the core network or any node that implements core network functions. Some examples of core network nodes include, for example, a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Opening Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of core network nodes include nodes that implement Access and Mobility Management Functions (AMF), User Plane Functions (UPF), Session Management Functions (SMF), Authentication Server Functions (AUSF), Network Slice Selection Functions (NSSF), Network Opening Functions (NEF), Network Functions (NF) Repository Functions (NRF), Policy Control Functions (PCF), Unified Data Management (UDM), or the like.

[0112] Communication device: As used herein, a “communication device” is any type of device authorized to access a network. Some examples of communication devices include, but are not limited to: mobile phones, smartphones, sensor devices, instruments, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting fixtures, tablets, laptops, or personal computers (PCs). Communication devices can be portable, handheld, computer-integrated, or vehicle-mounted mobile devices enabled to transmit voice and / or data via wireless or wired connections.

[0113] Wireless communication device: One type of communication device is a wireless communication device, which can be any type of wireless device authorized to access a wireless network (e.g., a cellular network) (i.e., served by a wireless network). Some examples of wireless communication devices include, but are not limited to: User Equipment (UE) devices, Machine-Type Communication (MTC) devices, and Internet of Things (IoT) devices in 3GPP networks. Such wireless communication devices can be or can be integrated into mobile phones, smartphones, sensor devices, instruments, vehicles, home appliances, medical devices, media players, cameras, or any type of consumer electronics, such as, but not limited to, televisions, radios, lighting fixtures, tablets, laptops, or PCs. Wireless communication devices can be portable, handheld, computer-integrated, or vehicle-mounted mobile devices enabled to transmit voice and / or data via a wireless connection.

[0114] Network node: As used in this document, a “network node” is any node that is part of the RAN or core network of a cellular communication network / system.

[0115] Transmit / Receive Point (TRP): In some embodiments, a TRP can be a network node, a radio headend, a spatial relation, or a Transmission Configuration Indicator (TCI) state. In some embodiments, a TRP can be represented by a spatial relation or a TCI state. 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 / from a UE according to the physical layer characteristics and parameters inherent to the element. In some embodiments, in multiple TRP (multi-TRP) operation, the serving cell can schedule a UE from two TRPs to provide better Physical Downlink Shared Channel (PDSCH) coverage, reliability, and / or data rate. There are two different operating modes for multi-TRP: single downlink control information (DCI) and multi-DCI. In both modes, uplink and downlink operation control is performed by both the physical layer and Media Access Control (MAC). In single-DCI mode, the UE is scheduled through the same DCI for both TRPs, while in multi-DCI mode, the UE is scheduled through independent DCIs from each TRP.

[0116] In some embodiments, a set of transport points (TPs) is a cell, a portion of a cell, or a geographically co-located set of transport antennas (e.g., an antenna array (having one or more antenna elements) for a Location Reference Signal (PRS)-only TP. A TP may include base station (eNB) antennas, remote radio head ends (RRHs), remote antennas of a base station, PRS-only TP antennas, etc. A cell may be formed by one or more TPs. For homogeneous deployments, each TP may correspond to one cell.

[0117] In some embodiments, a TRP set is a geographically co-located set of antennas (e.g., an antenna array (with one or more antenna elements)) that supports the functionality of a TP and / or a receiver point (RP).

[0118] Note that the descriptions given herein focus on 3GPP cellular communication systems, and therefore, 3GPP terminology or similar terms are frequently used. However, the concepts disclosed herein are not limited to 3GPP systems.

[0119] Note that the term “cell” may be referenced in the description herein; however, in particular with respect to the 5G NR concept, beams may be used instead of cells, and therefore it is important to note that the concepts described herein apply equally to both cells and beams.

[0120] There are currently some challenges. For dynamically scheduled Physical Uplink Shared Channels (PUSCH) and configured permitted PUSCH Type 2 (i.e., PUSCH transmissions), the existing codebook-based PUSCH in NR Release 15 / 16 only allows a single Sounding Reference Signal (SRS) resource to be indicated in the Downlink Control Information (DCI) via the gNB, where the spatial relationships of the PUSCH are then defined using this single indicated SRS resource. For non-codebook-based PUSCH schemes, a single Channel State Information (CSI) Reference Signal (CSI-RS) is associated with a set of SRS resources, and the spatial relationships of the PUSCH are defined by the CSI-RS configured for the corresponding SRS resource set. Therefore, the existing NR Release 15 / 16 PUSCH is only suitable for transmissions based on a single Transmitter and Receiver Point (TRP), where the PUSCH transmission is directed to a single TRP. It is not suitable for transmitting PUSCH to multiple TRPs. Therefore, how to configure the UE for PUSCH transmission to multiple TRPs, and in particular how to indicate the spatial relationships associated with the TRPs, is a problem.

[0121] Certain aspects and embodiments of the present invention may provide solutions to the foregoing or other challenges. Systems and methods are disclosed for supporting simultaneous uplink (UL) PUSCH transmissions toward two or more TRPs by indicating two or more SRS resources in a single SRS resource set or in different SRS resource sets, including:

[0122] • Transfer different layers of PUSCH to different TRPs.

[0123] • Transmitting PUSCH to different TRPs in different frequency resources, and / or

[0124] • Transmit two PUSCHs to different TRPs in different frequency resources.

[0125] This paper also discloses systems and methods for signaling enhancement in PUSCH power control and DCI for each TRP.

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

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

[0128] 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 spatial relationships, or two or more downlink (DL) RSs each associated with a Transport Configuration Indicator (TCI) state. In one embodiment, the indication of two or more SRS resources is via one or more SRS Resource Indicators (SRIs).

[0129] In one embodiment, the two or more RSs indicated in the DCI are two or more SRS resources, and each of the two or more SRS resources 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) through a spatial relationship configuration. In one embodiment, each SSB or NZPCSI-RS is associated with a different Physical Cell Identity (ID) through, for example, an SSB configuration or through a field in the TCI state configuration.

[0130] In one embodiment, indications of two or more SRS resources are sent via one or more SRIs, and the UE also receives (e.g., signaled notification) path loss RS and power control parameter sets for each of one or more PUSCHs via one or more SRIs, wherein the signaled notification SRI is associated with one or more path loss RSs and one or more power control parameter sets.

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

[0132] In one embodiment, the UE is signaled semi-statically (e.g. via Radio Resource Control (RRC)) and / or dynamically (e.g. via DCI) to indicate whether it is using an SDM scheme or an FDM scheme (one or more).

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

[0134] In one embodiment, two or more TRPs are indicated in the DCI by indication of two or more TCI states, wherein each TRP is associated with a TCI state.

[0135] 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 extremely low latency, wherein better reliability can be achieved simultaneously over multiple TRPs via spatial diversity.

[0136] Figure 3 An example of a cellular communication system 300 in which embodiments of the present disclosure may be implemented is shown. In the embodiments described herein, the cellular communication system 300 is a 5G system (5GS) including a next-generation RAN (NR-RAN) and a 5G core (5GC). In this example, the RAN includes base stations 302-1 and 302-2, which in the 5GS include an NR base station (gNB) and an optional next-generation eNB (ng-eNB) (i.e., an LTE RAN node connected to the 5GC) to control corresponding (macro)cells 304-1 and 304-2. Base stations 302-1 and 302-2 are generally referred to herein collectively as base station 302, and are individually referred to as base station 302. Similarly, (macro)cells 304-1 and 304-2 are generally referred to herein collectively as (macro)cell 304, and are individually referred to as (macro)cell 304. The RAN may also include a plurality of low-power nodes 306-1 to 306-4 controlling corresponding small cells 308-1 to 308-4. Low-power nodes 306-1 to 306-4 may be small base stations (such as pico or femto base stations) or remote radio head ends (RRHs) or similar. Notably, although not shown, one or more small cells among small cells 308-1 to 308-4 may alternatively be provided by base station 302. Low-power nodes 306-1 to 306-4 are generally referred to herein as low-power node 306, and are individually referred to as low-power node 306. Similarly, small cells 308-1 to 308-4 are generally referred to herein as small cell 308, and are individually referred to as small cell 308. Cellular communication system 300 also includes a core network 310, which is referred to as 5G core (5GC) in 5GS. Base station 302 (and optional low-power node 306) is connected to core network 310.

[0137] Base station 302 and low-power node 306 provide services to wireless communication devices 312-1 to 312-5 in corresponding cells 304 and 308. Wireless communication devices 312-1 to 312-5 are generally referred to herein as wireless communication device 312, and are individually referred to as wireless communication device 312. In the following description, wireless communication device 312 is often a UE, and is therefore sometimes referred to herein as UE 312, but this disclosure is not limited thereto.

[0138] Now, descriptions of some embodiments of this disclosure will be provided.

[0139] Simultaneous PUSCH transmission to multiple TRPs using spatial multiplexing (SDM).

[0140] In this embodiment, one or more PUSCHs of the same Transport Block (TB) are simultaneously transmitted to multiple TRPs on the same time and frequency resources or on different frequency resources. Examples of different TRPs are different base stations 302, different low-power nodes 306, a mixture of one or more base stations 302 and one or more low-power nodes 306, or the like. Note that these are non-limiting examples of TRPs. Other examples include remote radio heads, multiple panels, etc.

[0141] Figure 4 This 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 via DCI, where the first layer (layer 1) is transmitted to TRP1 and the second layer (layer 2) to TRP2. The first layer is associated with a first SRS resource, and the second layer is associated with a second SRS resource, where association means transmitting the layer on one or more SRS ports of the corresponding SRS resource. In frequency range 2 (FR2), each SRS resource is spatially associated with a DL RS (e.g., a CSI-RS or SSB) or another SRS via spatial relation configuration. In this example, the first DL RS (DL RS #1) is transmitted from TRP1, and the second DL RS (DL RS #2) is transmitted from TRP2. In one example, the two DL RSs belong to two different TCI states and may also have different SSBs as sources of quasi-co-bit (QCL) relations. Therefore, each TRP transmits a different SSB.

[0142] Specifically, the two SSBs may be configured with different physical cell IDs, even if they are both used by the same UE for PUSCH transmission. That is, the two TRPs transmit SSBs belonging to two different cells, and since the SSBs are the source of the QCL relationship for the DL RS (target), the DL RS is also transmitted from different cells. Alternatively, the DL RS is in a TCI state, and this TCI state includes a cell ID indicator, allowing different DL RSs to be configured to belong to different cells (i.e., transmitted from TRPs served by different cells with different cell IDs).

[0143] An example of DL RS is CSI-RS, or Tracking Reference Signal (TRS), used for tracking.

[0144] 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. The DCI for scheduling the PUSCH is then indicated to the UE via the Physical Downlink Control Channel (PDCCH). The two SRS resources are indicated in one or both of the "SRS Resource Indicator (SRI)" fields of the DCI. The DCI also indicates two DMRS ports (i.e., DMRS ports x and y) in two Code Division Multiplexing (CDM) groups (i.e., CDM groups 1 and 2), each DMRS port associated with one of the two layers. The first SRS resource is linked to the first DMRS port indicated in the DCI field "(one or more) Antenna Ports", and the second SRS resource is linked to the second DMRS port indicated in the DCI field "(one or more) Antenna Ports". For codebook-based SRS, and if each SRS resource has more than one SRS port, a Transmit Precoding Matrix Indicator (TPMI) is also indicated for each SRS resource. In this example, joint decoding is required by combining the PUSCH signals received from the two TRPs.

[0145] For UE to transmit a single PUSCH to different layers to two TRPs (e.g.) Figure 4 In the example shown, the same time and frequency resources are used to transmit to two different TRPs.

[0146] While the above example embodiment covers two layers for a single PUSCH, this embodiment can be extended to up to more than two layers. For example, the above example embodiment can be extended to up to four layers for a single PUSCH transmitted to up to three TRPs. Some examples are as follows:

[0147] • In one example, a PUSCH with four layers is scheduled via DCI, where layers 1 and 2 (layers 1-2) are delivered to TRP1, and layers 3-4 (layers 3-4) are delivered to TRP2. Layers 1-2 are associated with the first SRS resource, and layers 3-4 are associated with the second SRS resource, where association means delivering the layer on one or more SRS ports of the corresponding SRS resource. In this case, the 'one or more antenna ports' field can indicate the DMRS ports corresponding to the two CDM groups (one CDM group is associated with each TRP).

[0148] • In another example, a three-layer PUSCH is scheduled via DCI, where layers 1 and 2 (layers 1-2) are delivered to TRP1, and layer 3 (layer 3) is delivered to TRP2. Layers 1-2 are associated with the first SRS resource, and layer 3 is associated with the second SRS resource, where association means delivering the layer on one or more SRS ports of the corresponding SRS resource. In this case, the 'one or more antenna ports' field can indicate the DMRS ports corresponding to the two CDM groups (one CDM group is associated with each TRP).

[0149] • In another example, a PUSCH with four layers is scheduled via DCI, where layers 1 and 2 (layers 1-2) are delivered to TRP1, layer 3 (layer 3) to TRP2, and layer 4 to TRP3. Layers 1-2 are associated with the first SRS resource, layer 3 with the second SRS resource, and layer 4 with the third SRS resource, where association means delivering the layer on one or more SRS ports of the corresponding SRS resource. In this case, the 'one or more antenna ports' field can indicate the DMRS port corresponding to the three CDM groups (one CDM group is associated with each TRP).

[0150] Alternatively, for the same TB or different TBs, a separate PUSCH can be sent to each TRP. Figure 5 An example is shown where the UE transmits two PUSCHs (PUSCH1 and PUSCH2) of the same TB to two TRPs (TRP1 and TRP2). In this case, PUSCH2 can be considered a retransmission of the TB with the same or different redundant versions. Similarly, the two SRS resources and the DMRS in the two CDM groups are indicated in the DCI via the SRI field and (one or more) antenna port fields, respectively. In this case, if each of the two PUSCHs is self-decoding, independent decoding can be performed at each TRP. For the UE to transmit two PUSCHs to two TRPs (e.g., Figure 5The example shown above illustrates an embodiment that uses the same time-frequency resources to transmit to two different TRPs. While the example embodiment above covers two PUSCHs transmitting to the same TB to two TRPs, this embodiment can be extended to transmitting to at most [number missing] TRPs. N At most, the number of TRPs with the same TB and different RVs is [number missing]. N A PUSCH.

[0151] Simultaneous PUSCH transmission to multiple TRPs using frequency domain multiplexing (FDM)

[0152] In the example above, the same time-frequency resources were allocated to two TRPs. In this embodiment, different frequency domain resources are allocated to different TRPs. Figure 6 An example is shown where a single PUSCH is transmitted to two TRPs using a portion of the frequency domain resources allocated to each TRP (e.g., a portion of the RB). In this case, the two TRPs may share the same (one or more) DMRS ports because they use different resources, and therefore, a single CDM group can be allocated. Joint decoding is required by combining the PUSCH signals received from the two TRPs.

[0153] Alternatively, for the same TB or different TBs, send separate PUSCHs to each TRP on different frequency domain resources. Figure 7 An example is shown where the UE transmits two PUSCHs (PUSCH1 and PUSCH2) with the same TB to two TRPs (TRP1 and TRP2). In this case, PUSCH2 can be considered a retransmission of the same TB with the same or different Redundancy Versions (RVs). Again, two SRS resources and one CDM group are indicated in the DCI. In this case, if each of the two PUSCHs is self-decoding, independent decoding can be performed at each TRP.

[0154] A signal can be sent to notify the allocation of a single frequency resource, and then the frequency resource can be divided between two TRPs. In one embodiment, if N RBs are allocated, the first N / 2 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.

[0155] In one embodiment, when using two PUSCHs (e.g., PUSCH1 and PUSCH2), the TB size is determined based on the number of RBs (or subcarriers) allocated to the first TRP.

[0156] Configure the UE to use either SDM or FDM schemes.

[0157] In some embodiments, higher-layer (e.g., RRC) signaling is used to configure the UE to select either SDM or FDM schemes, as well as the variations covered above. That is, when the network configures the UE with the 'FDM' scheme, the UE assumes a multi-TRP PUSCH transmission scheme based on the embodiments described in the section "Simultaneous PUSCH Transmission to Multiple TRPs Using Frequency Domain Multiplexing (FDM)". In another embodiment, the UE is jointly indicated by the antenna port field and SRI field in the UL DCI as to whether to use 'SDM' or 'FDM' multi-TRP PUSCH transmission, as described below:

[0158] • If the 'Antenna Port' field indicates a DMRS port from two CDM groups, and if the SRI field indicates two SRS resources, then the UE assumes an SDM scheme.

[0159] • If the 'Antenna Port' field indicates a DMRS port from one CDM group, and if the SRI field indicates two SRS resources, then the UE assumes an FDM scheme.

[0160] PUSCH power control

[0161] For codebook-based PUSCH transmission, in one embodiment, a single SRS resource set with 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 relation configuration, which includes a DL RS (or path loss RS) for path loss measurement and estimation. A set of parameters related to PUSCH power control is also associated with the SRS resources. When one or more PUSCHs are scheduled to be transmitted to two TRPs via DCI, the two SRS resources are also indicated in the DCI. The transmission power of the PUSCH to each TRP can be calculated based on the path loss estimate and power control parameter set associated with the corresponding SRS resource.

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

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

[0164] In the case of codebook-based PUSCH transmission, one or two SRS resources can be indicated in the DCI for PUSCH transmission to one or two TRPs respectively. For non-codebook-based transmission, one or two sets of SRS resources can be indicated in the DCI for PUSCH transmission to one or two TRPs respectively. If one SRS resource is indicated, PUSCH is scheduled towards a single TRP. On the other hand, if two SRS resources are indicated, one or more PUSCH are scheduled towards two TRPs.

[0165] PUSCH can be scheduled using two SRI fields (one SRI field per TRP) in DCI. To support dynamic switching between a single TRP and two TRPs, each SRI field may also include code points indicating that no corresponding SRS resource has been selected.

[0166] To support independent power control from PUSCH to each TRP, a separate TPC command can be included in the DCI for each TRP. The "TPC command for PUSCH for scheduling" field in DCI 0_1 and DCI 0_2 can be extended from 2 bits to 4 bits, with 2 bits for each TRP.

[0167] UCI on PUSCH

[0168] Uplink control information (UCI) on PUCCH resources, such as Hybrid Automatic Repeat Request Acknowledgment (HARQ-Ack), CSI feedback, or scheduling request (SR), can exist in the same time slot as PUSCH. In this case, the UCI is carried on PUSCH (instead of PUCCH). How to reuse the UCI and PUSCH is the question.

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

[0170] If provided for UE ACKNACKFeedbackMode = JointFeedback If a PUCCH overlaps with a PUSCH that has at least one symbol, then the UCI is transmitted on both PUSCHs.

[0171] In another embodiment, a higher-layer configuration in which the UE always reuses UCI on the PUSCH regardless of spatial relationships can be provided to the UE.

[0172] DCI Indication

[0173] In addition to the "TPC commands for scheduling PUSCH" mentioned in the "PUSCH Power Control" section above, one or more DCI bit fields in DCI formats 0_1 and 0_2 can be expanded to have more bits in existing fields (i.e., for joint encoding of 2 TRPs) or to add new fields (for the second TRP) to support 2 PUSCH transmissions to two TRPs:

[0174] • Precoding information and number of layers

[0175] • Antenna port

[0176] • SRS Request

[0177] • PTRS-DMRS association

[0178] • DMRS sequence initialization

[0179] • First downlink assignment index

[0180] • Second downlink assignment index

[0181] Although the UE can switch between single-TRP mode and multi-TRP mode based on the indication in the received DCI, the DCI fields for each format 0_1 ​​and 0_2, as well as the size of each field, should be aligned. Truncation or padding can be applied to align the sizes of each DCI field. For example, multiple most significant bits with values ​​set to '0' can be inserted into the smaller bit width (i.e., single-TRP) until the bit widths of single-TRP and multi-TRP are the same.

[0182] If PUSCH Multi-TRP is enabled for each CORESET or for each SearchSpace, then each DCI field size should be aligned for each CORESET or for each SearchSpace, and the total DCI payload size should be aligned in the same format across all CORESETs and SearchSpaces.

[0183] Further description

[0184] While the above discussion focuses on simultaneous PUSCH transfers to two TRPs for the same TB (e.g., PUSCH1 and PUSCH2), the embodiments can be readily extended to different TBs (e.g., PUSCH1 carries TB1, while PUSCH2 carries TB2). Furthermore, the above discussion of PUSCH transfers is based on scheduling using a single DCI; however, the embodiments can be extended to multi-DCI-based scheduling, where PUSCHs are scheduled to each TRP via separate DCIs.

[0185] Furthermore, in the above embodiments, one or more SRIs are used to indicate the PUSCH transmission direction. However, in another embodiment, the UL TCI status can be used instead to indicate the PUSCH transmission direction. For example, two UL TCI statuses can be signaled in the DCI to indicate PUSCH transmissions to two TRPs.

[0186] Figure 8 The operation of a wireless communication device 312 (e.g., a UE) with two TRPs 800-1 and 800-2 is illustrated according to at least some of the embodiments described above. Note that optional steps are indicated by dashed lines / boxes. As shown, in one embodiment, the wireless communication device 312 receives a DCI from a network node (e.g., TRP1 in this example), which simultaneously schedules one or more PUSCH transmissions 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 806).

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

[0188] The details described above regarding the DCI received by wireless communication device 312 (e.g., UE) to schedule multi-TRP PUSCH transmissions are applicable to Figure 8 The process. Some of those details are repeated here; however, note that other details that are not repeated here also apply. In one embodiment, 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 corresponding TCI state.

[0189] In another embodiment, the two or more reference signals are two or more SRS resources, each SRS resource configured with a corresponding 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 corresponding reference signal via a spatial relationship configuration. In one embodiment, the corresponding reference signal is an SSB, an NZP CSI-RS, or another SRS. In one embodiment, two or more SRS resources are associated with two or more corresponding reference signals, and the two or more corresponding reference signals are associated with two or more corresponding cell IDs (i.e., each corresponding reference signal is associated with a different cell ID). In one embodiment, the two or more corresponding reference signals are two or more corresponding SSBs or two or more corresponding NZP CSI-RSs. In one embodiment, the two or more corresponding reference signals are associated with two or more corresponding cell IDs via a field in the TCI state configuration. In one embodiment, the two or more corresponding reference signals are two or more corresponding SSBs, and the two or more reference signals are associated with two or more corresponding cell IDs via the SSB configuration.

[0190] In one embodiment, the wireless communication device 312 further receives, via one or more SRIs, an indication of a path loss reference signal and power control parameter set for each of the one or more PUSCHs (e.g., TRP1 in this example) from a network node (e.g., TRP1 in this example), wherein the association between the SRI and the one or more path loss reference signals and power control parameter sets is signaled to the wireless communication device. In this example, the indication of the path loss reference signal and power control parameter set for each of the one or more PUSCHs is included in the DCI and, more specifically, is provided by (one or more) SRIs. In other words, in one embodiment, the wireless communication device 312 receives information that defines the association between the SRI and the one or more path loss reference signals and power control parameter sets for each SRI in the SRI set (step 802). In other words, as described in the above section entitled “PUSCH Power Control”, the wireless communication device 312 may receive a configuration of the path loss reference signal and power control related parameter set 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). Then, the wireless communication device 312 receives, via one or more SRIs included in the DCI of step 806, an indication of a path loss reference signal and a power control parameter set 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 power control parameter set for each of the one or more PUSCHs.

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

[0192] In one embodiment, the wireless communication device 312 receives an instruction from a network node (e.g., TRP1 in this example) to perform multi-TRP PUSCH transmission using SDM or FDM (step 804). In this case, in step 808, if the received instruction is to perform multi-TRP PUSCH transmission using SDM, the wireless communication device 312 transmits one or more PUSCHs to the TRP on the same time and frequency domain resources; or if the received instruction is to perform multi-TRP PUSCH transmission using FDM, the wireless communication device 312 transmits the one or more PUSCHs to the TRP on the same time domain resources but on different frequency domain resources.

[0193] In one example alternative embodiment, one or more PUSCHs include two or more PUSCHs, and each of the two or more PUSCHs is scheduled via separate downlink control information.

[0194] In one embodiment, the DCI indicates the TRP to which one or more PUSCHs are transmitted simultaneously via indications of two or more TCI states, wherein each TRP is associated with a TCI state.

[0195] Figure 9A and Figure 9B The operation of a wireless communication device 312 (e.g., a UE) and two TRPs 800-1 and 800-2 is illustrated according to at least some of the embodiments described above, particularly those described above in the section "PUSCH Power Control". Figure 9A As shown, in one embodiment, the wireless communication device 312 receives a configuration (step 902A) from a network node (e.g., TRP1 in this example) of a single SRS resource set comprising two or more SRS resources. As described above, each of the two or more SRS resources (in the single SRS resource set) is associated with the TRP via a spatial relation configuration that includes 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 resources. 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.

[0196] Wireless communication device 312 receives a DCI that schedules one or more PUSCHs to TRP1 900-1 and TRP2 900-2 (step 904A). In other words, the received DCI schedules PUSCH transmissions comprising a first portion to be transmitted to TRP1 900-1 (e.g., and therefore associated with the first SRS resource or first TCI state indicated in the DCI) and a second portion to be transmitted to TRP2 900-2 (e.g., and therefore associated with the second SRS resource or second TCI state indicated in the DCI). The DCI indicates two SRS resources (i.e., the first SRS resource and the second SRS resource) 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 the corresponding path loss RS and PUSCH power control related parameter set associated with the first SRS resource. Similarly, the indication of the second SRS resource in the DCI is also an indication of the corresponding path loss RS and PUSCH power control related parameter set associated with the second SRS resource. In addition, the first SRS resource is associated with TRP1 900-1 (or the first TCI state), and the second SRS resource is associated with TRP2 900-2 (or the second TCI state).

[0197] Wireless communication device 312 transmits one or more PUSCHs according to DCI (step 906A). More specifically, the PUSCH transmission in step 906A includes transmitting a first portion to TRP1 900-1 (e.g., using a first TCI state) using transmission power calculated based on an estimated path loss, the estimated path loss being based on a path loss reference signal associated with a first SRS resource indicated by the DCI (step 906A-1). The PUSCH transmission in step 906A also includes transmitting a second portion to TRP2 900-2 (e.g., using a second TCI state) using transmission power calculated based on a path loss estimate, the path loss estimate being 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 being transmitted. As another example, the first portion and the second portion are different PUSCH transmissions of different RVs of the same TB.

[0198] like Figure 9BAs shown, in another embodiment, the wireless communication device 312 receives configurations of two SRS resource sets from a network node (e.g., TRP1 900-1 in this example), each SRS resource set including one or more SRS resources (step 902B). As described above, each SRS resource set in the two SRS resource sets is associated with a set of DLRS (or path loss RS) and PUSCH power control related parameters used for path loss measurement and estimation. The wireless communication device 312 receives a DCI that schedules one or more PUSCH transmissions to TRP1 900-1 and TRP2 900-2 (step 904B). In other words, the received DCI schedules a PUSCH transmission comprising a first portion to be transmitted to TRP1 900-1 (e.g., and thus associated with a first SRS resource or a first TCI state from a first SRS resource set indicated in the DCI) and a second portion to be transmitted to TRP2 900-2 (e.g., and thus associated with a second SRS resource or a second TCI state from a second SRS resource set indicated in the DCI). The DCI indicates two SRS resources, including a first SRS resource from the first SRS resource set (which is thereby associated with the corresponding path loss RS and PUSCH power control related parameter set associated with the first SRS resource set) and a second SRS resource from the second SRS resource set (which is thereby associated with the corresponding path loss RS and PUSCH power control related parameter set associated with the second SRS resource set). Similarly, the first SRS resource is associated with TRP1 900-1 (or the first TCI state), and the second SRS resource is associated with TRP2 900-2 (or the second TCI state).

[0199] Wireless communication device 312 transmits one or more PUSCHs according to DCI (step 906A). More specifically, the PUSCH transmission in step 906A includes transmitting a first portion to TRP1 900-1 (e.g., using a first TCI state) using transmission power calculated based on an estimated path loss, the estimated path loss being based on a path loss reference signal associated with a first SRS resource indicated by the DCI (step 906A-1). The PUSCH transmission in step 906A also includes transmitting a second portion to TRP2 900-2 (e.g., using a second TCI state) using transmission power calculated based on a path loss estimate, the path loss estimate being 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 being transmitted. As another example, the first portion and the second portion are different PUSCH transmissions of different RVs of the same TB.

[0200] As discussed above, in one embodiment, the DCI of step 904A or 904B includes two SRI fields, one SRI field indicating the SRS resource of each TRP in TRPs 900-1 and 900-2. In one embodiment, to support dynamic switching between a single TRP and two TRPs, each SRI field may also include a code point indicating that no corresponding SRS resource has been selected, as described above.

[0201] In one embodiment, to support independent power control from PUSCH to each TRP, a separate TPC command can be included in the DCI of step 904A or 904B for each TRP in TRPs 900-1 and 900-2, as described above. In one embodiment, the "TPC command for PUSCH to be scheduled" field in DCI 0_1 and DCI 0_2 can be extended from 2 bits to 4 bits, with 2 bits for each TRP, as described above.

[0202] Figure 10 This is a schematic block diagram of a radio access node 1000 according to some embodiments of the present disclosure. Optional features are indicated by dashed boxes. The radio access node 1000 may be, for example, a TRP as described herein. As shown, the radio access node 1000 includes a control system 1002, which includes one or more processors 1004 (e.g., a central processing unit (CPU), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), and / or similar components), a memory 1006, and a network interface 1008. The one or more processors 1004 are also referred to herein as processing circuitry. Additionally, the radio access node 1000 may include one or more radio units 1010, each radio unit 1010 including one or more transmitters 1012 and one or more receivers 1014 coupled to one or more antennas 1016. The radio unit 1010 may be referred to as radio interface circuitry, or may be a portion thereof. In some embodiments, the radio units(s) 1010 are located outside the control system 1002 and are connected to the control system 1002 via, for example, a wired connection (e.g., an optical fiber). However, in some other embodiments, one or more radio units 1010 and potential antennas 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 as described herein (e.g., one or more functions of the TRP as described herein). In some embodiments, the functions are implemented using software stored, for example, in memory 1006 and executed by the one or more processors 1004.

[0203] Figure 11 This is a schematic block diagram illustrating a virtualization embodiment of a radio access node 1000 according to some embodiments of this disclosure. This discussion is equally applicable to other types of network nodes. Furthermore, other types of network nodes may have similar virtualization architectures. Similarly, optional features are indicated by dashed boxes.

[0204] As used herein, a “virtualized” radio access node is an implementation of radio access node 1000, wherein at least a portion of the functionality of radio access node 1000 is implemented as one or more virtual components (e.g., via one or more virtual machines executing on one or more physical processing nodes in one or more networks). As illustrated, in this example, radio access node 1000 may include a control system 1002 and / or one or more radio units 1010, as described above. Control system 1002 may be connected to radio units 1010 via, for example, fiber optic cable or the like. Radio access node 1000 includes one or more processing nodes 1100, which are coupled to or included as part of network 1102. If present, control system 1002 or one or more radio units are connected to processing nodes 1100 via network 1102. Each processing node 1100 includes one or more processors 1104 (e.g., CPU, ASIC, FPGA, and / or similar components), memory 1106, and network interface 1108.

[0205] In this example, the functions 1110 of the radio access node 1000 described herein (e.g., one or more functions of the TRP) are implemented at one or more processing nodes 1100 or distributed across one or more processing nodes 1100 with the control system 1002 and / or (one or more) radio units 1010 in any desired manner. In some specific 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, which are implemented in one or more virtual environments hosted by (one or more) processing nodes 1100. As those skilled in the art will recognize, additional signaling or communication is used between (one or more) processing nodes 1100 and the control system 1002 to perform at least some of the desired functions 1110. Notably, in some embodiments, the control system 1002 may not be included, in which case the (one or more) radio units 1010 communicate directly with (one or more) processing nodes 1100 via (one or more) suitable network interfaces.

[0206] In some embodiments, a computer program including instructions is provided that, when executed by at least one processor, causes the at least one processor to perform the functionality of a node (e.g., processing node 1100) that implements one or more of the functions of radio access node 1000 in a virtual environment according to any embodiment described herein. In some embodiments, a carrier including the aforementioned computer program product is provided. The carrier is one of the following: electronic signals, optical signals, radio signals, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0207] Figure 12 This 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 includes one or more modules 1200, each of which is implemented in software. The modules(one or more) 1200 provide the functionality of the radio access node 1000 described herein (e.g., the functionality of the TRP as described herein). This discussion is equally applicable to... Figure 11 The processing node 1100, wherein the module 1200 may be implemented at one of the processing nodes 1100, or distributed across multiple processing nodes 1100, and / or distributed across (one or more) processing nodes 1100 and the control system 1002.

[0208] Figure 13 This 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 Q112 or UE as described herein. As shown, the wireless communication device 1300 includes one or more processors 1302 (e.g., CPU, ASIC, FPGA, and / or similar components), a memory 1304, and one or more transceivers 1306. Each transceiver 1306 includes one or more transmitters 1308 and one or more receivers 1310 coupled to one or more antennas 1312. Each transceiver 1306 includes radio front-end circuitry connected to one or more antennas 1312, configured to modulate signals transmitted between the antennas 1312 and the processors 1302, as will be appreciated by those skilled in the art. The processor 1302 is also referred to herein as processing circuitry. The transceiver 1306 is also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device 1300 described above (e.g., the functionality of the wireless communication device 312 or UE as described herein) may be implemented wholly or partially using software stored, for example, in memory 1304 and executed by processor(s) 1302. Note that the wireless communication device 1300 may include... Figure 13 Additional components not shown in the document, such as one or more user interface components (e.g., input / output interfaces including displays, buttons, touchscreens, microphones, speakers (one or more) and / or similar components, and / or any other components that allow information to be input into and / or output from the wireless communication device 1300), power supplies (e.g., batteries and associated power circuitry), etc.

[0209] In some embodiments, a computer program including instructions is provided that, when executed by at least one processor, causes the at least one processor to perform the functionality of a wireless communication device 1300 according to any embodiment described herein. In some embodiments, a carrier including the aforementioned computer program product is provided. The carrier is one of the following: electronic signals, optical signals, radio signals, or a computer-readable storage medium (e.g., a non-transitory computer-readable medium such as a memory).

[0210] Figure 14 This 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 modules (one or more) 1400 provide the functionality of the wireless communication device 1300 described herein (e.g., the functionality of the wireless communication device 312 or UE as described herein).

[0211] Reference Figure 15 According to an embodiment, a communication system includes a telecommunications network 1500, such as a 3GPP-type cellular network, comprising an access network 1502, such as a RAN, and a core network 1504. The access network 1502 includes multiple base stations 1506A, 1506B, 1506C, such as Node B, eNB, gNB, or other types of radio access points (APs), each base station defining a corresponding coverage area 1508A, 1508B, 1508C. Each base station 1506A, 1506B, 1506C can be connected to the core network 1504 via a wired or wireless connection 1510. A first UE 1512 located in coverage area 1508C is configured to wirelessly connect to or be paged by the corresponding base station 1506C. A second UE 1514 located in coverage area 1508A can wirelessly connect to the corresponding base station 1506A. Although multiple UEs 1512 and 1514 are shown in this example, the disclosed embodiments are also applicable to situations where a single UE is located in the coverage area or a single UE is connected to the corresponding base station 1506.

[0212] Telecommunication network 1500 is itself connected to host computer 1516, which may be embodied in the hardware and / or software of a standalone server, a cloud-implemented server, a distributed server, or as a processing resource in a server cluster. Host computer 1516 may be owned or controlled by a service provider, or may be operated by or on behalf of a service provider. Connections 1518 and 1520 between telecommunications network 1500 and host computer 1516 may extend directly from core network 1504 to host computer 1516, or via an optional intermediate network 1522. Intermediate network 1522 may be one or a combination of public, private, or hosted networks; intermediate network 1522 (if any) may be a backbone network or the Internet; in particular, intermediate network 1522 may include two or more subnetworks (not shown).

[0213] Figure 15 The communication system as a whole enables connectivity between connected UEs 1512 and 1514 and host computer 1516. This connectivity can be described as an over-the-top (OTT) connection 1524. Host computer 1516 and connected UEs 1512 and 1514 are configured to use access network 1502, core network 1504, any intermediate network 1522, and possibly other infrastructure (not shown) as intermediaries to transmit data and / or signaling via OTT connection 1524. OTT connection 1524 can be transparent to participating communication devices traversing from OTT connection 1524, as they are unaware of the significance of uplink and downlink communication routing. For example, it may not be necessary or required to inform base station 1506 about past routing choices for incoming downlink communication that forwards (e.g., transfers) data originating from host computer 1516 to connected UE 1512. Similarly, base station 1506 does not need to know future routing choices for outgoing uplink communication originating from UE 1512 to host computer 1516.

[0214] Now refer to Figure 16This section describes example implementations of the UE, base station, and host computer discussed in the preceding paragraphs according to embodiments. In the communication system 1600, the host computer 1602 includes hardware 1604, which includes a communication interface 1606 configured to establish and maintain wired or wireless connections with different communication devices of the communication system 1600. The host computer 1602 further includes processing circuitry 1608, which may have storage and / or processing capabilities. In particular, the processing circuitry 1608 may include one or more programmable processors, ASICs, FPGAs, or combinations of such programmable processors, ASICs, and FPGAs (not shown) adapted to execute instructions. The host computer 1602 further includes software 1610, which is stored in or accessible by the host computer 1602 and executable by the processing circuitry 1608. The software 1610 includes a host application 1612. Host application 1612 is operable to provide services to remote users, such as UE 1614 connected via OTT connection 1616 terminated between UE 1614 and host computer 1602. In providing services to remote users, host application 1612 can provide user data transmitted using OTT connection 1616.

[0215] The communication system 1600 further includes a base station 1618 provided in the telecommunications system, and the base station 1618 includes hardware 1620 to enable it to communicate with the host computer 1602 and the UE 1614. Hardware 1620 may include a communication interface 1622 for establishing and maintaining wired or wireless connections with different communication devices of the communication system 1600, and for communicating with the coverage area served by the base station 1618. Figure 16 In the UE 1614 (not shown), a radio interface 1624 establishes and maintains at least a wireless connection 1626. A communication interface 1622 can be configured to facilitate a connection 1628 to a host computer 1602. The connection 1628 can be direct, or it can be via the core network of a telecommunications system (…). Figure 16 (Not shown) and / or via one or more intermediate networks outside the telecommunications system. In the illustrated embodiment, the hardware 1620 of base station 1618 further includes processing circuitry 1630, which may include one or more programmable processors, ASICs, FPGAs, or combinations of such programmable processors, ASICs, and FPGAs (not shown) adapted to execute instructions. Base station 1618 further has software 1632 stored internally or accessible via an external connection.

[0216] The communication system 1600 further includes the previously mentioned UE 1614. The hardware 1634 of the UE 1614 may include a radio interface 1636 configured to establish and maintain a wireless connection 1626 with a base station serving the coverage area where the UE 1614 is currently located. The hardware 1634 of the UE 1614 further includes processing circuitry 1638, which may include one or more programmable processors, ASICs, FPGAs, or combinations of such programmable processors, ASICs, and FPGAs (not shown) suitable for executing instructions. The UE 1614 further includes software 1640 stored in or accessible by the UE 1614 and executable by the processing circuitry 1638. The software 1640 includes a client application 1642. The client application 1642 is operable to provide services to human or non-human users via the UE 1614 with the support of a host computer 1602. In host computer 1602, a executing host application 1612 can communicate with a executing client application 1642 via an OTT connection 1616 terminated between UE 1614 and host computer 1602. In providing services to a user, client application 1642 can receive request data from host application 1612 and provide user data in response to the request data. OTT connection 1616 can transmit both request data and user data. Client application 1642 can interact with the user to generate the user data it provides.

[0217] Notice, Figure 16 The host computer 1602, base station 1618, and UE 1614 shown can respectively connect with... Figure 15 The host computer 1516, base stations 1506A, 1506B, and 1506C, and UEs 1512 and 1514 are similar to or identical to each other. This means that the internal operations of these entities can be as follows: Figure 16 As shown, and independently, the surrounding network topology can be Figure 15 The network topology.

[0218] exist Figure 16 The OTT connection 1616 has been abstractly depicted to illustrate communication between host computer 1602 and UE 1614 via base station 1618, without explicitly mentioning any intermediate devices or the exact routing of messages via these devices. The network infrastructure can determine the routing, which can be configured to be hidden from UE 1614, the service provider operating host computer 1602, or both. When OTT connection 1616 is active, the network infrastructure can make further decisions (e.g., based on load balancing considerations or network reconfiguration), through which it dynamically changes the routing.

[0219] The wireless connection 1626 between UE 1614 and base station 1618 is based on the teachings of embodiments described throughout this disclosure. One or more embodiments in various embodiments improve the performance of OTT services provided to UE 1614 using OTT connection 1616, in which wireless connection 1626 forms the final segment.

[0220] A measurement process may be provided for the purpose of monitoring data rates, latency, and other factors that improve upon them in one or more embodiments. Optional network functionality may further exist for reconfiguring the OTT connection 1616 between host computer 1602 and UE 1614 in response to changes in the measurement results. The measurement process and / or the network functionality for reconfiguring the OTT connection 1616 may be implemented in software 1610 and hardware 1604 of host computer 1602, or in software 1640 and hardware 1634 of UE 1614, or both. In some embodiments, sensors (not shown) may be deployed in or associated with communication devices through which the OTT connection 1616 traverses; the sensors may participate in the measurement process by supplying values ​​of the monitored quantities exemplified above or values ​​of other physical quantities from which 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.; reconfiguration does not need to affect base station 1618, and it may be unknown or imperceptible to base station 1618. Such processes and functionalities can be known and practiced in the art. In some embodiments, measurements may involve proprietary UE signaling, which facilitates measurements of throughput, propagation time, latency, and the like by the host computer 1602. Measurements can be made because software 1610 and 1640 enable messages (especially empty or 'fake' messages) to be transmitted using OTT connection 1616 while it monitors propagation time, errors, etc.

[0221] Figure 17 This is a flowchart 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 referenced... Figure 15 and Figure 16 Those described. For the sake of brevity, this section will only include descriptions of... Figure 17The accompanying drawings are referenced. 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 of step 1700 (which may be optional), the UE provides user data by executing a client application. In sub-step 1706 of step 1702 (which may be optional), the UE responds to the received input data provided by the host computer by executing the client application that provides user data. In providing user data, the executed client application may further consider user input received from the user. Regardless of the specific method used to provide user data, in sub-step 1708 (which may be optional), the UE initiates the transmission of user data to the host computer. In step 1710 of the method, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

[0222] Figure 18 This is a flowchart 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 referenced... Figure 15 and Figure 16 Those described. For the sake of brevity, this section will only include descriptions of... Figure 18 The accompanying drawings are referenced. 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 a 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 the transmission initiated by the base station.

[0223] Any suitable steps, methods, features, functions, or benefits disclosed herein may be performed by one or more functional units or modules of one or more virtual devices. Each virtual device may include multiple such functional units. These functional units may be implemented via processing circuitry (which may include one or more microprocessors or microcontrollers) and other digital hardware (which may include digital signal processors (DSPs), application-specific digital logic, and the like). The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. The program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for executing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause corresponding functional units to perform corresponding functions according to one or more embodiments of this disclosure.

[0224] While the processes in the accompanying drawings may illustrate a particular order of operations performed by certain embodiments of this disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform operations in a different order, combine certain operations, overlap certain operations, etc.).

[0225] Some example embodiments of this disclosure are as follows:

[0226] Group A Examples

[0227] Example 1: A method performed by a wireless communication device for uplink transmission to a cellular communication network, the method comprising: transmitting one or more Physical Uplink Shared Channels (PUSCH) (808) to two or more Transmit and Receive Points (TRPs) of the cellular communication network on the same time and frequency domain resources or on the same time domain resources but on different frequency domain resources; wherein the two or more TRPs are associated with two or more different reference signals respectively.

[0228] Example 2: The method of Example 1 further includes receiving (806) downlink control information from a network node (e.g., one of two or more TRPs) that schedules the transmission of one or more PUSCHs.

[0229] Example 3: The methods of Examples 1 and 2, wherein the downlink control information indicates two or more reference signals.

[0230] Example 4: The methods of Examples 1 to 3, wherein two or more reference signals are two or more downlink reference signals each associated with a corresponding TCI state.

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

[0232] Example 5: The methods of Examples 1 to 3, wherein two or more reference signals are two or more probe reference signal (SRS) resources, each configured with a corresponding spatial relationship.

[0233] Example 6: The method of Example 5, wherein the downlink control information includes one or more SRS Resource Indicators (SRIs) indicating two or more SRS resources.

[0234] Example 7: The method of Example 6, wherein each of two or more SRS resources is associated with a corresponding reference signal through spatial relationship configuration.

[0235] Example 8: The method of Example 7, wherein the corresponding reference signal is SSB, NZP CSI-RS or another SRS.

[0236] Example 9: The method of Example 6, wherein: two or more SRS resources are associated with two or more corresponding reference signals; and two or more corresponding reference signals are associated with two or more corresponding cell IDs (i.e., each corresponding reference signal is associated with a different cell ID).

[0237] Example 10: The method of Example 9, wherein two or more corresponding reference signals are two or more corresponding SSBs or two or more corresponding NZP CSI-RS.

[0238] Example 11: The method of Example 9 or 10, wherein two or more corresponding reference signals are associated with two or more corresponding cell IDs via fields in the TCI state configuration.

[0239] Example 12: The method of Example 9, wherein two or more corresponding reference signals are two or more corresponding SSBs, and the two or more reference signals are associated with two or more corresponding cell IDs via SSB configuration.

[0240] Example 13: The method of any of Examples 1 to 12 further includes receiving (806) an indication of a path loss reference signal and a power control parameter set for each of the one or more PUSCHs via one or more SRIs or one or more TCIs, wherein the association between the SRI or TCIs and one or more path loss reference signals and one or more power control parameter sets is signaled to the wireless communication device.

[0241] Example 14: The method of any of Examples 6 to 12 further includes: receiving (802) information that defines the association between each SRI in a set of SRIs including one or more SRIs or each TCI state in a set of TCI states including one or more TCI states and one or more path loss reference signals and one or more power control parameter sets; and receiving (806) an indication of the path loss reference signal and power control parameter set for each of one or more PUSCHs via one or more SRIs or one or more TCI states.

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

[0243] Example 16: The method of any of Examples 5 to 15, wherein two or more SRS resources belong to the same SRS resource set or different SRS resource sets.

[0244] Example 17: The method of any of Examples 1 to 16 further includes receiving (804) an indication from a network node (e.g., one of two or more TRPs) for multi-TRP PUSCH transmission using a spatial division multiplexing scheme or a frequency division multiplexing scheme.

[0245] Example 18: The method of Example 17, wherein transmitting one or more PUSCHs (808) to two or more TRPs comprises: if the received indication is an indication for multi-TRP PUSCH transmission using a space division multiplexing scheme, then transmitting one or more PUSCHs (808) to two or more TRPs on the same time and frequency domain resources; or if the received indication is an indication for multi-TRP PUSCH transmission using a frequency division multiplexing scheme, then transmitting one or more PUSCHs (808) to two or more TRPs on the same time domain resources but on different frequency domain resources.

[0246] Example 19: The method of Example 1, wherein one or more PUSCHs include two or more PUSCHs, and each of the two or more PUSCHs is scheduled via separate downlink control information.

[0247] Example 20: The method of any of Examples 1 to 19, wherein two or more TRPs are indicated in the downlink control information by indication of two or more TCI states or two or more SRS resources, wherein each TRP is associated with a TCI state or an SRS resource.

[0248] Example 21: The method of any of the previous embodiments further includes: providing user data; and forwarding the user data to a host computer via one or more PUSCHs to two or more TRPs.

[0249] Group B Implementation Examples

[0250] Example 22: A method performed by a Transmitting and Receiving Point (TRP) of a cellular communication network, the method 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 on the same time and frequency domain resources or on the same time domain resources but on different frequency domain resources to two or more TRPs of the cellular communication network; wherein the two or more TRPs are associated with two or more different reference signals respectively.

[0251] Example 23: The method of Example 22 further includes transmitting (806) downlink control information to the wireless communication device to schedule the transmission of one or more PUSCHs.

[0252] Example 24: The method of Examples 22 and 23, wherein the downlink control information indicates two or more reference signals.

[0253] Example 25: The method of Examples 22 to 24, wherein two or more reference signals are two or more downlink reference signals each associated with a corresponding TCI state.

[0254] Example 26: The methods of Examples 22 to 24, wherein two or more reference signals are two or more probe reference signal (SRS) resources, each configured with a corresponding spatial relationship.

[0255] Example 27: The method of Example 26, wherein the downlink control information includes one or more SRS Resource Indicators (SRIs) indicating two or more SRS resources.

[0256] Example 28: The method of Example 27, wherein each of two or more SRS resources is associated with a corresponding reference signal through a spatial relationship configuration.

[0257] Example 29: The method of Example 28, wherein the corresponding reference signal is SSB, NZP CSI-RS or another SRS.

[0258] Example 30: The method of Example 27, wherein: two or more SRS resources are associated with two or more corresponding reference signals; and two or more corresponding reference signals are associated with two or more corresponding cell IDs (i.e., each corresponding reference signal is associated with a different cell ID).

[0259] Example 31: The method of Example 30, wherein two or more corresponding reference signals are two or more corresponding SSBs or two or more corresponding NZP CSI-RS.

[0260] Example 32: The method of Example 30 or 31, wherein two or more corresponding reference signals are associated with two or more corresponding cell IDs via fields in the TCI state configuration.

[0261] Example 33: The method of Example 30, wherein two or more corresponding reference signals are two or more corresponding SSBs, and the two or more reference signals are associated with two or more corresponding cell IDs via SSB configuration.

[0262] Example 34: The method of any of Examples 27 to 33 further includes transmitting (806) an indication of a path loss reference signal and a power control parameter set for each of the one or more PUSCHs via one or more SRIs or one or more TCIs, wherein the association between the SRI or TCIs and one or more path loss reference signals and one or more power control parameter sets is signaled to the wireless communication device.

[0263] Example 35: The method of any of Examples 27 to 33 further includes: transmitting (802) information to a wireless communication device, the information defining an association between an SRI or TCI state and one or more path loss reference signals and one or more power control parameter sets for each SRI in a set of SRIs including one or more SRIs or for each TCI state in a set of TCI states including one or more TCI states; and transmitting (806) an indication of the path loss reference signal and power control parameter set for each of one or more PUSCHs via one or more SRIs or one or more TCI states to the wireless communication device.

[0264] Example 36: The method of any of Examples 26 to 35, wherein two or more SRS resources belong to the same SRS resource set or different SRS resource sets.

[0265] Example 37: The method of any of Examples 22 to 36 further includes transmitting (804) an instruction to a wireless communication device to perform multi-TRP PUSCH transmission using a spatial division multiplexing scheme or a frequency division multiplexing scheme.

[0266] Example 38: The method of Example 22, wherein one or more PUSCHs comprise two or more PUSCHs, and each of the two or more PUSCHs is scheduled via separate downlink control information.

[0267] Example 39: The method of any of Examples 22 to 38, wherein two or more TRPs are indicated in the downlink control information by indication of two or more TCI states or two or more SRS resources, wherein each TRP is associated with a TCI state or a TCI state.

[0268] Example 40: The method of any of the previous embodiments further includes: receiving user data from a wireless communication device via a first portion of a multi-TRP PUSCH transmission; and forwarding the user data to a host computer.

[0269] Group C Implementation Examples

[0270] Example 41: A wireless communication device includes: processing circuitry configured to perform any step of any embodiment in any of the Group A examples; and power supply circuitry configured to supply power to the wireless communication device.

[0271] Example 42: A TRP includes: processing circuitry configured to perform any step of any embodiment in the Group B examples; and power supply circuitry configured to supply power to the TRP.

[0272] Example 43: A user equipment (UE) includes: an antenna configured to transmit and receive wireless signals; a radio front-end circuit connected to the antenna and a processing circuit, and configured to regulate signals transmitted between the antenna and the processing circuit; a processing circuit configured to perform any step of any embodiment in the Group A examples; an input interface connected to the processing circuit and configured to allow information to be input into the UE for processing by the processing circuit; an output interface connected to the processing circuit and configured to output information processed by the processing circuit from the UE; and a battery connected to the processing circuit and configured to power the UE.

[0273] Example 44: A communication system including a host computer, the host computer comprising: a communication interface configured to receive user data originating from a user equipment (UE) to a multi-TRP PUSCH transmission of two or more TRPs; wherein the UE includes a radio interface and processing circuitry, the processing circuitry of the UE being configured to perform any step of any of the steps in any of the embodiments in Group A examples.

[0274] Example 45: The communication system of the previous embodiment further includes a UE.

[0275] Example 46: The communication system of the first two examples further includes two or more TRPs, wherein each of the two or more TRPs includes a radio interface configured to communicate with the UE and a communication interface configured to forward user data carried by a corresponding portion of a multi-TRPPUSCH transmission from the UE to the TRP to a host computer.

[0276] Example 47: The communication system of the first three examples, wherein: the processing circuit of the host computer is configured to execute a host application; and the processing circuit of the UE is configured to execute a client application associated with the host application, thereby providing user data.

[0277] Example 48: The communication system of the first four examples, wherein: the processing circuit of the host computer is configured to execute a host application to provide requested data; and the processing circuit of the UE is configured to execute a client application associated with the host application to provide user data in response to the requested data.

[0278] Example 49: A method implemented in a communication system including a host computer, two or more TRPs and a user equipment UE, the method comprising: at the host computer, receiving user data transmitted to the two or more TRPs from the UE, wherein the UE performs any step of any embodiment of any of the Group A examples.

[0279] Example 50: The method of the previous embodiment further includes: at the UE, providing user data to two or more TRPs.

[0280] Example 51: The method of the first two examples further includes: at the UE, executing a client application to provide user data to be transmitted; and at the host computer, executing a host application associated with the client application.

[0281] Example 52: The method of the first three examples further includes: executing a client application at the UE; and receiving input data from the client application at the UE, and providing the input data at the host computer by executing a host application associated with the client application; wherein the user data to be transmitted is provided by the client application in response to the input data.

[0282] Example 53: A communication system including a host computer, the host computer including a communication interface configured to receive user data originating from a user equipment (UE) to a multi-TRP PUSCH transmission of two or more TRPs, wherein each of the two or more TRPs includes a radio interface and processing circuitry, the processing circuitry of the TRP being configured to perform any step of any of the steps in any of the embodiments in Group B examples.

[0283] Example 54: The communication system of the previous embodiment further includes TRP.

[0284] Example 55: The communication system of the first two examples further includes a UE, wherein the UE is configured to communicate with two or more TRPs.

[0285] Example 56: The communication system of the first three examples, wherein: the processing circuit 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.

[0286] Example 57: A method implemented in a communication system including a host computer, two or more TRPs and a user equipment UE, the method comprising: at the host computer, receiving user data from two or more TRPs originating from multi-TRP PUSCH transmissions received from the UE by the two or more TRPs, wherein the UE performs any step of any embodiment of any of the Group A examples.

[0287] Example 58: The method of the previous embodiment further includes: receiving user data from the UE at two or more TRPs.

[0288] Example 59: The method of the first two examples further includes: initiating the transmission of received user data to the host computer at two or more TRPs.

[0289] Those skilled in the art will recognize improvements and modifications to the embodiments of this disclosure. All such improvements and modifications are considered to be within the scope of the concepts disclosed herein.

Claims

1. A method performed by a wireless communication device (312), the method comprising: The network node receives (902B) two probe reference signal SRS resource sets, namely the configuration of the first and second SRS resource sets, each SRS resource set including one or more SRS resources, wherein the first and second SRS resource sets are associated with the first and second transmit and receive points (TRP), respectively. Receive (904B) Downlink Control Information (DCI) from the network node, the 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, wherein the first and second SRS resources are indicated in the DCI; and According to the DCI transmission (906B), the first physical uplink channel transmission and the second physical uplink channel transmission are transmitted synchronously in time to the first and second TRPs respectively in one or more identical symbols, wherein the first physical uplink channel transmission and the second physical uplink channel transmission can be one of the following: (a) Layers 1 and 2 of the same physical uplink channel (b) First and second portions of the same physical uplink channel, wherein the first portion is transmitted in a first frequency domain resource and the second portion is transmitted in a second frequency domain resource. (c) First and second physical uplink channels, wherein the first physical uplink channel is transmitted in a first frequency domain resource, and the second physical uplink channel is transmitted in a second frequency domain resource. (d) First and second physical uplink channels associated with the same data transmission block, wherein the first physical uplink channel is encoded with a first redundancy version and the second physical uplink channel is encoded with a second redundancy version.

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

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

4. The method of any of claims 1 to 3, further comprising receiving configurations of first and second power control parameter sets respectively associated with the first and second SRS resources, wherein each power control parameter set in the first and second power control parameter sets 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.

5. The method of claim 4, wherein, The first and second portions of the physical uplink channel transmission are transmitted using first and second transmission powers, respectively, wherein the first and second transmission powers are calculated based on the first and second power control parameter sets, respectively.

6. The method according to any one of claims 1 to 3, wherein, The physical uplink channel transmission is the physical uplink shared channel (PUSCH) transmission.

7. The method of claim 2, wherein, The possible set of code points for each of the first and second SRI fields in the DCI includes code points used to indicate that no corresponding SRS resource has been selected.

8. The method according to any one of claims 1 to 3, wherein, The DCI further indicates the first and second transmit power control (TPC) commands for the first and second portions of the physical uplink channel transmission, respectively.

9. The method according to any one of claims 1 to 3, wherein, The first and second SRS resources indicated in the DCI can be replaced by first and second uplink transmission configuration indicator (TCI) states, each of the first and second TCI states including a reference signal index for spatial relationship indication, a path loss reference signal index, a power control parameter set, or any combination thereof.

10. A wireless communication device (312), suitable for: The configuration of two probe reference signal (SRS) resource sets received from the network node (902B), each SRS resource set including one or more SRS resources, wherein the first and second SRS resource sets are associated with the first and second transmit and receive points (TRP), respectively. Receive (904B) Downlink Control Information (DCI) from the network node, the 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, wherein the first and second SRS resources are indicated in the DCI; and According to the DCI transmission (906B), the first physical uplink channel transmission and the second physical uplink channel transmission are transmitted synchronously in time to the first and second TRPs respectively in one or more identical symbols, wherein, The first physical uplink channel transmission and the second physical uplink channel transmission can be one of the following: (a) Layers 1 and 2 of the same physical uplink channel (b) First and second portions of the same physical uplink channel, wherein the first portion is transmitted in a first frequency domain resource and the second portion is transmitted in a second frequency domain resource. (c) First and second physical uplink channels, wherein the first physical uplink channel is transmitted in a first frequency domain resource, and the second physical uplink channel is transmitted in a second frequency domain resource. (d) First and second physical uplink channels associated with the same data transmission block, wherein the first physical uplink channel is encoded with a first redundancy version and the second physical uplink channel is encoded with a second redundancy version.

11. The wireless communication device (312) as claimed in claim 10, wherein, The wireless communication device (312) is further adapted to perform the method as described in any of claims 2 to 9.

12. A wireless communication device (312; 1300), comprising: • One or more transmitters (1308); • One or more receivers (1310); as well as • A processing circuit (1302) associated with the one or more transmitters (1308) and the one or more receivers (1310), the processing circuit (1302) being configured to cause the wireless communication device (312; 1300) to: The network node receives (902B) two probe reference signal SRS resource sets, namely the configuration of the first and second resource sets, each SRS resource set including one or more SRS resources, wherein the first and second SRS resource sets are associated with the first and second transmit and receive points (TRP), respectively. Receive (904B) Downlink Control Information (DCI) from the network node, the 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, wherein the first and second SRS resources are indicated in the DCI; and According to the DCI transmission (906B), the first physical uplink channel transmission and the second physical uplink channel transmission are transmitted synchronously in time to the first TRP and the second TRP respectively in one or more identical symbols, wherein the first physical uplink channel transmission and the second physical uplink channel transmission can be one of the following: (a) Layers 1 and 2 of the same physical uplink channel (b) First and second portions of the same physical uplink channel, wherein the first portion is transmitted in a first frequency domain resource and the second portion is transmitted in a second frequency domain resource. (c) First and second physical uplink channels, wherein the first physical uplink channel is transmitted in a first frequency domain resource, and the second physical uplink channel is transmitted in a second frequency domain resource. (d) First and second physical uplink channels associated with the same data transmission block, wherein the first physical uplink channel is encoded with a first redundancy version and the second physical uplink channel is encoded with a second redundancy version.

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

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

15. The wireless communication device (312; 1300) as claimed in any 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 power control parameter sets respectively associated with the first and second SRS resources, wherein each power control parameter set in the first and second power control parameter sets 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.

16. The wireless communication device (312; 1300) as claimed in claim 15, wherein, The first and second portions of the physical uplink channel transmission are transmitted using first and second transmission powers, respectively, wherein the first and second transmission powers are calculated based on the first and second power control parameter sets, respectively.

17. The wireless communication apparatus (312; 1300) according to any of claims 12 to 14, wherein the physical uplink channel transmission is a physical uplink shared channel (PUSCH) transmission.

18. The wireless communication device (312; 1300) as claimed in claim 13, wherein, The possible set of code points for each of the first and second SRI fields in the DCI includes code points used to indicate that no corresponding SRS resource has been selected.

19. The wireless communication device (312; 1300) as claimed in any of claims 12 to 14, wherein, The DCI further indicates the first and second transmit power control (TPC) commands for the first and second portions of the physical uplink channel transmission, respectively.

20. The wireless communication apparatus (312; 1300) of any of claims 12 to 14, wherein the first and second SRS resources indicated in the DCI may be replaced by first and second uplink transmission configuration indicator (TCI) states, wherein each of the first and second TCI states includes a reference signal index for spatial relation indication, a path loss reference signal index, a power control parameter set, or any combination thereof.

21. A method performed by a network node, the method comprising: The wireless communication device (312) sends (902B) two probe reference signal SRS resource sets, namely the configuration of the first and second SRS resource sets, each SRS resource set including one or more SRS resources, wherein the first and second SRS resource sets are associated with the first and second transmit and receive points (TRP), respectively. The wireless communication device (312) sends downlink control information (DCI) (904B), which schedules 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, wherein the first and second SRS resources are indicated in the DCI. According to the DCI, the first physical uplink channel transmission and the second physical uplink channel transmission are received (906B) from the wireless communication device (312), wherein the first physical uplink channel transmission and the second physical uplink channel transmission are transmitted synchronously to the first and second TRPs in one or more identical symbols, wherein the first physical uplink channel transmission and the second physical uplink channel transmission can be one of the following: (a) Layers 1 and 2 of the same physical uplink channel (b) First and second portions of the same physical uplink channel, wherein the first portion is transmitted in a first frequency domain resource and the second portion is transmitted in a second frequency domain resource. (c) First and second physical uplink channels, wherein the first physical uplink channel is transmitted in a first frequency domain resource, and the second physical uplink channel is transmitted in a second frequency domain resource. (d) First and second physical uplink channels associated with the same data transmission block, wherein the first physical uplink channel is encoded with a first redundancy version and the second physical uplink channel is encoded with a second redundancy version.

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

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. The method of any of claims 21 to 23, further comprising sending to the wireless communication device (312) a configuration of first and second power control parameter sets respectively associated with the first and second SRS resources, wherein the power control parameters include 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. The method of claim 24, wherein, The first and second portions of the PUSCH transmission are transmitted using first and second transmission powers, respectively, wherein the first and second transmission powers are calculated based on the first and second power control parameter sets, respectively.

26. The method according to any one of claims 21 to 25, wherein, The physical uplink channel transmission is the physical uplink shared channel (PUSCH) transmission.

27. The method of claim 22, wherein, The possible set of code points for each of the first and second SRI fields in the DCI includes code points used to indicate that no corresponding SRS resource has been selected.

28. The method according to any one of claims 21 to 25, wherein, The DCI further indicates the first and second transmission power control (TPC) commands for the first and second portions of the PUSCH transmission, respectively.

29. The method according to any one of claims 21 to 25, wherein, The first and second SRS resources indicated in the DCI can be replaced by first and second uplink transmission configuration indicator (TCI) states, wherein each of the first and second TCI states includes a reference signal index for spatial relationship indication, a path loss reference signal index, a power control parameter set, or any combination thereof.

30. A network node suitable for: The wireless communication device (312) sends (902B) two probe reference signal SRS resource sets, namely the configuration of the first and second SRS resource sets, each SRS resource set including one or more SRS resources, wherein the first and second SRS resource sets are associated with the first and second transmit and receive points (TRP), respectively. The wireless communication device (312) sends downlink control information (DCI) (904B), which schedules 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, wherein the first and second SRS resources are indicated in the DCI. According to the DCI, the first physical uplink channel transmission and the second physical uplink channel transmission are received (906B) from the wireless communication device (312), wherein the first physical uplink channel transmission and the second physical uplink channel transmission are transmitted synchronously to the first and second TRPs respectively in one or more identical symbols, wherein, The first physical uplink channel transmission and the second physical uplink channel transmission can be one of the following: (a) Layers 1 and 2 of the same physical uplink channel (b) First and second portions of the same physical uplink channel, wherein the first portion is transmitted in a first frequency domain resource and the second portion is transmitted in a second frequency domain resource. (c) First and second physical uplink channels, wherein the first physical uplink channel is transmitted in a first frequency domain resource, and the second physical uplink channel is transmitted in a second frequency domain resource. (d) First and second physical uplink channels associated with the same data transmission block, wherein the first physical uplink channel is encoded with a first redundancy version and the second physical uplink channel is encoded with a second redundancy version.

31. The network node as described in claim 30, wherein, The network node is further adapted to perform the method as described in any of claims 22 to 29.

32. A network node including processing circuitry (1004; 11004), said processing circuitry (1004; 11004) configured to cause the network node to: The wireless communication device (312) sends (902B) two probe reference signal SRS resource sets, namely the configuration of the first and second SRS resource sets, each SRS resource set including one or more SRS resources, wherein the first and second SRS resource sets are associated with the first and second transmit and receive points (TRP), respectively. The wireless communication device (312) sends downlink control information (DCI) (904B), which schedules 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, wherein the first and second SRS resources are indicated in the DCI. According to the DCI, the first physical uplink channel transmission and the second physical uplink channel transmission are received (906B) from the wireless communication device (312), wherein the first physical uplink channel transmission and the second physical uplink channel transmission are transmitted synchronously to the first and second TRPs respectively in one or more identical symbols, wherein, The first physical uplink channel transmission and the second physical uplink channel transmission can be one of the following: (a) Layers 1 and 2 of the same physical uplink channel (b) First and second portions of the same physical uplink channel, wherein the first portion is transmitted in a first frequency domain resource and the second portion is transmitted in a second frequency domain resource. (c) First and second physical uplink channels, wherein the first physical uplink channel is transmitted in a first frequency domain resource, and the second physical uplink channel is transmitted in a second frequency domain resource. (d) First and second physical uplink channels associated with the same data transmission block, wherein the first physical uplink channel is encoded with a first redundancy version and the second physical uplink channel is encoded with a second redundancy version.

33. The network node as described in claim 32, wherein, The processing circuitry (1004; 1104) is further configured to cause the network node to perform the method as described in any of claims 22 to 29.

34. A method performed by a wireless communication device (312) for uplink transmission to a cellular communication network, the method comprising: The wireless communication device (312) receives (806) an indication of path loss reference signals and power control parameter sets associated with each of two or more TCI states via one or more probe reference signals (SRS) resource indicators (SRIs) included in the downlink control information (DCI) that schedules one or more physical uplink shared channels (PUSCH), wherein each of the one or more SRIs is signaled to the wireless communication device (312) to be associated with one or more path loss reference signals and one or more power control parameter sets. The one or more PUSCHs are transmitted (808) on any of the following resources according to two or more Transport Configuration Indicators (TCI) states: (a) the same time-domain and frequency-domain resources; Or (b) the same time-domain resource but different frequency-domain resources, wherein transmitting (808) the one or more PUSCHs includes: The first portion of the one or more PUSCHs is transmitted using the first TCI state from one of the two or more TCI states; and The second part of the one or more PUSCHs is transmitted using the second TCI state from one of the two or more TCI states; The two or more TCI states are each associated with two or more different reference signals, wherein the first physical uplink channel transmission and the second physical uplink channel transmission can be one of the following: (a) Layers 1 and 2 of the same physical uplink channel (b) First and second portions of the same physical uplink channel, wherein the first portion is transmitted in a first frequency domain resource and the second portion is transmitted in a second frequency domain resource. (c) First and second physical uplink channels, wherein the first physical uplink channel is transmitted in a first frequency domain resource, and the second physical uplink channel is transmitted in a second frequency domain resource. (d) First and second physical uplink channels associated with the same data transmission block, wherein the first physical uplink channel is encoded with a first redundancy version and the second physical uplink channel is encoded with a second redundancy version.

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

36. The method of claim 34 or 35, wherein, The two or more reference signals are two or more downlink reference signals, each associated with a corresponding TCI state among the two or more TCI states.

37. The method of claim 36, wherein, 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).

38. The method of claim 34 or 35, wherein, The two or more reference signals are two or more probe reference signal (SRS) resources, each configured with a corresponding spatial relationship.

39. The method of claim 38, wherein, The downlink control information includes one or more SRS Resource Indicators (SRIs) that indicate the two or more SRS resources.

40. The method of claim 39, wherein, Each of the two or more SRS resources is associated with a corresponding reference signal through spatial relationship configuration.

41. The method of claim 40, wherein, The corresponding reference signals are: Synchronization Signal Block (SSB); Non-zero Power NZP Channel State Information Reference Signal (CSI-RS); Or another SRS.

42. The method of claim 39, wherein: The two or more SRS resources are associated with two or more corresponding reference signals; and The two or more corresponding reference signals are associated with two or more corresponding cell identities.

43. The method of claim 42, wherein, The two or more corresponding reference signals are two or more corresponding synchronization signal blocks (SSBs) or two or more corresponding non-zero power NZP channel state information reference signals (CSI-RS).

44. The method of claim 42 or 43, wherein, The two or more corresponding reference signals are associated with the two or more corresponding cell identities via fields in the TCI state configuration.

45. The method of claim 42, wherein, The two or more corresponding reference signals are two or more corresponding synchronization signal blocks (SSBs), and the two or more reference signals are configured to be associated with the two or more corresponding cell identities via the SSBs.

46. ​​The method of claim 34, wherein, Transmitting (808-1) the first portion of the one or more PUSCHs includes transmitting (808-1) the first portion of the one or more PUSCHs according to the power control parameter set associated with the first TCI state, and transmitting (808-2) the second portion of the one or more PUSCHs includes transmitting (808-2) the second portion of the one or more PUSCHs according to the power control parameter set associated with the second TCI state.

47. The method of any of claims 34 to 35, further comprising receiving (804) an instruction from a network node to transmit PUSCH using a spatial multiplexing scheme or a frequency multiplexing scheme.

48. The method of claim 47, wherein, Transmitting (808) the one or more PUSCHs includes: if the received indication is an indication to transmit PUSCH using a space division multiplexing scheme, then transmitting (808) the one or more PUSCHs on the same time domain and frequency domain resources; or when the received indication is an indication to transmit PUSCH using a frequency division multiplexing scheme, then transmitting (808) the one or more PUSCHs on the same time domain resources but on different frequency domain resources.

49. The method of claim 34, wherein, The one or more PUSCHs include two or more PUSCHs, and each of the two or more PUSCHs is scheduled via separate downlink control information.

Images