Simultaneous uplink transmission in a multiple transmit / receive point configuration

Abstract

A method for wireless communication includes, upon determining that a network device and a wireless device operating in a multiple transmit / receive point wireless configuration satisfy a condition, transmitting one or more uplink control transmissions using codebook-based precoding, the one or more uplink control transmissions being performed in accordance with configuration information received from the network device indicating one or more sounding reference signal (SRS) resource sets associated with the one or more uplink control transmissions.

Description

[Technical Field]

[0001] TECHNICAL FIELD This document relates to systems, devices, and techniques for wireless communications. [Background technology]

[0002] Efforts are currently underway to define next generation wireless communication networks that offer greater deployment flexibility, support for multiple devices and services, and different techniques for efficient bandwidth utilization. Summary of the Invention [Means for solving the problem]

[0003] Various methods and apparatus for supporting configuration and transmission of an uplink control channel in a wireless communication system that supports a multi-transmit / receive point configuration.

[0004] In one exemplary aspect, a method of wireless communication is disclosed. The method includes, upon determining that a network device and a wireless device operating in a multiple transmit / receive point wireless configuration satisfy a condition, transmitting one or more uplink control transmissions using codebook-based precoding. The one or more uplink control transmissions are performed according to configuration information received from the network device indicating one or more sounding reference signal (SRS) resource sets associated with the one or more uplink control transmissions.

[0005] In another exemplary aspect, another method of wireless communication is disclosed. The method includes, upon determining that a network device and a wireless device operating in a multiple transmit / receive point wireless configuration satisfy a condition, transmitting one or more uplink control transmissions using non-codebook-based precoding. The one or more uplink control transmissions are performed in accordance with configuration information received from the network device indicating one or more sounding reference signal (SRS) resource sets associated with the one or more uplink control transmissions.

[0006] In yet another exemplary aspect, another method of wireless communication is disclosed, the method including, when a network device and a wireless device operating in a multiple transmit / receive point wireless configuration determine that a condition is satisfied, transmitting one or more uplink control transmissions according to a schedule from the network device, the one or more uplink control transmissions being performed according to a frequency domain resource allocation provided by the network device.

[0007] In yet another exemplary aspect, another method of wireless communication is disclosed. The method includes transmitting, by a network device, configuration information to a wireless device indicating one or more sounding reference signal (SRS) resource sets associated with one or more uplink control transmissions, and receiving, from the wireless device satisfying a condition and operating in a multiple transmit / receive point wireless configuration, the one or more uplink control transmissions using codebook-based precoding in accordance with the configuration information.

[0008] In yet another exemplary aspect, another method of wireless communication is disclosed. The method includes transmitting, by a network node, configuration information to a wireless device, the configuration information indicating one or more sounding reference signal (SRS) resource sets associated with one or more uplink control transmissions that the wireless device should use when a condition is met while operating in a multiple transmit / receive point radio configuration with the network device, and receiving, from the wireless device, the one or more uplink control transmissions using non-codebook-based precoding in accordance with the condition.

[0009] In yet another exemplary aspect, another method of wireless communication is disclosed that includes transmitting, by a network device, to the wireless device, a schedule for use by the wireless device operating in a multiple transmit / receive point wireless configuration to perform one or more uplink control transmissions to the network device upon satisfaction of a condition, and receiving, by the network device, the one or more uplink control transmissions in accordance with the schedule.

[0010] In yet another exemplary aspect, a wireless communication device is disclosed, comprising a processor configured to implement the methods described herein.

[0011] In another exemplary aspect, the various techniques described herein may be embodied as processor-executable code and stored on a computer-readable program medium.

[0012] The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features will be apparent from the description and drawings, and from the claims. [Brief explanation of the drawings]

[0013] [Figure 1] FIG. 1 is a block diagram of an example wireless communication device.

[0014] [Figure 2] FIG. 2 illustrates an exemplary wireless communication network.

[0015] [Figure 3A] 3A-3F are flowcharts of example wireless communication methods according to some implementations of the disclosed technology. [Figure 3B] 3A-3F are flowcharts of example wireless communication methods according to some implementations of the disclosed technology. [Figure 3C] 3A-3F are flowcharts of example wireless communication methods according to some implementations of the disclosed technology. [Figure 3D] 3A-3F are flowcharts of example wireless communication methods according to some implementations of the disclosed technology. [Figure 3E] 3A-3F are flowcharts of example wireless communication methods according to some implementations of the disclosed technology. [Figure 3F] 3A-3F are flowcharts of example wireless communication methods according to some implementations of the disclosed technology. DETAILED DESCRIPTION OF THE INVENTION

[0016] Section headings are used herein merely to improve readability and do not limit the scope of the disclosed embodiments and techniques within each section to that section alone. Furthermore, some embodiments are described with reference to the 3rd Generation Partnership Project (3GPP®) New Radio (NR) standard ("5G") for ease of understanding, and the described techniques may be implemented in different wireless systems implementing protocols other than 5G protocols.

[0017] In current 5G NR systems, several transmission schemes of multiple transmit / receive point (MTRP) operation are supported for uplink (UL) transmission in addition to single transmit / receive point (STRP) operation to improve the reliability and throughput of the UL channel or signal. However, due to current UE capability limitations, multiple uplink transmissions can only be implemented as non-overlapping in the time domain even when the UE is equipped with two or more panels, which would be a bottleneck for the reliability and throughput of the entire system if multi-TRP-based uplink transmissions could be supported.

[0018] With the evolution of mobile communication technology, a UE equipped with multiple panels may be supported to simultaneously transmit two or more uplink transmissions. Meanwhile, due to different channel conditions of the links between the multiple panels of a UE and multiple TRPs during MTRP operation, some transmission parameters (e.g., transmission precoder and spatial relationship indication) should be set between the panels and the TRPs for better performance.

[0019] Based on the above, several specific issues need to be addressed for the case of simultaneous uplink transmissions across multiple UE panels and towards different TRPs: (i) How to determine the SRS resource set configured for CB-based simultaneous PUSCH repetition in MTRP operation? (ii) How to determine the SRS resource set configured for CB-based simultaneous PUSCH non-repetition in MTRP operation? (iii) How to determine the SRS resource set configured for NCB-based simultaneous PUSCH repetition in MTRP operation? (iv) How to determine the SRS resource set configured for NCB-based simultaneous PUSCH non-repetition in MTRP operation? (v) How to determine the frequency-domain resource allocation for simultaneous PUSCH transmissions in MTRP operation?

[0020] The following abbreviations are used within this document: [Table 1]

[0021] In Release 15 and Release 16NR, due to PUSCH transmissions directed to only a single TRP, the UE uses the same indicated information for transmissions repeated over multiple slots, which means that each of these transmissions uses the same spatial relationship and transmit precoder. Note that both codebook-based and non-codebook-based PUSCH transmissions are supported from Release 15 onwards.

[0022] For codebook-based PUSCH transmission, the PUSCH can be scheduled by DCI (i.e., DCI format 0_0, DCI format 0_1, DCI format 0_2) or RRC signaling (i.e., higher layer parameter ConfiguredGrantConfig), and the UE determines its PUSCH transmission precoder based on the SRI, TPMI, and transmission rank. In this case, the SRI, TPMI, and transmission rank are given by several fields in the DCI (i.e., SRS resource indicator field, second SRS resource indicator field, number of second precoding information and layers field, number of precoding information and layers field) or several higher layer parameters in the RRC signaling (i.e., srs-ResourceIndicator, srs-ResourceIndicator2, precodingandNumberOfLayers, precodingandNumberOfLayers2).

[0023] For non-codebook-based PUSCH transmission, in contrast to codebook-based schemes, when multiple SRS resources are configured in an SRS resource set, the UE determines its precoder and transmission rank based on the SRI, which is given by the SRS resource indicator in the DCI. Specifically, the UE shall use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be configured for the UE for simultaneous transmission in the same symbol in an SRS resource set and the maximum number of SRS resources are UE capabilities. Simultaneously transmitted SRS resources occupy the same RB. Only one SRS port for each SRS resource is configured. Only one SRS resource set can be configured with the higher layer parameter usage in SRS-ResourceSet set to "nonCodebook." The maximum number of SRS resources in one SRS resource set that can be configured for non-codebook-based PUSCH transmission is four. The SRI indicated in slot n is associated with the most recent transmission on the SRS resource identified by the SRI, and the SRS transmission precedes the PDCCH carrying the SRI. The UE can then calculate the precoder to be used for the SRS transmission based on measurements of the associated NZP CSI-RS resource. The UE's selection of the precoder (and number of layers) for each scheduled PUSCH may be modified by the network (if multiple SRS resources are configured). The UE shall transmit the PUSCH using the same antenna port as the SRS port on the SRS resource indicated by the SRI given by the DCI.

[0024] (Example of frequency domain resource allocation)

[0025] The resource allocation type (in the frequency domain) indicates the method for resource allocation in the frequency domain. The resource allocation type specifies how the scheduler allocates resource blocks for each transmission.

[0026] According to the current approach in 3GPP specifications, the resource allocation type is determined implicitly by the DCI format or by RRC signaling, as described below.

[0027] The UE may assume that downlink resource allocation type 1 is used when a scheduling advance grant is received using DCI format 1_0.

[0028] If the scheduling DCI is configured to indicate the uplink resource allocation type as part of the frequency domain resource allocation field, the UE shall use the uplink resource allocation type 0 or type 1 as defined by this field. Otherwise, the UE shall use the uplink frequency resource allocation type as defined by the higher layer parameter resourceAllocation for the PUSCH.

[0029] (Allocation Type 0)

[0030] In this type, a certain number of consecutive RBs are bundled into an RBG (Resource Block Group) and PUSCH is allocated only in multiples of the RBG. The number of RBs in an RBG varies depending on the bandwidth portion size and configuration, as shown in the table below. The configuration type is determined by the higher layer parameter rbg-Size in PDSCH-Config. A bitmap in the DCI indicates the RBG number carrying the PDSCH or PUSCH data. Since this is a bitmap, it is not required that the RBGs be contiguous. [Table 2]

[0031] (Allocation Type 1)

[0032] In this type, resources are allocated to one or more consecutive RBs. The resource allocation area is defined by two parameters: RB_Start and the Number of Consecutive REs within a specific BWP. When resource allocation is specified in the DCI, the RB_Start and the Number of Consecutive REs within a specific BWP are combined into a specific single value called the RIV (Resource Indicator Value).

[0033] (Dynamic Switch)

[0034] Whether to use Type 0 or Type 1 is determined at each transmission by the frequency domain resource allocation field in the DCI.

[0035] If the scheduling DCI is configured to indicate the uplink resource allocation type as part of the frequency domain resource allocation field by setting the higher layer parameter resourceAllocation in pusch-Config to 'dynamicSwitch' for DCI format 0_1 or by setting the higher layer parameter resourceAllocationDCI-0-2 in pusch-Config to 'dynamicSwitch' for DCI format 0_2, the UE shall use the uplink resource allocation type 0 or type 1 as defined by this DCI field. Otherwise, the UE shall use the uplink frequency resource allocation type as defined by the higher layer parameter resourceAllocation for DCI format 0_1 or the higher layer parameter resourceAllocationDCI-0-2 for DCI format 0_2. The UE shall assume that uplink type 2 resource allocation is used when the scheduling PDCCH is received using DCI format 0_1 and useInterlacePUCCH-PUSCH in BWP-UpLInkDedicated is configured.

[0036] When resourceAllocation is configured as "dynamicSwitch", the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, with a bit value of 0 indicating resource allocation type 0 and a bit value of 1 indicating resource allocation type 1.

[0037] (Other aspects)

[0038] Generally, 5G NR includes a number of MIMO features that facilitate the use of multiple antenna elements at a base station for both the sub-6 GHz (frequency range 1, FR1) and above-6 GHz (frequency range 2, FR2) frequency bands. In addition, one of the MIMO features is that it supports multi-TRP operation. The key to this functionality is to cooperate with multiple TRPs to transmit or receive data to or from a UE to improve transmission performance. As NR is in the process of commercialization, various aspects requiring further improvement can be identified from actual deployment scenarios. According to the current evolution for 5G NR in 3GPP, simultaneous uplink transmission can be supported and implemented by a multi-panel UE in MTRP operation, which is beneficial for improving the throughput of uplink transmission.

[0039] In some embodiments, a "simultaneous uplink transmission scheme" refers to multiple uplink transmissions that can fully or partially overlap in the time domain, that can be associated with different panel / TRP IDs, and that can be scheduled by a single DCI or multiple DCIs. Additionally, whether a UE supports a "simultaneous uplink transmission scheme" can be reported as an optional capability of the UE.

[0040] In some embodiments, a "TRP" corresponds to at least one of an SRS resource set, a spatial relationship, a power control parameter set, a TCI state, a CORESET, a CORESETPoolIndex, a physical cell index (PCI), a subarray, a CDM group of DMRS ports, a group of CSI-RS resources, or a CMR set.

[0041] In some embodiments, a "UE panel" refers to at least one of a UE capability set, an antenna group, an antenna port group, a beam group, a subarray, an SRS resource set, or a panel mode.

[0042] In some embodiments, the definition of "beam state" refers to at least one of a quasi-co-location (QCL) state, a transmission configuration indicator (TCI) state, a spatial relationship (also referred to as spatial relationship information), a reference signal (RS), a spatial filter, or precoding. Furthermore, in this patent, a "beam state" is also referred to as a "beam." Specifically, -The definition of "Tx beam" is at least one of a QCL state, a TCI state, a spatial relationship state, a DL reference signal, a UL reference signal, a Tx spatial filter, or a Tx precoding; -The definition of "Rx beam" is at least one of a QCL state, a TCI state, a spatial relationship state, a spatial filter, an Rx spatial filter, or an Rx precoding; The definition of "Beam ID" is at least one of a QCL state index, a TCI state index, a spatial relationship state index, a reference signal index, a spatial filter index, or a precoding index.

[0043] Specifically, the spatial filter can be either on the UE side or the gNB side, and the spatial filter is also referred to as a spatial domain filter.

[0044] In some embodiments, the "spatial relationship" consists of one or more reference RSs, which is used to represent an identical or near-identical "spatial relationship" between a targeted "RS or channel" and one or more reference RSs.

[0045] In some embodiments, "spatial relationship" also refers to at least one of a beam, a spatial parameter, or a spatial domain filter.

[0046] In some embodiments, a "QCL state" consists of one or more reference RSs and their corresponding QCL type parameters, where the QCL type parameters include at least one of the following aspects or combinations: [1] Doppler spread, [2] Doppler shift, [3] delay spread, [4] mean delay, [5] mean gain, and [6] spatial parameters (also referred to as spatial Rx parameters). In this patent, a "TCI state" refers to a "QCL state." In this patent, the following definitions exist for "QCL Type A," "QCL Type B," "QCL Type C," and "QCL Type D." - "QCL Type A": {Doppler shift, Doppler spread, mean delay, delay spread} - "QCL Type B": {Doppler shift, Doppler broadening} - "QCL Type C": {Doppler shift, average delay} - "QCL Type D": {Spatial Rx parameters}

[0047] In some embodiments, the RS includes a channel state information reference signal (CSI-RS), a synchronization signal block (SSB) (also referred to as SS / PBCH), a demodulation reference signal (DMRS), a sounding reference signal (SRS), and a physical random access channel (PRACH). Additionally, the RS includes at least a DL reference signal and an UL reference signaling. -DL RS includes at least CSI-RS, SSB, DMRS (e.g., DL DMRS), The UL RS includes at least an SRS, a DMRS (e.g., an UL DMRS), and a PRACH.

[0048] In some embodiments, the "UL signal" can be a PUCCH, a PUSCH, or an SRS.

[0049] In some embodiments, the "DL signal" may be a PDCCH, a PDSCH, or a CSI-RS.

[0050] (Example 1)

[0051] These example embodiments may be used in one aspect to address problem (i) discussed above, for example, by incorporating SRS resource set related configuration for CB-based simultaneous PUSCH repetition in MTRP operation.

[0052] If at least one of the following conditions is met: 1) The UE is scheduled to transmit two or more PUSCH repetitions simultaneously, and the time domain of these PUSCH repetitions is fully or partially overlapping. a. The PUSCH repetition may be at least one of an inter-slot based PUSCH repetition or an intra-slot based PUSCH repetition. 2) Two or more PUSCH repetitions are associated with one or more SRS resource sets, which are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, with the higher layer parameter usage in SRS-ResourceSet set to "codeBook". 3) For a codebook-based transmission scheme, the PUSCH can be scheduled by DCI format 0_1, DCI format 0_2, or RRC signaling. 4) For those PUSCH repetitions that are transmitted simultaneously, each PUSCH repetition is associated with one SRS resource set.

[0053] The UE may obtain and apply the configuration of one or more SRS resource sets associated with these PUSCH repetitions. 1) Furthermore, the SRS resource set configuration is determined by RRC signaling. 2) Further, the SRS resource set configuration includes at least one of the following parameters: a. Parameter-1, the number of SRS resources in the SRS resource set. a) The number of SRS resources configured in different SRS resource sets can be the same or different. i. For an example, if the number of SRS resource sets is two, the number of SRS resources configured in the first SRS resource set is one, and the number of SRS resources configured in the second SRS resource set is two. ii. For another example, if the number of SRS resource sets is two, the number of SRS resources configured in the first SRS resource set is two, and the number of SRS resources configured in the second SRS resource set is two. b) The number of SRS resources configured in different SRS resource sets is determined by the higher layer parameter srs-ResourceIdList in SRS-Config. c) The maximum number of SRS resources configured in an SRS resource set depends on the UE capability report. i. Optionally, the UE reports the maximum number of SRS resources supported in each SRS resource set. ii. Optionally, the UE reports the total number of SRS resources jointly supported in all SRS resource sets. i) Furthermore, if the number of SRS resources configured in each SRS resource set is the same, the number of SRS resources in each SRS resource set is equal to the total number of supported SRS resources divided by the number of configured SRS resource sets. a. For one example, the UE reports that the total number of SRS resources is 4 and the number of configured SRS resource sets is 2, in which case the maximum number of SRS resources configured in each SRS resource set is 2. d) Except when the upper layer parameter ul-FullPowerTransmission is set to "fullpowerMode2", the maximum number of SRS resources configured in an SRS resource set is 2. Otherwise, according to the UE capabilities, a maximum of 2 or 4 SRS resources can be configured in an SRS resource set. e) If a PUSCH repetition is scheduled by DCI format 0_2, its corresponding SRS resource set, together with other configurations in the SRS resource set, is SRS,0_2 The other configuration is used for PUSCH repetitions scheduled by DCI format 0_1 and configured with the higher layer parameter usage of value “codeBook”. i. Furthermore, N configured in different SRS resource sets SRS,0_2 The values of can be the same or different. i) The SRS resource set is configured by the upper layer parameter rs-ResourceSetToAddModListDCI-0-2 or indicated by the SRS resource set indicator field in the DCI. ii) The index of the SRS resource set associated with the PUSCH repetition scheduled by DCI format 0_2 is the same as the index of the SRS resource set associated with the PUSCH repetition scheduled by DCI format 0_1. b. Parameter-2, the number of antenna ports configured in the SRS resource. a) The number of antenna ports for each SRS resource configured in an SRS resource set should be the same. b) The numbers of antenna ports of SRS resources configured in different SRS resource sets may be the same or different. c) The number of antenna ports for SRS resources configured in different SRS resource sets is determined by the higher layer parameter nrOfSRS-Ports in SRS-Config. d) Furthermore, the maximum transmission layer of these PUSCH repetitions should be less than or equal to the minimum of the maximum antenna port of the SRS resources indicated in all SRS resource sets.

[0054] (Example 2)

[0055] These example embodiments may be used in one aspect to address problem (ii) discussed above, for example, by incorporating SRS resource set related configuration for CB-based simultaneous PUSCH transmissions in MTRP operation.

[0056] If at least one of the following conditions is met: 1) The UE is scheduled to transmit two or more PUSCH transmissions simultaneously, and the time domains of these PUSCH transmissions are fully or partially overlapping. a. The PUSCH transmission may be at least one of an inter-slot based PUSCH transmission or an intra-slot based PUSCH transmission. b. The content of each PUSCH transmission is different. 2) Two or more PUSCH transmissions are associated with one or more SRS resource sets, which are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, with the higher layer parameter usage in SRS-ResourceSet set to "codeBook". 3) For a codebook-based transmission scheme, the PUSCH can be scheduled by DCI format 0_1, DCI format 0_2, or RRC signaling. 4) For those PUSCH transmissions that are transmitted simultaneously, each PUSCH transmission is associated with one SRS resource set.

[0057] The UE may obtain and apply the configuration of one or more SRS resource sets associated with these PUSCH transmissions. 1) Furthermore, the SRS resource set configuration is determined by RRC signaling. 2) Furthermore, the SRS resource set configuration includes at least one of the following parameters: a. Parameter-1, the number of SRS resources in the SRS resource set. a) The number of SRS resources configured in different SRS resource sets can be the same or different. i. For an example, if the number of SRS resource sets is two, the number of SRS resources configured in the first SRS resource set is one, and the number of SRS resources configured in the second SRS resource set is two. ii. For another example, if the number of SRS resource sets is two, the number of SRS resources configured in the first SRS resource set is two, and the number of SRS resources configured in the second SRS resource set is two. b) The number of SRS resources configured in different SRS resource sets is determined by the higher layer parameter srs-ResourceIdList in SRS-Config. c) The maximum number of SRS resources configured in an SRS resource set depends on the UE capability report. i. Optionally, the UE reports the maximum number of SRS resources supported in each SRS resource set. ii. Optionally, the UE reports the total number of SRS resources jointly supported in all SRS resource sets. i) Furthermore, if the number of SRS resources configured in each SRS resource set is the same, the number of SRS resources in each SRS resource set is equal to the total number of supported SRS resources divided by the number of configured SRS resource sets. a. For one example, the UE reports that the total number of SRS resources is 4 and the number of configured SRS resource sets is 2, in which case the maximum number of SRS resources configured in each SRS resource set is 2. d) Except when the upper layer parameter ul-FullPowerTransmission is set to "fullpowerMode2", the maximum number of SRS resources configured in an SRS resource set is 2. Otherwise, according to the UE capabilities, a maximum of 2 or 4 SRS resources can be configured in an SRS resource set. e) If a PUSCH transmission is scheduled by DCI format 0_2, its corresponding SRS resource set, together with other configurations in the SRS resource set, is SRS,0_2 SRS resources, which are used for PUSCH transmissions scheduled by DCI format 0_1 and configured with the higher layer parameter usage of the value “codeBook”. i. Furthermore, N configured in different SRS resource sets SRS,0_2 The values of can be the same or different. i) The SRS resource set is configured by the upper layer parameter rs-ResourceSetToAddModListDCI-0-2 or indicated by the SRS resource set indicator field in the DCI. ii) The index of the SRS resource set associated with the PUSCH transmission scheduled by DCI format 0_2 is the same as the index of the SRS resource set associated with the PUSCH transmission scheduled by DCI format 0_1. b. Parameter-2, the number of antenna ports configured in the SRS resource. a) The number of antenna ports for each SRS resource configured in an SRS resource set should be the same. b) The numbers of antenna ports of SRS resources configured in different SRS resource sets may be the same or different. c) The number of antenna ports for SRS resources configured in different SRS resource sets is determined by the higher layer parameter nrOfSRS-Ports in SRS-Config. d) Furthermore, the maximum transmission layer of these PUSCH transmissions should be less than or equal to the maximum antenna port of the SRS resource indicated in its associated SRS resource set.

[0058] (Embodiment Example 3)

[0059] These example embodiments may be used in one aspect to address problem (iii), discussed above, by incorporating, for example, SRS resource set related configuration for NCB-based simultaneous PUSCH repetition in MTRP operation.

[0060] If at least one of the following conditions is met: 1) The UE is scheduled to transmit two or more PUSCH repetitions simultaneously, and the time domain of these PUSCH repetitions is fully or partially overlapping. a. The PUSCH repetition may be at least one of an inter-slot based PUSCH repetition or an intra-slot based PUSCH repetition. 2) Two or more PUSCH repetitions are associated with one or more SRS resource sets, which are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the higher layer parameter usage in SRS-ResourceSet set to "nonCodebook". 3) For non-codebook-based transmission schemes, the PUSCH can be scheduled by DCI format 0_1, DCI format 0_2, or RRC signaling. 4) For those PUSCH repetitions that are transmitted simultaneously, each PUSCH repetition is associated with one SRS resource set.

[0061] The UE may obtain and apply the configuration of one or more SRS resource sets associated with these PUSCH repetitions. 1) Furthermore, the SRS resource set configuration is determined by RRC signaling. 2) Furthermore, the SRS resource set configuration includes at least one of the following parameters: a. Parameter-1, the number of SRS resources in the SRS resource set. a) The number of SRS resources configured in different SRS resource sets can be the same or different. i. For an example, if the number of SRS resource sets is two, the number of SRS resources configured in the first SRS resource set is one, and the number of SRS resources configured in the second SRS resource set is two. ii. For another example, if the number of SRS resource sets is two, the number of SRS resources configured in the first SRS resource set is two, and the number of SRS resources configured in the second SRS resource set is two. b) The number of SRS resources configured in different SRS resource sets is determined by the higher layer parameter srs-ResourceIdList in SRS-Config. c) The maximum number of SRS resources configured in an SRS resource set depends on the UE capability report. i. Optionally, the UE reports the maximum number of SRS resources supported in each SRS resource set. ii. Optionally, the UE reports the total number of SRS resources jointly supported in all SRS resource sets. i) Furthermore, if the number of SRS resources configured in each SRS resource set is the same, the number of SRS resources in each SRS resource set is equal to the total number of supported SRS resources divided by the number of configured SRS resource sets. a. For one example, the UE reports that the total number of SRS resources is 4 and the number of configured SRS resource sets is 2, in which case the maximum number of SRS resources configured in each SRS resource set is 2. d) Except when the upper layer parameter ul-FullPowerTransmission is set to "fullpowerMode2", the maximum number of SRS resources configured in an SRS resource set is 2. Otherwise, according to the UE capabilities, a maximum of 2 or 4 SRS resources can be configured in an SRS resource set. e) If a PUSCH repetition is scheduled by DCI format 0_2, its corresponding SRS resource set, together with other configurations in the SRS resource set, is SRS,0_2 SRS resources, which are used for PUSCH repetitions scheduled by DCI format 0_1 and configured with the higher layer parameter usage of value “codeBook”. i. Furthermore, N configured in different SRS resource sets SRS,0_2 The values of can be the same or different. i) The SRS resource set is configured by the upper layer parameter rs-ResourceSetToAddModListDCI-0-2 or indicated by the SRS resource set indicator field in the DCI. ii) The index of the SRS resource set associated with the PUSCH repetition scheduled by DCI format 0_2 is the same as the index of the SRS resource set associated with the PUSCH repetition scheduled by DCI format 0_1. f) Furthermore, the maximum transmission layer of these PUSCH repetitions should be less than or equal to the minimum of the maximum number of configured SRS resources in all SRS resource sets. b. Parameter-2, the associated NZP CSI-RS resource. a) The associated NZP CSI-RS of each SRS resource set can be the same or different. b) The associated NZP CSI-RS is configured by the higher layer parameter associatedCSI-RS in SRS-ResourceSet.

[0062] (Example 4)

[0063] These example embodiments may be used in one aspect to address problem (iv), discussed above, by incorporating, for example, SRS resource set related configuration for NCB-based simultaneous PUSCH transmissions in MTRP operation.

[0064] If at least one of the following conditions is met: 1) The UE is scheduled to transmit two or more PUSCH transmissions simultaneously, and the time domains of these PUSCH transmissions are fully or partially overlapping. a. The PUSCH transmission may be at least one of an inter-slot based PUSCH transmission or an intra-slot based PUSCH transmission. b. The content of each PUSCH transmission is different. 2) Two or more PUSCH transmissions are associated with one or more SRS resource sets, which are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 with the higher layer parameter usage in SRS-ResourceSet set to "nonCodebook". 3) For non-codebook-based transmission schemes, the PUSCH can be scheduled by DCI format 0_1, DCI format 0_2, or RRC signaling. 4) For those PUSCH transmissions that are transmitted simultaneously, each PUSCH transmission is associated with one SRS resource set.

[0065] The UE may obtain and apply the configuration of one or more SRS resource sets associated with these PUSCH transmissions. 1) Furthermore, the SRS resource set configuration is determined by RRC signaling. 2) Furthermore, the SRS resource set configuration includes at least one of the following parameters: a. Parameter-1, the number of SRS resources in the SRS resource set. a) The number of SRS resources configured in different SRS resource sets can be the same or different. i. For an example, if the number of SRS resource sets is two, the number of SRS resources configured in the first SRS resource set is one, and the number of SRS resources configured in the second SRS resource set is two. ii. For another example, if the number of SRS resource sets is two, the number of SRS resources configured in the first SRS resource set is two, and the number of SRS resources configured in the second SRS resource set is two. b) The number of SRS resources configured in different SRS resource sets is determined by the higher layer parameter srs-ResourceIdList in SRS-Config. c) The maximum number of SRS resources configured in an SRS resource set depends on the UE capability report. i. Optionally, the UE reports the maximum number of SRS resources supported in each SRS resource set. ii. Optionally, the UE reports the total number of SRS resources jointly supported in all SRS resource sets. i) Furthermore, if the number of SRS resources configured in each SRS resource set is the same, the number of SRS resources in each SRS resource set is equal to the total number of supported SRS resources divided by the number of configured SRS resource sets. a. For one example, the UE reports that the total number of SRS resources is 4 and the number of configured SRS resource sets is 2, in which case the maximum number of SRS resources configured in each SRS resource set is 2. d) Except when the upper layer parameter ul-FullPowerTransmission is set to "fullpowerMode2", the maximum number of SRS resources configured in an SRS resource set is 2. Otherwise, according to the UE capabilities, a maximum of 2 or 4 SRS resources can be configured in an SRS resource set. e) If a PUSCH transmission is scheduled by DCI format 0_2, its corresponding SRS resource set, together with other configurations in the SRS resource set, is SRS,0_2 SRS resources, which are used for PUSCH transmissions scheduled by DCI format 0_1 and configured with the higher layer parameter usage of the value “codeBook”. i. Furthermore, N configured in different SRS resource sets SRS,0_2 The values of can be the same or different. i) The SRS resource set is configured by the upper layer parameter rs-ResourceSetToAddModListDCI-0-2 or indicated by the SRS resource set indicator field in the DCI. ii) The index of the SRS resource set associated with the PUSCH transmission scheduled by DCI format 0_2 is the same as the index of the SRS resource set associated with the PUSCH repetition scheduled by DCI format 0_1. f) Furthermore, the maximum transmission layer of these PUSCH transmissions should be less than or equal to the sum of the SRS resources configured in that SRS resource set. b. Parameter-2, the associated NZP CSI-RS resource. a) The associated NZP CSI-RS of each SRS resource set can be the same or different. b) The associated NZP CSI-RS is configured by the higher layer parameter associatedCSI-RS in SRS-ResourceSet.

[0066] (Example 5)

[0067] These example embodiments may be used in one aspect to address problem (v), discussed above, by incorporating FDRA (Frequency Domain Resource Allocation) indication for, for example, FDM (Frequency Domain Division Multiplexing)-based simultaneous PUSCH transmissions scheduled by a single DCI in MTRP operation.

[0068] If at least one of the following conditions is met: 1) A UE is scheduled to transmit multiple PUSCH transmissions simultaneously, with the time domains of these PUSCH transmissions fully or partially overlapping. a. The PUSCH transmission may be at least one of an inter-slot based PUSCH transmission or an intra-slot based PUSCH transmission. b. The PUSCH transmission corresponds to at least one of a PUSCH repetition, a PUSCH non-repetition, and a PUSCH transmission opportunity. 2) Multiple PUSCH transmissions are transmitted in non-contiguous resource allocation in the frequency domain. 3) Multiple PUSCH transmissions may be indicated with the same or different RVs. 4) Two or more PUSCH transmissions are associated with one or more SRS resource sets, which are configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2, with the higher layer parameter usage in SRS-ResourceSet set to "Codebook" or "nonCodebook". Additionally, if more than one SRS resource set is configured, each PUSCH transmission is associated with one SRS resource set. b. For codebook or non-codebook based transmission schemes, the PUSCH can only be scheduled by DCI format 0_1, DCI format 0_2, or RRC signaling. 5) These PUSCH transmissions are shown in different beams or spatial relationships. 6) These PUSCH transmissions can be scheduled to transmit in frequency range 1 or frequency range 2.

[0069] The UE may obtain and apply frequency-domain resource allocations for these PUSCH transmissions. 1) The frequency domain resource allocation for these PUSCH transmissions is assigned according to at least one of the following principles: a. When these PUSCH transmissions are transmitted by a CP-OFDM waveform and for uplink resource allocation scheme type 0, a) If these PUSCH transmissions are transmitted within frequency range 1, i. The frequency domain resource allocation between different PUSCH transmissions within a component carrier can be non-contiguous or contiguous only if the frequency domain resources lie within a "nearly contiguous allocation." For example, 3GPP TS38.101-1 section 6.2.2 describes one embodiment of a near-contiguous allocation. i) Furthermore, the frequency domain resource allocation for each PUSCH transmission can be non-contiguous or contiguous. ii. Otherwise, the frequency domain resource allocation among different PUSCH transmissions is contiguous. i) Furthermore, the frequency domain resource allocation for each PUSCH transmission is contiguous. b) If these PUSCH transmissions are transmitted in frequency range 2: i. The frequency domain resource allocation among different PUSCH transmissions is contiguous. i) Furthermore, the frequency domain resource allocation for each PUSCH transmission is contiguous. b. when these PUSCH transmissions are transmitted over a CP-OFDM waveform, and for uplink resource allocation scheme type 1 or 2, regardless of whether these PUSCH transmissions are transmitted in frequency range 1 or frequency range 2; a) The frequency domain resource allocation among different PUSCH transmissions is contiguous. i. Furthermore, the frequency domain resource allocation for each PUSCH transmission is contiguous. c. When these PUSCH transmissions are transmitted over a DFT-s-OFDM waveform, uplink resource allocation scheme type 0 is not supported, regardless of whether these PUSCH transmissions are transmitted in frequency range 1 or frequency range 2. d. If these PUSCH transmissions are transmitted over a DFT-s-OFDM waveform and, for uplink resource allocation scheme Type 1 or Type 2, if these PUSCH transmissions are transmitted in Frequency Range 1 or Frequency Range 2; a) The frequency domain resource allocation among different PUSCH transmissions is contiguous. i. Furthermore, the frequency domain resource allocation for each PUSCH transmission is contiguous. 2) The frequency domain resource allocation for each PUSCH transmission is indicated by at least one of the FDRA indication fields in DCI format 0_1 or DCI format 0_2. a. Furthermore, the uplink resource allocation scheme indicated by the FDRA indication field is determined by the higher layer parameter resourceAllocation in the case of DCI format 0_1, and by the higher layer parameter resourceAllocationDCI-0-2 in the case of DCI format 0_2. a) Furthermore, the value of the upper layer parameter resourceAllocation or resourceAllocationDCI-0-2 can be set as 'resourceAllocationType0', 'resourceAllocationType1', or 'dynamicSwitch'. b. Optionally, two or more FDRA indication fields are used to indicate the frequency domain resource allocation for all these PUSCH transmissions. a) Optionally, each of a plurality of indication fields is used to indicate a frequency domain resource allocation for each PUSCH transmission. i. For example, if the number of these PUSCH transmissions is two, two FDRA indication fields are used to indicate the frequency domain resource allocation of these two PUSCH transmissions, respectively. c. Optionally, only one FDRA indication field is used to indicate the frequency domain resource allocation for all these PUSCH transmissions. a) Furthermore, different portions of the indicated frequency domain resource allocation are used for different PUSCH transmissions, respectively, and the number of divided portions corresponds to the number of these PUSCH transmissions. i. Optionally, the indicated frequency domain resource allocation is divided equally into multiple portions for each PUSCH transmission. i) For example, if the number of these PUSCH transmissions is two, then the first half of the indicated frequency-domain resource allocation is used for the first PUSCH transmission, and the remaining half of the indicated frequency-domain resource allocation is used for the second PUSCH transmission. ii. Optionally, even and odd RBs within the allocated frequency domain resources are used for different PUSCH transmissions. i) For example, if the number of these PUSCH transmissions is two, then the even RBs in the allocated frequency domain resources are used for the first PUSCH transmission, and the odd RBs in the allocated frequency domain resources are used for the second PUSCH transmission. iii. Optionally, even RBGs (resource block groups, which refer to groups of consecutive RBs) and odd RBGs within the allocated frequency domain resources are used for different PUSCH transmissions. i) For example, if the number of these PUSCH transmissions is two, then the even RBGs in the allocated frequency domain resources are used for the first PUSCH transmission, and the odd RBGs in the allocated frequency domain resources are used for the second PUSCH transmission. iv. Optionally, the indicated frequency-domain resource allocation is divided by a factor to determine the indicated frequency-domain resource allocation fraction. i) Optionally, the coefficients associated with each PUSCH transmission can be the same or different. ii) Optionally, the coefficients depend on the MCS used for the PUSCH transmission. iii) Optionally, the coefficients depend on the transmission layer number of the PUSCH transmission. a. Optionally, the transmission layer number is determined by higher layer parameters in RRC signaling. b. Optionally, the transmission layer number is determined by an indication in the DCI. iv) Optionally, the coefficient depends on the UE capability report associated with the PUSCH transmission. v) Optionally, the coefficients depend on the antenna port number of the PUSCH transmission. a. Optionally, the antenna port number is determined by a higher layer parameter in RRC signaling. b. Optionally, the antenna port number is determined by an indication in the DCI. vi) Optionally, the coefficients are configured by higher layer parameters in the RRC signaling for each PUSCH transmission. d. Optionally, only one FDRA indication field is used to indicate the frequency-domain resource allocation of one first PUSCH transmission, and then an offset of the frequency-domain resource allocation between the first PUSCH transmission and another PUSCH transmission is determined for the frequency-domain resource allocation of the other PUSCH transmission. a) Optionally, the offset is indicated by a field in the scheduling DCI. b) Optionally, the offset is configured by a higher layer parameter in RRC signaling. c) Optionally, the offset is a gap between the first RB of the first PUSCH transmission and the first RB of the other PUSCH transmission in the frequency domain. d) Optionally, the offset is a gap between the last RB of the first PUSCH transmission and the first RB of the other PUSCH transmission in the frequency domain. 3) The frequency domain resource allocation for each PUSCH transmission is determined solely by higher layer parameters in RRC signaling. a. Furthermore, the upper layer parameter is resourceAllocation in the case of DCI format 0_1 based scheduling, and the upper layer parameter is resourceAllocationDCI-0-2 in the case of DCI format 0_2 based scheduling. a. Furthermore, the value of the upper layer parameter resourceAllocation or resourceAllocationDCI-0-2 can be set as 'resourceAllocationType0', 'resourceAllocationType1', or 'dynamicSwitch'. b. Optionally, multiple higher layer parameters are used for these PUSCH transmissions, one at a time. a) For example, if the number of these PUSCH transmissions is two, two higher layer parameters resourceAllocation or resourceAllocationDCI-0-2 are configured to determine these two PUSCH transmissions. c. Optionally, only one higher layer parameter is configured to indicate the frequency domain resource allocation for all these PUSCH transmissions. a) Furthermore, different portions of the indicated frequency domain resource allocation are used for different PUSCH transmissions, respectively, and the number of divided portions corresponds to the number of these PUSCH transmissions. i. Optionally, the indicated frequency domain resource allocation is divided equally into multiple portions for each PUSCH transmission. i) For example, if the number of these PUSCH transmissions is two, then the first half of the indicated frequency-domain resource allocation is used for the first PUSCH transmission, and the remaining half of the indicated frequency-domain resource allocation is used for the second PUSCH transmission. ii. Optionally, even and odd RBs within the allocated frequency domain resources are used for different PUSCH transmissions. i) For example, if the number of these PUSCH transmissions is two, then the even RBs in the allocated frequency domain resources are used for the first PUSCH transmission, and the odd RBs in the allocated frequency domain resources are used for the second PUSCH transmission. iii. Optionally, even and odd RBGs within the allocated frequency domain resources are used for different PUSCH transmissions. i) For example, if the number of these PUSCH transmissions is two, then the even RBGs in the allocated frequency domain resources are used for the first PUSCH transmission, and the odd RBGs in the allocated frequency domain resources are used for the second PUSCH transmission. iv. Optionally, the indicated frequency-domain resource allocation is divided by a factor to determine the indicated frequency-domain resource allocation fraction. i) Optionally, the coefficients associated with each PUSCH transmission can be the same or different. ii) Optionally, the coefficients depend on the MCS used for the PUSCH transmission. iii) Optionally, the coefficients depend on the transmission layer number of the PUSCH transmission. a. Optionally, the transmission layer number is determined by higher layer parameters in RRC signaling. iv) Optionally, the coefficient depends on the UE capability report associated with the PUSCH transmission. v) Optionally, the coefficients depend on the antenna port number of the PUSCH transmission. a. Optionally, the antenna port number is determined by a higher layer parameter in RRC signaling. vi) Optionally, the coefficients are configured by higher layer parameters in the RRC signaling for each PUSCH transmission. b. Optionally, only one higher layer parameter is configured to indicate a frequency-domain resource allocation of one first PUSCH transmission, and then an offset of the frequency-domain resource allocation between the first PUSCH transmission and another PUSCH transmission is determined for the frequency-domain resource allocation of the other PUSCH transmission. a) Optionally, the offset is configured by a higher layer parameter in RRC signaling. b) Optionally, the offset is a gap between the first RB of the first PUSCH transmission and the first RB of the other PUSCH transmission in the frequency domain. c) Optionally, the offset is a gap between the last RB of the first PUSCH transmission and the first RB of the other PUSCH transmission in the frequency domain.

[0070] In this patent document, several solutions are disclosed for determining transmission parameters for the case of multiple simultaneous PUSCH repetitions / transmissions transmitted from multiple panels towards multiple TRPs. More specifically, they include one or more of the following: ● SRS resource set configuration, e.g.: ■SRS resource port number ■ Number of SRS resources in one SRS resource set ■ Composition of SRS resources within one SRS resource set when PUSCH is scheduled by DCI format 0_2 ■ NZP-CSI-RS associated with SRS resource set for non-codebook-based PUSCH transmission Frequency domain resource allocation for FDM-based simultaneous PUSCH transmission in MTRP operation Uplink complete power mode decision ●Instruction of dynamic switching between STRP and MTRP operation

[0071] 1 is a block diagram of an example implementation of a wireless communication device 1200. Methods described herein may be implemented by the device 1200. In some embodiments, the device 1200 may be a base station or network device of a wireless network. In some embodiments, the device 1200 may be a user device (e.g., a wireless device or user equipment UE). The device 1200 includes one or more processors, e.g., processor electronics 1210, transceiver circuitry 1215, and one or more antennas 1220 for transmitting and receiving wireless signals. The device 1200 may include memory 1205 that may be used to store data and instructions used by the processor electronics 1210. The device 1200 may include additional network interfaces to one or more core networks or additional equipment of a network operator. This additional network interface, although not explicitly shown in the figure, may be wired (e.g., fiber or Ethernet) or wireless.

[0072] 2 depicts an example of a wireless communication system 1300 in which various techniques described herein may be implemented. The system 1300 includes a base station 1302, which may have a communication connection with a core network (1312) and a communication connection to a wireless communication medium 1304 for communicating with one or more user devices 1306. The user devices 1306 may be smartphones, tablets, machine-to-machine communication devices, Internet of Things (IoT) devices, etc.

[0073] Some preferred embodiments may include the following solutions:

[0074] 1. A method of wireless communication (e.g., method 310 as shown in FIG. 3A ), the method including, upon determining that a network device and a wireless device operating in a multiple transmit / receive point wireless configuration satisfy a condition, transmitting 312 one or more uplink control transmissions using codebook-based precoding, the one or more uplink control transmissions being performed in accordance with configuration information received from the network device indicating one or more sounding reference signal (SRS) resource sets associated with the one or more uplink control transmissions.

[0075] 2. The method of Solution 1, wherein the conditions include the wireless device being scheduled to transmit two or more uplink control transmissions, and the two or more uplink control transmissions partially or wholly overlapping in the time domain.

[0076] 3. The method according to any of Solutions 1-2, wherein the conditions include that one or more uplink control transmissions are each associated with one or more SRS resource sets and use codebook-based precoding.

[0077] 4. The method according to any of Solutions 1-2, wherein one or more uplink control transmissions are transmitted simultaneously using the same SRS resource set.

[0078] 5. The method of any of Solutions 1-4, wherein at least one of the one or more uplink control transmissions includes at least one of a Physical Uplink Shared Channel (PUSCH) transmission, a PUSCH transmission opportunity, or a PUSCH repetition.

[0079] 6. The method according to solution 5, wherein the configuration information is received by radio resource control layer signaling including one or more parameters.

[0080] 7. The method of Solution 6, wherein one parameter indicates the number of SRS resources in the SRS resource set.

[0081] 8. The method according to any of Solutions 6-7, wherein the maximum number of SRS resources in the SRS resource set depends on the capabilities reported by the wireless device.

[0082] 9. The method according to any of Solutions 6-8, wherein one parameter indicates the number of antenna ports configured for uplink control transmission.

[0083] 10. The method of solution 9, wherein the same number of antenna ports are configured for each SRS resource in the SRS resource set.

[0084] 11. The method of solution 9, wherein different numbers of antenna ports are configured for SRS resources in an SRS resource set.

[0085] 12. The method according to any of Solutions 6-11, wherein the maximum number of transmission layers for one or more uplink control transmissions is less than or equal to the minimum of the maximum number of antenna ports of the indicated SRS resources in the SRS resource set.

[0086] Embodiments 1 and 2 provide further exemplary features of the solutions listed above.

[0087] 13. A method of wireless communication (e.g., method 320 as shown in FIG. 3B ), the method including, upon determining that a network device and a wireless device operating in a multiple transmit / receive point wireless configuration satisfy a condition, transmitting 322 one or more uplink control transmissions using non-codebook-based precoding, the one or more uplink control transmissions being performed in accordance with configuration information received from the network device indicating one or more sounding reference signal (SRS) resource sets associated with the one or more uplink control transmissions.

[0088] 14. The method of solution 13, wherein the conditions include the wireless device being scheduled to transmit two or more uplink control transmissions, and the two or more uplink control transmissions partially or wholly overlapping in the time domain.

[0089] 15. The method of any of Solutions 13-14, wherein the conditions include one or more uplink control transmissions each associated with one or more SRS resource sets and using non-codebook-based precoding.

[0090] 16. The method according to any of Solutions 13-14, wherein one or more uplink control transmissions are transmitted simultaneously using the same SRS resource set.

[0091] 17. The method of any of Solutions 13-16, wherein at least one of the one or more uplink control transmissions includes at least one of a Physical Uplink Shared Channel (PUSCH) transmission, a PUSCH transmission opportunity, or a PUSCH repetition.

[0092] 18. The method according to solution 17, wherein the configuration information is received by radio resource control layer signaling including one or more parameters.

[0093] 19. The method of solution 18, wherein one parameter indicates the number of SRS resources in the SRS resource set.

[0094] 20. The method according to any of Solutions 18-19, wherein the maximum number of SRS resources in the SRS resource set depends on the capabilities reported by the wireless device.

[0095] 21. The method of any of Solutions 18-20, wherein one parameter indicates one or more non-zero power (NZP) channel state information reference signal (CSI-RS) resources associated with one or more SRS resource sets, respectively.

[0096] 22. The method according to any of Solutions 18-21, wherein the maximum number of transmission layers for one or more uplink control transmissions is less than or equal to the minimum of the maximum number of antenna ports of the indicated SRS resources in the SRS resource set.

[0097] Embodiments 3 and 4 provide further exemplary features of the solutions listed above.

[0098] 23. A method of wireless communication (e.g., method 330 as shown in FIG. 3C ), the method including, upon determining that a network device and a wireless device operating in a multiple transmit / receive point wireless configuration satisfy a condition, transmitting 332 one or more uplink control transmissions, the one or more uplink control transmissions being performed in accordance with a frequency domain resource allocation provided by the network device.

[0099] 24. The method of solution 23, wherein the conditions include the wireless device being scheduled to transmit two or more uplink control transmissions, and the two or more uplink control transmissions partially or wholly overlapping in the time domain.

[0100] 25. The method of any of Solutions 23-24, wherein the condition includes that one or more uplink control transmissions are transmitted on non-contiguous resources in the frequency domain.

[0101] 26. The method according to any of Solutions 23-25, wherein the condition includes that one or more uplink control transmissions are indicated using the same or different redundancy versions.

[0102] 27. The method according to any of Solutions 23-25, wherein the condition includes that one or more uplink control transmissions are indicated using different redundancy versions.

[0103] 28. The method of any of Solutions 23-27, wherein the condition includes that one or more uplink control transmissions are associated with one or more SRS resource sets, each indicated as a codebook or non-codebook based transmission.

[0104] 29. The method of any of Solutions 23-28, wherein the condition includes that one or more uplink control transmissions are shown in different beams or in different spatial relationships.

[0105] 30. The method of any of Solutions 23-29, wherein the conditions include one or more uplink control transmissions being scheduled for transmission in Frequency Range 1 or Frequency Range 2.

[0106] 31. The method of any of Solutions 23-30, wherein the one or more uplink control transmissions include at least one of one or more Physical Uplink Shared Channel (PUSCH) transmission opportunities, one or more PUSCH repetitions, one or more PUSCH non-repetitions, one or more inter-slot based PUSCH transmission opportunities, or one or more intra-slot based PUSCH transmission opportunities.

[0107] 32. The method according to any of Solutions 23-31, wherein conducting one or more uplink control transmissions in accordance with a frequency domain resource allocation provided by the network device includes allocating frequency domain resources to the one or more uplink control transmissions in accordance with a rule.

[0108] 33. The rule is that if one or more uplink control transmissions use a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform and uplink resource allocation scheme type 0 is configured for the wireless device, one or more of the following are used:

[0109] If frequency range 1 is used, using contiguous or non-contiguous frequency domain resources within a component carrier for one or more uplink control transmissions if the frequency domain resources are allocated with a nearly contiguous allocation, otherwise using only contiguous frequency domain resources, or

[0110] When Frequency Range 2 is used, using contiguous frequency domain resources for each and every one or more uplink channel transmissions 33. The method of solution 32, defining

[0111] 34. The method of solution 32, wherein the rule specifies that, when one or more uplink control transmissions use a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform and uplink resource allocation scheme type 1 or 2 is configured for the wireless device, contiguous frequency domain resources are used for each and all of the one or more uplink channel transmissions, for both frequency range 1 and frequency range 2.

[0112] 35. The method of solution 32, wherein the rule specifies that, when one or more uplink control transmissions use a discrete Fourier transform orthogonal frequency division multiplexing (DFT-s-OFDM) waveform and uplink resource allocation scheme type 1 or 2 is configured for the wireless device, contiguous frequency domain resources are used for each and all of the one or more uplink channel transmissions, for both frequency range 1 and frequency range 2.

[0113] 36. The method of solution 32, wherein the frequency domain allocation of one or more uplink control transmissions is indicated by at least one indication field in a downlink control information (DCI) message having format 0_1 or format 0_2.

[0114] 37. The method according to any of solutions 23-36, wherein the frequency domain allocation is provided in a radio resource control (RRC) message comprising one or more parameters.

[0115] 38. The method according to solution 37, wherein the RRC message indicates the higher layer parameter resourceAllocation in the case of DCI format 0_1 based scheduling, and indicates resourceAllocationDCI-0-2 in the case of DCI format 0_2 based scheduling.

[0116] Embodiment 5 provides further exemplary features of the solutions listed above.

[0117] 39. A method of wireless communication (e.g., method 340 as shown in FIG. 3D ), the method including: transmitting 342, by a network device, to a wireless device, configuration information indicating one or more sounding reference signal (SRS) resource sets associated with one or more uplink control transmissions; and receiving 344, from a wireless device that satisfies a condition and is operating in a multiple transmit / receive point wireless configuration, in accordance with the configuration information using codebook-based precoding.

[0118] The above solutions may further include features as recited in solutions 2-12 listed above.

[0119] 40. A method of wireless communication (e.g., method 350 as shown in FIG. 3E), the method including: transmitting 352, by a network node, configuration information to a wireless device, the configuration information indicating one or more sounding reference signal (SRS) resource sets associated with one or more uplink control transmissions; and receiving 354, from the wireless device, the one or more uplink control transmissions using non-codebook-based precoding according to a condition.

[0120] The above solutions may further include features as enumerated in solutions 14-22 listed above.

[0121] 41. A method of wireless communication (e.g., method 360 as shown in FIG. 3F ), the method including: transmitting 362, by the network device, to a wireless device operating in a multiple transmit / receive point wireless configuration, a schedule for use by the wireless device to perform one or more uplink control transmissions to the network device upon satisfaction of a condition; and receiving 364, by the network device, one or more uplink control transmissions in accordance with the schedule.

[0122] The above solutions may further include features as enumerated in solutions 26-40 listed above.

[0123] 42. A wireless communication device comprising a processor configured to implement a method according to any one of solutions 1-41.

[0124] 43. A computer storage medium having code stored thereon, the code, when executed by a processor, causing the processor to perform a method according to any of solutions 1-41.

[0125] The embodiments, modules, and functional operations described herein, and others disclosed herein, can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed herein and their structural equivalents, or in one or more combinations thereof. Other disclosed embodiments can be implemented as one or more computer program products (i.e., one or more modules of computer program instructions encoded on a computer-readable medium for execution by or to control the operation of a data processing apparatus). The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter producing a machine-readable propagated signal, or a combination of one or more thereof. The term "data processing apparatus" encompasses all apparatuses, devices, and machines for processing data, including, by way of example, a programmable processor, a computer, or multiple processors or computers. In addition to hardware, an apparatus can include code that creates an execution environment for the computer program, such as code comprising processor firmware, a protocol stack, a database management system, an operating system, or one or more combinations thereof. A propagated signal is an artificially generated signal, for example, a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to an appropriate receiver device.

[0126] A computer program (also known as a program, software, software application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program can be stored within a portion of a file that holds other programs or data (e.g., one or more scripts stored in a markup language document), within a single file dedicated to the program, or within multiple collaborative files (e.g., files that store one or more modules, subprograms, or portions of code). A computer program can be deployed to run on one computer or on multiple computers located at a single site or distributed across multiple sites and interconnected by a communications network.

[0127] The processes and logic flows described herein may be implemented by one or more programmable processors executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows may also be implemented by, and apparatus may be implemented as, special purpose logic circuitry, such as an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

[0128] Processors suitable for the execution of a computer program include, by way of example, both general-purpose and specialized microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random-access memory, or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from, transfer data to, or both, one or more mass storage devices, such as magnetic, magneto-optical, or optical disks, for storing data. However, a computer need not have such devices. Computer-readable media suitable for storing computer program instructions and data include, by way of example, all forms of non-volatile memory, media, and memory devices, including, by way of example, semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices, magnetic disks, e.g., internal hard disks or removable disks, magneto-optical disks, and CD-ROM and DVD-ROM disks. The processor and memory can be supplemented by, or incorporated in, special purpose logic circuitry.

[0129] While this document contains many details, these should not be construed as limitations on the scope of the claimed invention or what may be claimed, but rather as descriptions of features specific to particular embodiments. Certain features described herein in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, while features may be described above as performing a function in a combination and may initially be claimed as such, one or more features from the claimed combination can, in some cases, be deleted from the combination, and the claimed combination may be directed to a subcombination or a variation of the subcombination. Similarly, although acts are depicted in the figures in a particular order, this should not be understood as requiring such acts to be performed in the particular order shown, or in a sequential order, or that all of the illustrated acts be performed, to achieve desirable results.

[0130] Only some examples and implementations are disclosed. Variations, modifications, and extensions to the described examples and implementations, as well as other implementations, can be made based on what is disclosed.

Claims

1. 1. A method of wireless communication, said method comprising: transmitting one or more uplink control transmissions using codebook-based precoding when the network device and the wireless device operating in the multiple transmit / receive point wireless configuration determine that a condition is met; 11. The method of claim 10, wherein the one or more uplink control transmissions are performed according to configuration information received from a network device, the configuration information indicating one or more sounding reference signal (SRS) resource sets associated with the one or more uplink control transmissions.

2. 2. The method of claim 1, wherein the conditions include the wireless device being scheduled to transmit two or more uplink control transmissions, the two or more uplink control transmissions partially or wholly overlapping in the time domain.

3. The method of any one of claims 1-2, wherein the condition includes that the one or more uplink control transmissions are respectively associated with the one or more SRS resource sets to use codebook-based precoding.

4. The method according to any one of claims 1-2, wherein the one or more uplink control transmissions are transmitted simultaneously using the same SRS resource set.

5. 5. The method of claim 1, wherein at least one of the one or more uplink control transmissions comprises at least one of a Physical Uplink Shared Channel (PUSCH) transmission, a PUSCH transmission opportunity, or a PUSCH repetition.

6. The method of claim 5 , wherein the configuration information is received by radio resource control layer signaling comprising one or more parameters.

7. The method of claim 6 , wherein one parameter indicates a number of SRS resources in the SRS resource set.

8. The method according to any of claims 6-7, wherein the maximum number of SRS resources in the SRS resource set depends on the capabilities reported by the wireless device.

9. The method according to any of claims 6-8, wherein one parameter indicates the number of antenna ports configured for uplink control transmission.

10. The method of claim 9 , wherein the same number of antenna ports are configured for each SRS resource in the SRS resource set.

11. The method of claim 9 , wherein different numbers of antenna ports are configured for SRS resources in the SRS resource set.

12. A method according to any one of claims 6 to 11, wherein the maximum number of transmission layers for the one or more uplink control transmissions is less than or equal to the minimum of the maximum number of antenna ports of the indicated SRS resources in the SRS resource set.

13. 1. A method of wireless communication, said method comprising: transmitting one or more uplink control transmissions using non-codebook based precoding when the network device and the wireless device operating in the multiple transmit / receive point wireless configuration determine that a condition is met; 11. The method of claim 10, wherein the one or more uplink control transmissions are performed according to configuration information received from a network device, the configuration information indicating one or more sounding reference signal (SRS) resource sets associated with the one or more uplink control transmissions.

14. 14. The method of claim 13, wherein the conditions include the wireless device being scheduled to transmit two or more uplink control transmissions, the two or more uplink control transmissions partially or wholly overlapping in the time domain.

15. The method of any of claims 13-14, wherein the condition includes that the one or more uplink control transmissions are respectively associated with the one or more SRS resource sets to use non-codebook based precoding.

16. The method according to any of claims 13-14, wherein the one or more uplink control transmissions are transmitted simultaneously using the same SRS resource set.

17. 17. The method of claim 13, wherein at least one of the one or more uplink control transmissions comprises at least one of a Physical Uplink Shared Channel (PUSCH) transmission, a PUSCH transmission opportunity, or a PUSCH repetition.

18. 20. The method of claim 17, wherein the configuration information is received by radio resource control layer signaling comprising one or more parameters.

19. 20. The method of claim 18, wherein one parameter indicates a number of SRS resources in the SRS resource set.

20. The method according to any of claims 18-19, wherein the maximum number of SRS resources in the SRS resource set depends on the capabilities reported by the wireless device.

21. 21. The method of claim 18, wherein one parameter indicates one or more non-zero power (NZP) channel state information reference signal (CSI-RS) resources, and the one or more NZP CSI-RS resources are associated with the one or more SRS resource sets, respectively.

22. The method according to any one of claims 18 to 21, wherein the maximum number of transmission layers for the one or more uplink control transmissions is less than or equal to the minimum of the maximum number of antenna ports of the indicated SRS resources in the SRS resource set.

23. 1. A method of wireless communication, said method comprising: transmitting one or more uplink control transmissions when the network device and the wireless device operating in the multiple transmit / receive point wireless configuration determine that a condition is met; The one or more uplink control transmissions are performed in accordance with a frequency domain resource allocation provided by the network device.

24. 24. The method of claim 23, wherein the conditions include the wireless device being scheduled to transmit two or more uplink control transmissions, the two or more uplink control transmissions partially or wholly overlapping in the time domain.

25. The method according to any of claims 23-24, wherein the condition includes that the one or more uplink control transmissions are transmitted on non-contiguous resources in the frequency domain.

26. The method of any of claims 23-25, wherein the condition includes that the one or more uplink control transmissions are indicated using the same or different redundancy versions.

27. The method of any of claims 23-25, wherein the condition comprises that the one or more uplink control transmissions are indicated using different redundancy versions.

28. The method of any of claims 23-27, wherein the condition includes that the one or more uplink control transmissions are associated with one or more SRS resource sets, each indicated as a codebook or non-codebook based transmission.

29. A method according to any of claims 23 to 28, wherein the condition comprises that the one or more uplink control transmissions are shown on different beams or with different spatial relationships.

30. A method according to any of claims 23-29, wherein the conditions include that the one or more uplink control transmissions are scheduled for transmission in frequency range 1 or frequency range 2.

31. 31. The method of claim 23, wherein the one or more uplink control transmissions include at least one of one or more Physical Uplink Shared Channel (PUSCH) transmission opportunities, one or more PUSCH repetitions, one or more PUSCH non-repetitions, one or more inter-slot based PUSCH transmission opportunities, or one or more intra-slot based PUSCH transmission opportunities.

32. 32. The method of claim 23, wherein performing the one or more uplink control transmissions in accordance with the frequency domain resource allocation provided by the network device comprises allocating frequency domain resources to the one or more uplink control transmissions in accordance with a rule.

33. The rule is: If the one or more uplink control transmissions use a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform and uplink resource allocation scheme Type 0 is configured for the wireless device, If frequency range 1 is used, using contiguous or non-contiguous frequency domain resources within a component carrier for the one or more uplink control transmissions if the frequency domain resources are allocated with a nearly contiguous allocation; otherwise, only use contiguous frequency domain resources, or If frequency range 2 is used, using contiguous frequency domain resources for each and every one of the one or more uplink channel transmissions.

33. The method of claim 32, wherein one or more of:

34. 33. The method of claim 32, wherein the rule specifies that, when the one or more uplink control transmissions use a cyclic prefix orthogonal frequency division multiplexing (CP-OFDM) waveform and uplink resource allocation scheme type 1 or 2 is configured for the wireless device, contiguous frequency domain resources are used for each and all of the one or more uplink channel transmissions, for both frequency range 1 and frequency range 2.

35. 33. The method of claim 32, wherein the rule specifies that when the one or more uplink control transmissions use a Discrete Fourier Transform Orthogonal Frequency Division Multiplexing (DFT-s-OFDM) waveform and uplink resource allocation scheme type 1 or 2 is configured for the wireless device, contiguous frequency domain resources are used for each and all of the one or more uplink channel transmissions, for both Frequency Range 1 and Frequency Range 2.

36. 33. The method of claim 32, wherein the frequency domain allocation of the one or more uplink control transmissions is indicated by at least one indication field in a downlink control information (DCI) message having a format 0_1 or a format 0_2.

37. A method according to any of claims 23-36, wherein the frequency domain allocation is provided in a Radio Resource Control (RRC) message comprising one or more parameters.

38. The method of claim 37, wherein the RRC message indicates an upper layer parameter resourceAllocation in case of DCI format 0_1 based scheduling, and indicates resourceAllocationDCI-0-2 in case of DCI format 0_2 based scheduling.

39. 1. A method of wireless communication, said method comprising: transmitting, by the network device, configuration information to the wireless device indicating one or more sounding reference signal (SRS) resource sets associated with one or more uplink control transmissions; receiving one or more uplink control transmissions from a wireless device that satisfies a condition and that is operating in a multiple transmit / receive point wireless configuration in accordance with the configuration information using codebook-based precoding; A method comprising:

40. 1. A method of wireless communication, said method comprising: transmitting, by a network node, configuration information to a wireless device, the configuration information indicating one or more sounding reference signal (SRS) resource sets associated with one or more uplink control transmissions, the one or more SRS resource sets to be used by the wireless device when a certain condition is met while operating in a multiple transmit / receive point radio configuration with the network device; receiving, from the wireless device, the one or more uplink control transmissions using non-codebook based precoding in accordance with the condition; A method comprising:

41. 1. A method of wireless communication, said method comprising: transmitting, by the network device to the wireless device, a schedule for use by the wireless device operating in a multiple transmit / receive point wireless configuration to effect one or more uplink control transmissions to the network device upon satisfaction of a condition; receiving, by the network device, one or more uplink control transmissions according to the schedule; A method comprising:

42. A wireless communication device comprising a processor configured to perform the method of any of claims 1-41.

43. A computer storage medium having code stored thereon, said code, when executed by a processor, causing said processor to perform a method according to any of claims 1-41.

Images