Method and apparatus for a physical uplink shared channel for multi-transmit / receive point communications in a wireless communications network

Abstract

To disclose methods to be executed by UE.SOLUTION: A method comprises: a step of receiving, from a network node, a single PDCCH or a higher layer grant that schedules two or more PUSCH transmission occasions for UE, where all the scheduled PUSCH transmission occasions are associated with the same PUSCH transport block, where the scheduling PDCCH or higher layer grant provides two or more groups of SRS resources, where each group comprises at least one SRS resource and the SRS resources of each group is associated with a different SRS resource set, and an SRS resource set is a higher layer configuration that comprises one or more SRS resources, two or more TPC commands, and one or more DMRS ports; and a step of executing scheduled PUSCH transmission.SELECTED DRAWING: Figure 5

Description

[Technical Field]

[0001] The present disclosure relates to the field of wireless communications, and more particularly to methods and apparatus for enabling a physical uplink shared channel (PUSCH) for multi-transmit / receive point (TRP) communications in wireless communications networks such as 5G. [Background technology]

[0002] Wireless transmission from multiple transmit / receive points (TRPs) to a user equipment (UE) or from a single UE to multiple TRPs helps improve transmission coverage, reliability, and throughput. A TRP can refer to a base station, and one or more base stations can be associated with a network node (e.g., a gNodeB or gNB). A TRP can also refer to an antenna panel. For example, a base station may have two panels, each corresponding to a TRP.

[0003] The 3rd Generation Partnership Project Release 16 (3GPP® Rel. 16) specifies a method for multi-TRP transmission in the downlink, but only single-TRP transmission is possible in the uplink. Similar to multi-TRP transmission in the downlink, transmission coverage, reliability, and throughput can also be improved by transmitting on multiple TRPs in the uplink. The challenges in scheduling multi-TRP transmission in the UL are quite different from those faced in DL multi-TRP transmission: it is a noncoherent transmission scenario in the DL, but a noncoherent reception scenario in the uplink. Some of the issues that must be considered in scheduling multi-TRP UL transmissions include antenna port indication at the UE, power control for UL transmissions, time-frequency resource utilization, the multiplexing method used, and beam management.

[0004] In millimeter wave (mmWave) frequencies (Frequency Range 2 (FR2)), i.e., frequencies above 6 GHz, wireless communication between communicating devices is typically accomplished using spatially selective / directional transmission and reception, called beams. Therefore, beam management is an important framework for link establishment, adaptation, and recovery in FR2.

[0005] In 3GPP Re.16, beam management in the uplink (UL) is handled separately for various UL channels and UL reference signals. The functionality of the UL beam management framework is distributed across three communication layers: the physical (PHY) layer [Non-Patent Documents 1-4], the medium access control (MAC) layer [Non-Patent Document 5], and the radio resource control (RRC) layer [Non-Patent Document 6]. To enable beamforming uplink transmissions between the UE and the radio network node (gNB), beam management performs two tasks: indicating the beam direction for UL transmissions and the associated transmit power setting. The two tasks are handled differently for the physical uplink shared channel (PUSCH), the physical uplink control channel (PUCCH), and the sounding reference signal (SRS).

[0006] On the other hand, in the downlink (DL), instructions must be given to the UE to obtain various parameters such as delay spread, mean delay, Doppler and Rx beam direction for reception of the DL channel or reference signal (RS).

[0007] The term "beam" is used hereinafter to refer to spatially selective / directional outgoing signal transmission and incoming signal reception achieved by precoding / filtering signals at a device's antenna port with a specific set of coefficients. The terms precoding or filtering can refer to signal processing in the analog or digital domain. The set of coefficients used to spatially direct transmission / reception in a particular direction can vary depending on the direction. The term "Tx beam" refers to spatially selective / directional transmission, and "Rx beam" refers to spatially selective / directional reception. The set of coefficients used to precode / filter transmission or reception is referred to as a "spatial filter." Because the spatial filter coefficients determine the direction in which transmission / reception is spatially directed, the term "spatial filter" is used interchangeably with the term "beam direction" herein.

[0008] A "spatial relationship" for an UL channel "Uc" or RS "Ur" relative to or in accordance with a DL or UL reference signal (RS) "R" means that the UE uses the spatial filter used to receive or transmit the RS "R" to transmit the UL channel "Uc" or RS "Ur", or that the UE uses the spatial filter used to receive or transmit the RS "R" as a reference for determining the spatial filter used to transmit the UL channel "Uc" or RS "Ur".

[0009] The term "upper layer", when used independently, hereinafter refers to any communication layer above the physical layer in a protocol stack. The terms serving cell and carrier component (CC) are used interchangeably in this disclosure as a serving cell configured for a UE, which is typically a separate physical carrier with a specific carrier frequency. Depending on the frequency of the component carrier / serving cell, the size of the cell and the beamformed reference signal may vary.

[0010] In the following, the prior art (SoTA) for DL ​​channel, SRS, and PUSCH is presented, then the issues to be considered for scheduling PUSCH transmission to multiple TRPs are discussed, and then solutions to address the related issues are discussed.

[0011] <Downlink transmission configuration display> The Physical Downlink Control Channel (PDCCH) and the Physical Downlink Shared Channel (PDSCH) carry DL control information and DL data to the UE, respectively [Non-Patent Documents 1 to 6].

[0012] The PDCCH is configured at the Radio Resource Control (RRC) layer level by the base station, network node, or gNodeB (gNB). The gNB transmits the PDCCH on one or more control resource sets (CORESETs) configured at the RRC level. A CORESET is a set of resource blocks carrying control information. Each CORESET contains one or more PDCCHs, each linked to a search space configuration. The UE monitors the configured search space to acquire the PDCCH. The PDCCH may be part of a common search space (CSS) or a UE-specific search space (USS). The PDCCH belonging to the CSS typically contains information broadcast by the gNB to all UEs, such as system information broadcasts or paging information. The PDCCH belonging to the USS contains UE-specific information, such as downlink control information (DCI) for scheduling the PDSCH or PUSCH or SRS triggers.

[0013] It should be noted that the terms PDCCH and DCI may be used interchangeably in this disclosure, as both terms refer to downlink control channel information obtained via the physical layer.

[0014] A demodulation reference signal (DMRS) is embedded for coherent demodulation of the PDCCH / PDSCH at the UE. The DMRS consists of a set of DMRS ports. For the PDSCH, the number of DMRS ports determines the number of transmission layers included in the PDSCH. The DMRS is used for channel estimation at the UE to coherently demodulate the PDSCH or PDCCH. For the PDCCH, one or more of them may be transmitted on the CORESET. Thus, the DMRS for coherent demodulation of the PDCCH on the CORESET may be embedded across the PDCCH transmitted on the CORESET.

[0015] <Sounding Reference Signal (SRS)> As its name suggests, a Sounding Reference Signal (SRS) is used for sounding the UL channel. The basic unit of an SRS is an SRS resource. An SRS resource is a specific pattern of reference symbols in time, frequency, and code that are transmitted by all or a subset of the UE's antenna ports in the UL to sound the UL channel. A UE is configured by the gNB via RRC with one or more SRS resource sets, each consisting of one or more SRS resources. The RRC information element (IE) for configuring SRS resource sets and SRS resources using SRS-SpatialRelationInfo is shown in Figures 1 and 2, respectively [Non-Patent Document 6].

[0016] As indicated in the SRS set configuration provided in FIG. 1, the parameter "usage" indicates the purpose for which the SRS is used. 1) Usage = 'codebook': Sounds the UL channel before codebook-based PUSCH transmission is performed by the UE. 2) Usage = 'non-codebook': Sounds the UL channel before non-codebook based PUSCH transmission is performed by the UE. 3) Usage = 'beamManagement': Sound the UL channel with beamformed SRS resources to identify a suitable UL beam. 4) Usage = 'antennaSwitching': Sound the UL channel to obtain DL channel information.

[0017] For codebook- and non-codebook-based SRS transmissions, the gNB measures SRS resources and provides digital precoding / port selection information to the UE for subsequent PUSCH transmissions. For "beam management" SRS, the UE beamforms the SRS in various directions with the gNB to determine the appropriate UL beam. The selected beam is used to indicate the spatial relationship, i.e., the beam direction, for PUCCH and / or PUSCH and / or other SRS resources. (The parameter "spatialRelationInfo" includes the RS used to indicate the spatial relationship for the SRS resource, which can be a Channel State Information Reference Signal (CSI-RS), a Synchronization Signal Block (SSB), or an SRS.) The "antenna switching" SRS is used to exploit channel reciprocity and to obtain channel DL information via UL sounding so that the gNB can precode DL transmissions with more accurate CSI.

[0018] <Physical Uplink Shared Channel (PUSCH)> PUSCH transmissions from the UE can be dynamically scheduled by the network node via the UL grant indicated in the PDCCH, or can be semi - persistently / statically scheduled using the configured grant configuredGrantConfig configured at the upper layer. The configured grant Type1 PUSCH transmission is quasi - statically configured to operate upon receiving the upper layer parameters of configuredGrantConfig including rrc - ConfiguredUplinkGrant without detecting the UL grant in the PDCCH. The configured grant Type 2 PUSCH transmission is semi - persistently scheduled by the UL grant in the valid activation DCI / PDCCH [Non - Patent Document 3] after receiving the upper layer parameters configuredGrantConfig that do not include rrc - ConfiguredUplinkGrant [Non - Patent Document 4].

[0019] The upper layer configurations of PUSCH and configuredGrantConfig according to the New Radio (NR) specification are shown below. <Upper layer configuration of PUSCH [Non - Patent Document 6]>

[0020]

Table 1

[0021]

Table 2

[0022] The mode of PUSCH transmission is determined by the higher layer parameter "txConfig." This parameter can be set to either "codebook" or "nonCodebook," or it may not be configured. When PUSCH is scheduled via PDCCH, two different downlink control information (DCI) formats can be used in the scheduling PDCCH: DCI format 0_0 or DCI format 0_1. Codebook- and non-codebook-based PUSCH transmissions are scheduled using DCI format 0_1 ​​[Non-Patent Document 4] when scheduled via PDCCH. If "txConfig" is not configured, the UE does not expect PUSCH to be scheduled using DCI format 0_1. When PUSCH is scheduled with DCI format 0_0, the UE uses a single port for PUSCH transmission [Non-Patent Document 4].

[0023] The following sequence of events may occur in scheduling of PUSCH in codebook or non-codebook mode (actions performed by the UE are configured via the network node):

[0024] 0) Optional step "0" may occur for a particular UE: The UE uses beam management SRS for sounding the UL channel on both TRPs and determines the appropriate beam direction for both TRPs. This step may be required for a UE without beam alignment to align the DL and UL beams. A UE may indicate that it satisfies beam alignment when it can align the beam direction in the UL based on DL measurements alone [Non-Patent Documents 7-8]. A UE does not satisfy beam alignment when it requires UL sounding to align the UL beam.

[0025] 1) A "codebook" or "non-codebook" configured SRS resource set is transmitted by the UE to sound the channel between the UE and the TRP / base station (which may correspond to a gNB). The SRS resources in the resource set are assigned appropriate spatial relationships (they may be borrowed from the beam directions obtained from the SRS sounding in step 0). Furthermore, the SRS resource set is assigned a pathloss reference RS associated with the TRP / gNB.

[0026] 2) The network node schedules the PUSCH by pointing to one or more SRS resources from the SRS resource set used for UL sounding in step 1 to indicate the transmission of the PUSCH. In this disclosure, the SRS resource set may be referred to as the "SRS resource set associated with PUSCH scheduling" or simply as the "associated SRS resource set."

[0027] When scheduling a PUSCH, various transmission parameters need to be indicated either in the higher layer grant scheduling the PUSCH or in the DCI / PDCCH or via other higher layer signaling. Some transmission parameters are briefly described below.

[0028] <verbose version> The PUSCH is transmitted in units of transport blocks, where a transport block (TB) is a block of B bits received by the physical layer from the upper layer for transmission. The allowed values ​​of B are given in [Non-Patent Document 4]. A set of L cyclic redundancy check (CRC) parity bits is added to the transport block. Therefore, the size of the TB with CRC is B tot = B + L. Then, B of PUSCH totChannel coding is performed on the bits using low-density parity check (LDPC) coding, and the coded bits are processed by a rate matcher to ensure that the number of coded bits matches the predetermined code rate of the PUSCH. The rate matcher essentially punctures certain bits from the bit stream to match the predetermined code rate. The pattern of punctured bits or the set of bits selected by the rate matcher is determined by a "redundancy version." The redundancy version applied to a PUSCH TB is indicated in the PDCCH or higher layer grant scheduling the PUSCH. Depending on the size of the incoming TB, coding and rate matching may segment the incoming TB (along with the corresponding CRC parity bits) into one or more code blocks. The outputs of the encoder and rate matcher for the segmented code blocks of a particular transport block are concatenated into a "codeword." Thus, a transport block is the bit stream at the input to the encoder-rate matcher module, and the output of the module is a codeword. The codewords are then scrambled, modulated with a given modulation order, and mapped to a given number of layers before transmission [1-4].

[0029] When scheduling a PUSCH TB transmission, the UE indicates a Hybrid Automatic Repeat Request (HARQ) process ID. The process ID is used as the TB identifier. Acknowledgments of TB reception sent by the UE or retransmissions of transport blocks scheduled by the gNB are associated with the HARQ process ID. Acknowledgments and retransmissions help improve PUSCH reliability. The redundancy version also plays an important role in PUSCH reliability. If a PUSCH transport block is transmitted and decoded incorrectly at the TRP / base station or gNB, the TRP / base station or gNB can use the corresponding HARQ process ID to indicate a PUSCH retransmission with a different redundancy version than the first PUSCH transmission. Upon receiving a second PUSCH transmission with a different redundancy version, the gNB can appropriately combine the two PUSCHs for PUSCH decoding. The diversity provided by different channels for the two transmissions provides an improved SNR for channel decoding.

[0030] <Number of antenna ports, DMRS ports, precoding, and layers> Different types of antenna ports are defined in the UE for PUSCH transmission. DMRS ports in the UE are used to indicate the mapping of data streams to data layers for transmission; that is, the number of DMRS ports used for transmission indicates the spatial layer used for transmission. The DMRS ports used for PUSCH transmission are indicated by the "Antenna ports" field in the scheduling DCI. The symbols of DMRS resource elements corresponding to different ports can be code division multiplexed (CDM-ed). Each port belongs to a specific CDM group as specified in [Non-Patent Documents 1-4]. From the DMRS ports, the data layers are mapped to antenna ports (or SRS ports) by the precoder from which the PUSCH is transmitted.

[0031] - Codebook and non-codebook PUSCH transmission: If a "codebook" or "non-codebook" PUSCH is scheduled using DCI format 0_1 ​​or a higher layer grant, i.e., the higher layer parameter "txConfig" is set to "codebook" or "non-codebook", the UE may transmit the PUSCH using one or more antenna ports. The antenna ports are indicated for codebook and non-codebook-based PUSCH by an SRI, which points to one or more SRS resources associated with a "codebook" or "non-codebook" SRS resource set. The SRS port associated with the indicated SRS resource is the antenna port to which the data layer (data stream in the DMRS port) is mapped. Depending on the mode of PUSCH transmission, the precoding scheme is either explicitly indicated or implicitly determined [Non-Patent Documents 1-4]. For codebook-based PUSCH, the precoding scheme is explicitly indicated by the "precoding and layer number field" (the indicated precoding matrix F is of size P × L and maps data streams from L DMRS ports to P antenna ports). For non-codebook-based PUSCH, the precoding scheme is not indicated and is therefore predetermined or left to the UE implementation [Non-Patent Documents 1-4]. In this disclosure, the term "DMRS port" refers to the port to which data (coded, rate-matched, and modulated symbols, i.e., modulated codewords) are mapped to layers, and the terms "antenna port" or "SRS port" refer to the port to which a DMRS port is mapped via a precoding scheme.

[0032] - Single-port PUSCH transmission: If PUSCH is scheduled using DCI format 0_0, the UE uses a single antenna port, which is mapped to a single DMRS port (port 0) [Non-Patent Document 4]. In this case, no precoder is indicated and a single layer of PUSCH is transmitted by the UE.

[0033] <Transmit Power Control (TPC) Command> A transmit power control command is provided in the DCI scheduling the PUSCH. This provides the power ramping or downscaling that needs to be performed for a PUSCH transmission relative to a previous PUSCH transmission [Non-Patent Document 3]. If the higher layer parameter "tpc-Accumulation" is enabled, the power ramping or downscaling may be accumulated over each PUSCH transmission. The gNB uses such power control to control the amount of interference, UE throughput, link reliability, etc.

[0034] Spatial Relationship and Path Loss Criterion RS In FR2 (Frequency Range 2: frequencies above 6 GHz) deployments, directional UL transmission is required, and therefore beam direction is an important parameter to be indicated for the PUSCH. The beam direction / spatial relationship of the PUSCH is determined from the beam direction / spatial relationship of the SRS or PUCCH resources, depending on the mode of PUSCH transmission.

[0035] - Codebook or non-codebook based PUSCH transmission is indicated by SRS resources. The UE sounds the UL channel using SRS resources (dedicated to codebook / non-codebook transmission mode), and the gNB then schedules the PUSCH via the SRS resource indication. The UE then transmits the PUSCH from the same port on which the SRS resources are transmitted and uses the same beam direction / spatial relationship for the PUSCH transmission as for the SRS resource transmission.

[0036] - If the UE is scheduled by DCI format 0_0 (single-port PUSCH), the spatial relationship used for transmitting the PUSCH shall be the same as that used for transmitting the PUCCH resource with the lowest ID in the currently active UL bandwidth portion (BWP).

[0037] The pathloss reference RS configured / indicated via higher layers is used in the power control configuration of the PUSCH to determine the pathloss estimate for the PUSCH transmission [Non-Patent Document 3]. The pathloss reference RS for the PUSCH is determined in different ways for different PUSCH transmission modes. The PUSCH is configured with a list of pathloss reference RSs in the "PUSCH-PathlossReferenceRS" IE and in most cases uses that list to derive the pathloss reference RS.

[0038] - For codebook or non-codebook-based PUSCH transmissions scheduled by the PDCCH, the pathloss reference RS is configured in the 'SRI-PUSCH-PowerControl' IE (described in the section "Higher Layer Configuration of Power Control Parameters for PUSCH" below). These IEs contain the power control settings for the PUSCH, such as the ID of the PUSCH-pathlossReference, the 'alpha' value (pathloss compensation factor), and the closed-loop power control index. The mapping between the PUSCH-pathlossReferenceRS IE and the SRI-PUSCH-PowerControl IE can be modified using a MAC-CE message [Non-Patent Document 3]. The SRS resource indicators mentioned for codebook / non-codebook PUSCH transmissions are mapped to the 'SRI-PUSCH-PowerControl' IE, which provides these power control settings. When the SRI field is absent in the scheduling PDCCH, the UE uses the SRI-PUSCH-PowerControl IE with the ID value set to 0.

[0039] - For a single-port PUSCH (scheduled by PDCCH via DCI format 0_0), the pathloss reference RS is obtained from the same PUCCH resource from which it obtains the spatial relationship.

[0040] - When the PUSCH is scheduled by a higher layer grant, the pathloss reference RS to be used is indicated via the pathlossReferenceIndex that points to the PUSCH-pathlossReferenceRS IE, or is obtained from the SRI-PUSCH-PowerControl with the ID value set to 0 when there is no SRI field.

[0041] The higher layer configuration [Non-Patent Document 6] of the power control parameters for PUSCH is shown in the following figure.

[0042]

Table 3

[0043]

Equation

[0044]

number

[0045] 3GPP Rel. 16 standardized multi-TRP transmission to improve the reliability and robustness of PDSCH transmission. Multiple PDSCHs transmitted from multiple TRPs carrying the same transport block (applied with the same or different redundancy versions) can be scheduled using a single PDCCH, allowing UEs to appropriately combine data received from different TRPs to improve PDSCH reliability. Transmissions can be multiplexed in the time, frequency, or spatial domains. The activation and indication of each PDSCH multi-TRP reliability scheme is managed using a combination of higher layer and PHY layer indications. However, the scheduling challenges faced in the uplink are different from those in the downlink. This disclosure discusses the key issues in uplink scheduling related to the specification and then provides a general framework for reliability-based PUSCH scheduling for single-TRP and multi-TRP.

[0046] The 3GPP Rel. 16 specification describes a procedure for multiplexing multiple downlink PDSCH transmissions scheduled by a single PDCCH [Non-Patent Document 4]. However, the current specification does not describe such a multiplexing method for PUSCH that can be utilized in a multi-TRP scenario. [Prior art documents] [Non-patent literature]

[0047] [Non-Patent Document 1] 3GPP TS 38.211 V16.0.0: "3GPP; TSG RAN; NR; Physical channels and modulation (Rel. 16)", Jan. 2020 [Non-patent document 2] 3GPP TS 38.212 V16.0.0: "3GPP; TSG RAN; NR; Multiplexing and channel coding (Rel. 16) (3GPP; TSG RAN; NR; Multiplexing and channel coding (Rel. 16))", Jan. 2020 [Non-patent document 3] 3GPP TS 38.213 V16.0.0: "3GPP; TSG RAN; NR; Physical layer procedures for control (Rel. 16)", Jan. 2020 [Non-patent document 4] 3GPP TS 38.214 V16.0.0: "3GPP; TSG RAN; NR; Physical layer procedures for data (Rel. 16)", Jan. 2020 [Non-patent document 5] 3GPP TS 38.321 V15.8.0: "3GPP; TSG RAN; NR; Medium Access Control (MAC) protocol specification (Rel. 15)", Jan. 2020 [Non-patent document 6] 3GPP TS 38.331 V15.8.0: "3GPP; TSG RAN; NR; Radio Resource Control (RRC); Protocol specification (Rel. 15) (3GPP; TSG RAN; NR; Radio Resource Control (RRC); Protocol specification (Rel. 15))", Jan. 2020 [Non-Patent Document 7] 3GPP TS 38.101-1 V16.2.0: "3GPP; TSG RAN; User Equipment (UE) radio transmission and reception; Part 1: Range 1 Standalone (Rel. 16)", Jan. 2020 [Non-patent document 8] 3GPP TS 38.101-2 V16.2.0: "3GPP; TSG RAN; User Equipment (UE) radio transmission and reception; Part 2: Range 2 Standalone (Rel. 16)", Jan. 2020 Summary of the Invention [Problem to be solved by the invention]

[0048] In view of the above drawbacks, it is an object of the embodiments herein to provide at least a method and apparatus for improving the robustness and performance of PUSCH through an improved transmission scheme and its configuration that applies to both single-TRP and multiple-TRP scenarios. [Means for solving the problem]

[0049] According to some aspects of embodiments herein, there is provided a method according to any one of the subject matter of method claims 1 to 6 or any one of the subject matter of method claims 7 to 39, performed by a UE.

[0050] According to another aspect of an embodiment of the present specification, there is provided a UE comprising a processor and a memory, the memory including instructions executable by the processor to thereby perform any one of the subject matter of method claims 1 to 6 or any one of the subject matter of method claims 7 to 39.

[0051] Also provided is a computer program comprising instructions which, when executed on at least one processor of a UE, cause at least said processor to perform a method according to any one of method claims 1 to 6 or any one of method claims 7 to 39.

[0052] According to another aspect of some embodiments of the present disclosure, there is provided a method according to the subject matter of method claim 40 or method claim 41, performed by a network node. According to another aspect of an embodiment of the present specification, there is provided a network node comprising a processor and a memory, the memory including instructions executable by the processor, thereby configured to perform the subject matter of method claim 40 or method claim 41.

[0053] Also provided is a computer program comprising instructions which, when executed on at least one processor of a network node, cause at least said processor to perform the subject matter of method claim 40 or method claim 41.

[0054] Also provided is a carrier containing the computer program, the carrier being one of a computer readable storage medium, an electronic signal, an optical signal, or a radio signal. [Effects of the Invention]

[0055] An advantage of the embodiments herein is that they improve the reliability and performance of PUSCH in multi-TRP scenarios. Another advantage of the embodiments herein is improved scheduling of PUSCH transmissions.

[0056] Another advantage of some embodiments herein is that a multiplexing scheme is used to increase the diversity of the PUSCH transmission. Further advantages of the embodiments herein are provided in the detailed description. [Brief explanation of the drawings]

[0057] [Figure 1] A diagram showing SRS Resource Set Arrangement (SoTA). [Figure 2] A diagram showing SRS resource configuration (SoTA). [Figure 3] FIG. 10 illustrates an example of dynamic switching between multiplexing schemes according to some embodiments. [Figure 4] FIG. 10 illustrates another example of dynamic switching between multiplexing schemes according to some embodiments. [Figure 5] 1 is a flow diagram of a method performed by a network node according to some embodiments. [Figure 6] 1 is a block diagram of a network node according to some example embodiments. [Figure 7]4 is a flow diagram of a method performed by a UE according to some embodiments. [Figure 8] 1 is a block diagram of a UE in accordance with some exemplary embodiments. DETAILED DESCRIPTION OF THE INVENTION

[0058] In the following, detailed descriptions of exemplary embodiments are described in conjunction with drawings, which can facilitate understanding of the solutions described herein in some scenarios. The transmission parameters involved in scheduling PUSCH transmissions have been covered above. The solutions herein are provided in the context of scheduling multiple PUSCH transmissions or scheduling segmented transmissions of a single PUSCH, and therefore scheduling can be implemented in either single-TRP or multi-TRP scenarios as required.

[0059] Scheduling according to embodiments herein is performed with the aim of improving the reliability and robustness of the PUSCH. Transmission of the same PUSCH data for different TRPs may aid in non-coherent combining of the PUSCH data and thus improve the overall SNR of the received PUSCH data. In this disclosure, various methods of PUSCH transmission in multi-TRP scenarios are discussed to provide flexibility in scheduling.

[0060] Embodiments herein focus on transmission schemes and their configurations for one or more PUSCH transmissions scheduled by a single PDCCH or higher layer grant. The scheduled PUSCHs may be transmitted on a single TRP or multiple TRPs based on the transmission configuration or transmission parameters used for each transmission. The purpose of scheduling such transmissions is to improve one or more of the PUSCH metrics, namely, reliability, diversity, and latency. This disclosure addresses various issues related to scheduling PUSCHs for such purposes. 1) Indication of PUSCH scheduling (number of scheduled PUSCHs, resource allocation, etc.) 2) SRS and DMRS port display, 3) Redundant Version (RV), 4) Transmit Power Control (TPC), 5) Scheduling of one or a combination of multiplexing methods such as time division multiplexing (TDM), frequency division multiplexing (FDM), or space division multiplexing (SDM). 6) PUSCH Repetition for Reliability 7) Indication of transmission parameters of the transmission configuration with TCI status as configured in the UL Throughout this disclosure, scheduling n PUSCHs or n PUSCH transmissions via a single PDCCH or a single higher layer grant means that the PDCCH or higher layer grant schedules n PUSCH transmission opportunities or n PUSCH codewords, which may be associated with the same or different transport blocks.

[0061] Configuring and displaying multiple or segmented PUSCH transmissions Improving PUSCH reliability, diversity, and latency in multi-TRP contexts can be achieved using a combination of higher layer configuration and PHY layer signaling. A UE may receive scheduling requests for multiple PUSCH transmissions or segmented PUSCH transmissions, where each PUSCH transmission or PUSCH segment is associated with a different transmission parameter(s) of a transmission configuration, which includes a set of transmission parameters as described below.

[0062] According to some embodiments herein, a UE is configured by a network node (or gNB) to receive a single PDCCH / DCI or higher layer grant that schedules one or more PUSCH transmission opportunities.

[0063] When one PUSCH transmission opportunity is scheduled, the UE may be scheduled to transmit at least two segments / portions of the PUSCH, where for one segment, at least one of the following transmission parameters associated with the segment, namely, DMRS port, antenna port, path loss reference RS, TPC command, spatial relationship, frequency domain resource, and time domain resource, differs from a corresponding parameter associated with at least one other segment / portion of the PUSCH. Thus, each segment of the PUSCH is associated with a transmission configuration including a set of transmission parameters, and at least one transmission parameter associated with at least one of the segments of the PUSCH differs from a corresponding transmission parameter associated with at least one other segment of the PUSCH.

[0064] When multiple PUSCH transmission opportunities are scheduled, each PUSCH transmission opportunity is associated with a transmission configuration including transmission parameters, wherein at least one transmission parameter associated with one of the PUSCH transmission opportunities differs from a corresponding transmission parameter associated with at least one other PUSCH transmission opportunity, and the transmission parameters include a DMRS port, an antenna port, a pathloss reference RS for determining an estimated pathloss for transmission, a TPC command, a spatial relationship or beam direction, a frequency-domain resource, and a time-domain resource.

[0065] A segment of a PUSCH transmission opportunity, or a segment of a PUSCH transmission, or a PUSCH segment, may be defined as a portion of an associated PUSCH codeword, where at least one of the following parameters of the transmission configuration associated with the portion or segment, namely, antenna port, DMRS port, path loss reference RS, TPC command, spatial relationship, frequency domain resource, and time domain resource, differs from at least one corresponding transmission parameter of at least one other portion or segment of the same PUSCH codeword.

[0066] The transmission configuration including the transmission parameters may be indicated in the PDCCH (or DCI) or a higher layer grant. The UE may be informed via a higher layer that the PDCCH or higher layer grant may schedule multiple PUSCH transmissions.

[0067] Thus, if one PUSCH transmission opportunity is scheduled and the PDCCH (or DCI) or higher layer grant contains, for example, two transmission configurations, this means that the UE is scheduled to transmit two segments of the PUSCH, each segment of the PUSCH being associated with a transmission configuration as described above.

[0068] In the case of PUSCH repetition described in the above embodiments, i.e. scheduling of multiple PUSCH transmission opportunities, special schemes of scheduling may be possible. According to an embodiment, a single PDCCH / DCI or a higher layer grant schedules n>1 PUSCH or PUSCH transmission opportunities from a UE, and the same PUSCH transport block is scheduled to be transmitted n times by the UE as follows. That is, n'<n of the n transmissions are scheduled using a first set of uplink transmission parameters, and the remaining n-n' transmissions are scheduled using at least one uplink transmission parameter different from the corresponding transmission parameters from the first set of transmission parameters used for the other n' transmissions. For example, n'<n of the n transmissions may be scheduled using a first set of antenna ports, path loss reference RS, TPC commands, etc. The remaining n-n' transmissions are scheduled using a different set of antenna ports, path loss reference RS, TPC commands from the other n' transmissions. The order in which the n' transmissions of the first set and the n-n' transmissions of the second set are scheduled among all n transmissions may be indicated by the gNB or a network node, or may be fixed in the specification. A use case of this method is, for example, the repetition of the same PUSCH TB for two different TRPs. The first n' transmissions may be directed to the first TRP, and the remaining n-n' transmissions may be directed to the second TRP.

[0069] In the case of segmented PUSCH transmission, for example, the spatial relationship of the transmission parameters in one transmission setting associated with one segment of the PUSCH is different from the spatial relationship of the corresponding transmission parameters in another transmission setting associated with another segment of the same PUSCH. Therefore, different segments of the same PUSCH are beamformed in different directions, and each direction may correspond to a specific TRP.

[0070] According to one embodiment, the UE is configured to receive higher layer parameters from a gNB or network node, the higher layer parameters indicating that the UE may receive a single PDCCH or higher layer grant scheduling n (n≧1) PUSCH transmission opportunities or n (n≧1) PUSCH segments of a single PUSCH. For example, a new transmission configuration for PUSCH transmissions, along with codebook and non-codebook PUSCH transmissions, may be introduced in "txConfig." For example, if the parameter "txConfig" is set to "multiPUSCH," it indicates that the UE may receive a single PDCCH scheduling one or multiple PUSCH transmissions. In another example, the higher layer configuration for PUSCH may include an additional parameter entitled "enabledMultiPUSCHscheduling," indicating the scheduling of one or multiple PUSCH transmissions using a single PDCCH or higher layer grant.

[0071] Alternatively, when the parameter "txConfig" is not set, the UE may expect the PDCCH to schedule multiple PUSCH transmission opportunities or multiple PUSCH segments of a single PUSCH. In 3GPP Rel. 16, when the UE is not configured with the parameter "txConfig", the UE does not expect to be scheduled with DCI format 0_1. In the following method, this scenario is utilized to schedule multiple PUSCH transmissions.

[0072] According to an exemplary embodiment, if the UE is not configured with the higher layer parameter "txConfig", the UE expects to receive a single PDCCH scheduling n (n≧1) PUSCH transmissions or n (n≧1) PUSCH segments of a single PUSCH.

[0073] For example, if the UE is not configured using the upper layer parameter "txConfig", the UE may receive the PDCCH using DCI format 0_1 that schedules n PUSCH transmissions (n≥1) or n (n≥1) PUSCH segments of a single PUSCH, or a newly introduced DCI format. By this method, the gNB can switch between multiple PUSCH scheduling via the aforementioned DCI format and single PUSCH scheduling via DCI format 0_0. Such dynamic scheduling via the PHY layer considerably reduces the latency compared to the indication of single / multi-TRP PUSCH scheduling via the upper layer. Furthermore, it enables the gNB to dynamically adjust the scheduling of the PUSCH regarding the channel state between the UE and each TRP via the physical layer.

[0074] When the PDCCH or the upper layer grant schedules multiple PUSCH transmissions or segmented PUSCH transmissions, multiplexing techniques are indicated to the UE. There are various possibilities for transmitting the PUSCH transmission opportunity to multiple TRPs. The following embodiments propose various multiplexing schemes to enhance the reliability of PUSCH transmission.

[0075] <TDM-based PUSCH Multiplexing> According to one embodiment, in the case of TDM-based PUSCH scheduling within a slot, the network node is configured to schedule at least two PUSCH segments or at least two PUSCH transmission opportunities for the UE, where all PUSCH segments or all PUSCH transmission opportunities are scheduled within the same slot, and each PUSCH segment or each PUSCH transmission opportunity is scheduled in a different set of symbols from the set of symbols in which the other PUSCH segments or PUSCH transmission opportunities are scheduled.

[0076] Different schemes associated with TDM-based transmission within a slot are discussed below. (Mode 1-1: In-slot TDM-based PUSCH Transmission) According to one embodiment, the UE is configured to receive a single PDCCH or a higher layer grant that schedules n (n>1) PUSCH transmission opportunities. The n PUSCH transmissions are time division multiplexed (TDMed) within the same slot, where the i-th PUSCH transmission is from symbol a i to symbol b i and a i ≤ b i ∀i, and b i < a j ∀i < j. The n PUSCH transmission opportunities may be associated with the same or different PUSCH transport blocks. This type of TDM-based in-slot scheduling of multiple PUSCH transmission opportunities may be enabled via configuration of higher layer parameters for the UE. When the parameters are configured for the UE, the UE may expect to receive a single PDCCH that schedules n (n>1) PUSCH transmissions TDM'd in the same (time) slot.

[0077] The in-slot TDM scheme can enhance the reliability of transmission. For example, the UE can transmit the coded words associated with the same TB for n PUSCH transmission opportunities to n different TRPs that can combine the received coded words via a backhaul network. When transmission is performed for different TRPs, each PUSCH transmission may be associated with different transmission settings or parameters.

[0078] According to an exemplary embodiment, at least one of the following parameters associated with PUSCH transmission, namely, antenna port, DMRS port, transmit power control (TPC) command, path loss reference RS, and spatial relationship, may be different from the parameters associated with other PUSCH transmissions scheduled by the PDCCH or the higher layer grant. This is used in the case of multi-TRP transmission where different power control and / or beamforming settings are used for transmission to different TRPs.

[0079] (Mode 1-2: TDM-based PUSCH transmission with TB segmentation) In an exemplary embodiment, the UE is configured to receive a single PDCCH or a higher layer grant that schedules a single PUSCH transmission opportunity, and the scheduled PUSCH transmission may include n (n>1) segments, where the i-th segment of the PUSCH is symbol a i to symbol b i in a given slot, where a i ≤b i ∀i, and b i <a j ∀i<j. This means that the segments of the PUSCH transmission are TDM'd to different symbol sets within the slot. This method of PUSCH transmission that is TDM-based on a slot basis can be enabled, for example, via higher layer signaling to the UE.

[0080] Different segments of a single PUSCH codeword may be transmitted to different TRPs, and thus each transmission may have different transmission settings. The individual segments are coupled between the TRPs via a backhaul network. This type of multiplexing increases the diversity of the transmission. Slot-based TDM-based PUSCH transmission with codeword segmentation can be enabled, for example, via higher layer signaling to the UE.

[0081] According to an exemplary embodiment, at least one of the following parameters associated with a segment of a PUSCH transmission, namely, antenna port, DMRS port, transmit power control (TPC) command, path loss reference RS, and spatial relationship, may be different from the parameters associated with other segments of the same PUSCH transmission scheduled by the PDCCH or higher layer grant. When different transmission settings are set for different TDM'd segments, each segment may be transmitted to a different TRP.

[0082] (Mode 2-1: Inter-slot TDM-based PUSCH transmission) In an inter-slot TDM-based transmission scenario, the network node is configured to schedule at least two different PUSCH transmission opportunities for the UE, and each PUSCH transmission opportunity is scheduled in a different slot, as described below. According to an embodiment, the UE is configured to receive a single PDCCH or a higher layer grant that schedules n (n>1) PUSCH transmissions, and the i-th PUSCH transmission is in slot p i in symbol a i from symbol b i to, where a i ≦b i ∀i, and p i <p j ∀i<j. The n PUSCH transmission opportunities may be associated with the same or different PUSCH transport blocks. This type of inter-slot multi-TRP PUSCH transmission may be enabled, for example, via the configuration of higher layer parameters for the UE. When the parameters are configured, the UE expects to receive a PDCCH that schedules n (n>1) PUSCH transmissions TDM'd across multiple slots or different slots.

[0083] In a multi-TRP context, this inter-slot TDM scheme enhances the reliability of transmission when the coded words associated with the same TB are transmitted in the n scheduled PUSCH transmission opportunities. Similar to conventional multiplexing techniques, different transmission settings can be applied to each PUSCH transmission opportunity.

[0084] According to an exemplary embodiment, at least one of the following parameters associated with a PUSCH transmission scheduled by a PDCCH or a higher layer grant, namely, an antenna port, a DMRS port, a transmission power control (TPC) command, a path loss reference RS, and a spatial relationship, may be different from the parameters associated with other PUSCH transmissions scheduled by the PDCCH or the higher layer grant. This opens the way for multi-TRP based transmission of TDM PUSCH between slots.

[0085] <FDM-based PUSCH Multiplexing> According to one embodiment, a network node is configured to schedule at least two PUSCH segments or at least two PUSCH transmission opportunities for a UE, and the set of PRBs for which at least one PUSCH segment or PUSCH transmission opportunity is scheduled is partially or completely different from the set of PRBs for which another PUSCH segment or another PUSCH transmission opportunity is scheduled. Some embodiments related to the FDM-based PUSCH multiplexing scheme are described below.

[0086] (Scheme 3-1: FDM-based PUSCH Transmission) According to an embodiment, a UE is configured to receive a single PDCCH or a higher layer grant that schedules n (n>1) PUSCH transmissions, and the i-th PUSCH transmission is in PRB Ψ i ={a i,1 ,…a i,P} in the scheduled slot. The PRBs for the n PUSCH transmissions may partially overlap or not overlap, that is, Ψ i ∩Ψ j ≠φ, or Ψ i ∩Ψ j =φ ∀i≠j may be true. All PUSCH transmissions are in symbol s start to symbol s endUp to n PUSCH transmission opportunities may occur. The n PUSCH transmission opportunities may be associated with the same or different PUSCH transport blocks. This type of frequency division multiplexing (FDM)-based multiple PUSCH transmission scheme may be enabled, for example, through configuration of higher layer parameters for the UE. When the parameters are configured, the UE may expect to receive a single PDCCH scheduling n (n>1) FDM-based PUSCH transmissions in a given slot.

[0087] For example, non-overlapping frequency allocations may be made by dividing the bandwidth available for the PUSCH (or the UL BWP (bandwidth portion) over which the PUSCH is transmitted) into equal portions for each PUSCH transmission. The portions allocated to each PUSCH may or may not be contiguous depending on higher layer configuration or indication.

[0088] When transmitting PUSCH for different TRPs, different transmission configurations may be applied to the PUSCH transmission opportunities. According to an example embodiment, at least one of the following parameters associated with a PUSCH transmission may differ from parameters associated with other PUSCH transmissions scheduled by a PDCCH or higher layer grant: antenna port, DMRS port, transmit power control (TPC) command, path loss reference RS, and spatial relationship.

[0089] (Method 3-2: FDM-based PUSCH transmission with TB segmentation) According to one embodiment, the UE is configured to receive a PDCCH or higher layer grant scheduling a single PUSCH transmission, where the scheduled PUSCH transmission may include n (n>1) segments, and the i-th segment is within a PRB Ψ i ={a i,1 ,…a i,P}, and the PRBs for each part may be partially overlapping or non-overlapping (i.e., different from each other), i.e., for some or all i≠j, Ψi ∩Ψ j ≠φ, or Ψ i ∩Ψ j =φ for all i≠j. All PUSCH transmissions can be in symbol s start from symbol s end to symbol s

[0090] For example, as described above, non - overlapping frequency allocations can be made by dividing the bandwidth available for PUSCH (or the UL BWP in which the PUSCH is transmitted) into equal parts for individual segments. The parts allocated to each segment may or may not be consecutive according to the upper layer signaling.

[0091] Similar to the method described above, when the UE transmits each segment to a different TRP, different transmission parameters may be required for each segment. According to an exemplary embodiment, at least one of the following parameters associated with a segment of PUSCH transmission, namely, antenna port, DMRS port, transmission power control (TPC) command, path loss reference RS, and spatial relationship, may be different from the parameters associated with other segments of PUSCH transmission scheduled by PDCCH or upper layer grant.

[0092] <SDM - based PUSCH Multiplexing> In this scenario, the network node is configured to schedule at least two PUSCH segments of at least two PUSCH transmission opportunities or USCH transmission opportunities for the UE, and each PUSCH segment or each PUSCH transmission opportunity is associated with a different set of DMRS ports and / or antenna ports as described below.

[0093] (Method 4-1: SDM-based PUSCH Transmission) According to an embodiment, the UE is configured to receive a PDCCH or a higher layer grant that schedules n (n>1) PUSCH transmissions, and each PUSCH transmission is performed for a different antenna and / or DMRS port. All PUSCH transmissions may be associated with the same time and frequency domain resources in the scheduled slot. This method of spatial multiplexing multiple PUSCH transmissions may be enabled, for example, via a higher layer configuration or higher layer parameters indicated to the UE. In one example, when n (n>1) PUSCH transmissions are scheduled, n'<n transmissions may be associated with the same set of antennas and / or DMRS ports, while at least one of the remaining n - n' transmissions may be associated with a set of antennas or DMRS ports different from the above n' transmissions.

[0094] For example, two spatially multiplexed (SDMed) PUSCH transmissions may be scheduled via a PDCCH or higher layer grant indicating d DMRS ports and a1 + a2 antenna ports, where a1 antenna ports in a first set are associated with a first SRS resource or a first DL RS, and a2 antenna ports in a second set, different from the first set, are associated with a second SRS resource or a second DL RS. The i-th PUSCH is transmitted using the i-th set of DMRSs and antenna ports (the antenna port set is determined based on the associated SRS resource or DL ​​RS, as described above). The DMRS ports may be divided into sets according to the code division multiplexing (CDM) group to which the port is associated or based on the number of antenna ports used for the i-th PUSCH transmission. For example, four antenna ports and three DMRS ports may be defined for two PUSCH transmissions, and the three DMRS ports may be grouped into two different CDM groups (e.g., three ports p0, p1, and p2 are designated, where ports p0 and p1 belong to CDM group 0 and port p2 belongs to CDM group 1), with the first PUSCH transmitted using the first two antenna ports and DMRS ports p0 and p1, and the second PUSCH transmitted using the second two antenna ports and DMRS port p2. In this example, each PUSCH may be transmitted for a different TRP using the corresponding DMRS and antenna port.

[0095] Reliability-based SDM can be performed when n PUSCHs are scheduled for n different TRPs, and all transmissions are associated with the same transport block (TB). As with other methods, the transmission configuration of each PUSCH can be different, for example, when transmitting each PUSCH for a different TRP.

[0096] According to an exemplary embodiment, at least one of the following parameters (or transmission settings) associated with PUSCH transmission, i.e., a transmission power control (TPC) command, a path loss reference RS, and a spatial relationship, may be different from the parameters (or transmission settings) associated with other PUSCH transmissions scheduled by a PDCCH or a higher layer grant.

[0097] (Scheme 4-2: SDM-based PUSCH transmission with TB segmentation) According to an embodiment, the UE is configured to receive a PDCCH or a higher layer grant that schedules a single PUSCH transmission, and the PUSCH may include n (n>1) segments, and each segment may be transmitted using different antennas and / or DMRS ports. All segments of the above PUSCH transmission may be associated with the same time and frequency domain resources in the scheduled slot. The difference between this method and the conventional spatial multiplexing method is that at least one of the following parameters associated with the segments of the PUSCH transmission, i.e., a transmission power control (TPC) command, a path loss reference RS, and a spatial relationship, is different from the parameters associated with other segments of the PUSCH transmission. In one example, when n (n>1) PUSCH segments are scheduled, n'<n segments may be associated with the same set of antennas and / or DMRS ports, while at least one of the remaining n - n' segments may be associated with a different set of antennas and / or DMRS ports from the above n' segments.

[0098] For example, segmented SDM-based PUSCH transmissions may be scheduled via a PDCCH or a higher layer grant indicating d DMRS ports and a1 + a2 antenna ports. The first set of a1 antenna ports is associated with the reception of the first SRS resource or the first DL RS, and the second set of a2 antenna ports, which is different from the first set of antenna ports, is associated with the reception of the second SRS resource or the second DL RS. The i-th segment of the PUSCH is transmitted using the i-th set of DMRS and antenna ports (the antenna port set is determined based on the associated SRS resource or DL RS as described above). The DMRS ports may be split into sets according to the CDM group to which the (DMRS) ports are associated, or based on the number of antenna ports used for the i-th PUSCH segment. For example, 4 antenna ports and 3 DMRS ports are defined for two PUSCH segments, and it is possible to group the 3 DMRS ports into two different CDM groups (3 ports p0, p1, p2 are indicated, port p0 and p1 belong to CDM group 0, and port p2 belongs to CDM group 1). The first PUSCH is transmitted on the first two antenna ports and DMRS ports p0, p1, and the second PUSCH is transmitted on the second two antenna ports and DMRS port p2. In this example, each PUSCH segment may be transmitted to a different TRP using the corresponding DMRS and antenna ports.

[0099] The SDM-based PUSCH transmission mode may be enabled via a higher layer configuration or indication to the UE. <Activation of PUSCH Multiplexing Method> According to an embodiment, the multiplexing scheme (e.g., a TDM- or FDM- or SDM-based scheme, or a combination of TDM- or FDM- or SDM-based schemes) can be configured or indicated to the UE via one or more upper layer parameters. This can be performed by introducing one or more new upper layer parameters or by reusing existing NR Release 16 upper layer parameters, e.g., the parameter "txConfig" in the configuration of PUSCH. For example, when the upper layer parameter is configured using "multiPUSCHTDMintraSlotA" or "multiPUSCHTDMintraSlotB", the UE expects a PDCCH or an upper layer grant that schedules PUSCH transmission within a TDM-based slot. Similarly, when the upper layer parameter is configured using "multiPUSCHTDMinterSlot", the UE expects a PDCCH or an upper layer grant that schedules PUSCH transmission between TDM-based slots. Similarly, other multiplexing schemes are indicated by configuring the upper layer parameter using "multiPUSCHFDMSchemeA", "multiPUSCHFDMSchemeB", "multiPUSCHSDMSchemeA", or "multiPUSCHSDMSchemeB". It may also be possible to indicate a combination of two or more multiplexing schemes. In such an indication, the UE may use an appropriate combination of the methods described above. For example, the UE may be indicated via the upper layer that it can transmit multiple PUSCHs or PUSCH segments multiplexed in both time and space.

[0100] <Antenna port indication for PUSCH multiplexing> In the following embodiments, the antenna port indication for the aforementioned multiplexing scheme when a network node schedules one or more PUSCH transmissions to the UE is discussed.

[0101] According to one embodiment, the UE is configured to receive a PDCCH or a higher layer grant from the gNB that schedules n (n>1) PUSCH transmissions using one of the multiplexing schemes proposed above. A single PDCCH or higher layer grant indicates n different SRS resources, and each SRS resource may be associated with a PUSCH transmission opportunity. Each PUSCH transmission opportunity is executed by the UE using the SRS port associated with the corresponding SRS resource. The n SRS resources may be indicated via an SRS resource indicator, an SRI field, or a new field in the scheduling PDCCH or higher layer grant. The n SRS resources may be associated with the same SRS resource set or different SRS resource sets. A special case of this method is the indication of up to n SRS resources. In a first example, a single PDCCH or higher layer grant can indicate 1 < n’ ≤ n different SRS resources, and each PUSCH transmission opportunity is associated with one of the n’ SRS resources. If n’ ≤ n, a single SRS resource may be associated with multiple PUSCH transmission opportunities. In a second example, a single PDCCH or higher layer grant can indicate 1 < n’ ≤ n groups of SRS resources, each group includes one or more SRS resources, and each PUSCH transmission opportunity is associated with one of the groups of one or more SRS resources. When n’ < n, a group of SRS resources may be associated with multiple PUSCH transmission opportunities. Here, each group of SRS resources can belong to different SRS resource sets. In a special case, the SRS resources may be indicated via one or more SRI fields.

[0102] For example, two PUSCH transmission opportunities of PUSCH are scheduled via a PDCCH indicating two SRS resources, and the first SRS resource and the second SRS resource are respectively the antenna port

[0103]

Number

[0104]

number

[0105]

number

[0106]

number

[0107] Diversity-based PUSCH transmission is configured / indicated as follows: According to one embodiment, the UE is configured to receive a PDCCH or higher layer grant scheduling a single PUSCH transmission opportunity together with an indication of n (n>1) SRS resources, where the indication of the SRS resources may be performed using an SRS resource indicator field or a new field in the scheduling PDCCH or higher layer grant. The transmission of the i-th PUSCH segment is performed using an SRS port associated with the i-th SRS resource indicated via the scheduling PDCCH or higher layer grant. The UE may be configured using the above-described scheme (1-2), scheme (3-2), or scheme (4-2).

[0108] For example, if a PUSCH is scheduled via a PDCCH that points to two SRS resources, the first SRS resource and the second SRS resource are respectively assigned to antenna ports 1 and 2.

[0109]

number

[0110]

number

[0111]

number

[0112]

number

[0113] Alternatively, all PUSCH transmissions (segmented or complete PUSCH transmission opportunities) may be performed over antenna ports associated with a single SRS resource.

[0114] According to one embodiment, a UE is configured to receive a single PDCCH or higher layer grant scheduling n (n≧1) PUSCH transmissions (segmented or complete PUSCH transmission opportunities), where the PDCCH or higher layer grant points to only a single SRS resource, and all PUSCH transmissions are performed on the same antenna port corresponding to the SRS port associated with the pointed SRS resource.

[0115] Such scheduling may occur in UEs equipped with only a single antenna port or configured with only a single SRS resource in the associated SRS resource set. It may also be desirable from a scheduler perspective to provide the option of multiplexing the PUSCH in time / frequency / space within a desired antenna port set, where all ports may be associated with the same resource.

[0116] Also, instructions may be included in the scheduling PDCCH or higher layer grant to the UE with constraints on the number of antenna ports the UE is equipped with or the number of SRS resources or SRS resource sets that the UE can configure (UE capabilities may limit the higher layer configuration that can be received for SRS). The following embodiments present relevant constraints.

[0117] According to an exemplary embodiment, when a UE receives a single PDCCH or higher layer grant scheduling n (n≧1) PUSCH transmissions (segmented or full PUSCH transmission opportunities), the UE expects that the scheduling PDCCH or higher layer grant does not indicate SRS resources. The SRS resources are known a priori to the UE, i.e., the UE uses default SRS resources defined in the specification, or there are only SRS resources configured for the UE via higher layers in the SRS resource set associated with the scheduling PDCCH or higher layer grant. The SRS resource set associated with the PUSCH scheduling PDCCH or higher layer grant is the one used for sounding the UL channel most recently prior to reception of the PDCCH or higher layer grant scheduling the PUSCH (the usage state parameters may need to match the corresponding PUSCH transmission configuration).

[0118] According to an exemplary embodiment, the UE does not expect to receive a single PDCCH or a single higher layer grant that indicates an SRS resource for a scheduled PUSCH transmission when configured with only one SRS resource or only one SRS port within an SRS resource set associated with a scheduling PDCCH or a higher layer grant.

[0119] According to another exemplary embodiment, when one or more SRS resource sets are associated with a PDCCH or a higher layer grant that schedules a PUSCH transmission opportunity, or when one or more SRS resource sets are associated with any PUSCH transmission opportunity, the UE does not expect to be provided with one or more indicators or one or more fields in the scheduling PDCCH or higher layer grant that indicate an SRS resource from an associated SRS resource that comprises only one SRS resource.

[0120] Due to such restrictions regarding PUSCH scheduling, not all of the above multiplexing techniques are applicable. For example, in a single-port UE or a UE that can be configured with only one SRS resource configuration via the higher layer, only FDM or TDM-based multiple PUSCH transmissions may be possible. Spatial multiplexing of multiple PUSCH transmissions may not be possible because the UE does not have a sufficient number of indicated antenna ports or SRS resources.

[0121] In the above, restrictions have been proposed in the scheduling PDCCH or higher layer grant for the UE with constraints regarding the number of antenna ports the UE has, or the SRS resources or SRS resource sets that the UE can configure (UE performance may limit the higher layer configurations that can be received regarding SRS).

[0122] <Uplink Transmission Configuration Indication for PUSCH Multiplexing> In the following, a framework for indicating the spatial relationship, antenna port, and path loss reference RS for one or more PUSCH transmissions based on the uplink transmission configuration indication (UL-TCI) state framework is proposed. The UL TCI state, like its DL counterpart, can indicate the configuration for uplink transmission, including at least one of the following transmission parameters used for one or more PUSCH transmissions: DMRS port, antenna port, spatial relationship, and path loss reference RS. The antenna or DMRS port can be indicated in the UL-TCI via a reference signal or channel resource in the UL or DL. In addition to the above parameters, the UL-TCI may also provide one or more power control parameters, such as alpha, p0, or a closed-loop power control index.

[0123] For example, if the UL-TCI state indicates a DL RS (CSI-RS or SSB) or DL ​​channel (CORESET) as a reference, the UE shall use the antenna port used to receive the DL RS or DL ​​channel for the transmission of the PUSCH. Similarly, if the UL-TCI state includes a UL RS (SRS) or UL channel (PUCCH resource) as a reference, the UE shall use the antenna port used to transmit the UL RS or UL channel for the transmission of the PUSCH. Therefore, references to "antenna ports indicated by the UL-TCI state" in this disclosure refer to antenna ports associated with the transmission or reception of the RS or channel resource indicated by the UL-TCI state. Similarly, the UL-TCI state may indicate a path loss reference or spatial relationship for UL transmissions using DL or UL reference signals and / or channel resources.

[0124] The UL TCI state may be configured for the UE and, optionally, selected through higher layers and indicated through the PDCCH. Thus, the PDCCH comprises a UL-TCI state indication field (e.g., DCI) and is capable of scheduling one or more PUSCH transmissions. The UL-TCI state may be used standalone or together with an SRI-based port indication for scheduling PUSCH transmissions.

[0125] According to one embodiment, a UE is configured to receive a single PDCCH that schedules n (n>1) PUSCH transmissions (segmented or complete PUSCH transmission opportunities), the scheduling PDCCH comprising an UL-TCI field (within a DCI), where each codepoint of the field is mapped to up to n UL-TCI states, each UL-TCI state indicating at least one of the following transmission parameters: DMRS port, antenna port, spatial relationship, and path loss reference RS. This means that a first UL-TCI state indicated by a codepoint may be associated with a first PUSCH transmission, a second UL-TCI state indicated by a codepoint may be associated with a second PUSCH transmission, and so on. Each PUSCH transmission is performed using the transmission configuration indicated by the associated UL-TCI state.

[0126] Similar parameters may be introduced in higher layer grants that schedule multiple PUSCH transmissions. According to one embodiment, a UE is configured to receive a higher layer grant scheduling n (n>1) PUSCH transmissions (segmented or full PUSCH transmission opportunities), where the parameters in the configuration indicate up to n UL-TCI states, each UL-TCI state indicating at least one of the following transmission parameters: DMRS port, antenna port, spatial relationship, and path loss reference RS. This means that a first UL-TCI state indicated by a codepoint may be associated with a first PUSCH transmission, a second UL-TCI state indicated by a codepoint may be associated with a second PUSCH transmission, and so on.

[0127] Alternatively, the antenna port to be applied to each PUSCH transmission may be indicated by the SRS resource indicator field (in the DCI or higher layer grant) instead of the UL-TCI status field. For example, a PDCCH or higher layer grant scheduling n PUSCH transmissions may indicate the antenna port to be used for each PUSCH transmission by indicating up to n SRS resources via the SRI field of the DCI or higher layer grant, and the spatial relationship to be used for the n PUSCH transmissions may be indicated via the UL-TCI field of the DCI or higher layer parameter indicating the UL-TCI status. The SRI field (a field of the DCI or an SRI parameter of the higher layer grant) may map to up to n SRS resources. This means that a first value of the SRI field may be associated with a first group of n1≦n SRS resources, a second value of the SRI field may be associated with a second group of n2≦n SRS resources, and so on. The antenna port indicated by the SRI field or the SRS resource provided by the codepoint of the SRI field may be used for PUSCH transmission in at least one of the n scheduled PUSCH opportunities. This means that when the number of indicated SRS resources is less than n, multiple PUSCH transmission opportunities may be associated with the SRS resource.

[0128] In another example, the PDCCH or higher layer grant for scheduling n PUSCH transmissions may be:

[0129]

number

[0130] In an alternative form, the PDCCH or upper layer grant that schedules n PUSCH transmissions (segmented or complete PUSCH transmission opportunities) may indicate both the antenna ports and the spatial relationships used for the n PUSCH transmissions via the UL-TCI field in the DCI indicating the UL-TCI state or parameters in the configuration of the upper layer grant. The code point of the UL-TCI field in the DCI or the value of the parameter in the configuration of the upper layer grant may indicate / map a maximum of n UL-TCI states, and each UL-TCI state indicates the ports and spatial relationships used for the corresponding PUSCH transmission. This means that the first code point of the above DCI field or the first value of the above upper layer parameter may be associated with a first group of n1 ≤ n UL-TCI states and n1 ≤ n SRS resources, the second code point of the above DCI field or the second value of the above upper layer parameter may be associated with a second group of n2 ≤ n UL-TCI states and n2 ≤ n SRS resources, and so on.

[0131] The transmission of the i-th PUSCH is via the antenna port associated with the i-th SRS resource pointed to by the SRI field or the antenna port pointed to by the i-th UL-TCI state pointed to by the UL-TCI field of the scheduling DCI.

[0132] Diversity-based PUSCH transmission may be configured / indicated using the UL-TCI state approach described above as follows: According to one embodiment, a UE is configured to receive a PDCCH or higher layer grant scheduling a single PUSCH transmission opportunity with an indication of n (n>1) different UL-TCI states, where the i-th UL-TCI state is associated with the i-th segment of the scheduled PUSCH. The UE performs transmission of the i-th segment of the PUSCH using the transmission configuration indicated in the i-th UL-TCI state indicated via the scheduling PDCCH or higher layer grant. The UE may be configured using the above-described scheme (1-2), scheme (3-2), or scheme (4-2). The above-described alternatives regarding the spatial relationship and antenna port indications with various combinations of SRI and UL-TCI state indications are also applicable when n (n>1) PUSCH segments are scheduled instead of n PUSCH transmissions.

[0133] <DMRS port indication for multiple PUSCH transmissions> The following embodiments describe the DMRS port indications required for layer mapping of PUSCH transmissions. Various examples of DMRS and antenna port indications and mappings are presented in the following embodiments for multiple PUSCH and / or segmented PUSCH transmissions.

[0134] According to one embodiment, a UE is indicated p (p≧1) DMRS ports and q (q≧1) antenna (SRS) ports via a PDCCH or higher layer grant for a PUSCH, and the DMRS ports are grouped into m≦p code division multiplexed (CDMed) DMRS port groups for n (n≧1) PUSCH transmissions (segmented or full PUSCH transmission opportunities). The antenna ports to be used for transmission may be indicated via (a) an SRS resource indicator field in the PDCCH or higher layer grant, which may indicate up to l≦q SRS resources, or (b) a DCI field or higher layer parameter, which indicates up to l≦q UL-TCI states.

[0135] Depending on the designation of the antenna port, the CDM group of the indicated DMRS port, and various other criteria, the mapping between the DMRS port and the antenna port may be determined.

[0136] (single port send) According to one embodiment, a UE is configured to receive a PDCCH or higher layer grant indicating p DMRS ports and q=p antenna ports for n (n≧1) PUSCH transmissions (segmented or full PUSCH transmission opportunities), where the q antenna ports are indicated via an SRS resource indicator field (SRI) present in the DCI or higher layer grant scheduling the PUSCH. The antenna ports are associated with the q SRS resources indicated using the SRI field, and each SRS resource is configured with one SRS port. Thus, a one-to-one mapping between antenna ports and DM-RS ports can be performed. If a DMRS and antenna port are indicated for n>1 PUSCH transmission opportunities, where n=p, each PUSCH is transmitted using a single DM-RS port and associated antenna port. If a DMRS and antenna port are indicated for a single n=1 PUSCH transmission opportunity and q>1 ports are indicated via q SRS resources, then q segments of the PUSCH are transmitted by the UE, each segment being transmitted using a single DM-RS port and associated antenna port.

[0137] According to another embodiment, a UE is configured to receive a PDCCH or higher layer grant indicating p DMRS ports and q=p antenna ports for n=p PUSCH transmissions (segmented or full PUSCH transmission opportunities), where the q antenna ports are indicated via a field in the DCI or higher layer grant indicating up to n UL-TCI states. The antenna ports are associated with the UL-TCI states indicated via the scheduling PDCCH or higher layer grant, and each UL-TCI state indicates one antenna port. Thus, a one-to-one mapping between antenna ports and DM-RS ports can be performed. If a DMRS and antenna port are indicated for n>1 PUSCH transmission opportunities, each PUSCH is transmitted using a single DM-RS port and associated antenna port. If a DMRS and antenna port are indicated for a single n=1 PUSCH transmission opportunity and q>1 ports are indicated via q SRS resources, then q segments of the PUSCH are transmitted by the UE, each segment using a single DM-RS port and associated antenna port.

[0138] (single / multi-port transmission) According to one embodiment, a UE is indicated p DMRS ports belonging to m (m≧1) CDM groups and q antenna ports, where the q antenna ports are associated with l=m SRS resources, and the l SRS resources are indicated via an SRS resource indicator field (SRI) present in the DCI or higher layer grant scheduling the PUSCH. The DMRS port associated with the i-th CDM group is mapped to the antenna port corresponding to the SRS port associated with the indicated i-th SRS resource.

[0139] If a DMRS and antenna port are indicated for n>1 PUSCH transmission opportunities, where n=m, the i-th PUSCH is transmitted using the DMRS port corresponding to the i-th CDM group and the antenna port associated with the indicated i-th SRS resource. If a DMRS and antenna port are indicated for n=1 PUSCH transmission opportunities, where l segments of the PUSCH are transmitted, where l=m, the i-th PUSCH segment is transmitted using the DMRS port corresponding to the i-th CDM group and the antenna port associated with the i-th SRS resource.

[0140] According to another embodiment, a UE is indicated p DMRS ports belonging to m (m≧1) CDM groups and q antenna ports, where the q antenna ports are associated with l=m UL-TCI states, and the l UL-TCI states are indicated via a field indicating up to l UL-TCI states in a DCI or higher layer grant scheduling a PUSCH, and the DMRS port associated with the i-th CDM group is mapped to the antenna port corresponding to the antenna port associated with the indicated i-th UL-TCI state.

[0141] If the DMRS and antenna port are pointed to for n>1 PUSCH transmission opportunities, where n=m, the i-th PUSCH is transmitted using the DMRS port corresponding to the i-th CDM group and the antenna port associated with the i-th UL-TCI state. If the DMRS and antenna port are pointed to for n=1 PUSCH transmission opportunities, where l segments of the PUSCH are transmitted, where l=m, the i-th PUSCH segment is transmitted using the DMRS port corresponding to the i-th CDM group and the antenna port associated with the i-th UL-TCI state.

[0142] The above method may be used to schedule PUSCH transmissions using any of the multiplexing techniques previously mentioned (TDM, FDM, or SDM). According to another embodiment, a UE is configured to receive a single PDCCH or configured with a higher layer grant to schedule n (n≧1) PUSCH transmission opportunities, and the UE is configured to receive an indication of m DMRS ports (m≧1) and perform each PUSCH transmission using the m indicated DMRS ports, i.e., the same set of DMRS ports is used for transmission of all n PUSCH transmissions. Depending on the number of scheduled PUSCH transmissions and / or the antenna port indication, a DMRS-to-antenna port mapping can be determined. This means that all PUSCH transmissions have the same number of data layers or streams.

[0143] When n>1 PUSCH transmissions are scheduled and q antenna ports are indicated via the SRI field or UL-TCI state indication field in the scheduling PDCCH or higher layer grant, which respectively point to up to l=n SRS resources or UL-TCI states, each PUSCH transmission is performed using the same set of m indicated DMRS ports and antenna ports associated with the i-th SRS resource or i-th UL-TCI state.

[0144] When n=1 PUSCH transmissions are scheduled and q antenna ports are indicated via the SRI field or UL-TCI state indication field in the scheduling PDCCH or higher layer grant indicating up to l>n SRS resources or UL-TCI states, respectively, the UE performs l segment transmissions of the PUSCH, where each PUSCH segment is transmitted on the same set of m indicated DMRS ports and antenna ports associated with the i-th SRS resource or i-th UL-TCI state.

[0145] In the above method, only one DMRS port may be used for every transmission opportunity. In the next embodiment, it is proposed that the UE may apply precoding between the DMRS port and the antenna / SRS port.

[0146] According to one embodiment, if a UE is configured to perform one or more PUSCH transmissions or transmissions of one or more PUSCH segments via a single PDCCH or higher layer grant, and a specific mapping between DMRSs and antenna ports is signaled to the UE for the PUSCH transmissions as described in one or more of the above methods, and if the scheduling PDCCH or higher layer grant does not provide a precoding vector or matrix to be applied for at least one of the scheduled PUSCH (or PUSCH segment) transmissions, the UE may apply a specified default precoder matrix or vector, or the precoder matrix or vector may be left to the UE implementation.

[0147] For example, if the number of DMRS ports and SRS ports is the same, the precoder matrix or vector used by the UE for PUSCH transmission is given by an identity or diagonal matrix, i.e., the precoding matrix or vector for the ith PUSCH associated with x DMRS ports mapped to x antenna ports is

[0148]

number

[0149]

number

[0150]

number

[0151] In another example, it may be specified that the precoding matrix or vector for the PUSCH transmission is obtained from one of the precoding matrices or vectors in a codebook for a predetermined number of DMRSs and antenna ports for the transmission.

[0152] According to another embodiment, the UE may map m DMRS ports to p antenna ports for n (n>1) PUSCH transmissions or n (n>1) segments of a single PUSCH transmission via a single PDCCH or via a higher layer grant, with up to m≧n DMRS ports, p≧m antenna ports, and n precoding matrices or vectors {F1,...,F nThe network node may be configured to receive an indication of the UL-TCI states, where the antenna port is indicated via an SRS resource indicator field (SRI) present in the scheduling DCI or higher layer grant, or via a field indicating up to n UL-TCI states in the scheduling DCI or higher layer grant. A precoding matrix may be indicated by the network node via a "Precoding and number of layers" field in the scheduling DCI or higher layer grant, where a codepoint in the field of the DCI or a value of a parameter in the higher layer grant may indicate up to n precoding matrices. For example, a first precoding matrix is ​​associated with a first PUSCH (or PUSCH segment) transmission, a second precoding matrix is ​​associated with a second PUSCH (or PUSCH segment) transmission, and so on. In another example, the precoding matrix may be indicated by the network node via a "Precoding and number of layers" field in a scheduling DCI or higher layer grant, where the field is divided into multiple parts or partitions, each part providing a precoding matrix, and each precoding matrix may be associated with at least one PUSCH transmission opportunity or segment.

[0153] In an example scenario, a PDCCH or higher layer grant may schedule two PUSCH transmissions, which point to DMRS ports {p0, p1, p2} along with four antenna ports (via SRI or UL-TCI indication as described above). The scheduling PDCCH or higher layer grant also specifies the precoders for the two PUSCH transmissions.

[0154]

number

[0155]

number

[0156]

number

[0157]

number

[0158] In the given example, the DMRS port may be divided among multiple PUSCH transmissions or multiple segments of a single PUSCH by considering the CDM group of the indicated DMRS port.

[0159] The above DMRS and antenna port indication methods may be combined with any of the multiplexing schemes described above to schedule segmented PUSCH transmissions or multiple PUSCH transmissions.

[0160] The above port indication methods may specify a method for dynamically switching between single-TRP transmission and multi-TRP transmission for codebook-based and non-codebook-based PUSCH transmission.

[0161] According to some example embodiments, when a UE is configured with the higher layer parameter “txConfig” set to the value “codebook” or “nonCodebook”, it expects to receive a single PDCCH or higher layer grant scheduling n (n≧1) PUSCH transmissions (multiple PUSCH transmissions or multiple segments of a single PUSCH transmission).

[0162] For example, if the UE is configured with "codebook" or "nonCodebook" for the higher layer parameter "txConfig," it may receive the PDCCH using DCI format 0_1 ​​or a newly introduced DCI format or higher layer grant that schedules n PUSCH transmissions (n≧1). If the scheduling PDCCH or higher layer grant configures the UE with a codebook-based or non-codebook-based PUSCH depending on one or more of the following parameters: DMRS port, antenna port, precoding information, and TPC command, the UE may transmit a single PUSCH without segmentation or perform segmented / multiple PUSCH transmissions. For example, if the UE is indicated with two precoding matrices for codebook-based PUSCH scheduling, the UE may perform segmented / multiple PUSCH transmissions, and if the UE is indicated with one precoding matrix for codebook-based PUSCH scheduling, the UE may perform a single non-segmented PUSCH transmission.

[0163] In another example, if a UE is pointed to DMRS ports from multiple CDM groups for non-codebook-based PUSCH scheduling, the UE can perform segmented / multiple PUSCH transmissions, and if the UE is pointed to DMRS ports in the same CDM group for non-codebook-based PUSCH scheduling, the UE can perform a single non-segmented PUSCH transmission. This method can pave the way for dynamic switching between codebook / non-codebook-based single-TRP and multi-TRP scheduling of the PUSCH.

[0164] <Indication of power control for multiple PUSCH transmissions> Another parameter of interest is the transmit power control command that powers up or down the PUSCH transmission with respect to the previous transmission. This is performed independently for each PUSCH transmission, which means that the scheduling PDCCH indicates as many TPC commands as there are scheduled PUSCHs or PUSCH segments.

[0165] According to one embodiment, a UE is configured to receive a PDCCH or higher layer grant for scheduling n (n>1) PUSCH transmissions or a single PUSCH transmission having n (n>1) segments, where the scheduling PDCCH may indicate n TPC commands corresponding to the n PUSCH transmissions or the n segments of the single PUSCH transmission. The scheduling PDCCH or higher layer grant may comprise a p-bit field, which may be an existing TPC command field or another field, whose codepoints map to up to n TPC commands for the n PUSCH transmissions or n PUSCH segments scheduled by the PDCCH. The mapping of the codepoints of the field to the n TPC commands may be already known to the UE (each codepoint is specified by default in the TPC command to which it maps) or the mapping may be configured or indicated to the UE via higher layers (e.g., MAC (medium access control), RRC (radio resource control) signaling).

[0166] According to another embodiment, TPC commands for multiple PUSCH transmissions (or segments of PUSCH transmissions) may be indicated via DCI format 2_2, which is exclusively used to indicate TPC commands for PUCCH or PUSCH.

[0167] According to one embodiment, the UE is configured to receive PDCCH using DCI format 2_2, and the DCI indicates a maximum of n (n>1) TPC commands. The field indicating the n TPC commands in the DCI is an existing TPC command field or a new field. The maximum n TPC commands indicated may be applied to a maximum of n PUSCH transmissions or n segments of a PUSCH transmission that are scheduled via a single PDCCH or a higher layer grant. The mapping of the n code points of the field in the DCI to the n TPC commands may already be known to the UE (each code point is specified by the TPC command to which they map by default), or the mapping may be configured or indicated to the UE via a higher layer (e.g., MAC, RRC).

[0168] According to an exemplary embodiment, the field indicating the n (n>1) TPC commands in the DCI format may be extended from a p-bit field to an np-bit field, where the i-th p-bit pattern indicates the TPC command for the i-th PUSCH transmission, and the mapping of the p-bit pattern to the TPC command is specified and known to the UE. For example, the value of p may be equal to 2. If power increase / decrease is indicated for two PUSCH transmissions, the DCI indication may be 4 bits in size, with the first 2 bits indicating the TPC command for the first PUSCH transmission and the next 2 bits corresponding to the second PUSCH transmission, where the mapping of the 2 bits to the TPC command may be as per the specifications of [Non-Patent Documents 2-3]. The np-bit field may include n separate fields each having p bits.

[0169] <Display of Various Parameters for PUSCH Multiplexing> (Redundant Version) When multiple transmissions of the same PUSCH transport block are scheduled by a single PDCCH or higher layer grant, each PUSCH transmission may be associated with a different redundancy version. When the same PUSCH transport block is transmitted with different redundancy versions, the receiver obtains different sets of parity bits added by the channel encoder, which provides diversity in decoding the PUSCH transport block and thereby improves decoding performance. The indication of the redundancy version for the PUSCH may be performed using a combination of higher layer and PHY layer signaling.

[0170] According to one embodiment, the UE is configured to receive a PDCCH or higher layer grant scheduling n (n>1) PUSCH transmissions. Up to n redundancy versions (RVs) may be indicated for the n PUSCH transmissions. All RV values ​​may be indicated in the scheduling PDCCH or higher layer grant. Alternatively, RV values ​​may be indicated via a combination of physical layer and higher layer signaling. Different schemes for RV indication are proposed below.

[0171] In one method, the RV of one of the PUSCH transmissions may be configured or indicated via higher layers, and the RV for the remaining PUSCH transmissions may be indicated via an RV indication field in the PDCCH or higher layer grant, and the value of the RV field may map to a particular RV offset value (the difference of the RV from the indicated RV value) relative to the RV of the first PUSCH transmission.

[0172] In another way, the RV for one of the PUSCH transmissions may be indicated via the scheduling PDCCH or the upper layer grant, and the redundant versions of the remaining PUSCH transmissions may be determined using one or more RV offset values configured via the upper layer indicating the offsets of the RVs of the remaining PUSCH transmissions relative to that indicated via the scheduling PDCCH or the upper layer grant. In one example, the RVs of n' < n PUSCH transmissions scheduled by the PDCCH or the upper layer grant may be provided via the scheduling PDCCH or the upper layer grant, and the RVs of the remaining n - n' transmissions may be determined based on the indicated RV value configured via the upper layer and / or one or more RV offset values.

[0173] (Gap between transmissions in TDM'd PUSCH transmissions) (For TDM'd PUSCH transmissions within a slot as presented earlier in mode 1-1 and mode 1-2), the indication of the symbols for the PUSCH transmissions may be performed, where applicable, by a combination of upper layer and PHY layer signaling. In one way, the symbols scheduled for one of the PUSCHs may be indicated, and the scheduling of the remaining PUSCHs may be determined using the offsets of the PUSCHs from the previous PUSCH transmission.

[0174] According to one embodiment, when a UE is scheduled for n (n>1) PUSCH transmissions via a PDCCH or a higher layer grant, and all PUSCH transmissions are scheduled within the same slot on different time domain resources, the UE is configured to receive from a network node or a gNB a higher layer parameter indicating the number of symbols between two PUSCH transmission opportunities, i.e., the offset of the PUSCH transmission from the previous PUSCH transmission in terms of the number of symbols. If the parameter is not configured when multiple PUSCH transmissions are scheduled within a slot, the UE may assume a default value for the number of symbols between two PUSCH transmissions. For example, if the parameter is not configured, the UE may assume that the number of symbols between any two PUSCH transmission opportunities scheduled via a single PDCCH or a higher layer grant is zero.

[0175] According to another embodiment, when a UE is scheduled via a PDCCH or a higher layer grant having n (n>1) segments of PUSCH transmission, and all segments are scheduled within the same slot on different time domain resources, the UE is configured to receive a higher layer parameter indicating the number of symbols between two segments of the PUSCH transmission, i.e., the offset of the PUSCH segment from the previous PUSCH segment in terms of the number of symbols. If the parameter is not configured when multiple PUSCH transmissions are scheduled within a slot, the UE may assume a default value for the number of symbols between two PUSCH segments. For example, if the parameter is not configured, the UE may assume that the number of symbols between any two PUSCH segments scheduled via a single PDCCH or a higher layer grant is zero.

[0176] <Display of PUSCH Transmission, PUSCH Repetition, and Number of Repetition Patterns> The UE may determine the number of scheduled PUSCH transmissions via a PDCCH or higher layer grant either via explicit higher layer signaling or indirectly via a scheduling PDCCH or higher layer grant.

[0177] According to one embodiment, the UE may be configured to receive an indication from a network node or gNB via a higher layer regarding the number of PUSCH transmissions or segments of PUSCH transmissions that may be scheduled by a single PDCCH or higher layer grant. Upon receiving the indication, the UE may expect a single PDCCH or higher layer grant that schedules the indicated number of PUSCH transmission opportunities or the indicated number of PUSCH segments. All scheduled PUSCH transmission opportunities may be associated with the same PUSCH transport block or different PUSCH transport blocks.

[0178] According to one embodiment, the number of PUSCH transmissions or the number of segments of a single PUSCH transmission scheduled via a PDCCH or higher layer grant may be determined via the number of UL-TCI states or the number of SRS resources or the number of TPC commands or the number of CDM groups of a DMRS port indicated to the UE.

[0179] For example, if the PDCCH or higher layer grant indicates n UL-TCI states, the UE is configured to perform transmission of n PUSCHs or n segments of a single PUSCH, and the i-th PUSCH transmission opportunity or the i-th segment of the single PUSCH is associated with the i-th indicated UL-TCI state.

[0180] In another example, if the scheduling PDCCH or higher layer grant indicates n SRS resources (via the SRI field or any other field indicating SRS resources) or n TPC commands or DMRS ports belonging to n CDM groups, the UE is configured to perform transmission of n PUSCHs or n segments of a single PUSCH, where the i-th PUSCH transmission opportunity or the i-th segment of the single PUSCH is associated with the i-th indicated SRS resource or the i-th indicated TPC command or the DMRS port belonging to the i-th CDM group. All n PUSCH transmissions in this scenario may be associated with the same PUSCH transport block.

[0181] Alternatively, the number of indicated RVs may be used to determine the number of scheduled PUSCH transmission opportunities or PUSCH segments. According to another embodiment, the number of PUSCH transmissions or the number of segments of a single PUSCH transmission scheduled via a PDCCH or higher layer grant may be determined via the number of RVs indicated in the scheduling PDCCH or higher layer grant, or via a combination of physical and higher layer signaling.

[0182] For example, if a UE is indicated a single RV in the PDCCH that schedules a PUSCH, and RV offset values ​​for the other two PUSCHs are indicated to the UE via higher layers, the UE will understand that it must perform a total of three PUSCH transmissions.

[0183] The reliability of the PUSCH can be improved by PUSCH repetition. In a multi-TRP context, repetition of the PUSCH transport block can be performed for different TRPs using a specified or indicated sequence / pattern. In the following embodiments, various methods for PUSCH repetition are provided.

[0184] According to one embodiment, a PDCCH or a higher layer grant for scheduling PUSCH transmission is received, where the n-1 repetitions of the PUSCH transmission opportunity are indicated via the higher layer, that is, a total of n (n>1) PUSCH transmissions will be performed. Also, when the scheduling PDCCH or the higher layer grant indicates p≦n UL-TCI states or p≦n SRS resources, the first UL-TCI state or SRS resource indicated via the scheduling PDCCH or the higher layer grant is associated with m1<n PUSCH transmission opportunities, the second UL-TCI state or SRS resource indicated is associated with m2<n PUSCH transmission opportunities, and so on, and m1+m2+…+m p =n. Each PUSCH transmission is performed using the transmission configuration (which may include antenna ports) provided in the associated UL-TCI state or using the antenna / SRS ports corresponding to the associated SRS resource.

[0185] The mapping of the indicated SRS resource or UL-TCI state to the PUSCH transmission opportunity may be indicated via higher layer signaling and / or a default mapping method may be specified for the UE. This mapping affects the pattern in which the PUSCH transport block is transmitted for each TRP.

[0186] According to another embodiment, if the number of PUSCH repetitions configured for a UE is equal to the number of UL-TCI states or SRS resources indicated via the scheduling PDCCH or higher layer grant, the indicated UL-TCI states or SRS resources may follow the order of PUSCH transmission opportunities, i.e., the first UL-TCI state or SRS resource is associated with the first PUSCH transmission opportunity, the second UL-TCI state or SRS resource is associated with the second PUSCH transmission opportunity, etc. Each PUSCH transmission is performed using the transmission configuration (which may include antenna port) provided in the associated UL-TCI state or using the antenna / SRS port corresponding to the associated SRS resource.

[0187] According to another embodiment, if the configured number of repetitions of PUSCH transmission opportunities is greater than the number of indicated UL-TCI states or SRS resources in the scheduling PDCCH or higher layer grant, the UE is configured to allow a specific pattern (e.g., configured via higher layers) of PUSCH transmission opportunities. In one example, the pattern follows a periodic mapping between the indicated UL-TCI states or SRS resources and the PUSCH transmission opportunities.

[0188] For example, if 2n transmissions of the PUSCH need to be performed and the scheduling PDCCH or higher layer grant indicates two UL-TCI states or two SRS resources, the first UL-TCI state or SRS resource is associated with the first PUSCH transmission opportunity, the second UL-TCI state or SRS resource is associated with the second transmission opportunity, and the same pattern of association is repeated for the remaining PUSCH transmission opportunities (i.e., the first UL-TCI state or SRS resource is associated with the third PUSCH transmission opportunity, the second UL-TCI state or SRS resource is associated with the fourth transmission opportunity, and so on). In one example, a repeating block pattern is used for the association of UL-TCI states or SRS resources. If 2n transmissions of the PUSCH need to be performed and the scheduling PDCCH or higher layer grant indicates two UL-TCI states or two SRS resources, the first UL-TCI state or SRS resource is associated with the odd-numbered (1st, 3rd, ..., (2n-1)th) PUSCH transmission opportunities, and the second TCI state is associated with the even-numbered (2nd, 4th, ..., (2n)th) PUSCH transmission opportunities. In an alternative, the UE may apply a specified pattern of association of the indicated UL-TCI states or SRS resources with PUSCH transmission opportunities without a higher layer indication thereof, i.e., the applied association pattern is fixed in the specification. In a second example, if 2n transmissions of PUSCH need to be performed and the scheduling PDCCH or higher layer grant indicates two UL-TCI states or two SRS resources, the first UL-TCI state or SRS resource is associated with the first and second PUSCH transmission opportunities, the second UL-TCI state or SRS resource is associated with the third and fourth PUSCH transmission opportunities, and this pattern is repeated for the remaining PUSCH transmission opportunities.

[0189] According to one embodiment, if the configured number of repetitions of PUSCH transmission opportunities is greater than the number of groups of indicated SRS resources in the scheduling PDCCH or higher layer grant, each group containing one or more SRS resources, the UE is configured to allow a particular pattern (e.g., configured via higher layers) of PUSCH transmission opportunities. In one example, the pattern follows a periodic mapping between the SRS resources of the indicated groups and the PUSCH transmission opportunities.

[0190] In one example, if 2n transmissions of the PUSCH are to be performed and the scheduling PDCCH or higher layer grant indicates two groups of SRS resources, each group comprising one or more SRS resources, the SRS resources of the first group are associated with the first PUSCH transmission opportunity, the SRS resources of the second group are associated with the second transmission opportunity, and the same pattern of association is repeated for the remaining PUSCH transmission opportunities (i.e., the SRS resources of the first group are associated with the third PUSCH transmission opportunity, the SRS resources of the second group are associated with the fourth transmission opportunity, and so on). In the second example, a repeating block pattern is used. If 2n transmissions of the PUSCH are to be performed and the scheduling PDCCH or higher layer grant indicates two groups of SRS resources, each group comprising one or more SRS resources, then the SRS resources of the first group are associated with the odd-numbered (1st, 3rd, ..., (2n-1)th) PUSCH transmission opportunities, and the SRS resources of the second group are associated with the even-numbered (2nd, 4th, ..., (2n)th) PUSCH transmission opportunities. In a third example, if 2n transmissions of the PUSCH are to be performed and the scheduling PDCCH or higher layer grant indicates two groups of SRS resources, each group comprising one or more SRS resources, then the SRS resources of the first group are associated with the first and second PUSCH transmission opportunities, and the SRS resources of the second group are associated with the third and fourth PUSCH transmission opportunities, and this pattern is repeated for the remaining transmission opportunities. Alternatively, the UE may apply a specified pattern of association of PUSCH transmission opportunities without any higher layer indication thereof, i.e., the applied association pattern is fixed in the specification. Note that the two groups of indicated SRS resources may be associated with two different SRS resource sets.

[0191] In the above embodiment, the UE is configured to use any of the given patterns of application of the provided settings (SRS resource, UL-TCI state, etc.) for the scheduled PUSCH transmission opportunity through the configuration or display of the pattern provided by the network node via the PHY layer or the upper layer, or by a predetermined behavior fixed in the specification.

[0192] The mapping method indicated above can also be applied when m < n TPC commands, TPMI values, or redundancy versions are indicated for n PUSCH transmission opportunities or n PUSCH segments.

[0193] According to another embodiment, if the configured or indicated or scheduled number of repetitions / transmissions / opportunities of the PUSCH is greater than the number of indicated TPC commands, precoder indication (e.g., RI and / or TPMI), or redundancy versions provided for the PUSCH transmission opportunity, the UE is configured to enable a specific pattern (e.g., configured via the upper layer) of application of the TPC command, TPMI value, or redundancy version for the PUSCH transmission opportunity. In one example, the pattern follows a periodic mapping between the above parameters (TPC command, precoder indication, or redundancy version) and the PUSCH transmission opportunity. [[ID=(此处原文ID=9有误,已修正为ID=8)]]

[0194] For example, if 2n transmissions of a PUSCH are scheduled by a PDCCH or higher layer grant and two TPC commands / precoder indications / redundancy versions are provided for these PUSCH transmission opportunities, the first TPC command / precoder indication / redundancy version is associated with the first PUSCH transmission opportunity, the second TPC command / precoder indication / redundancy version is associated with the second transmission opportunity, and the same pattern of association is repeated for the remaining PUSCH transmission opportunities (i.e., the first TPC command / precoder indication / redundancy version is associated with the third PUSCH transmission opportunity, the second TPC command / precoder indication / redundancy version is associated with the fourth transmission opportunity, and so on). In one example, a repeating block pattern is used for the association of the TPC commands / precoder indications / redundancy versions. If 2n transmissions of the PUSCH are scheduled by the PDCCH or higher layer grant and two TPC commands / precoder indications / redundancy versions are provided, the first TPC command / precoder indication / redundancy version is associated with the odd-numbered (1st, 3rd, ..., (2n-1)th) PUSCH transmission opportunities and the second TPC command / precoder indication / redundancy version is associated with the even-numbered (2nd, 4th, ..., (2n)th) PUSCH transmission opportunities. In a second example, if 2n transmissions of the PUSCH are scheduled by the PDCCH or higher layer grant and two TPC commands / precoder indications / redundancy versions are provided, the first TPC command / precoder indication / redundancy version is associated with the first and second PUSCH transmission opportunities and the second TPC command / precoder indication / redundancy version is associated with the third and fourth PUSCH transmission opportunities, and this pattern is repeated for the remaining PUSCH transmission opportunities. In the alternative, the UE may apply a specified pattern of association of indicated TPC commands / precoder indications / redundancy versions with PUSCH transmission opportunities without any higher layer indication thereof.

[0195] In the above methods / examples, the UE is configured to use one of the above given patterns of application of provided settings (RV, precoding indication, TPC commands, etc.) for scheduled PUSCH transmission opportunities via configuration or indication of said pattern provided by a network node via the PHY layer or higher layers or by a predetermined behavior fixed in a specification.

[0196] Another parameter of interest in PUSCH repetition is the so-called start and length indication vector (SLIV), which is used to indicate the start symbol and the number of symbols used for PUSCH transmission in a slot.

[0197] According to one embodiment, if n PUSCH transmission opportunities are scheduled to be transmitted in n different slots via a PDCCH or higher layer grant, all PUSCH transmission opportunities may follow the same start and length indication vector. The SLIV may be indicated by the scheduling PDCCH or higher layer grant, or it may be configured for the UE via higher layers.

[0198] In all of the above methods / embodiments, scheduling of n PUSCH transmissions (n>1) by a single PDCCH or higher layer grant may be enabled via an indication of a repetition parameter. When a PUSCH transmission opportunity is scheduled by a PDCCH or higher layer grant and a repetition value is configured or indicated via a higher layer, the UE repeats the transmission the indicated number of times. Thus, in all of the above and following methods, descriptions of scheduling "n PUSCH transmission opportunities," "n PUSCHs," or "n PUSCH opportunities" may refer to a PUSCH scheduled by a PDCCH or higher layer grant for a total of n transmissions (which may be understood as scheduling with n-1 repetitions of the first PUSCH transmission, or simply n repetitions of PUSCH transmissions), where the value of n or n-1 is indicated via a higher layer. In an alternative embodiment, the repetition parameter or value may be configured and / or indicated via the PHY layer as well.

[0199] Uplink channel sounding for multi-TRP transmission Before a UE performs uplink PUSCH transmission for multiple TRPs, the UE may apply SRS-based channel sounding using one or more SRS resource sets. For such uplink channel sounding, the beam direction (or spatial relationship) and power control setting of the transmitted SRS need to be adjusted for each TRP. Various methods for SRS configuration are discussed below.

[0200] First, the timeline of the sounding process and PUSCH scheduling following an SRS transmission is discussed. Considering an example scenario where a UE is attempting to perform UL transmission for two TRPs, the following sequence of events or steps may follow: 0) If the UE does not satisfy beam compatibility, the UE is configured to perform uplink beam sweeping using SRS transmission, and SRS is configured as "beam management". The UE performs UL channel sounding for both TRPs and thus determines the suitable beam direction for both TRPs. 1) SRS resources in an SRS resource set associated with a first TRP are transmitted by the UE to sound a channel between the UE and the first TRP. The SRS resources are assigned one or more spatial relationships (e.g., spatial relationships obtained from the SRS sounding event in step 0). The SRS resource set is associated with a path loss reference RS associated with the first TRP. 2) Repeat step 1 for the second TRP. 3) The network node indicates to the UE one or more SRS resources from the SRS resource set used in steps 1 and 2 for PUSCH transmission for the two TRPs.

[0201] The SRS resources used for channel sounding for one or more TRPs may be from the same or different SRS resource sets. In the first method, the SRS resources in steps 1 and 2 may be associated with different SRS resource sets, and the SRS resource in the DCI scheduling the PUSCH needs to be indicated.

[0202] According to one embodiment, the UE is configured to receive a single PDCCH or a higher layer grant that schedules n (n>1) PUSCH transmissions or n (n>1) PUSCH segments, and the PDCCH indicates n SRS resources from n different SRS resource sets. The SRS resources may be indicated, for example, via an existing field (e.g., the SRI field) or via a newly defined field of the DCI. Each indicated SRS resource is associated with a PUSCH transmission or a PUSCH segment, and the transmission is performed by the UE using the SRS port associated with the SRS resource. In a special case, the PDCCH or the higher layer grant can provide a maximum of n SRS resources, that is, the number of indicated SRS resources is n’≦n. In one example, a field including n’ SRIs may be provided in the scheduling PDCCH or the higher layer grant. This field can include

[0203] [Number] bits, and b i bits are used for a single SRI, and each SRI indicates an SRS from a different SRS resource set. In a second example, the SRI field can be mapped to n’ SRS resources, and each SRS resource is from a different SRS resource set. When n’<n, the indicated SRS resources can be associated with multiple PUSCH transmission opportunities or PUSCH segments.

[0204] The following method may also be used for non-codebook-based PUSCH. According to one embodiment, the UE is configured to receive a single PDCCH or a higher layer grant that schedules n (n>1) PUSCH transmissions or n (n>1) PUSCH segments, and the PDCCH is from the i-th set with a maximum of 1≦l i ≦R iThe value R for i=1...n points to SRS resources from n' ≤ n different SRS resource sets, selecting the resources. i and / or l i n' may be the same for all values ​​of i or may be different. It may represent the maximum number of layers scheduled for the UE, or the maximum number of layers supported by the UE, or the maximum number of resources in the i-th SRS resource set. It may be reported by the UE, or obtained / determined via PHY layer or higher layer configuration or signaling, or fixed in the NR specifications. SRS resources may be indicated, for example, via an existing field (e.g., an SRI field) or via a newly defined field in the DCI. Each indicated group of SRS resources from the SRS resource set is associated with a PUSCH transmission or PUSCH segment, and the transmission is performed by the UE using the SRS / antenna port associated with the group of SRS resources. In one example, a field containing n' SRIs may be provided in the scheduling PDCCH or higher layer grant. This field may be

[0205]

number

[0206] If multiple SRS resource sets are used for uplink channel sounding for each TRP, the path loss reference RS and spatial relationship for each SRS resource set may be configured or indicated to the UE individually. The network node may jointly trigger the SRS resource sets for multi-TRP uplink channel sounding as proposed in the following exemplary embodiments.

[0207] According to one embodiment, the UE is configured to receive, via a higher layer from a network node or gNB, an indication associating one or more SRS resource sets with a common index (e.g., a trigger state index). A trigger state may be associated with multiple SRS resource sets, thereby enabling transmission of multiple SRS resource sets with a single message via the PHY layer (PUSCH / PDSCH scheduling DCI or PDCCH using any other DCI format) or via a higher layer indicating the associated trigger state. The association of multiple SRS resource sets with a trigger state and the triggering of SRS resource set transmissions via the trigger state may be performed via the same or different communication layers. For example, the trigger state of an SRS resource set may be indicated by a MAC-CE message, and another MAC-CE message from the network node may use the trigger state to trigger one or more SRS resource sets associated with the trigger state. In another example, trigger states for SRS resource sets may be indicated via RRC, and a MAC-CE message or PHY layer indication from a network node may use the trigger state to trigger one or more SRS resource sets associated with the trigger state. Similar to the use of trigger states to trigger or activate transmission of SRS resource sets, they may also be used to deactivate or terminate transmission of an activated or transmitted SRS resource set. The trigger state may be used in a MAC-CE message, a PHY layer indication, or an RRC message, or a combination of two or more thereof, to indicate deactivation, disabling, or termination of transmission of an SRS resource set associated with the trigger state.

[0208] In a second method, the same SRS resource set can be used to sound two TRPs, as described above in steps 1 and 2. In this case, the pathloss reference RS and spatial relationship associated with the SRS resource set need to be associated with the TRP. One method is to reconfigure the pathloss reference RS and spatial relationship of the SRS between SRS transmissions from one TRP to the other via higher layers. However, such a method may result in long latency and signaling overhead, and requires specifying the interval between SRS transmissions for different TRPs. An alternative method is to define SRS resource sets associated with different spatial relationships and pathloss reference RS assumptions for different transmission opportunities without requiring reconfiguration between transmission opportunities.

[0209] In a third method, a single message or signaling may be received by the UE from a network node or gNB to trigger or activate transmission of multiple SRS resource sets. For example, a MAC-CE message may be received by the UE to activate or trigger transmission of multiple SRS resource sets. The MAC-CE message may include at least an identifier or index that maps to each of the multiple activated or triggered SRS resource sets. In another example, the activation or triggering may be included in PHY layer signaling (e.g., downlink control information), and the signaling may include an index or identifier that maps to each of the multiple activated or triggered SRS resource sets. Similarly, deactivation or termination of an activated or transmitting SRS resource set may be performed via a single PHY layer message, a single MAC-CE message, an RRC message, or a combination of two or more thereof, and the identifiers or indexes that map to each of the multiple SRS resource sets to be terminated are present in a message or signaling from at least one of the communication layers.

[0210] According to one embodiment, the UE is configured to receive a PDCCH or a higher layer grant that schedules n (n>1) PUSCH transmissions, and the PDCCH or higher layer grant that schedules indicates an SRS resource via one or more SRI fields in the PDCCH or higher layer grant that schedules. The antenna / SRS port associated with one or more SRS resources indicated by the PDCCH or higher layer grant is used for at least one PUSCH transmission opportunity scheduled by the PDCCH or higher layer grant. The UE may be indicated with a maximum of n'≤n groups of SRS resources, each group includes one or more SRS resources, and all groups of SRS resources are associated with different SRS resource sets. For the indicated group of one or more SRS resources via the SRI field, the SRS resource set to which the SRS resource belongs or is associated can be determined based on at least one of the following methods.

[0211] - The first group of one or more SRS resources indicated by the SRI field is associated with an SRS resource set having an ID s1, and after the SRS resources of the first group in the order of indication by the SRI field, the second group of one or more SRS resources indicated by the SRI field is associated with an SRS resource set having an ID s2, where s2>s1 or s2<s1. This means that the order in which the groups of one or more SRS resources are indicated has a one-to-one mapping with the ordered set of SRS resource sets according to their SRS resource set ID values (e.g., ascending or descending order), and this rule can be fixed in the NR specification. The SRI can be associated with the most recent transmission of the SRS resource set using the above ordering of the SRS resource set indication.

[0212] - A first group of one or more SRS resources indicated by the SRI field is associated with an SRS resource set, the resources of which are most recently transmitted before or after a particular time or reference time t', and a second group of one or more SRS resources indicated by the SRI field, which follows the one or more SRS resources of the first group in the order indicated by the SRI field, is associated with the SRS resource set that is second most recently transmitted before or after the particular time or reference time t'. In a special case, when the SRI field indicates SRS resources from only one SRS resource set, or when an indication of a single group of one or more SRS resources from one of the SRS resource sets is valid, selected, or considered, the SRS resource set that was most recently transmitted with respect to the particular time or reference time t' is the referenced or associated SRS resource set.

[0213] The antenna ports associated with the SRS resources indicated by the one or more SRI fields are used for PUSCH transmission in at least one of the n scheduled PUSCH opportunities. The mapping of the SRI fields to PUSCH transmission opportunities may be in accordance with any of the relevant embodiments of this disclosure.

[0214] The time reference t' may be determined or assumed based on at least one of the following, among others: - the first or last slot / symbol of one of the scheduled PUSCH transmissions, - The first or last slot / symbol of one of the PDCCHs scheduling the PUSCH (the PDCCH / DCI scheduling the PUSCH transmission may be repeated over multiple PDCCHs due to PDCCH reliability). Using the first PDCCH / DCI of multiple PDCCH / DCI repetitions for PUSCH scheduling as a reference would mean that subsequent PDCCHs / DCIs would also provide the same SRI reference, which would be a better choice. If any of the later PDCCHs / DCIs are used, the PDCCHs / DCIs before the reference point may provide a different SRI reference than the PDCCHs / DCIs after the reference point. - the first or last slot / symbol of one of the PDCCHs that triggers the SRS resource set, - the first or last slot / symbol of one of the PDSCHs comprising a MAC-CE command activating an SRS resource set; - The first or last slot / symbol of one of the PUCCH resources carrying a HARQ ACK for the PDSCH with a MAC-CE command activating an SRS resource set.

[0215] Note: The time points t1...t correspond to the start or end of transmission. n For n different UL / DL transmissions, the most recent transmission before or after time t' is |t'-t i |, i=1...n, which has the smallest value.

[0216] The SRS resource sets corresponding to the SRI fields of the scheduling PDCCH or higher layer grant may be associated with different time domain behaviors according to the above embodiments. Depending on the transmission time, the SRS resources corresponding to the SRI fields may be determined regardless of their time domain behavior. However, if a conflict arises regarding which type of SRS resource set should be selected, a corresponding indication for the UE is required when various resource sets with different periodicities exist in the same usage state.

[0217] According to one embodiment, at least one of the following properties of the SRS resource set associated with a first SRI field is the same as that of the SRS resource set corresponding to another SRI field in the scheduling PDCCH or higher layer grant: the usage state of the SRS resource set (all of them may be either codebook or non-codebook SRS resource sets), the time-domain behavior (all of them may be either aperiodic, periodic, or semi-persistent resource sets). This can be ensured in several ways. In a first example, the UE is configured to associate the SRI field with an SRS resource set with the same time-domain behavior as the most recently transmitted SRS resource set before or after the above-mentioned time t', where time t' can be any of the aforementioned reference points. In a second example, the UE is configured to associate the SRI field with an SRS resource set S with the same time-domain behavior as the most recently transmitted SRS resource set before or after the above-mentioned time t', where time t' can be any of the aforementioned reference points. R and SRS resource set S R is determined based on at least one of the following rules: SRS resource set S R has a higher priority for time domain behavior. The priority rule is

[0218]

number

[0219]

number

[0220] - SRS Resource Set S R is configured via higher layers. MAC-CE or RRC signaling may be provided to indicate to the UE which SRS resource to select for a given PDCCH / DCI or higher layer grant, which may be provided in the higher layer grant itself.

[0221] Note: In the above embodiment, the methods applicable to multiple SRS resource sets associated with multiple SRI fields may also be applicable when using a single SRI field associated with multiple SRS resource sets.

[0222] According to one embodiment, a UE is configured to receive higher layer configuration of an SRS resource set, where the SRS resource set includes one or more SRS resources. Each SRS resource is associated with one or more SRS ports. Furthermore, the SRS resource set may be associated with multiple path loss reference RSs. Furthermore, each SRS resource in the configured SRS resource set may be associated with multiple spatial relationship parameters, if applicable. In a variation of this embodiment, the association of the SRS resource set or SRS resources with multiple path loss reference RSs or spatial relationships may be performed via MAC-CE messages or any other higher layer.

[0223] For example, a UE may be configured with one of the above SRS resource sets via higher layers that includes four SRS resources. The SRS resource set may be configured with two pathloss reference RSs, and each SRS resource in the set may be configured with two spatial relationship parameters. When the SRS resources are triggered for transmission, the UE transmits the SRS resources in the SRS resource set at a first transmission opportunity with a first spatial relationship and pathloss reference RS assumption provided in the SRS configuration and at a second transmission opportunity with a second spatial relationship and pathloss reference RS assumption provided in the SRS configuration.

[0224] After the UE performs transmissions on the above SRS resource set on two occasions, the UE can schedule one or more PUSCH transmissions by pointing to one or more SRS resources from the SRS resource set used in sounding on the two occasions, thereby pointing to the antenna ports to be used for PUSCH transmissions.

[0225] Note: In any embodiment of the present disclosure, in downlink control information or higher layer grants, the term "one or more fields" corresponding to a parameter (if applicable) or the indication "one or more values" by a field or codepoint of a field corresponding to a parameter (if applicable) may be interpreted in different ways. A field, if applicable, is interpreted as a collection of x≧1 bits used to indicate one or more values ​​for a particular parameter. When a field is said to provide y≧1 values, this may be done in two different ways:

[0226] - A single codepoint of the field, i.e. a given x-bit pattern of the field, can provide y values, to which the single codepoint is mapped, and this mapping is indicated to the UE by the network node via the PHY layer in higher layer signaling, or is pre-configured or signaled to the UE, i.e. is fixed in the NR specification.

[0227] - A given x-bit pattern of a field, i.e., a code point of the field, contains y partitions or parts, where the i-th part (i=1,…,y) points to the i-th value. The x-bit pattern as a whole provides y values, and the i-th partition or part provides or points to a single value. i The field size is z bits. i For i=1,...y,

[0228]

number

[0229] When multiple fields are said to provide multiple values for the parameter, each field may provide one or more values via a partition of the field or via a mapping of one or more values to a single code point of the field as described above, where a partition of the field for interpreting individual values may not be possible. Thus, the interpretation of fields and their indicated values in the present disclosure may be done in any of the above ways.

[0230] Note: References to the transmission of SRS resource sets in this disclosure refer to the transmission of at least one resource within the SRS resource set. <SRI indication> The indication of SRS resources for n ≧ 1 PUSCH transmissions scheduled via PDCCH or a higher layer grant is done via one or more SRI fields. When one SRI field is used, each code point of the field may provide up to n' ≦ n SRS resources for n PUSCH transmission opportunities. When multiple SRI fields are used, each SRI field may indicate a single SRS resource. In both SRI indication methods, an important issue is the possibility of dynamic switching between single-TRP-based and multi-TRP-based PUSCH transmission scheduling. When a single SRI field is used for the indication of SRS resources, there may be a code point in the field that indicates only one SRS resource from one SRS resource set, thereby enabling PUSCH transmission for a single TRP. When multiple SRI fields are used, dynamic switching between single TRP and multi-TRP needs to be done by other means.

[0231] According to an embodiment, the UE is configured to receive a PDCCH or higher layer grant scheduling n>1 transmissions comprising n′≦n SRI fields, where at least one of the SRI fields may comprise at least one of the following:

[0232] - a reserved codepoint in the SRI field, indicating that no SRS resource is selected from the SRS resource set or sets corresponding to the SRI field; - A 1-bit value indicating whether the SRS resource indicated by the SRI field in the corresponding SRS resource set or sets, which may be provided by the remaining bits of the SRI field, is used for at least one of the PDCCH or PUSCH transmission opportunities scheduled by a higher layer grant. In the special case where the SRI field corresponding to an SRS resource set has a 0 bit, which may occur when the SRS resource set has only one resource, a 1-bit value may still be present to indicate whether the SRS resource set is used.

[0233] According to an embodiment, the UE is configured to receive a PDCCH or higher layer grant scheduling n>1 transmissions comprising n'≦n SRI fields, wherein a b-bit field may be present within the SRI fields, or together with the SRI fields, or as a separate field, where b≧1 and the b-bit field indicates at least one of the following:

[0234] - None of the SRS resources indicated by the SRI field are used for PDCCH or PUSCH transmission opportunities scheduled by higher layer grant.

[0235] - The SRS resource indicated by at least one of the SRI fields is not used for any PDCCH or PUSCH transmission opportunity scheduled by higher layer grant.

[0236] - at least one bit field of the SRI field is not used to determine SRS resources from the corresponding SRS resource set for either PDCCH or higher layer-granted scheduled PUSCH transmission opportunities;

[0237] - that only a proper subset of the SRI field bit fields in the PDCCH or higher layer grant are used for at least one PUSCH transmission opportunity scheduled by the PDCCH or higher layer grant.

[0238] - The SRS resources indicated by all SRI fields in the PDCCH or higher layer grant are used for at least one PUSCH transmission opportunity scheduled by the PDCCH or higher layer grant.

[0239] If one of the SRIs in the PDCCH or higher layer grant that schedules the PUSCH is not used for any of the PUSCH transmission opportunities, other corresponding parameters may also be “disabled.” Examples of the corresponding parameters may include RV values, precoder indexes / values, and / or TPC commands. For example, if a first SRI indicated by the PDCCH or higher layer grant is indicated not to be used for any of the PUSCH transmission opportunities or is not associated with any of the PUSCH transmission opportunities, then a first RV value, precoder index / value, and / or TPC command indicated by the PDCCH or higher layer grant, which may or may not have a correspondence with the first SRI, is also not associated with any of the PUSCH transmission opportunities. If the second SRI indicated by the PDCCH or higher layer grant is indicated not to be used for any PUSCH transmission opportunity, or if the second SRI indicated by the PDCCH or higher layer grant is not associated with any PUSCH transmission opportunity, then the second RV value and / or precoder index / value and / or TPC command indicated by the PDCCH or higher layer grant, which may or may not have a correspondence with the second SRI, are also not associated with any PUSCH transmission opportunity.

[0240] Note: The use of the "SRI field" in the above embodiment can also refer to the use of a single SRI field consisting of multiple partitions or parts, where each partition or part points to an SRI. In this case, each pointed-to SRI can be associated with a different SRS resource set.

[0241] For non-codebook PUSCH, when the number of layers is kept the same in different transmission opportunities, the SRI field may also point to the same number of SRS resources for different PUSCH transmission opportunities.

[0242] According to an embodiment, the UE is configured to receive a PDCCH or higher layer grant scheduling n>1 transmissions comprising n′≦n SRI fields, where a given SRI field indicates the same number of SRS resources as at least one other SRI field.

[0243] It should be noted that the number of scheduled transmission opportunities is not limited to two or any particular number, and therefore the examples presented above do not limit the subject matter of the presented embodiments.

[0244] Using the above higher layer configuration and PHY layer signaling, various PUSCH reliability techniques can be enabled through various methods of multiplexing. In the following, two examples are presented that discuss multi-TRP based PUSCH frameworks that can be realized using the previously described embodiments.

[0245] (Example 1: Higher Layer Indication and DMRS Port Indication Based Multi / Segmented PUSCH) In this example, higher layer indication assisted scheduling of multi-PUSCH or segmented PUSCH is provided, and the multiplexing scheme is determined by a combination of the DMRS port indication and higher layer signaling.

[0246] - The UE may be indicated via the above layers that it can receive PDCCH or higher layer grants scheduling: n PUSCH transmission opportunities (n>1), or One PUSCH transmission opportunity with n (n>1) segments.

[0247] - The multiplexing scheme may be determined via one or more higher layers, e.g., depending on some indicated parameters for the specific multiplexing scheme indication or parameters required for a particular multiplexing scheme. Thus, switching between schemes requires a higher layer indication. The illustration in Figure 3 provides an example where the indicated CDM grouping of DMRS ports together with the higher layer indication of the required parameters determines the multiplexing scheme used in transmission. This is shown in Figure 3 as follows: 301. Higher layer signaling indicating scheduling of multi-PUSCH transmissions (opportunities) or segmented PUSCH transmissions is received by a UE (not shown), for example on a PDCCH, and optionally higher layer signaling indicating a multiplexing scheme.

[0248] 302. If the PDCCH indicates DMRS ports in n (n>1) CDM groups, the following may be done: 302a. If higher layers indicate FDM transmission, the UE performs FDM multi-PUSCH transmission or segmented PUSCH transmission; 302b. If no higher layer signaling of the multiplexing scheme is received, the UE performs SDM multi-PUSCH transmission or segmented PUSCH transmission.

[0249] 303. If the PDCCH points to DMRS ports in n=1 CDM groups, the following may be done: 303a. If scheduling is within a slot and / or higher layer signaling indicates a symbol offset between two transmission opportunities / segments, the UE performs intra-slot TDM of the multi-PUSCH or segmented PUSCH; 303b. If the higher layer signaling indicates a repetition value for the number of PUSCHs, the UE performs inter-slot TDM of the multi-PUSCHs.

[0250] (Example 2: Dynamic switching between multiplexing methods) In this example, a method for using dynamic scheduling of a desired multiplexing scheme over an indicated number of DMRS ports is presented with reference to FIG.

[0251] Figure 4 shows the representations required for each of the following multiplexing schemes: - multi-PUSCH or segmented PUSCH SDM, - Multi-PUSCH or segmented PUSCH FDM, - Intra-slot TDM for multi-PUSCH and segmented PUSCH, or - Multi-PUSCH inter-slot TDM In this exemplary scenario, the multiplexing scheme is dynamically switched between segmented SDM and FDM because no additional higher layer parameters are required for their transmission. Depending on the number of CDM groups, an appropriate multiplexing scheme between SDM and FDM can be scheduled. The selected TDM scheme may be indicated via appropriate higher layer parameters. This framework provides scheduling flexibility using dynamic switching via PHY layer signaling of DMRS ports.

[0252] This is shown in Figure 4 as follows: 401. Higher layer signaling indicating segmented / multi-PUSCH scheduling is received by a UE (not shown), for example on a PDCCH. 402. If the PDCCH points to DMRS ports in n (n>1) CDM groups: 402a. A segmented PUSCH / multi-PUSCH SDM transmission is performed by a UE, with each CDM group associated with one segment or PUSCH transmission opportunity. 403. If the PDCCH indicates DMRS ports in n=1 CDM groups, the following may be done: 403a. When higher layer signaling indicates a multi-PUSCH / segmented PUSCH with a symbol offset between PUSCH transmissions, the UE performs intra-slot TDM of the multi-PUSCH / segmented PUSCH transmissions; 403b. When the higher layer signaling indicates a multi-PUSCH with a repetition value of the number of PUSCHs, the UE performs inter-slot TDM of the multi-PUSCH transmission; 403c. If no additional higher layer parameters are received, and if the higher layer signaling indicates a segmented PUSCH / multi-PUSCH, the UE performs segmented PUSCH / multi-PUSCH FDM transmission on n different sets of PRBs associated with each segment or each PUSCH transmission opportunity.

[0253] The above two examples for multi-PUSCH or segmented PUSCH transmission may be implemented using the previously described embodiments of the present disclosure. Referring to Figure 5, there is shown a flowchart of a method performed by a network node according to some example embodiments described above. As shown, the method includes: (501) A method for providing a PDCCH or higher layer grant scheduling channel for a UE, comprising: configuring a UE to receive a single PDCCH or higher layer grant scheduling at least one PUSCH transmission opportunity for the UE; (502) When one PUSCH transmission opportunity is scheduled, the method comprises: (502a) comprising: scheduling a UE to transmit at least two segments of a PUSCH, each segment of the PUSCH associated with a transmission configuration comprising a set of transmission parameters, and at least one transmission parameter associated with one of the segments of the PUSCH being different from a corresponding transmission parameter associated with at least one other segment of the PUSCH; (503) When multiple PUSCH transmission opportunities are scheduled, the method further comprises: (503a) A method comprising: scheduling at least two PUSCH transmission opportunities for a UE, each PUSCH transmission opportunity being associated with a transmission configuration comprising a set of transmission parameters, and at least one transmission parameter associated with one of the PUSCH transmission opportunities being different from a corresponding transmission parameter associated with at least one other PUSCH transmission opportunity.

[0254] As described above, the transmission configuration including the transmission parameters is included in the PDCCH (or DCI) or a higher layer grant. According to one embodiment, a transmission associated with a PUSCH segment or a PUSCH transmission opportunity includes the following transmission parameters: antenna port, DMRS port, pathloss reference RS for determining a pathloss estimate for the transmission, one or more TPC commands for the transmission, a spatial relationship or beam direction, frequency domain resources, and time domain resources.

[0255] As mentioned above, the method comprises scheduling at least two PUSCH segments or at least two PUSCH transmission opportunities for a UE, wherein the set of PRBs on which at least one PUSCH segment or PUSCH transmission opportunity is scheduled is partially or completely different from the set of PRBs on which at least one other PUSCH segment or other PUSCH transmission opportunity is scheduled.

[0256] The method further comprises scheduling at least two PUSCH segments or at least two PUSCH transmission opportunities for the UE, where all the PUSCH segments or all the PUSCH transmission opportunities are scheduled in the same slot and each PUSCH segment or each PUSCH transmission opportunity is scheduled in a set of symbols that is different from the sets of symbols in which other PUSCH segments or PUSCH transmission opportunities are scheduled, where the same slot means the same time slot.

[0257] As previously described, the method may include scheduling at least two PUSCH segments or at least two PUSCH transmission opportunities for a UE, each PUSCH segment or each PUSCH transmission opportunity being associated with a different set of DMRS ports and / or antenna ports.

[0258] The method further comprises scheduling at least two PUSCH transmission opportunities to the UE, each PUSCH transmission opportunity scheduled in a different slot.

[0259] PUSCH transmission opportunities may be associated with the same or different PUSCH transport blocks. According to one embodiment, the method comprises scheduling at least two PUSCH transmission opportunities or at least two PUSCH segments to a UE, each PUSCH transmission opportunity or PUSCH segment associated with a different antenna port and / or DMRS port, a first set of antenna ports associated with a first SRS resource and a second set of antenna ports associated with a second SRS resource.

[0260] As mentioned above, a single PDCCH or higher layer grant scheduling at least two PUSCH transmission opportunities or at least two PUSCH segments includes an SRS resource indicator field that maps to or points to one or more SRS resources, each SRS resource being associated with at least one PUSCH transmission opportunity or PUSCH segment, and each PUSCH transmission opportunity or PUSCH segment being transmitted using the SRS port of the associated SRS resource.

[0261] A single PDCCH or higher layer grant scheduling at least two PUSCH transmission opportunities or at least two PUSCH segments may comprise an uplink transmission configuration indicator (UL-TCI) field, where the value or codepoint of the UL-TCI field maps to or indicates one or more UL-TCI states, each indicated UL-TCI state being associated with one or more PUSCH transmission opportunities or PUSCH segments, each UL-TCI state providing at least one of the following transmission parameters: DMRS port, antenna port, spatial relationship, and path loss reference RS, and each PUSCH transmission opportunity or PUSCH segment is transmitted using the transmission parameters provided by the associated UL-TCI state.

[0262] A PDCCH or higher layer grant scheduling one or more PUSCH transmission opportunities may indicate at least one antenna port to be used for the PUSCH by means of an SRS resource indicator field indicating one or more SRS resources and at least one spatial relationship or beam direction to be used for the PUSCH by means of an UL-TCI field indicating one or more UL-TCI states.

[0263] According to one embodiment, the method comprises configuring, via a higher layer, for a UE, a number of repetitions of at least one scheduled PUSCH transmission opportunity, wherein the scheduling PDCCH or higher layer grant indicates one or more UL-TCI states and / or one or more SRS resources, and each PUSCH transmission opportunity is associated with one of the indicated UL-TCI states and / or one of the indicated SRS resources. The number of repetitions may be equal to the number of indicated UL-TCI states or SRS resources. If the number of repetitions of the PUSCH transmission opportunity is greater than the number of UL-TCI states or greater than the number of SRS resources, the method comprises configuring the UE to apply a periodic or sequential association pattern between the indicated UL-TCI states or SRS resources and the PUSCH transmission opportunities.

[0264] According to an embodiment, as mentioned above, the PDCCH or higher layer grant may indicate as many TPC commands or SRS resources or UL-TCI states or sets of DMRS ports or redundancy version (RV) values ​​as the number of scheduled PUSCH transmission opportunities or PUSCH segments, with each PUSCH transmission opportunity or PUSCH segment being associated with a different TPC command or SRS resource or UL-TCI state or set of DMRS ports or redundancy version value.

[0265] According to one embodiment, one or more RV offset values ​​may be indicated in the PDCCH, or in a higher layer grant, or by other higher layer signaling, and the RV of at least one PUSCH transmission opportunity is determined using the indicated RV offset value and one of the RVs of another scheduled PUSCH transmission opportunity.

[0266] According to one embodiment, the method may comprise configuring, for the UE, a higher layer parameter indicating an offset in number of symbols between two PUSCH transmission opportunities or two PUSCH segments.

[0267] According to one embodiment, the method may comprise configuring, via a higher layer, for the UE, an indication of a common index or a trigger condition for one or more SRS resource sets, and enabling, via a physical layer or a higher layer, transmission of the SRS resource sets associated with the common index or the trigger condition.

[0268] According to one embodiment, an SRS resource set is associated with multiple pathloss reference RSs via higher layer signaling or configuration, and at least one SRS resource in the SRS resource set is associated with multiple spatial relationships via higher layer signaling or configuration, where a first pathloss reference RS and / or spatial relationship is used for a first SRS transmission opportunity and a second configured pathloss reference RS and / or spatial relationship is used for a second SRS transmission opportunity.

[0269] A network is also provided for implementing the aforementioned process or method steps performed by the network node. FIG. 6 shows a block diagram illustrating a network node. The network node 600 includes a processor 610, a processing circuit or module, a receiving circuit or module 640, a transmitting circuit or module 650, a memory module 620, and a transceiver circuit or module 1330, which may include the transmitting circuit 650 and the receiving circuit 640. The network node 600 further includes an antenna system 660, which includes antenna circuitry for transmitting and receiving signals to and from at least the UE. The antenna system utilizes beamforming, as described above. Operations performed by the network node have been described above. The network node may be considered a TRP.

[0270] The processing module / circuit 610 may include a processor, microprocessor, application specific integrated circuit (ASIC), or field programmable gate array (FPGA), etc., and may be referred to as a "processor." The processor 610 controls the operation of the network node and its components. The memory (circuit or module) 620 includes random access memory (RAM), read-only memory (ROM), and / or another type of memory for storing data and instructions that may be used by the processor 610. In general, it will be understood that the network node in one or more embodiments includes fixed or programmed circuitry configured to perform the operations in any of the embodiments disclosed herein.

[0271] In at least one such example, the processor 610 includes a microprocessor, microcontroller, DSP, ASIC, FPGA, or other processing circuitry configured to execute computer program instructions from a computer program stored on a non-transitory computer-readable medium within or accessible to the processing circuitry. Here, "non-transitory" does not necessarily mean permanent or unchanging storage, but may include working or volatile memory storage, but implies at least some persistent storage. Execution of the program instructions specifically adapts or configures the processing circuitry to perform the operations disclosed in this disclosure. It will be further understood that a network node may comprise additional components.

[0272] The network node 600 may belong to any radio access technology, including 4G or LTE, LTE-A, 5G, advanced 5G, or a combination thereof, supporting beamforming techniques. The network node, comprising a processor and a memory, includes instructions executable by the processor, whereby the network node 600 is operative / configured to perform any one of the subject matter disclosed in this disclosure, including a method according to the appended claims relating to the method performed by the network node and the method steps disclosed above with respect to the operations performed by the network node.

[0273] Referring to Figure 7, a flowchart of a method performed by a UE in accordance with some exemplary embodiments described above is shown. As shown, the method includes: (701) receiving a single PDCCH or higher layer grant from a network node scheduling at least one PUSCH transmission opportunity for a UE; (702) if one PUSCH transmission opportunity is scheduled, the method comprising: (702a) transmitting at least two segments of a PUSCH, each segment of the PUSCH associated with a transmission configuration comprising a set of transmission parameters, and at least one transmission parameter associated with one of the segments of the PUSCH differs from a corresponding transmission parameter associated with at least one other segment of the PUSCH; (703) When multiple PUSCH transmission opportunities are scheduled, the method further comprises: (703a) transmitting at least two PUSCHs, each PUSCH transmission associated with a transmission configuration comprising a set of transmission parameters, and at least one transmission parameter associated with one of the PUSCH transmission opportunities differs from a corresponding transmission parameter associated with at least one other PUSCH transmission opportunity.

[0274] As mentioned above, the transmission configuration associated with a PUSCH segment or a PUSCH transmission opportunity includes the following transmission parameters: antenna port, DMRS port, pathloss reference RS for determining a pathloss estimate for the transmission, TPC command for the transmission, spatial relationship or beam direction, frequency domain resource, and time domain resource.

[0275] The additional operations performed by the UE have already been described in detail. A UE 800 is also provided for performing the aforementioned process or method steps performed by the UE according to the aforementioned embodiments. FIG. 8 shows a block diagram of a UE. The UE 800 includes a processor 810, a receiving circuit or module 840, a transmitting circuit or module 850, a memory module 820, and a transceiver circuit or module 830, which may include the transmitting circuit 850 and the receiving circuit 840. The UE 800 further includes an antenna system 860, which includes antenna circuitry for transmitting and receiving signals to and from at least a network node. The antenna system 860 utilizes beamforming, as described above. Operations performed by the UE have been described above.

[0276] The UE 800 may belong to any radio access technology, including 4G or LTE, LTE-A, 5G, advanced 5G, or a combination thereof, that supports beamforming technology. The UE, which includes a processor 810 and a memory, includes instructions executable by the processor, such that the UE 800 is operative / configured to perform at least the subject matter of claims 22 and 23.

[0277] The processing module / circuit 810 may include a processor, microprocessor, application specific integrated circuit (ASIC), field programmable gate array (FPGA), or the like, and may be referred to as a "processor." The processor 810 controls the operation of the UE and its components. The memory (circuit or module) 820 includes random access memory (RAM), read-only memory (ROM), and / or another type of memory for storing data and instructions that may be used by the processor 810. In general, it will be understood that the UE in one or more embodiments includes fixed or programmed circuitry configured to perform the operations in any of the embodiments disclosed herein.

[0278] In at least one such example, the processor 810 includes a microprocessor, microcontroller, DSP, ASIC, FPGA, or other processing circuitry configured to execute computer program instructions from a computer program stored on a non-transitory computer-readable medium within or accessible to the processing circuitry. Here, "non-transitory" does not necessarily mean permanent or unchanging storage, but may include working or volatile memory storage, but implies at least some persistent storage. Execution of the program instructions specifically adapts or configures the processing circuitry to perform the operations disclosed in this disclosure, including methods according to any one of the appended claims related to methods performed by the UE. It will be understood that the UE 800 may further include additional components.

[0279] References throughout this specification to an "example" or "exemplary" mean that the particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the technology. Thus, appearances of the phrase "in an example" or "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

[0280] Throughout this disclosure, the terms "comprise" or "comprising" are used in a non-limiting sense, i.e., to mean "consist at least of." Although specific terms may be used herein, they are used in a generic and descriptive sense only and not for purposes of limitation. Embodiments herein may be applied to any wireless system, including LTE or 4G, LTE-A (or LTE-Advanced), 5G, advanced 5G, WiMAX®, WiFi®, satellite communications, television broadcasting, etc.

Claims

1. A method performed by a user equipment (UE) (800), comprising: receiving a single Physical Downlink Control Channel (PDCCH) or higher layer grant from a network node (600) scheduling at least two Physical Uplink Shared Channel (PUSCH) transmissions for the UE, all the scheduled at least two PUSCH transmissions are associated with the same PUSCH transport block; The PDCCH or higher layer grant to be scheduled is at least two groups of sounding reference signal (SRS) resources, each group comprising at least one SRS resource, the SRS resources of each group being associated with a different SRS resource set, the SRS resource set being a higher layer configuration comprising one or more SRS resources; at least two transmit power control (TPC) commands; and One or more demodulation reference signal (DMRS) ports The process indicates performing the scheduled at least two PUSCH transmissions, each PUSCH transmission being performed using an SRS port for one of the at least two indicated groups of SRS resources and the indicated one or more DMRS ports in a set of symbols different from any other PUSCH transmissions scheduled by the PDCCH or higher layer grant, and associated with one of the at least two indicated TPC commands.

2. When the number of DMRS ports and the number of SRS ports are the same, the precoder matrix or vector used by the UE for the PUSCH transmission is given by an identity matrix or a diagonal matrix, and the precoder matrix or vector for the i-th PUSCH associated with x DMRS ports mapped to x antenna ports is [Equation 1] or [Equation 2] where: [Equation 3] 2. The method of claim 1, wherein x is an integer value representing the number of the DMRS ports or the number of the antenna ports.

3. The method of claim 1 , wherein an SRS resource in any of the associated SRS resource sets comprises one antenna port / SRS port.

4. The UE supports up to R layers of PUSCH, and all the SRS resource sets have R ｉ 4. The method of claim 1, wherein the UE has 1≦l≦R layers of PUSCH by pointing to l resources from each of the one or more SRS resource sets, allowing the same number of data layers or streams for each PUSCH transmission.

5. 5. The method of claim 1, wherein the scheduling PDCCH or higher layer grant indicates SRS resources of up to n′≦n groups via one or more SRI fields in the scheduling PDCCH or higher layer grant, each group comprising one or more SRS resources, and the SRS resources of every group are associated with a different SRS resource set.

6. The method described in claim 5, wherein if the number of repetitions of the at least two scheduled PUSCH transmissions is greater than the number of groups of the indicated SRS resources, the UE applies a periodic or sequential association pattern between the SRS resources of the at least two indicated groups and the at least two scheduled PUSCH transmissions.

7. 7. The method of claim 6, wherein if 2n transmissions of a PUSCH are performed and the scheduling PDCCH or higher layer grant indicates SRS resources of two groups of the indicated at least two groups of SRS resources, each group comprising one or more SRS resources, SRS resources of a first group are associated with a first PUSCH transmission, SRS resources of a second group are associated with a second PUSCH transmission, and the same pattern of association is repeated for the remaining PUSCH transmissions.

8. 7. The method of claim 6, wherein, when 2n transmissions of a PUSCH are performed and the scheduling PDCCH or higher layer grant indicates SRS resources of two groups of the indicated at least two groups of SRS resources, each group comprising one or more SRS resources, SRS resources of a first group are associated with odd-numbered, i.e., first, third, ..., (2n-1), PUSCH transmissions and SRS resources of a second group are associated with even-numbered, i.e., second, fourth, ..., (2n) PUSCH transmissions, or SRS resources of the first group are associated with the first and second PUSCH transmissions and SRS resources of the second group are associated with the third and fourth PUSCH transmissions, and the pattern is repeated for the remaining transmissions.

9. A method according to any one of claims 1 to 8, wherein each PUSH transmission of the at least two scheduled PUSH transmissions is scheduled in a different slot.

10. A method according to any one of claims 1 to 9, wherein the scheduling of at least two PUSCH transmissions by the single PDCCH or the higher layer grant is enabled via indication of a recurrence parameter via the PHY layer or higher layer.

11. 11. The method of claim 1, comprising receiving from the network node a higher layer parameter indicating that the UE will receive the single PDCCH or the higher layer grant scheduling n (n≧1) PUSCH transmissions, wherein a transmission configuration of the PUSCH transmission is set to a "multiPUSCH" parameter indicating that the UE will receive a single PDCCH scheduling one or more PUSCH transmissions, or the higher layer configuration of the PUSCH comprises an additional parameter indicating the scheduling of one or more PUSCH transmissions using the single PDCCH or the higher layer grant.

12. 12. The method according to claim 1, wherein at least one of the following parameters associated with the PDCCH or a PUSCH transmission scheduled by a higher layer grant is different from the parameters associated with other PUSCH transmissions scheduled by the PDCCH or a higher layer grant, the following parameters being a transmit power control (TPC) command, a path loss reference RS, and a spatial relationship.

13. 13. The method of claim 12, wherein the spatial relationship used for the PUSCH transmission is indicated via an uplink transmission configuration indication (UL-TCI) field in downlink control information (DCI) or a higher layer parameter indicating a UL-TCI state.

14. A method according to any one of claims 1 to 13, wherein if the number of repetitions of the at least two scheduled PUSCH transmissions is greater than the number of TPC commands or precoder indications or redundancy versions (RVs) indicated for the PUSCH transmissions, the UE is configured to enable a periodic or sequential pattern of application of the TPC commands, precoder indications or redundancy versions for the PUSCH transmissions.

15. 15. The method of claim 14, wherein, when 2n transmissions of a PUSCH are scheduled by a PDCCH or a higher layer grant and two TPC commands / precoder indications / RVs are indicated for the PUSCH transmissions, a first TPC command / precoder indication / redundancy version is associated with odd-numbered, i.e., first, third, ..., (2n-1), PUSCH transmissions and a second TPC command / precoder indication / redundancy version is associated with even-numbered, i.e., second, fourth, ..., (2n) PUSCH transmissions, or the first TPC command / precoder indication / redundancy version is associated with the first and second PUSCH transmissions and the second TPC command / precoder indication / redundancy version is associated with the third and fourth PUSCH transmissions, and the pattern is repeated for the remaining PUSCH transmissions.

16. If the PDCCH or the higher layer grant indicates, via one or more SRI fields, one or more groups of SRS resources, each group comprising one or more SRS resources, the SRS resource set to which the SRS resource belongs or is associated is: A first group of one or more SRS resources indicated by the SRI field has ID s １ and a second group of one or more SRS resources indicated by the SRI field that is associated with an SRS resource set having ID s ２ where s ２ >s １ or s ２ <s １ and the SRI is associated with the most recent transmission of the SRS resource set using the order of indication; 16. The method of claim 1, wherein the SRI field indicates SRS resources from only one SRS resource set, or when an indication of a single group of one or more SRS resources from one of the SRS resource sets is valid, selected, or considered, the most recently transmitted SRS resource set with respect to the reference time t′ is the referenced or associated SRS resource set.

17. The received PDCCH or higher layer grant scheduling n>1 PUSCH transmissions comprises n′≦n SRI fields, and a b-bit field is present within, together with, or as a separate field of the SRI fields, where b≧1, and the b-bit field is none of the SRS resources indicated by the SRI field are used for the PDCCH or the PUSCH transmission scheduled by a higher layer grant; the SRS resource indicated by at least one of the SRI fields is not used for either the PDCCH or the PUSCH transmission scheduled by a higher layer grant; at least one bit field of the SRI field is not used to determine the SRS resource from the corresponding SRS resource set for either the PDCCH or the PUSCH transmission scheduled by a higher layer grant; only a proper subset of the SRI field bit fields in the PDCCH or higher layer grant are used for at least one PUSCH transmission scheduled by the PDCCH or higher layer grant; 17. The method according to claim 1, wherein the SRS resources indicated by all SRI fields in the PDCCH or higher layer grant indicate at least one of being used for at least one PUSCH transmission scheduled by the PDCCH or higher layer grant.

18. A user equipment (UE) (800) comprising a processor (810) and a memory (820), the memory (820) including instructions executable by the processor (810); receiving a single Physical Downlink Control Channel (PDCCH) or higher layer grant from a network node (600) scheduling at least two Physical Uplink Shared Channel (PUSCH) transmissions for the UE, all the scheduled at least two PUSCH transmissions are associated with the same PUSCH transport block; The PDCCH or higher layer grant to be scheduled is at least two groups of sounding reference signal (SRS) resources, each group comprising at least one SRS resource, the SRS resources of each group being associated with a different SRS resource set, the SRS resource set being a higher layer configuration comprising one or more SRS resources; at least two transmit power control (TPC) commands; and One or more demodulation reference signal (DMRS) ports The process indicates a UE (800) configured to: perform the scheduled at least two PUSCH transmissions, each PUSCH transmission being performed using an SRS port for one of the at least two indicated groups of SRS resources and the indicated one or more DMRS ports in a set of symbols different from any other PUSCH transmissions scheduled by the PDCCH or higher layer grant, and associated with one of the at least two indicated TPC commands.

19. 19. The UE (800) of claim 18, wherein the UE (800) is configured to perform the method of any one of claims 2 to 17.

20. A method performed by a network node (600), comprising: A transmitting step of transmitting, to a UE (800), a single Physical Downlink Control Channel (PDCCH) or higher layer grant scheduling at least two Physical Uplink Shared Channel (PUSCH) transmissions for the UE, comprising: all the scheduled at least two PUSCH transmissions are associated with the same PUSCH transport block; The PDCCH or higher layer grant to be scheduled is at least two groups of sounding reference signal (SRS) resources, each group comprising at least one SRS resource, the SRS resources of each group being associated with a different SRS resource set, the SRS resource set being a higher layer configuration comprising one or more SRS resources; at least two transmit power control (TPC) commands; and One or more demodulation reference signal (DMRS) ports the transmitting step indicating receiving the at least two scheduled PUSCH transmissions from the UE (800), wherein each PUSCH transmission is performed using an SRS port for one of the at least two indicated groups of SRS resources and the indicated one or more DMRS ports in a set of symbols different from any other PUSCH transmissions scheduled by the PDCCH or higher layer grant, and is associated with one of the at least two indicated TPC commands.

21. A network node (600) comprising a processor (610) and a memory (620), said memory (620) containing instructions executable by said processor (610), said network node (600) comprising: A transmitting step of transmitting, to a UE (800), a single Physical Downlink Control Channel (PDCCH) or higher layer grant scheduling at least two Physical Uplink Shared Channel (PUSCH) transmissions for the UE, comprising: all the scheduled at least two PUSCH transmissions are associated with the same PUSCH transport block; The PDCCH or higher layer grant to be scheduled is at least two groups of sounding reference signal (SRS) resources, each group comprising at least one SRS resource, the SRS resources of each group being associated with a different SRS resource set, the SRS resource set being a higher layer configuration comprising one or more SRS resources; at least two transmit power control (TPC) commands; and One or more demodulation reference signal (DMRS) ports the transmitting step indicating and receiving from the UE (800) the scheduled at least two PUSCH transmissions, each PUSCH transmission being performed using an SRS port for one of the at least two indicated groups of SRS resources and the indicated one or more DMRS ports in a set of symbols different from any other PUSCH transmissions scheduled by the PDCCH or higher layer grant, and associated with one of the at least two indicated TPC commands.

Images