Patent Description:
The technology of the disclosure relates generally to enhancing reliability of Physical Uplink Shared Channel (PUSCH) transmissions.

NR uses CP-OFDM (Cyclic Prefix Orthogonal Frequency Division Multiplexing) in both Downlink (DL) (e.g., from a network node, a gNB, or a base station to a User Equipment (UE)) and Uplink (UL) (e.g., from a UE to a gNB). Discrete Fourier Transform (DFT) spread 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 each having a <NUM> duration. A subframe is further divided into multiple slots of equal duration, which may depend on specific subcarrier spacing. For subcarrier spacing of Δf=<NUM>, there is only one slot per subframe, and each slot consists of <NUM> OFDM symbols.

Data is typically scheduled in NR based on slots. An example is shown in <FIG> with a <NUM>-symbol slot, where the first two symbols contain Physical Downlink Control Channel (PDCCH) and the rest contains physical shared data channel, either PDSCH (Physical Downlink Shared Channel) or PUSCH (Physical Uplink Shared Channel).

NR can be configured to support different subcarrier spacing values. The supported subcarrier spacing values (also referred to as different numerologies) are given by Δf = (<NUM> × <NUM>µ) kHz where E {<NUM>,<NUM>,<NUM>,<NUM>,<NUM>}. Δf = <NUM>kHz is the basic subcarrier spacing. The slot durations at different subcarrier spacings is given by <MAT>.

In the frequency domain, a system bandwidth is divided into Resource Blocks (RBs), each corresponding to <NUM> contiguous subcarriers. The RBs are numbered starting with <NUM> from one end of the system bandwidth. The basic NR physical time-frequency resource grid is illustrated in <FIG>, where only one RB within a <NUM>-symbol slot is shown. One OFDM subcarrier during one OFDM symbol interval forms one Resource Element (RE).

In NR Rel-<NUM>, uplink data transmission can be dynamically scheduled using PDCCH. A UE first decodes uplink grants in PDCCH and then transmits data over PUSCH based on the decoded control information in the uplink grant such as modulation order, coding rate, uplink resource allocation, etc..

In dynamic scheduling of PUSCH, there is also a possibility to configure semi-persistent transmission of PUSCH using Configured Grants (CG). There are two types of CG based PUSCH defined in NR Rel-<NUM>. In CG type <NUM>, a periodicity of PUSCH transmission and a time domain offset are configured by Radio Resource Control (RRC). In CG type <NUM>, a periodicity of PUSCH transmission is configured by RRC and then the activation and release of the PUSCH transmission is controlled by Downlink Control Information (DCI), for example, with a PDCCH.

In NR, it is possible to schedule a PUSCH with time repetition, by the RRC parameter pusch-AggregationFactor (for dynamically scheduled PUSCH) and repK (for PUSCH with UL configured grant). In this case, the PUSCH is scheduled but transmitted in multiple adjacent slots (if the slots are available for UL) up until the number of repetitions as determined by the configured RRC parameter.

In the case of PUSCH with UL configured grant, the Redundancy Version (RV) sequence to be used is configured by the repK-RV field when repetitions are used. If repetitions are not used for PUSCH with UL configured grant, then the repK-RV field is absent.

In NR Release-<NUM>, there are two mapping types, Type A and Type B, applicable to PDSCH and PUSCH transmissions. Type A is usually referred to as slot-based while Type B transmissions may be referred to as non-slot-based or mini-slot-based.

Mini-slot transmissions can be dynamically scheduled and for NR Rel-<NUM>:.

Note that mini-slot transmissions in NR Rel-<NUM> may not cross a slot-boundary.

One of the <NUM> frequency hopping modes, inter-slot and intra-slot frequency hopping, can be configured by higher layer for PUSCH transmission in NR Rel-<NUM> in IE PUSCH-Config for dynamic transmission or IE configuredGrantConfig for type1 and type2 CGs.

Spatial relation is used in NR to refer to a relationship between an UL Reference Signal (RS) to be transmitted such as PUCCH/PUSCH DMRS (Demodulation Reference Signal) and another previously transmitted or received RS, which can be either a DL RS (CSI-RS (Channel State Information RS) or SSB (Synchronization Signal Block)) or an UL RS (SRS (Sounding Reference Signal)). This is defined from a UE perspective.

If an UL transmitted RS is spatially related to a DL RS, it means that the UE should transmit the UL RS in the opposite (reciprocal) direction from which it received the DL RS previously. More precisely, the UE should apply the "same" Transmit (Tx) spatial filtering configuration for the transmission of the UL RS as the Rx spatial filtering configuration the UE used to receive the spatially related DL RS previously. Herein, the terminology 'spatial filtering configuration' may refer to the antenna weights that are applied at either the transmitter or the receiver for data/control transmission/reception. Another way to describe this is that the same "beam" should be used to transmit the signal from the UE as was used to receive the previous DL RS signal. The DL RS is also referred as the spatial filter reference signal.

On the other hand, if a first UL RS is spatially related to a second UL RS, then the UE should apply the same Tx spatial filtering configuration for the transmission for the first UL RS as the Tx spatial filtering configuration used to transmit the second UL RS previously. In other words, same beam is used to transmit the first and second UL RSs, respectively.

Since the UL RS is associated with a layer of PUSCH or PUCCH transmission, it is understood that the PUSCH/PUCCH is also transmitted with the same TX spatial filter as the associated UL RS.

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

The Codebook based UL transmission is used in both NR and LTE for non-calibrated UEs and/or UL FDD (Frequency Division Duplex). Codebook based PUSCH is enabled in NR if higher layer parameter txConfig = codebook. For dynamically scheduled PUSCH and configured grant PUSCH type <NUM>, the Codebook based PUSCH transmission scheme can be summarized as follows:.

• the UE transmits one or two SRS resources (e.g., one or two SRS resources configured in the SRS resource set associated with the higher layer parameter usage of value 'CodeBook'). Note that in NR Rel-<NUM>/<NUM>, the number of SRS resource sets with higher layer parameter usage set to 'CodeBook' is limited to one (e.g., only one SRS resource set is allowed to be configured for the purposes of Codebook based PUSCH transmission). • the gNB determines a preferred Multiple-Input Multiple-Output (MIMO) transmit precoder for PUSCH (e.g., Transmit Precoding Matrix Indicator (TPMI)) from a codebook and the associated number of layers corresponding to the one or two SRS resources. • the gNB indicates a selected SRS resource via a <NUM>-bit 'SRS resource indicator' field if two SRS resources are configured in the SRS resource set. The 'SRS resource indicator' field is not indicated in DCI if only one SRS resource is configured in the SRS resource set. • The gNB indicates a TPMI and the associated number of layers corresponding to the indicated SRS resource (in case <NUM> SRS resources are used) or the configured SRS resource (in case of <NUM> SRS resource is used). TPMI and the number of PUSCH layers is indicated by the 'Precoding information and number of layers' field in DCI formats 0_1 and 0_2. The number of bits in the 'Precoding information and number of layers' for Codebook based PUSCH is determined as follows:.

∘<NUM> bits if <NUM> antenna port is used for PUSCH transmission. ∘ <NUM>, <NUM>, or <NUM> bits according to Table <NUM> for <NUM> antenna ports, according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank, and codebookSubset. That is, 'Precoding information and number of layers' field size takes values of <NUM>, <NUM>, and <NUM> bits if codebookSubset is set to 'fullyAndPartialAndNonCoherent', 'PartialAndNonCoherent', and 'NonCoherent', respectively.

∘ <NUM>, <NUM>, or <NUM> bits according to Table <NUM> for <NUM> antenna ports, according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank, and codebookSubset. That is, 'Precoding information and number of layers ' field size takes values of <NUM>, <NUM>, and <NUM> bits if codebookSubset is set to 'fullyAndPartialAndNonCoherent', 'PartialAndNonCoherent', and 'NonCoherent', respectively.

∘ <NUM> or <NUM> bits according to Table <NUM> for <NUM> antenna ports, according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank and codebookSubset. That is, 'Precoding information and number of layers' field size takes on values of <NUM> and <NUM> bits if codebookSubset is set to 'fullyAndPartialAndNonCoherent' and 'NonCoherent', respectively.

∘ <NUM> or <NUM> bits according to Table <NUM> for <NUM> antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank and codebookSubset. That is, 'Precoding information and number of layers ' field size takes on values of <NUM> and <NUM> bits if codebookSubset is set to 'fullyAndPartialAndNonCoherent' and 'NonCoherent', respectively.

• the UE performs PUSCH transmission using the TPMI and number of layers indicated. If one SRS resource is configured in the SRS resource set associated with the higher layer parameter usage of value 'CodeBook', then the PUSCH DMRS is spatially related to the most recent SRS transmission in this SRS resource. If two SRS resources are configured in the SRS resource set associated with the higher layer parameter usage of value 'CodeBook', then the PUSCH DMRS is spatially related to the most recent SRS transmission in the SRS resource indicated by the 'SRS resource indicator' field.

The TPMI is used to indicate the precoder to be applied over the layers {<NUM>. v-<NUM>} and that corresponds to the SRS resource selected by the SRI when multiple SRS resources are configured, or if a single SRS resource is configured TPMI is used to indicate the precoder to be applied over the layers {<NUM>. v-<NUM>} and that corresponds to the SRS resource. The transmission precoder is selected from the uplink codebook that has a number of antenna ports equal to higher layer parameter nrofSRS-Ports in SRS-Config.

Non-Codebook based UL transmission is available in NR, enabling reciprocity-based UL transmission. By assigning a DL CSI-RS to the UE, the UE can measure and deduce suitable precoder weights for PUSCH transmission of up to four spatial layers. The candidate precoder weights are transmitted using up to four single-port SRS resources corresponding to the spatial layers. Subsequently, the gNB indicates the transmission rank and multiple SRS resource indicators, jointly encoded using <MAT>, where N_"SRS" indicates the number of configured SRS resources, and L_max is the maximum number of supported layers for PUSCH. Non-Codebook based PUSCH in NR is enabled if higher layer parameter txConfig = noncodebook. Table <NUM> shows the mapping of codepoints of the SRI field to SRI(s) for different number of N_"SRS" when Lmax = <NUM>.

Note that in NR Rel-<NUM>/<NUM>, the number of SRS resource sets with higher layer parameter usage set to 'nonCodeBook' is limited to one (e.g., only one SRS resource set is allowed to be configured for the purposes of non-Codebook based PUSCH transmission). The maximum number of SRS resource sets that can be configured for non-codebook based uplink transmission is <NUM>.

In NR, for non-codebook based PUSCH, the UE performs a one-to-one mapping from the indicated SRI(s) to the indicated DM-RS port(s) and their corresponding PUSCH layers {<NUM>. v-<NUM>} in increasing order. The UE shall transmit PUSCH using the same antenna ports as the SRS port(s) in the SRS resource(s) indicated by SRI(s), where the SRS port in (i+<NUM>)-th SRS resource in the SRS resource set is indexed as pi = <NUM> +i.

In NR Release <NUM>, PUSCH repetition enhancements were made for both PUSCH type A and type B for the purposes of further latency reduction (e.g., for Rel-<NUM> Ultra-Reliable Low-Latency Communication (URLLC)).

In NR Rel-<NUM>, the number of aggregated slots for both dynamic grant and configured grant Type <NUM> are RRC configured. In NR Rel-<NUM>, this was enhanced so that the number of repetitions can be dynamically indicated (e.g., change from one PUSCH scheduling occasion to next PUSCH scheduling occasion). That is, in addition to the starting symbol S, and the length of the PUSCH L, a number of nominal repetitions K are signaled as part of Time-Domain Resource Allocation (TDRA). Furthermore, the maximum number of aggregated slots was increased to K=<NUM> to account for DL heavy Time Division Duplex (TDD) patterns. Inter-slot and intra-slot hopping can be applied for Type A repetition. The number of repetitions K is nominal since some slots may be DL slots and are then skipped for PUSCH transmissions. So, K is the maximal number of repetitions possible.

PUSCH repetition Type B applies both to dynamic and configured grants. Type B PUSCH repetition can cross the slot boundary in Rel-<NUM>. When scheduling a transmission with PUSCH repetition Type B, in addition to the starting symbol S, and the length of the PUSCH L, a number of nominal repetitions K are signaled as part of TDRA in NR Rel-<NUM>. Inter-slot frequency hopping and inter-repetition frequency hopping can be configured for Type B repetition. To determine the actual time domain allocation of Type B PUSCH repetitions, a two-step process is used:.

Although the term 'PUSCH repetition' is used in the disclosure, it can be interchangeably used with other terms such as 'PUSCH transmission occasion'.

In NR Rel-<NUM>/<NUM>, when PUSCH is repeated according to PUSCH repetition Type A or Type B, the PUSCH is limited to a single transmission layer.

The channel encoder can be controlled by the RV. In NR, an information payload can be encoded with four different RVs, to allow for incremental redundancy decoding. The redundancy version to be applied on the nth transmission occasion of the TB, where n = <NUM>, <NUM>,. K -<NUM>, is determined according to table below.

<CIT> describes a technique for signaling information transmission. A method comprises receiving signaling information, and determining channel state information of M physical uplink channels based on the signaling information, wherein M is a positive integer greater than <NUM>.

<CIT> describes a power control method comprising determining Y pieces of spatial parameter information associated with uplink transmission, and determining the sending power of X times of repeated transmission of uplink transmission according to the power control parameters associated with the Y pieces of space parameter information, wherein X and Y are integers greater than or equal to <NUM>.

<CIT> describes a technique for beam indication for uplink transmission in a wireless communication system from the perspective of a UE. The method includes: the UE is configured with a first serving cell, and is indicated to activate the first serving cell and an active UL BWP, wherein the first serving cell or the active UL BWP is not configured with PUCCH resources. The UE does not expect to be indicated to transmit a first PUSCH in the first serving cell or the active UL BWP in RRC connected mode, wherein the first PUSCH is scheduled by a DCI format without spatial relation field.

Embodiments disclosed herein include methods for enhancing Physical Uplink Shared Channel (PUSCH) reliability.

The scope of the present invention is defined by the scope of the appended claims.

Core Network Node: As used herein, a "core network node" is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing a Access and Mobility Function (AMF), a UPF, a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like.

In some embodiments, a TRP may be either a network node, a radio head, a spatial relation, or a Transmission Configuration Indicator (TCI) state. A TRP may be represented by a spatial relation, a SRS resource set or a TCI state in some embodiments. In some embodiments, a TRP may a part of the gNB transmitting and receiving radio signals to/from UE according to physical layer properties and parameters inherent to that element.

There currently exist certain challenge(s). For dynamically scheduled Physical Uplink Shared Channel (PUSCH) and configured grant PUSCH type <NUM>, existing NR rel-<NUM>/<NUM> codebook based PUSCH only allows a single Sounding Reference Signal (SRS) resource to define the spatial relation for PUSCH Demodulation Reference Signal (DMRS). As a result, it may not be efficient to use multiple Transmission/Reception Points (TRPs) for reception, especially in a Frequency Range (FR) above <NUM> (FR2), wherein the UL Transmit (TX) beams can be narrow in beam-width.

As shown in the example of <FIG>, existing NR rel-<NUM>/<NUM> codebook based PUSCH is suitable for single TRP based reception, where the PUSCH transmission is targeted towards a single TRP. That is, the PUSCH DMRS is spatially related to the latest SRS transmission in the SRS resource indicated by a single SRI. When a number of PUSCH repetitions are either configured (e.g., via pusch-AggregationFactor for dynamically scheduled PUSCH or via repK for PUSCH with UL configured grant) or dynamically indicated (e.g., as part of TDRA), the same spatial relation for PUSCH DMRS is assumed for all the PUSCH repetitions. Since the same spatial relation only targets a single TRP, it unsuitable for multi-TRP reception, whereby a better reliability may be achieved as a result of spatial diversity.

Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Embodiments disclosed herein are related to PUSCH transmission with a plurality of repetitions, wherein multiple sets of spatial relations are assumed for PUSCH DMRS in different subsets of the plurality of repetitions. For PUSCH transmission with multiple repetitions, signaling/indication methods are disclosed to allow more than one spatial relation to be used in different subset of the plurality of PUSCH repetitions. For codebook based PUSCH transmission, signaling/configuration aspects related to how to indicate multiple SRS Resource Indicators (SRIs) and how to indicate multiple Transmit Precoding Matrix Indicators (TPMIs) are disclosed. For non-codebook based PUSCH transmission, signaling/configuration aspects related to how to indicate multiple SRIs with different spatial relations being used in different subset of repetitions with single or multiple PUSCH layer(s) per repetition for PUSCH are disclosed.

There are, proposed herein, various embodiments which may address one or more of the issues disclosed herein. Embodiments disclosed herein include methods for enhancing PUSCH reliability by transmitting from a wireless device (e.g., a UE) a number of PUSCH repetitions to multiple TRPs in a network node (e.g., a base station) and receiving by the network node via the multiple TRPs the number of PUSCH repetitions.

In one aspect, a method performed by the wireless device for enhancing PUSCH reliability is provided. The method includes receiving an instruction(s) (e.g., via RRC) from the network node for transmitting a plurality of PUSCH repetitions to multiple TRPs. The method also includes transmitting the plurality of PUSCH repetitions to the multiple TRPs in accordance to the instruction(s) received from the network node.

In another aspect, a method performed by the base station for enhancing PUSCH reliability is provided. The method includes providing an instruction(s) (e.g., via RRC) to the wireless device for transmitting a plurality of PUSCH repetitions to multiple TRPs in the base station via codebook based PUSCH transmission or non-codebook based PUSCH transmission. The method also includes receiving the plurality of PUSCH repetitions via the multiple TRPs based on the instruction(s) provided to the wireless device.

Certain embodiments may provide one or more of the following technical advantage(s).

<FIG> illustrates one example of a cellular communications system <NUM> in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system <NUM> is a <NUM> system (5GS) including a NR RAN. In this example, the RAN includes base stations <NUM>-<NUM> and <NUM>-<NUM>, which in <NUM> NR are referred to as gNBs (e.g., LTE RAN nodes connected to 5GC, which are referred to as gn-eNBs), controlling corresponding (macro) cells <NUM>-<NUM> and <NUM>-<NUM>. The base stations <NUM>-<NUM> and <NUM>-<NUM> are generally referred to herein collectively as base stations <NUM> and individually as base station <NUM>. Likewise, the (macro) cells <NUM>-<NUM> and <NUM>-<NUM> are generally referred to herein collectively as (macro) cells <NUM> and individually as (macro) cell <NUM>. The RAN may also include a number of low power nodes <NUM>-<NUM> through <NUM>-<NUM> controlling corresponding small cells <NUM>-<NUM> through <NUM>-<NUM>. The low power nodes <NUM>-<NUM> through <NUM>-<NUM> can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells <NUM>-<NUM> through <NUM>-<NUM> may alternatively be provided by the base stations <NUM>. The low power nodes <NUM>-<NUM> through <NUM>-<NUM> are generally referred to herein collectively as low power nodes <NUM> and individually as low power node <NUM>. Likewise, the small cells <NUM>-<NUM> through <NUM>-<NUM> are generally referred to herein collectively as small cells <NUM> and individually as small cell <NUM>. The cellular communications system <NUM> also includes a core network <NUM>, which in the 5GS is referred to as the <NUM> core (5GC). The base stations <NUM> (and optionally the low power nodes <NUM>) are connected to the core network <NUM>.

As previously mentioned, for dynamically scheduled PUSCH and configured grant PUSCH type <NUM>, existing NR rel-<NUM>/<NUM> codebook based PUSCH only allows a single SRS resource to define the spatial relation for PUSCH DMRS. As a result, it may not be efficient to use multiple TRPs for reception, especially in a frequency range (FR) above <NUM> (FR2), wherein the UL TX beams can be narrow in beam-width. In this regard, to enhance PUSCH reliability, methods for enhancing PUSCH reliability are disclosed herein.

In one aspect, <FIG> is a flowchart of an exemplary method performed by the wireless device for enhancing PUSCH reliability. The method includes one or more of the following: receiving (<NUM>) an instruction(s) (e.g., via RRC) from the network node for transmitting a plurality of PUSCH repetitions to multiple TRPs, and transmitting (<NUM>) the plurality of PUSCH repetitions to the multiple TRPs in accordance to the instruction(s) received from the network node.

In another aspect, <FIG> is a flowchart of an exemplary method performed by the base station for enhancing PUSCH reliability. The method includes one or more of the following: providing (<NUM>) an instruction(s) (e.g., via RRC) to the wireless device for transmitting a plurality of PUSCH repetitions to multiple TRPs in the base station via codebook based PUSCH transmission or non-codebook based PUSCH transmission, and receiving (<NUM>) the plurality of PUSCH repetitions via the multiple TRPs based on the instruction(s) provided to the wireless device.

Specific embodiments of the present disclosure can enhance PUSCH reliability in accordance with codebook based PUSCH transmission or non-codebook based PUSCH transmission. In this regard, <FIG> is a flowchart of a method according to the present invention, performed by a wireless device for enhancing PUSCH reliability according to two SRS resource sets and based on codebook based PUSCH transmission or non-codebook based PUSCH transmission. Note that the various aspects of the process of <FIG> are illustrated in <FIG>, which are described below.

According to <FIG>, the wireless device receives a configuration of two SRS resource sets that includes a first SRS resource set and a second SRS resource set (step <NUM>). The wireless device also receives an instruction for transmitting a plurality of PUSCH repetitions according to the two SRS resource sets (step <NUM>). In a non-limiting example, the wireless device is configured to receive the instruction to transmit the PUSCH repetitions based on codebook based PUSCH transmission (step <NUM>-<NUM>) or non-codebook based PUSCH transmission (step <NUM>-<NUM>). The wireless device may also receive multiple spatial relations each associated with one of multiple SRS resources in a respective one of the two SRS resource sets (step <NUM>-<NUM>).

Accordingly, the wireless device transmits the PUSCH repetitions to the multiple network nodes based on the received instruction (step <NUM>). In one aspect, the wireless device is configured to transmit a first group of the PUSCH repetitions according to the first SRS resource set and a second group of the PUSCH repetitions according to the second SRS resource set (step <NUM>-<NUM>). Alternatively, the wireless device is configured to transmit the PUSCH repetitions according the first SRS resource and the second SRS resource set (step <NUM>-<NUM>). Specifically, the wireless device may transmit each of the PUSCH transmissions based on a single spatial layer (step <NUM>-2a) or multiple spatial layers (step <NUM>-2b). The wireless device may transmit the PUSCH repetitions based on a first spatial relation associated with one of the SRS resources in the first SRS resource set and a second spatial relation associated with one of the SRS resources in the second SRS resource set (step <NUM>-<NUM>). In a non-limiting example, the wireless device can transmit the first group of the PUSCH repetitions on even numbered PUSCH repetitions and the second group of the PUSCH repetitions on odd numbered PUSCH repetitions (step <NUM>-<NUM>). Alternatively, the wireless device may transmit the first group of PUSCH repetitions on a first number of consecutive PUSCH repetitions and the second group of PUSCH repetitions on a second number of consecutive PUSCH repetitions subsequent to the first number of consecutive PUSCH repetitions (step <NUM>-<NUM>).

The wireless device may also apply an RV sequence to each of the PUSCH repetitions (step <NUM>). The wireless device may also receive the instruction for transmitting the PUSCH repetitions according to one of the two SRS resource sets (step <NUM>) and transmit the PUSCH repetitions according to the one of the two SRS resource sets (step <NUM>). In this regard, the wireless device may switch between transmitting the PUSCH repetitions according to the two SRS resource sets and according to the one of the two SRS resource sets (step <NUM>).

<FIG> is a flowchart of a method according to the present invention, performed by a base station for enhancing PUSCH reliability according to two SRS resource sets and based on codebook based PUSCH transmission or non-codebook based PUSCH transmission. Note that the various aspects of the process of <FIG> are illustrated in <FIG>, which are described below.

According to <FIG>, the base station transmits, to a wireless device, a configuration of two SRS resource sets that includes a first SRS resource set and a second SRS resource set (step <NUM>). The base station provides an instruction to the wireless device for transmitting a plurality of PUSCH repetitions according to the two SRS resource sets (step <NUM>). In a non-limiting example, the base station is configured to provide the instruction to transmit the PUSCH repetitions based on codebook based PUSCH transmission (step <NUM>-<NUM>) or non-codebook based PUSCH transmission (step <NUM>-<NUM>). The base station may also provide multiple spatial relations each associated with one of multiple SRS resources in a respective one of the two SRS resource sets (step <NUM>-<NUM>).

Accordingly, the base station receives the PUSCH repetitions based on the instruction provided to the wireless device (step <NUM>). In one aspect, the base station is configured to receive a first group of the PUSCH repetitions according to the first SRS resource set and a second group of the PUSCH repetitions according to the second SRS resource set (step <NUM>-<NUM>). Alternatively, the base station is configured to receive the PUSCH repetitions according to the first SRS resource and the second SRS resource set (step <NUM>-<NUM>). Specifically, the base station may receive each of the PUSCH transmissions based on a single spatial layer (step <NUM>-2a) or multiple spatial layers (step <NUM>-2b). The base station may receive the PUSCH repetitions based on a first spatial relation associated with one of the SRS resources in the first SRS resource set and a second spatial relation associated with one of the SRS resources in the second SRS resource set (step <NUM>-<NUM>). In a non-limiting example, the base station can receive the first group of PUSCH repetitions on even numbered PUSCH repetitions and the second group of PUSCH repetitions on odd numbered PUSCH repetitions (step <NUM>-<NUM>). Alternatively, the base station may receive the first group of PUSCH repetitions on a first number of consecutive PUSCH repetitions and the second group of PUSCH repetitions on a second number of consecutive PUSCH repetitions subsequent to the first number of consecutive PUSCH repetitions (step <NUM>-<NUM>).

The base station may also apply an RV sequence to each of the PUSCH repetitions (step <NUM>). The base station may also provide the instruction for transmitting the PUSCH repetitions according to one of the two SRS resource sets (step <NUM>) and receive the PUSCH repetitions according to the one of the two SRS resource sets (step <NUM>). In this regard, the base station may dynamically switch between receiving the PUSCH repetitions according to the two SRS resource sets and according to the one of the two SRS resource sets (step <NUM>).

Specific embodiments for enhancing PUSCH reliability between the wireless device and the network node are now described in detail below.

In one embodiment, a higher layer configuration (e.g., via Radio Resource Control (RRC)) from a network node (e.g., base station) to a UE can be used to configure the following mode of operations:.

wherein more than one spatial relations for PUSCH DMRS is assumed for different PUSCH repetitions.

The second mode enables PUSCH transmission towards multiple TRPs. <FIG> shows an example (e.g., <NUM>, <NUM>, <NUM>, <NUM>) where two SRS resources are configured in an SRS resource set. Since there are two TRPs in this example, the network will determine the preferred TPMI corresponding to each SRS resource. The network then indicates the two TPMIs (TPMI1 and TPMI2) corresponding to the two SRS resources. In this case the UE can have two different spatial relations for PUSCH DMRS to be used across different repetitions:.

These two spatial relations for PUSCH DMRS can be used to direct PUSCH transmission towards TRPs <NUM> and <NUM> in different PUSCH repetition instances. As shown in the example of <FIG>, the first spatial relation can be used in even numbered PUSCH repetitions while the second spatial relation can be used in odd numbered PUSCH repetitions (e.g., <NUM>-<NUM>, <NUM>-<NUM>). Alternatively (e.g., <NUM>-<NUM>, <NUM>-<NUM>), the first spatial relation can be applied to the first two repetitions and the second spatial relations can be applied to the next two repetitions and this sequence may be repeated until the last repetition is reached. Note that the PUSCH repetitions as illustrated in <FIG> can be either nominal PUSCH repetitions or actual PUSCH repetitions.

It should be noted that when the number of SRS resources configured per SRS resource set is equal to the number of different spatial relations for PUSCH DMRS to be alternated across different PUSCH repetitions, SRI does not need to be indicated in Downlink Control Information (DCI). For instance, in the example of <FIG>, there are two different spatial relations for PUSCH DMRS, which are alternated across different PUSCH repetitions and there are two SRS resources configured per SRS resource set. Hence, in some embodiments, when this condition is met, then SRI does not need to be indicated to the UE and 'SRS resource indicator' field can be absent from DCI.

In the more general case, the number of SRS resources configured per SRS resource set can be NSRS and the number of different spatial relations for PUSCH DMRS to be alternated across different PUSCH repetitions can be Q, where NSRS > Q. In this case, Q SRS resources need to be selected out of the NSRS SRS resources, and there are ( <MAT>) such combinations possible. Hence, in one embodiment, the field size of 'SRS resource indicator'field is given by <MAT> for Codebook based PUSCH. Table <NUM> shows an example with NSRS = <NUM> and Q = <NUM>, where the 'SRS resource indicator'field consists of <NUM> bits and each codepoint in the bit field indicates two SRIs which are used to provide two different spatial relations for PUSCH DMRS to be alternated across different PUSCH repetitions.

A different number of SRIs are indicated by different codepoints in the SRI field, which is used to determine the number of different spatial relations for PUSCH DMRS to be alternated across different PUSCH repetitions. For instance, if a codepoint in the SRI field indicates a single SRS resource, then a single spatial relation associated with the single SRS resource is used for PUSCH DMRS across all the PUSCH repetitions. On the other hand, if a codepoint in the SRI field indicates multiple SRS resources, then multiple spatial relations associated with the multiple SRS resources are used for PUSCH DMRS across different PUSCH repetitions.

In some scenarios, the UE may be served with different types of traffic (e.g., URLLC traffic vs eMBB traffic). In these scenarios, it may be beneficial to dynamically switch between multi-TRP based PUSCH reception and single-TRP based PUSCH reception. That is, switching between the following modes may be supported dynamically via information in DCI:.

In one embodiment, a single bit in the 'SRS resource indicator' field in DCI is used to dynamically switch between the first mode (e.g., single-TRP mode) and the second mode (e.g., multi-TRP mode). <FIG> shows an example, wherein the most significant bit SL-<NUM> of the 'SRS resource indicator' field is used to dynamically switch between the first mode and the second mode. In the example, the first mode and the second mode are indicated to the UE when the most significant bit is set to values of SL- <NUM> = <NUM> and SL-<NUM> =<NUM>, respectively. If the first mode is indicated to the UE, the remaining bits SL-<NUM>, SL-<NUM>,. , S<NUM>, S<NUM> are used to indicate a single SRI to be used to determine spatial relation for PUSCH DMRS. If the second mode is indicated to the UE, the remaining bits SL-<NUM>, SL-<NUM>,. , S<NUM>, S<NUM> are used to indicate a combination of multiple SRIs to be used to determine spatial relations for PUSCH DMRS.

In an alternative embodiment, an indication of whether the first mode (e.g., single-TRP based PUSCH repetition) or second mode (e.g., multi-TRP based PUSCH repetition) should be used by the UE can be indicated as part of a row in the TDRA table. This is advantageous as whether to use single-TRP or multi-TRP based repetitions can be indicated along with the number of nominal repetitions K in a particular row of the TDRA table. For instance, two rows in the TDRA table can be configured with K=<NUM> with one row being configured for single-TRP based PUSCH repetition while the other row being configured for multi-TRP based PUSCH repetition. Thus, by dynamically indicating these two different rows in the TDRA table via the TDRA field in DCI, one can switch between single-TRP based PUSCH repetition and multi-TRP based PUSCH repetition.

In another alternative embodiment, a number X of different spatial relations for PUSCH DMRS to be used across different PUSCH repetitions is higher layer configured to the UE (e.g., via RRC signaling). The DCI then contains X different 'SRS resource indicator' fields with each such field corresponding to PUSCH transmission towards a different TRP. The X different 'SRS resource indicator' fields can be used to independently indicate X different SRS resources to be used by the UE to derive the spatial relations for PUSCH DMRS corresponding to X different TRPs.

In an alternative embodiment, a single SRI field in DCI is split into X different subfield with each subfield indicating an SRI for each TRP. In some embodiments, the number of subfields in the SRI field can be dependent on a higher layer parameter or another field in DCI. For example, depending on a higher layer parameter configuration (e.g., RRC configuration), the single SRI field in DCI may consist of a single subfield (e.g., X=<NUM>) or multiple subfields (e.g., X><NUM>).

In yet another embodiment, two spatial relations may be configured for an SRS resource. Each of the two spatial relations is associated with one TRP. When the SRS resource is selected by the SRI field in a DCI scheduling a PUSCH, and PUSCH repetition is also indicated, PUSCH repetition would be performed over the two TRPs associated with the two spatial relations. The SRI may also point to two sets of PUSCH power control parameters, one for each of the two spatial relations.

In another embodiment (e.g., <NUM>, <NUM>), the Redundancy Version (RV) sequence defined in Rel-<NUM>/<NUM> (shown in Table <NUM>) may be applied in a per TRP (e.g., per SRS resource or per SRS spatial relation) basis. A RV offset between two TRPs may be configured by RRC.

In yet another embodiment, multiple SRS resource sets may be configured by RRC for a UE for Codebook based PUSCH transmission. Each SRS resource set may contain one or more SRS resource each with one SRS port. One or more SRS resource sets may be dynamically indicated in DCI together with one or more SRS resources in the SRS resource set to a UE. For example, if two SRS resource sets are configured, either the first SRS resource set, the second SRS resource set, or both the first and the second SRS resource sets may be indicated to the UE. When both SRS resource sets are indicated, the UE would transmit the PUSCH according to the first SRS resource set (e.g., according to the spatial relation associated with the first SRS resource set) in the first PUSCH transmission occasion and according to the second SRS resource set (e.g., according to the spatial relation associated with the second SRS resource set) in the second PUSCH transmission occasion.

As shown in <FIG>, for multi-TRP based PUSCH repetition, multiple TPMIs need to be indicated. It is assumed that the number of SRS ports in different SRS resources is the same.

In one embodiment, the multiple TPMIs that need to be indicated to the UE are jointly encoded using the same 'Precoding information and number of layers' field. An example is shown in Table <NUM> below where two TPMIs are jointly indicated. In one variant of the embodiment, the same number of spatial layers is associated with each TPMI (e.g., both TPMI1 and TPMI2 have a single spatial layer). In an alternative embodiment, different number of spatial layers can be associated with each TPMI (e.g., TPMI1 has <NUM> spatial layers while TPMI2 has a single spatial layer).

In an alternate embodiment, additional 'Precoding information and number of layers' fields are added to the DCI to independently indicate the TPMIs corresponding to different TRPs. If a number X of different spatial relations for PUSCH DMRS to be used across different PUSCH repetitions is higher layer configured to the UE (e.g., via RRC signaling), then DCI then contains X different 'Precoding information and number of layers' fields with each such field corresponding to PUSCH transmission towards a different TRP. In some variants of this embodiment, the number of layers indicated by each of these fields needs to be identical while the TPMIs indicated can be different.

In another embodiment, at least one Phase Tracking Reference Signal (PTRS) port is associated with a DMRS layer(s) corresponding to each of the multiple TPMIs indicated to the UE. For example, if two TPMIs are indicated to the UE, the UE will transmit two PTRS ports. Specifically, the UE may transmit a first of the two PTRS port corresponds to the DMRS layer corresponding to the first TPMI and a second of the two PTRS port corresponds to the DMRS layer corresponding to the second TPMI.

In case of non-codebook based transmission, an L-layer transmission with repetition over Q TRPs needs to have Q subsets of L out of NSRS SRS resources. In one embodiment, when multi-TRP transmission is indicated, the SRS resource indicator is extended from <MAT> in the single-TRP case (i.e., from what is currently supported in NR) to Q times <MAT> in the multi-TRP case. However, this may lead to ambiguity since the number of layers is jointly encoded with the SRS resource subset for each TRP. Since a repetition should have the same number of spatial layers, a better option is to jointly encode the number of spatial layers with multiple SRS resource sets. In another embodiment, this is done by joint encoding using <MAT>. This assumes a pre-defined rule of transmission of the different sets (e.g., a lexicographic order). Alternatively, if desired to also signal an explicit order of transmission to the different TRPs, the joint encoding can take the order into account using <MAT>.

In some embodiments (e.g., <NUM>-2a, <NUM>-2a, <NUM>-2a, <NUM>-2a), the maximum number of spatial layers per PUSCH repetition is limited to <NUM> spatial layer. Assume that the number of different spatial relations for PUSCH DMRS to be alternated across different PUSCH repetitions is denoted by Q. Then, all PUSCH repetitions using the Q alternating spatial relations is limited to a single PUSCH layer. In this embodiment, the UE maps the indicated SRI(s) the same DM-RS port and its corresponding PUSCH layer <NUM> in all the repetitions. That is, the SRS port in the multiple SRS resources in the SRS resource set indicated via the SRI field is in indexed as p_i=<NUM> irrespective of i. This embodiment applies to non-codebook based PUSCH transmissions with repetition.

In another embodiment (e.g., <NUM>-2b, <NUM>-2b, <NUM>-2b, <NUM>-2b), the maximum number of layers per PUSCH repetition is limited to L layers, wherein the value of L may represent a UE capability (e.g., whether a UE supports two PUSCH layers (e.g., L=<NUM>) per repetition is reported as part of UE capability). In this embodiment, the SRS resources in an SRS resource set are grouped into two different SRS resource groups. An example is shown in <FIG>. The SRS resources <NUM> and <NUM> in SRS resource group <NUM>, which are indicated via the SRI field and corresponding spatial relations, are used for transmitting up to L=<NUM> layers in the 1st PUSCH transmission occasion. Similarly, the SRS resources <NUM> and <NUM> in SRS group <NUM>, which are indicated via the SRI field and corresponding spatial relations, are used for transmitting up to L=<NUM> layers in the 2nd PUSCH transmission occasion. In some embodiments, the number of SRS resources in each SRS resource group indicated via SRI field should be identical in order to support the same number of layers transmitted in each repetition. For example, if an SRI indicates <NUM> SRS resources, then there must be <NUM> SRS resources belonging to each SRS resource group. Similarly, if SRI indicates <NUM> SRS resources, then there must be <NUM> SRS resource belonging to each SRS resource group. If SRI indicates only a single SRS resource, it may correspond to a single layer PUSCH transmission using the spatial relation of indicated SRS resource in all the repetitions. In some embodiments, the SRS group is configured to a SRS resource by including an SRS group ID per SRS resource configuration.

Although the example in <FIG> shows the 1st group of SRS resources and 2nd group of SRS resources being used for PUSCH transmission in 1st and 2nd transmission occasions respectively, other patterns may also be possible. For instance, the 1st group of SRS resources may be used for PUSCH transmission in the 1st and 2nd transmission occasions, while the 2nd group of SRS resources may be used for PUSCH transmission in the 3rd and 4th transmission occasions. The same pattern may be repeated if more than <NUM> transmission occasions are configured or indicated for PUSCH. In the example embodiment in <FIG>, even though two SRS resource groups are presented, the idea can be equally presented with two SRS resource sets in place of two SRS resource groups (e.g., <NUM>-<NUM>, <NUM>-<NUM>).

In another embodiment, one PTRS port is associated with each SRS resource group. For example, if the UE selects a first set of layers of PUSCH on SRS resources in a first SRS group for transmitting a first PUSCH, but transmits a second PUSCH or a second set of layers of a PUSCH on SRS resources in a second SRS group, the UE will transmit two PTRS ports, one per SRS resource group. If the UE selects layers from a single SRS group, the UE transmits only a single PTRS port.

In some further embodiments, for codebook based PUSCH transmission, a single SRS resource set with two SRS resources, each associated with a TRP, may be configured for a UE. For non-codebook based PUSCH transmission, two SRS resource sets (e.g., <NUM>, <NUM>), each associated with a TRP, may be configured for a UE. To support dynamic switching between PUSCH transmission over a single TRP and two TRPs, a bit filed in DCI may be used for the purpose. In case of codebook based PUSCH transmission, two SRS resources may be indicated for PUSCH transmission to two TRPs. For non-codebook based transmission, two SRS resource sets may be indicated for PUSCH transmission to two TRPs (e.g., <NUM>, <NUM>).

<FIG> is a schematic block diagram of a radio access node <NUM> according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The radio access node <NUM> may be, for example, a base station <NUM> or <NUM> or a network node that implements all or part of the functionality of the base station <NUM> or gNB described herein. As illustrated, the radio access node <NUM> includes a control system <NUM> that includes one or more processors <NUM> (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory <NUM>, and a network interface <NUM>. The one or more processors <NUM> are also referred to herein as processing circuitry. In addition, the radio access node <NUM> may include one or more radio units <NUM> that each includes one or more transmitters <NUM> and one or more receivers <NUM> coupled to one or more antennas <NUM>. The radio units <NUM> may be referred to or be part of radio interface circuitry. In some embodiments, the radio unit(s) <NUM> is external to the control system <NUM> and connected to the control system <NUM> via, e.g., a wired connection (e.g., an optical cable). However, in some other embodiments, the radio unit(s) <NUM> and potentially the antenna(s) <NUM> are integrated together with the control system <NUM>. The one or more processors <NUM> operate to provide one or more functions of a radio access node <NUM> as described herein (e.g., one or more functions of a network node as described above, for example, with reference to <FIG>). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory <NUM> and executed by the one or more processors <NUM>.

As used herein, a "virtualized" radio access node is an implementation of the radio access node <NUM> in which at least a portion of the functionality of the radio access node <NUM> is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the radio access node <NUM> may include the control system <NUM> and/or the one or more radio units <NUM>, as described above. The control system <NUM> may be connected to the radio unit(s) <NUM> via, for example, an optical cable or the like. The radio access node <NUM> includes one or more processing nodes <NUM> coupled to or included as part of a network(s) <NUM>. If present, the control system <NUM> or the radio unit(s) are connected to the processing node(s) <NUM> via the network <NUM>. Each processing node <NUM> includes one or more processors <NUM> (e.g., CPUs, ASICs, FPGAs, and/or the like), memory <NUM>, and a network interface <NUM>.

In this example, functions <NUM> of the radio access node <NUM> described herein (e.g., one or more functions of a network node as described above, for example, with reference to <FIG>) are implemented at the one or more processing nodes <NUM> or distributed across the one or more processing nodes <NUM> and the control system <NUM> and/or the radio unit(s) <NUM> in any desired manner. In some particular embodiments, some or all of the functions <NUM> of the radio access node <NUM> described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) <NUM>. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) <NUM> and the control system <NUM> is used in order to carry out at least some of the desired functions <NUM>. Notably, in some embodiments, the control system <NUM> may not be included, in which case the radio unit(s) <NUM> communicate directly with the processing node(s) <NUM> via an appropriate network interface(s).

In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of radio access node <NUM> or a node (e.g., a processing node <NUM>) implementing one or more of the functions <NUM> of the radio access node <NUM> in a virtual environment according to any of the embodiments described herein is provided (e.g., one or more functions of a network node as described above, for example, with reference to <FIG>).

The module(s) <NUM> provide the functionality of the radio access node <NUM> described herein (e.g., one or more functions of a network node as described above, for example, with reference to <FIG>).

<FIG> is a schematic block diagram of a wireless communication device <NUM> according to some embodiments of the present disclosure. As illustrated, the wireless communication device <NUM> includes one or more processors <NUM> (e.g., CPUs, ASICs, FPGAs, and/or the like), memory <NUM>, and one or more transceivers <NUM> each including one or more transmitters <NUM> and one or more receivers <NUM> coupled to one or more antennas <NUM>. The transceiver(s) <NUM> includes radio-front end circuitry connected to the antenna(s) <NUM> that is configured to condition signals communicated between the antenna(s) <NUM> and the processor(s) <NUM>, as will be appreciated by on of ordinary skill in the art. The processors <NUM> are also referred to herein as processing circuitry. The transceivers <NUM> are also referred to herein as radio circuitry. In some embodiments, the functionality of the wireless communication device <NUM> described above (e.g., one or more functions of a network node as described above, for example, with reference to <FIG>) may be fully or partially implemented in software that is, e.g., stored in the memory <NUM> and executed by the processor(s) <NUM>. Note that the wireless communication device <NUM> may include additional components not illustrated in <FIG> such as, e.g., one or more user interface components (e.g., an input/output interface including a display, buttons, a touch screen, a microphone, a speaker(s), and/or the like and/or any other components for allowing input of information into the wireless communication device <NUM> and/or allowing output of information from the wireless communication device <NUM>), a power supply (e.g., a battery and associated power circuitry), etc..

In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the wireless communication device <NUM> according to any of the embodiments described herein (e.g., one or more functions of a network node as described above, for example, with reference to <FIG>) is provided.

The module(s) <NUM> provide the functionality of the wireless communication device <NUM> described herein (e.g., one or more functions of a network node as described above, for example, with reference to <FIG>).

With reference to <FIG>, in accordance with an embodiment, a communication system includes a telecommunication network <NUM>, such as a 3GPP-type cellular network, which comprises an access network <NUM>, such as a RAN, and a core network <NUM>. The access network <NUM> comprises a plurality of base stations 1706A, 1706B, 1706C, such as Node Bs, eNBs, gNBs, or other types of wireless Access Points (APs), each defining a corresponding coverage area 1708A, 1708B, 1708C. Each base station 1706A, 1706B, 1706C is connectable to the core network <NUM> over a wired or wireless connection <NUM>. A first UE <NUM> located in coverage area 1708C is configured to wirelessly connect to, or be paged by, the corresponding base station 1706C. A second UE <NUM> in coverage area 1708A is wirelessly connectable to the corresponding base station 1706A.

It is noted that the host computer <NUM>, the base station <NUM>, and the UE <NUM> illustrated in <FIG> may be similar or identical to the host computer <NUM>, one of the base stations 1706A, 1706B, 1706C, and one of the UEs <NUM>, <NUM> of <FIG>, respectively.

The wireless connection <NUM> between the UE <NUM> and the base station <NUM> is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE <NUM> using the OTT connection <NUM>, in which the wireless connection <NUM> forms the last segment. More precisely, the teachings of these embodiments may improve the PUSCH reliability and flexible switching between the 'standard mode' and the 'enhanced mode' and thereby provide benefits such as enabling multi-TRP codebook based transmission and multi-TRP non-codebook based transmission.

The scope of the present invention is defined by the scope of the appended claims.

Claim 1:
A method performed by a wireless device for enhancing Physical Uplink Shared Channel, PUSCH, reliability, comprising:
receiving (<NUM>) a configuration of two Sounding Reference Signal, SRS, resource sets, comprising a first SRS resource set and a second SRS resource set;
receiving (<NUM>) an instruction from a network node for transmitting a plurality of PUSCH repetitions according to the two SRS resource sets; and
transmitting (<NUM>) the plurality of PUSCH repetitions according to the first SRS resource set and the second SRS resource set based on the received instruction,
the method being characterized in that:
the plurality of PUSCH repetitions comprises a first group of PUSCH repetitions and a second group of PUSCH repetitions, the second group being complementary to the first group, and the first group of PUSCH repetitions is transmitted according to the first SRS resource set and the second group of PUSCH repetitions is transmitted according to the second SRS resource set,
wherein the two SRS resource sets are configured for codebook based PUSCH transmission, wherein:
- receiving (<NUM>) the instruction further comprises receiving (<NUM>-<NUM>) the instruction for transmitting the plurality of PUSCH repetitions via codebook based PUSCH transmission, and
- transmitting (<NUM>) the plurality of PUSCH repetitions comprises transmitting (<NUM>-<NUM>) the first group of PUSCH repetitions among the plurality of PUSCH repetitions according to the first SRS resource set and the second group of PUSCH repetitions among the plurality of PUSCH repetitions according to the second SRS resource set based on the codebook based PUSCH transmission,
wherein the instruction for transmitting the plurality of PUSCH repetitions via the codebook based PUSCH transmission comprises:
- a first SRS Resource Indicator, SRI, indicating a first SRS resource from the first SRS resource set, and a second SRI indicating a second SRS resource from the second SRS resource set, and
- a first Transmit Precoding Matrix Indicator, TPMI, associated with the first SRS resource, and a second TPMI associated with the second SRS resource, and
wherein the multiple SRIs are provided in different SRI fields of Downlink Control Information, DCI.