WO2022183347A1

WO2022183347A1 - Pusch repeat transmission method, terminal device and network device

Info

Publication number: WO2022183347A1
Application number: PCT/CN2021/078551
Authority: WO
Inventors: 陈文洪; 方昀
Original assignee: Oppo广东移动通信有限公司
Priority date: 2021-03-01
Filing date: 2021-03-01
Publication date: 2022-09-09
Also published as: CN116326100A

Abstract

Provided in the embodiments of the present invention are a PUSCH repeat transmission method, a terminal device and a network device, which are applied to the technical field of communications. The method in the embodiments of the present invention comprises: receiving DCI which is sent by a network device and is used for scheduling a PUSCH repeat transmission, wherein the DCI comprises at least two SRI domains, and each SRI domain is used for indicating at least one sounding reference signal (SRS) resource; and determining, according to information indicated by the at least two SRI domains, to use the at least two SRI domains for the PUSCH repeat transmission scheduled by the DCI.

Description

A PUSCH repeated transmission method, terminal device and network device

technical field

The present invention relates to the field of communication technologies, and in particular, to a PUSCH repeated transmission method, terminal equipment and network equipment.

Background technique

In order to improve the transmission reliability of the Physical Uplink Shared Channel (PUSCH), New Radio (NR) introduces repeated transmission of PUSCH, and a Downlink Control Information (DCI) can schedule multiple PUSCHs in the It is transmitted on multiple consecutive time slots or multiple orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM) symbols. Currently, the DCI that schedules repeated PUSCH transmission may include two SRI fields, which are respectively used to determine beams and/or precoding matrices for repeated PUSCH transmission sent to different transmission nodes (Transmission Reception Point, TRP). However, if the channel between one of the TRPs and the terminal becomes poor, the repeated transmissions sent to the TRP will be difficult to receive by the corresponding TRP, which will result in waste of resources and power, and poor uplink transmission performance. Therefore, how to implement a single TRP based on Flexible switching between PUSCH repeated transmission based on multiple TRPs and PUSCH repeated transmission based on multiple TRPs to improve uplink transmission performance is an urgent problem to be solved.

SUMMARY OF THE INVENTION

The embodiments of the present invention provide a PUSCH repeated transmission method, terminal equipment and network equipment, which can realize flexible switching between PUSCH repeated transmission based on a single TRP and PUSCH repeated transmission based on multiple TRPs to improve uplink transmission performance.

In a first aspect, a method for repeated PUSCH transmission is provided, including:

receiving the DCI sent by the network device, where the DCI is used to schedule repeated PUSCH transmissions, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one sounding reference signal SRS resource;

According to the information indicated by the at least two SRI fields, it is determined that the at least two SRI fields are used for the repeated transmission of the PUSCH scheduled by the DCI.

In a second aspect, a method for repeated PUSCH transmission is provided, including:

Sending DCI to the terminal device, where the DCI is used to schedule repeated PUSCH transmissions, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

Through the information indicated by the at least two SRI fields, the terminal device is instructed to use the at least two SRI fields for repeated transmission of the PUSCH scheduled by the DCI.

In a third aspect, a terminal device is provided, including:

a receiving module, configured to receive the DCI sent by the network device, the DCI is used to schedule repeated PUSCH transmission, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

A processing module, configured to determine, according to the information indicated by the at least two SRI fields, to use the at least two SRI fields for the repeated transmission of the PUSCH scheduled by the DCI.

In a fourth aspect, a network device is provided, including:

a sending module, configured to send DCI to the terminal device, the DCI is used to schedule repeated PUSCH transmission, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

The processing module is configured to instruct the terminal device to use the at least two SRI fields for repeated transmission of the PUSCH scheduled by the DCI through the information indicated by the at least two SRI fields.

In a fifth aspect, a terminal device is provided, including:

a receiver, configured to receive the DCI sent by the network device, the DCI is used to schedule repeated PUSCH transmission, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

The processor is configured to determine, according to the information indicated by the at least two SRI fields, to use the at least two SRI fields for the repeated transmission of the PUSCH scheduled by the DCI.

In a sixth aspect, a network device is provided, including:

a transmitter, configured to send DCI to the terminal device, where the DCI is used to schedule repeated PUSCH transmissions, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

The processor is configured to instruct the terminal device to use the at least two SRI fields for repeated transmission of the PUSCH scheduled by the DCI through the information indicated by the at least two SRI fields.

In a seventh aspect, a computer-readable storage medium is provided, comprising: computer instructions that, when executed on a computer, cause the computer to execute the method as described above in the first aspect or any one of the optional implementations of the first aspect, Alternatively, perform the method of the second aspect or any optional implementation manner of the second aspect.

In an eighth aspect, a computer program product is provided, including computer instructions, when the computer program product runs on a computer, the computer executes the computer instructions, so that the computer executes the first aspect as above or any one of the optional aspects of the first aspect. The method of the implementation manner, or the method of executing the second aspect or any optional implementation manner of the second aspect.

A ninth aspect provides a chip, where the chip is coupled to a memory in a terminal device, so that the chip calls program instructions stored in the memory when running, so that the terminal device executes the first aspect or any one of the optional options of the first aspect. The method of the implementation manner of the second aspect, or, the network device is made to execute the method of the second aspect or any optional implementation manner of the second aspect.

In this embodiment of the present invention, the terminal device may receive downlink control information DCI sent by the network device for scheduling repeated PUSCH transmission, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource; and according to the at least two SRI fields According to the information indicated by the two SRI fields, it is determined that at least two SRI fields are used for the repeated transmission of the PUSCH scheduled by the DCI, and an uplink transmission manner in which the at least two SRI fields are used for the repeated transmission of the PUSCH is provided.

Further, the terminal device may determine, according to the information indicated by the at least two SRI fields, whether to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI, or to use the first SRI field of the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI. Repeat transmission for all PUSCH scheduled by DCI. In this way, the terminal device can, according to the information indicated by the at least two SRI fields in the DCI, in a timely manner, using the at least two SRI fields respectively for the different PUSCH scheduled by the DCI to repeatedly transmit the repeated transmission, which is different from the method of repeatedly transmitting the at least two SRI fields. The first SRI field in the SRI fields is used for all PUSCH repeated transmissions scheduled by DCI to switch between repeated transmissions. Even if the TRP channel corresponding to a certain SRI field deteriorates during the transmission process, the terminal device can pass the network The indication in the DCI of the device supports switching between single TRP transmission (using a single SRI field) and multiple TRP transmissions (using multiple SRI fields), so that the uplink transmission performance can be improved.

Description of drawings

1 is a schematic diagram of a codebook-based PUSCH transmission provided by an embodiment of the present invention;

2 is a schematic diagram of a non-codebook-based PUSCH transmission provided by an embodiment of the present invention;

3 is a schematic diagram of a time slot-based PUSCH repeated transmission provided by an embodiment of the present invention;

FIG. 4 is a schematic diagram of OFDM symbol-based PUSCH repeated transmission according to an embodiment of the present invention;

5 is a schematic diagram of PUSCH repeated transmission based on multiple TRPs and multiple Panels provided by an embodiment of the present invention;

FIG. 6 is a schematic diagram of PUSCH repeated transmission based on multiple TRPs provided by an embodiment of the present invention;

7 is a system architecture diagram of a communication system provided by an embodiment of the present invention;

FIG. 8 is a schematic diagram of a method for repeated PUSCH transmission provided by an embodiment of the present invention;

9A is a schematic diagram of PUSCH repeated transmission based on multiple SRI domains according to an embodiment of the present invention;

9B is a schematic diagram of PUSCH repeated transmission based on a single SRI domain according to an embodiment of the present invention;

10A is a schematic structural diagram of a terminal device according to an embodiment of the present invention;

FIG. 10B is a schematic structural diagram of a network device according to an embodiment of the present invention;

11 is a schematic structural diagram of a mobile phone according to an embodiment of the present invention;

FIG. 12 is a schematic structural diagram of a base station according to an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be described below with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative efforts shall fall within the protection scope of the present invention.

In the embodiments of the present invention, words such as "exemplary" or "for example" are used to mean serving as an example, illustration or illustration. Any embodiments or designs described as "exemplary" or "such as" in the embodiments of the present invention should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present the related concepts in a specific manner.

The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases. The symbol "/" in this document indicates the relationship in which the associated object is or, for example, A/B indicates A or B.

The related technologies involved in the embodiments of the present invention will be described below:

Upstream codebook transmission and non-codebook transmission

When a terminal device sends uplink data (PUSCH), it needs to perform precoding processing on the uplink data to obtain an uplink precoding gain. The precoding process is generally divided into two parts: analog domain processing and digital domain processing. For the analog signal sent, the analog domain processing generally uses beamforming to map the RF signal to the physical antenna; the digital domain processing is generally performed at the baseband for the digital signal, using a precoding matrix to precode the digital signal to transmit The data of the layer is mapped to the radio port. Due to the limited number of radio frequency channels of terminal equipment, two processing methods are generally used at the same time, that is, precoding for digital signals, and then beamforming for analog signals.

The PUSCH transmission can be divided into codebook-based transmission and non-codebook-based transmission according to the above-mentioned different precoding methods.

In the uplink codebook-based precoding method, the network side (network device) configures a terminal device with a set of SRS resources dedicated to codebook transmission, as shown in FIG. 1 , which is a schematic diagram of a codebook-based PUSCH transmission. The terminal device (UE in FIG. 1 ) will send SRS on multiple Sounding Reference Signal (Sounding Reference Signal, SRS) resources in the SRS resource set, wherein the SRS on each SRS resource uses a different beam, and the network side ( The gNB in Figure 1) selects the best SRS resource for obtaining the uplink channel state information (Channel State Information, CSI). The SRS Resource Indicator, SRI) field is indicated to the terminal device, so that the terminal device uses the beam corresponding to the SRS resource to perform analog beamforming on the data. The network side can also indicate a rank indication (RI), a precoding matrix indicator (PMI), and a modulation and coding strategy (Modulation and Coding Scheme, MCS) through DCI, so that the terminal device can be based on the RI and PMI. The number of transmission layers and the precoding matrix are determined from the codebook, and the precoded data and demodulation reference signal (Demodulation Reference Signal, DMRS) are sent to the terminal device.

For some terminal devices that support the reciprocity of uplink and downlink channels, non-codebook-based precoding methods can also be supported. As shown in FIG. 2, it is a schematic diagram of a non-codebook-based PUSCH transmission. A terminal device (UE in FIG. 2) can use downlink channel information to obtain uplink channel information, so as to perform uplink analog beamforming and/or digital For precoding, at this time, the network side (the network device, the gNB in FIG. 2 ) does not need to indicate the relevant information of the precoding matrix, so that the overhead of DCI can be reduced. Specifically, the network side first sends a CSI Resource Indicator (CSI-RS), so that the terminal device determines beams and precoding matrices of N layers (layers) based on the CSI-RS. The terminal device uses the beams and precoding matrices of the N layers to transmit N single-port SRS resources (ie, N SRS ports (SRS ports)). These N SRS resources are configured as one for non-codebooks The set of transmitted SRS resources. After receiving the SRS resources, the network side measures, selects the best K SRS resources and indicates the corresponding SRI to the terminal equipment through the SRI field in the DCI, and the terminal equipment determines the number of transmission layers and precoding used according to the SRI. Matrix and analog beams. The indicated number of SRS resources is the number of transmission layers, and the precoding matrix and the analog beam used by the corresponding SRS resource are the precoding matrix and beam used by the corresponding layer of the data. At this time, RI and PMI need not be indicated in DCI.

PUSCH repeated transmission

In order to improve the transmission reliability of PUSCH, NR introduces the repeated transmission of PUSCH, that is, the PUSCH carrying the same data is transmitted multiple times through different time-frequency resources, antennas and redundancy versions, etc., so as to obtain diversity gain and reduce the probability of false detection (Block Error Rate, BLER).

Optionally, as shown in FIG. 3 , it is a schematic diagram of a time slot-based PUSCH repeated transmission. As shown in FIG. 3 , the PUSCH repeated transmission can be performed in different time slots (Slots).

Optionally, as shown in FIG. 4 , it is a schematic diagram of OFDM symbol-based PUSCH repeated transmission. As shown in FIG. 4 , PUSCH repeated transmission can be performed in different orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM) symbols. The repeated transmission in FIG. 4 may be performed in the same time slot or across time slots.

Optionally, as shown in FIG. 5 , which is a schematic diagram of PUSCH repeated transmission based on multiple TRPs and multiple Panels, PUSCH transmission may also be performed on multiple antenna panels (Panels). The DCI scheduling PUSCH repeated transmission in Figure 5 may contain two SRI fields. The PUSCH repeated transmission sent to TRP1 uses one SRI field to obtain the beam and/or the precoding matrix, and the PUSCH repeated transmission sent to TRP2 uses another SRI field to obtain the beam and/or precoding matrix. The beams and/or precoding matrices are obtained, so as to determine the respective beams and/or precoding moments according to the channel conditions of different TRPs.

For multiple timeslots or multiple symbols of PUSCH repeated transmission (such as the PUSCH repeated transmission shown in Figure 3 or 4), one DCI can schedule multiple PUSCHs to be transmitted on consecutive multiple timeslots or multiple OFDM symbols, carrying the same data but in different redundant versions. At this time, the receiving ends of different repeated transmissions may be the same TRP or different TRPs. For multi-Panel repetition, PUSCHs carrying the same data are transmitted on different Panels at the same time, and the receiving end can be the same TRP or different TRPs. In PUSCH repeated transmission, different repeated transmissions can use different beams, different precoding matrices, different redundancy versions and different frequency domain resources.

For PUSCH repeated transmission of multiple TRPs (such as the PUSCH repeated transmission shown in Figure 5 above), different beams and/or precoding matrices can be used for PUSCH sent to different TRPs, and these different beams and/or precoding matrices can usually be Indicated by different SRI fields. Currently, the DCI for scheduling repeated PUSCH transmission may include two SRI fields, which are respectively used to determine beams and/or precoding matrices for repeated transmission of PUSCH sent to different TRPs.

Exemplarily, as shown in FIG. 6 , it is a schematic diagram of PUSCH repeated transmission based on multiple TRPs. If the channel between the TRP0 and the terminal device becomes poor, the repeated transmission sent to the TRP0 is difficult to be received by the corresponding TRP, and it will be waste of resources and power. At this time, if it can support switching between a single TRP (such as TRP0) transmission (using a single SRI domain) and multiple TRP transmissions (that is, two TRPs TRP0 and TRP1, using multiple SRI domains of SRI0 and SRI1), it can avoid causing Waste of resources and power.

In practical applications, if RRC signaling is used to configure the number of SRI fields, it is difficult to support dynamic switching, and it is impossible to switch according to the channel in real time; if additional bits in the DCI are used for indication, the DCI overhead will increase and the performance of the control channel will be affected; if Determining the number of SRI fields included in the DCI blind detection to perform handover will significantly increase the blind detection complexity of the terminal device. Therefore, how to implement a single SRI field and a blind detection complexity without increasing the DCI overhead and blind detection complexity? Dynamic switching between multiple SRI domains is a problem that needs to be solved.

Based on the above problems, an embodiment of the present invention provides a method for repeated PUSCH transmission. In this method, a terminal device can receive downlink control information DCI sent by a network device for scheduling repeated PUSCH transmission. The DCI includes at least two SRI fields, each SRI field It is used to indicate at least one SRS resource; and according to the information indicated by the at least two SRI fields, it is determined whether to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI, or to use the first one of the at least two SRI fields The SRI field is used for all PUSCH repeat transmissions scheduled by DCI. In this way, the terminal device can, according to the information indicated by the at least two SRI fields in the DCI, in a timely manner, using the at least two SRI fields respectively for the different PUSCH scheduled by the DCI to repeatedly transmit the repeated transmission, which is different from the method of repeatedly transmitting the at least two SRI fields. The first SRI field in the SRI fields is used for all PUSCH repeated transmissions scheduled by DCI to switch between repeated transmissions. Even if the TRP channel corresponding to a certain SRI field deteriorates during the transmission process, the terminal device can pass the network The indication in the DCI of the device supports switching between single TRP transmission (using a single SRI field) and multiple TRP transmissions (using multiple SRI fields), thereby improving the transmission performance of the uplink.

As shown in FIG. 7 , it is a system architecture diagram of a communication system to which an embodiment of the present invention is applied. The communication system may include a network device, and the network device may be a device that communicates with a terminal device (or referred to as a communication terminal, a terminal). A network device can provide communication coverage for a specific geographic area, and can communicate with terminal devices located within the coverage area. FIG. 7 exemplarily shows one network device and two terminal devices. Optionally, the communication system may include multiple network devices and the coverage of each network device may include other numbers of terminal devices. This application implements The example does not limit this. Optionally, the communication system may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present application.

Optionally, the communication system may include multiple network devices, and the coverage of each network device may include other numbers of terminal devices, which are not limited in this embodiment of the present invention. Optionally, the communication system may further include other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present invention.

The embodiments of the present invention describe various embodiments in conjunction with network equipment and terminal equipment, where the terminal equipment may also be referred to as user equipment (User Equipment, UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

The terminal device can be a station (STAION, ST) in the WLAN, can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a personal digital processing (Personal Digital Assistant, PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, next-generation communication systems such as end devices in NR networks, or future Terminal equipment in the evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In this embodiment of the present invention, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable, or vehicle-mounted; it can also be deployed on water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons, and satellites) superior).

In the embodiment of the present invention, the terminal device may be a mobile phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiver function, a virtual reality (Virtual Reality, VR) terminal device, and an augmented reality (Augmented Reality, AR) terminal Equipment, wireless terminal equipment in industrial control, wireless terminal equipment in self driving, wireless terminal equipment in remote medical, wireless terminal equipment in smart grid , wireless terminal equipment in transportation safety, wireless terminal equipment in smart city or wireless terminal equipment in smart home, etc.

As an example but not a limitation, in this embodiment of the present invention, the terminal device may also be a wearable device. Wearable devices can also be called wearable smart devices, which are the general term for the intelligent design of daily wear and the development of wearable devices using wearable technology, such as glasses, gloves, watches, clothing and shoes. A wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include full-featured, large-scale, complete or partial functions without relying on smart phones, such as smart watches or smart glasses, and only focus on a certain type of application function, which needs to cooperate with other devices such as smart phones. Use, such as all kinds of smart bracelets, smart jewelry, etc. for physical sign monitoring.

Wherein, the network equipment may further include access network equipment and core network equipment. That is, the wireless communication system further includes a plurality of core networks for communicating with the access network equipment. The access network equipment may be a long-term evolution (long-term evolution, LTE) system, a next-generation (mobile communication system) (next radio, NR) system, or an authorized auxiliary access long-term evolution (authorized auxiliary access long-term evolution, LAA- The evolved base station (evolutional node B, may be referred to as eNB or e-NodeB for short) in the LTE) system is a macro base station, a micro base station (also called a "small base station"), a pico base station, an access point (AP), Transmission site (transmission point, TP) or new generation base station (new generation Node B, gNodeB), etc.

In this embodiment of the present invention, the network device may be a device for communicating with a mobile device, and the network device may be an access point (Access Point, AP) in WLAN, or a base station (Base Transceiver Station, BTS) in GSM or CDMA , it can also be a base station (NodeB, NB) in WCDMA, it can also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or access point, or in-vehicle equipment, wearable devices and NR networks The network equipment (gNB) in the PLMN network in the future evolution or the network equipment in the NTN network, etc.

As an example but not a limitation, in this embodiment of the present invention, the network device may have a mobile characteristic, for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a High Elliptical Orbit (HEO) ) satellite etc. Optionally, the network device may also be a base station set in a location such as land or water.

In this embodiment of the present invention, a network device may provide services for a cell, and a terminal device communicates with the network device through transmission resources (for example, frequency domain resources, or spectrum resources) used by the cell, and the cell may be a network device ( For example, the cell corresponding to the base station), the cell can belong to the macro base station, or it can belong to the base station corresponding to the small cell (Small cell). Pico cell), Femto cell (Femto cell), etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.

It should be understood that, in the embodiment of the present invention, a device having a communication function in the network/system may be referred to as a communication device. Taking the communication system shown in FIG. 7 as an example, the communication device may include a network device and a terminal device with a communication function, and the network device and the terminal device may be specific devices in the embodiments of the present invention, which will not be repeated here; It may include other devices in the communication system, for example, other network entities such as a network controller and a mobility management entity, which are not limited in this embodiment of the present invention.

The technical solutions of the embodiments of the present invention can be applied to various communication systems, such as: Global System of Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, wideband Code Division Multiple Access (CDMA) system (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (General Packet Radio Service, GPRS), Long Term Evolution (Long Term Evolution, LTE) system, Advanced Long Term Evolution (Advanced long term evolution, LTE-A) system , New Radio (NR) system, evolution system of NR system, LTE (LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum) unlicensed spectrum, NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (Wireless Fidelity, WiFi), fifth-generation communication (5th-Generation, 5G) system or other communication systems, etc.

Generally speaking, traditional communication systems support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication, but also support, for example, Device to Device (Device to Device, D2D) communication, Machine to Machine (M2M) communication, Machine Type Communication (MTC), Vehicle to Vehicle (V2V) communication, or Vehicle to everything (V2X) communication, etc. , the embodiments of the present invention can also be applied to these communication systems.

The communication system in the embodiment of the present invention can be applied to a carrier aggregation (Carrier Aggregation, CA) scenario, also can be applied to a dual connectivity (Dual Connectivity, DC) scenario, and can also be applied to a standalone (Standalone, SA) network deployment scenario.

In the method for repeated PUSCH transmission provided by the embodiment of the present invention, the terminal device can receive the downlink control information DCI sent by the network device, and the DCI is used to schedule the repeated transmission of the physical uplink shared channel PUSCH. The DCI includes at least two SRI fields, and each SRI field is used for Indicate at least one sounding reference signal SRS resource; and according to the information indicated by the at least two SRI fields, determine that the at least two SRI fields are used for repeated transmission of the PUSCH scheduled by the DCI.

Example 1

As shown in FIG. 8, an embodiment of the present invention provides a method for repeated PUSCH transmission, including:

801. The network device sends the DCI for scheduling repeated PUSCH transmission to the terminal device.

The DCI includes at least two SRI fields, and each SRI field is used to indicate at least one sounding reference signal SRS resource.

Optionally, different SRI fields in the at least two SRI fields in the DCI indicate resources in different SRS resource sets. For example, the DCI includes two SRI fields, namely SRI field 1 and SRI field 2, wherein SRI field 1 may indicate SRS resources in SRS resource set A, and SRI field 2 may indicate SRS resources in SRS resource set B.

The network device may use the information indicated by the at least two SRI fields to instruct the terminal device to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by DCI, or to instruct the terminal device to use the first SRI in the at least two SRI fields. field is used for all PUSCH repeat transmissions scheduled by DCI.

802. The terminal device determines, according to the information indicated by the at least two SRI fields, whether to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI, or to use the first SRI field of the at least two SRI fields for the DCI All scheduled PUSCH transmissions are repeated.

Optionally, the above-mentioned first SRI domain includes one of the following:

(a) the nth SRI field in at least two SRI fields, where n is an integer greater than or equal to 1;

(b) the SRI field with the least number of SRS resources indicated in the at least two SRI fields;

(c) the SRI field with the largest number of SRS resources indicated in the at least two SRI fields;

(d) an SRI field indicating a single SRS resource in at least two SRI fields;

(e) SRI fields indicating multiple SRS resources in at least two SRI fields;

(f) SRI fields indicating m SRS resources in at least two SRI fields, where m is an integer greater than or equal to 1;

(g) An SRI domain selected from at least two SRI domains.

Wherein, the SRI field selected from at least two SRI fields includes: an SRI field randomly selected from at least two SRI fields; or, an SRI field selected from at least two SRI fields according to channel reciprocity and downlink channel information area.

In this embodiment of the present invention, PUSCH repeated transmission is divided into codebook-based transmission and non-codebook-based transmission.

(1) PUSCH repeated transmission is codebook-based transmission. There are two possible situations in the above 802:

(1.1) If at least one SRI field in the above at least two SRI fields indicates a specific value, the terminal device uses the first SRI field for repeated transmission of all PUSCH scheduled by DCI;

If at least one of the at least two SRI fields indicates a specific value, the at least two SRI fields instruct the terminal device to use the first SRI field for all PUSCH repeated transmissions scheduled by the DCI.

There are several optional ways of indicating the eigenvalues:

An implementation manner: one of the at least two SRI fields indicates a specific value, and the at least two SRI fields instruct the terminal device to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI.

Another implementation manner: there are multiple SRI fields in at least two SRI fields that indicate a specific value, but not all of them indicate a specific value, then the at least two SRI fields indicate that the terminal device uses the first SRI field for all the DCI scheduling PUSCH is repeatedly transmitted.

Another implementation manner: at least two SRI fields both indicate specific values, and the at least two SRI fields indicate that the terminal device uses the first SRI field for all PUSCH repeated transmissions scheduled by the DCI.

The specific value is pre-agreed between the terminal device and the network device; or, the specific value is pre-configured by the network device.

Exemplarily, the above specific value may indicate reservation, or the above specific value may be all 0, or the above specific value may be all 1.

Optionally, for the case where the DCI includes two SRI fields, SRI field 1 and SRI field 2, if both SRI field 1 and SRI field 2 indicate specific values, the terminal device can select one SRI from SRI field 1 and SRI field 2. The field is used for all PUSCH repeated transmissions scheduled by DCI, and the other SRI field is discarded. Exemplarily, the terminal device may select the SRI field (ie, the first SRI field) with the first bit in SRI and 1 and SRI field 2 for repeated transmission of all PUSCHs scheduled by the DCI, and the SRI field with the later bit (ie, the first SRI field) the second SRI field) is discarded.

Exemplarily, assuming that the SRI field includes two bits, and both SRI field 1 and SRI field 2 indicate a specific value of 11, the terminal device can select the SRI field 1 with the first bit in SRI1 and SRI field 2 for the DCI scheduling. All PUSCHs are repeatedly transmitted, and the SRI field 2 with the later bits is discarded.

Optionally, for the case where the DCI includes two SRI fields, SRI field 1 and SRI field 2, if the SRI field 2 indicates a specific value, the terminal device can use the SRI field 1 for all PUSCHs scheduled by the DCI for repeated transmission, and the other one. The SRI field 2 is discarded, or, if the SRI field 1 indicates a specific value, the terminal device may use the SRI field 2 for repeated transmission of all PUSCH scheduled by the DCI, and discard the other SRI field 1.

Exemplarily, assuming that the SRI field includes two bits, and the SRI field 2 indicates a specific value of 11, the terminal device may select SRI1 for repeated transmission of all PUSCH scheduled by the DCI, and the SRI field 2 is discarded.

Optionally, for the case that the DCI includes SRI field 1, SRI field 2 and SRI field 3, a total of 3 SRI fields, if SRI field 2 and SRI field 3 both indicate specific values, the terminal device can use SRI field 1 for All PUSCHs scheduled by DCI are repeatedly transmitted, and the other two SRI fields are discarded. Exemplarily, the terminal device may select the SRI field (ie, the first SRI field) with the first bit in SRI and 1, SRI field 2 and SRI field 3 for repeated transmission of all PUSCHs scheduled by the DCI, and the SRI field with the last bit position. The other two SRI fields are discarded.

Exemplarily, assuming that the SRI field includes two bits, and both SRI field 2 and SRI field 3 indicate a specific value of 11, the terminal device can use SRI field 1 for repeated transmission of all PUSCH scheduled by DCI, and the SRI with the later bits Domain 2 and SRI Domain 3 are discarded.

Optional, optional, for the case where the DCI includes SRI and 1, SRI field 2 and SRI field 3, if SRI field 1 indicates a specific value, and SRI field 2 and SRI field 3 indicate other values, then the terminal device can SRI field 1 is used for all PUSCH repeated transmissions scheduled by DCI, and the other SRI fields 2 and 3 are discarded.

Exemplarily, assuming that the SRI field includes two bits, the SRI field 1 indicates a specific value of 11, and the SRI field 2 and SRI field 3 indicate other values, then the terminal device can select SRI1 for all PUSCH repeated transmissions scheduled by the DCI, and the SRI field 2 discard.

Optionally, for the case where the DCI includes SRI and 1, SRI field 2 and SRI field 3, if SRI field 1 and SRI field 2 indicate specific values, and SRI field 3 indicates other values, the terminal device can use SRI field 3 as All PUSCHs scheduled for DCI are repeatedly transmitted, and the other SRI field 2 and SRI field 1 are discarded.

Exemplarily, assuming that the SRI field includes 2 bits, the SRI field 1 and the SRI field 2 indicate a specific value of 00, and the SRI field 3 indicates other values, then the terminal device can use the SRI3 for all PUSCH repeated transmissions scheduled by the DCI, and the SRI field 2 and SRI domain 1 are discarded.

(1.2) If the above at least two SRI fields indicate non-specific values, the terminal device uses the at least two SRI fields for repeated transmission of different PUSCHs scheduled by DCI respectively.

If the at least two SRI fields indicate non-specific values, the at least two SRI fields indicate that the terminal device uses the at least two SRI fields for different PUSCH repeated transmissions scheduled by DCI respectively.

Optionally, for the case where the DCI includes two SRI fields, SRI field 1 and SRI field 2, if both SRI field 1 and SRI field 2 indicate non-specific values, the terminal device can use SRI field 1 and SRI field 2 for DCI. Different PUSCHs are scheduled for repeated transmission.

Exemplarily, assuming that the SRI field includes two bits, the SRI field 1 and the SRI field 2 both indicate other values except the specific value 11, and the terminal device can use the SRI field 1 and the SRI field 2 for different PUSCHs scheduled by DCI Repeat transmission.

Optionally, for the case where the DCI includes SRI field 1, SRI field 2 and SRI field 3, a total of 3 SRI fields, if SRI field 1, SRI field 2 and SRI field 3 all indicate non-specific values, the terminal device can SRI field 1, SRI field 2 and SRI field 3 are used for different PUSCH repeated transmissions scheduled by DCI.

Exemplarily, assuming that the SRI field includes two bits, the SRI field 1 and the SRI field 2 both indicate other values than the specific value 11, and the terminal device can use the SRI field 1, the SRI field 2, and the SRI field 3 for DCI scheduling different PUSCH transmissions are repeated.

(2) PUSCH repeated transmission is non-codebook-based transmission, and there are two possible situations:

(2.1) If there are at least two SRI fields in the at least two SRI fields that indicate different numbers of SRS resources, the terminal device uses the first SRI field for repeated transmission of all PUSCHs scheduled by DCI;

Optionally, for the case where the DCI includes two SRI fields, one SRI field indicates one SRS resource, the other SRI field indicates multiple SRS resources, and the terminal device determines that one of the two SRI fields indicates one SRS resource, When another SRI field indicates multiple SRS resources, the terminal device uses the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI.

If there are at least two SRI fields in the at least two SRI fields indicating different numbers of SRS resources, the terminal device is instructed to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI.

The quantities of SRS resources indicated by all the SRI fields in the above-mentioned at least two SRI fields are different, or the quantities of SRS resources indicated by at least two SRI fields in the above-mentioned at least two SRI fields are different.

Different SRI fields in the at least two SRI fields indicate different numbers of SRS resources may include the following implementations:

The first implementation manner: each of the at least two SRI fields indicates a different number of SRS resources.

For example, the two SRI fields are respectively SRI field 1 and SRI field 2, SRI field 1 indicates 1 SRS resource, and SRI field 2 indicates 4 SRS resources.

The second implementation manner: at least two SRI fields exist in two SRI fields to indicate different numbers of SRS resources. For example, the three SRI fields are SRI field 1, SRI field 2, and SRI field 3. SRI field 1 indicates one SRS resource, SRI field 3 indicates one SRS resource, and SRI field 2 indicates four SRS resources.

The third implementation manner: the existence of more than two SRI fields in at least two SRI fields indicates different numbers of SRS resources. For example, the four SRI fields are SRI field 1, SRI field 2, SRI field 3, and SRI field 4. SRI field 1 indicates 1 SRS resource, SRI field 3 indicates 1 SRS resource, and SRI field 2 indicates 4 SRS resources. Resource, SRI field 4 indicates 2 SRS resources.

Optionally, different SRI fields in the at least two SRI fields in the DCI indicate SRS resources in different SRS resource sets. For example, the DCI includes two SRI fields, namely SRI field 1 and SRI field 2, wherein SRI field 1 may indicate SRS resources in SRS resource set A, and SRI field 2 may indicate SRS resources in SRS resource set B.

Optionally, each SRI field may be used to indicate the index of one single-port SRS resource or the indices of multiple single-port SRS resources, and the number of SRS resource indexes is the number of SRS resources. According to whether the number of SRS resources indicated by different SRI fields is the same, the terminal device determines whether to use the first SRI field for repeated transmission of all PUSCH scheduled by DCI.

For the case where different SRI fields in at least two SRI fields indicate SRS resources in different SRS resource sets, when each SRI field indicates an index of a single-port SRS resource or an index of multiple single-port SRS resources, the different SRI fields indicate is the index of SRS resources in different SRS resource sets. For example, DCI includes SRI field 1 and SRI field 2. SRI field 1 is used to indicate SRS resources in SRS resource set A, and SRI field 2 is used to indicate SRS resources in SRS resource set B. If SRI field 1 indicates a single The index of the port SRS resource is 0, and the SRI field 2 indicates the indexes 1 and 2 of the two single-port SRS resources, then the SRI field 1 indicates the SRS resource with index 0 in the SRS resource set A, and the SRI field 2 indicates the SRS resource. SRS resources with index 1 and SRS resources with index 2 in set B.

Exemplarily, DCI includes SRI field 1 and SRI field 2, SRI field 1 indicates index 0 of a single-port SRS resource, and SRI field 2 indicates indexes 1 and 2 of two single-port SRS resources, then at this time SRI field 1 Indicates one SRS resource, and SRI field 2 indicates 2 SRS resources. The number of SRS resources indicated by the two is different. It can be determined that the first SRI field (it can be the SRI field with the first bit in SRI field 1 and SRI field 2) All PUSCH transmissions for DCI scheduling are repeated.

Exemplarily, the DCI includes SRI field 1, SRI field 2 and SRI3, SRI field 1 indicates index 0 of one single-port SRS resource, SRI field 2 indicates index 1 and 2 of two single-port SRS resources, and SRI3 indicates 1 index The index of the single-port SRS resource is 1; then the SRI field 1 indicates one SRS resource, the SRI field 2 indicates 2 SRS resources, and the SRI3 indicates 1 SRS resource, wherein the number of SRS resources indicated by the SRI field 2 is the same as the SRI field. Both 1 and SRI field 3 are different, and it can be determined that the first SRI field (which may be the SRI field with the first bit in SRI field 1, SRI field 2 and SRI field 3) is used for all PUSCH repeated transmissions scheduled by DCI.

Exemplarily, the DCI includes SRI field 1, SRI field 2 and SRI3, SRI field 1 indicates index 0 of one single-port SRS resource, SRI field 2 indicates index 1 and 2 of two single-port SRS resources, and SRI3 indicates three single-port SRS resources. The indices of single-port SRS resources are 0, 1 and 2; then SRI field 1 indicates one SRS resource, SRI field 2 indicates 2 SRS resources, and SRI3 indicates 3 SRS resources, wherein SRI field 1, SRI field 2 and SRI The number of SRS resources indicated by field 3 is different, and it can be determined that the first SRI field (which can be the SRI field with the first bit in SRI field 1, SRI field 2 and SRI field 3) is used for all PUSCH repeated transmissions scheduled by DCI .

Optionally, the number of SRS resources indicated by the SRI is equal to the number of transmission layers (rank). In this embodiment of the present invention, different SRI field indications may indicate different SRS resource numbers or the same SRS resource number, and correspondingly, different SRI field indications may also indicate the same transmission layer number (rank) or different transmission layer numbers.

Optionally, when determining the number of SRS resources according to the content indicated by the SRS field, it is related to the maximum number of transmission layers _Lmax configured by the high-level signaling. Explanation, wherein, SRI(s), N _SRS =2 indicates that the number of SRS resources included in the SRS resource set is 2, and SRI(s), N _SRS =3 indicates that the number of SRS resources included in the SRS resource set is 3; SRI(s), N _SRS =4 indicates that the number of SRS resources included in the SRS resource set is 4 for description.

As shown in Table 1, for the case where the maximum number of transmission layers L _max =1, the content indicated by the SRI field corresponds to the corresponding SRS resource. In this case, the SRI field indicates at most one SRS resource.

Specifically, as shown in Table 1 below, for SRI(s), N _SRS = 2: if the value indicated by the bit in the SRI field (Bit field mapped to index) is 0 (for example, two bits are 00 ), the corresponding SRI indicates 1 resource whose index is 0 in the SRS resource set; if the Bit field mapped to index is 1 (for example, two bits are 01), the corresponding SRI indicates the SRS resource set in the 1 resource with index 1;

For SRI(s), N _SRS =3, if Bit field mapped to index is 2 (for example, two bits are 10), then the corresponding SRI indicates 1 resource whose index is 2 in the SRS resource set; If the Bit field mapped to index is 3 (for example, two bits are 11), the corresponding SRI does not indicate any resource in the SRS resource set. Among them, reserved means reserved.

For SRI(s), N _SRS =4, if Bit field mapped to index is 3 (for example, two bits are 11), the corresponding SRI indicates 1 resource whose index is 3 in the SRS resource set.

Table 1

As shown in Table 2, it is the correspondence between the content indicated by the SRI field and the corresponding SRS resources in the case of the maximum number of transmission layers L _max =2, in this case, the SRI field indicates at most 2 SRS resources.

Specifically, as shown in Table 2 below, for SRI(s), N _SRS = 2: if the Bit field mapped to index is 0, the corresponding SRI indicates a resource whose index is 0 in the SRS resource set; If the field mapped to index is 1, the corresponding SRI indicates a resource whose index is 1 in the SRS resource set; if the Bit field mapped to index is 2, the corresponding SRI indicates two resources in the SRS resource set ( Respectively, the resource with index 0 and the resource with index 1); if the Bit field mapped to index is 3, the corresponding SRI does not indicate any resource in the SRS resource set;

For SRI(s), N _SRS =3, if Bit field mapped to index is 3, the corresponding SRI indicates two resources in the SRS resource set (resources with index 0 and resources with index 1 respectively) ); if Bit field mapped to index is 4, the corresponding SRI indicates two resources in the SRS resource set (resources with index 0 and resource with index 2); if Bit field mapped to index is 5 , the corresponding SRI indicates two resources in the SRS resource set (resources with index 1 and resource with index 2); if Bit field mapped to index is 6 or 7, the corresponding SRI does not indicate any resource in the SRS resource collection;

For SRI(s), N _SRS =4, if Bit field mapped to index is 6, the corresponding SRI indicates two resources in the SRS resource set (resources with index 0 and resources with index 3 respectively) ); if Bit field mapped to index is 7, the corresponding SRI indicates two resources in the SRS resource set (resources with index 1 and resources with index 2); if Bit field mapped to index is 8 , the corresponding SRI indicates two resources in the SRS resource set (respectively, the resource with index 1 and the resource with index 3); if the Bit field mapped to index is 9, the corresponding SRI indicates the SRS resource set The two resources in (respectively, the resource with index 2 and the resource with index 3); if the Bit field mapped to index is 10 to 15, the corresponding SRI does not indicate any resource in the SRS resource set.

Table 2

As shown in Table 3, it is the correspondence between the content indicated by the SRI field and the corresponding SRS resource in the case of the maximum number of transmission layers L _max =3. At this time, the SRI field indicates at most 3 SRS resources. The specific instructions are similar to those in Table 1 and Table 2 above, and are not repeated here.

table 3

As shown in Table 4, it is the correspondence between the content indicated by the SRI field and the corresponding SRS resource in the case of the maximum number of transmission layers L _max =4. At this time, the SRI field indicates at most 4 SRS resources. The specific instructions are similar to those in Table 1 and Table 2 above, and are not repeated here.

(2.2) If the above at least two SRI fields both indicate the same number of SRS resources, the terminal device uses the at least two SRI fields for repeated transmission of different PUSCHs scheduled by DCI respectively.

Optionally, the terminal device uses at least two SRI fields for different PUSCH repeated transmissions scheduled by DCI respectively. It can be understood that the terminal device uses at least two SRI fields respectively for DCI scheduling repeated PUSCH transmissions for different TRPs.

If both of the above at least two SRI fields indicate the same number of SRS resources, the terminal device is instructed to use the at least two SRI fields for different PUSCH repeated transmissions scheduled by DCI respectively.

Optionally, if the number of SRS resources indicated by all the SRI fields in the at least two SRI fields is the same, the terminal device uses the at least two SRI fields respectively for the repeated transmission of different PUSCHs scheduled by the DCI.

Exemplarily, DCI includes SRI field 1 and SRI field 2, SRI field 1 indicates index 0 of a single-port SRS resource, and SRI field 2 indicates index 1 of one single-port SRS resource, then at this time SRI field 1 and SRI Both fields 2 indicate one SRS resource, and the two indicate the same number of SRS resources. It can be determined that all PUSCH repeated transmissions of SRI field 1 and SRI field 2 used for DCI scheduling are respectively used for different PUSCH repeated transmissions of DCI scheduling.

Exemplarily, the DCI includes SRI field 1 and SRI field 2, SRI field 1 indicates indices 0, 1 and 2 of three single-port SRS resources, and SRI domain 2 indicates indices 1, 2 and 3 of three single-port SRS resources , then both SRI domain 1 and SRI domain 2 indicate 3 SRS resources, and the number of SRS resources indicated by the two is the same. It can be determined that all PUSCH repeated transmissions that SRI domain 1 and SRI domain 2 are used for DCI scheduling are respectively used for Different PUSCHs scheduled by DCI are repeatedly transmitted.

Optionally, if the information in the first SRI field is used for repeated transmission of all PUSCHs scheduled by the DCI, the information in the second SRI field is not used for any PUSCH transmission, and the second SRI field is at least two SRI fields except the first SRI field. outside the SRI domain.

Optionally, if the first SRI field is used for repeated transmission of all PUSCH scheduled by DCI, and the DCI contains at least two TPC commands, the first TPC command is used for repeated transmission of all PUSCH scheduled by DCI, and the first TPC command is at least TPC commands in the two TPC domains associated with the first SRI domain;

Optionally, there are two possible situations for the association between the SRI domain and the TPC command:

The first possible situation: the kth SRI field in the DCI is associated with the kth TPC command in the DCI, and k is a positive integer;

Exemplarily, it is assumed that the DCI includes two SRI fields and two TPC commands. According to its bit order, the first SRI field is SRI field 1, the second SRI field is SRI field 2, the first TPC command is TPC command 1, and the second TPC command is TCP command 2, where the SRI field 1 is associated with TPC command 1, and SRI domain 2 is associated with TCP command 2.

Exemplarily, it is assumed that the DCI includes three SRI fields and three TPC commands. According to its bit order, the first SRI field is SRI field 1, the second SRI field is SRI field 2, the third SRI field is SRI field 3, the first TPC command is TPC command 1, and the second TPC command is TPC command 1. The command is TCP command 2, and the third TPC command is TCP command 3, wherein SRI domain 1 is associated with TPC command 1, SRI domain 2 is associated with TCP command 2, and SRI domain 3 is associated with TCP command 3.

The second possible situation: at least two TPC commands are associated with different closed-loop power adjustment states, and the first TPC command is a TPC command associated with the same closed-loop power adjustment state as the information indicated by the first SRI field.

Among them, at least two SRI domains are associated with different closed-loop highway adjustment states.

Exemplarily, it is assumed that the DCI includes two SRI fields (SRI field 1 and SRI field 2), and two TPC commands (TPC command 1 and TPC command 2), wherein the TPC command 1 is associated with a closed-loop power index of 0. Adjustment state, SRI field 1 is also associated with the closed-loop power adjustment state with index 0, TPC command 2 is associated with the closed-loop power adjustment state with index 1, and SRI field 2 is associated with the closed-loop power adjustment state with index 1, then SRI field 1 is the first In the SRI domain, TPC command 1 is the first TPC command.

Exemplarily, it is assumed that the DCI includes 3 SRI fields (SRI field 1, SRI field 2 and SRI field 3), and 3 TPC commands (TPC command 1, TPC command 2 and TPC command 3), wherein the TPC command 1 is associated with the closed-loop power adjustment state with index 0, SRI domain 1 is also associated with the closed-loop power adjustment state with index 0, TPC command 2 is associated with the closed-loop power adjustment state with index 1, and SRI domain 2 is associated with the closed-loop power adjustment state with index 1 , TPC command 3 is associated with a closed-loop power adjustment state with index 0, and SRI domain 3 is associated with a closed-loop power adjustment state with index 1, then when SRI domain 1 is the first SRI domain, TPC command 1 and TPC command 3 are the first TPC command .

In one embodiment, if there is no TPC command associated with the same closed-loop power adjustment state as the information indicated by the first SRI field in the at least two TPC commands, neither of the at least two TPC commands is used for the DCI The scheduled PUSCH is repeatedly transmitted.

In another embodiment, if both the at least two TPC commands are associated with the same closed-loop power adjustment state with the information indicated by the first SRI field, the at least two TPC commands are both used for the PUSCH scheduled by the DCI Repeated transmission, that is, the at least two TPC commands are both used for the transmission power adjustment of the PUSCH.

Optionally, the second TPC commands in at least two TPC domains are not used for power control of any PUSCH transmission,

Optionally, the second TPC commands in at least two TPC domains are used for power accumulation in a second closed-loop power adjustment state, and the second closed-loop power adjustment state is a closed-loop power adjustment state determined according to information indicated by the second SRI domain.

The second TPC command is a TPC command other than the first TPC command among the at least two TPC commands, and the second SRI field is an SRI field other than the first SRI field among the at least two SRI fields.

Optionally, if at least two SRI fields are respectively used for different PUSCH repeated transmissions scheduled by DCI, and the DCI includes at least two TPC commands, the at least two TPC commands are respectively used for different PUSCH repeated transmissions scheduled by DCI.

Optionally, each TPC command in the at least two TPC commands is respectively indicated by different TPC fields in the DCI. For example, for two TPC commands, TPC command 1 and TPC command 2, the DCI includes TCP domain 1 and TCP domain 2, where TCP domain 1 indicates TPC command 1 and TCP domain 2 indicates TPC command 2.

Optionally, at least two TPC commands are indicated by the same TPC field in the DCI. For example, for two TPC commands, TPC command 1 and TPC command 2, the DCI includes TCP field 1, where TCP field 1 indicates TPC command 1 and TPC command 2.

In this embodiment of the present invention, the terminal device may receive downlink control information DCI sent by the network device for scheduling repeated PUSCH transmission, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource; and according to the at least two SRI fields The information indicated by the two SRI fields determines whether at least two SRI fields are used for different PUSCH repeated transmissions scheduled by DCI respectively, or whether the first SRI field of the at least two SRI fields is used for all PUSCH repeated transmissions scheduled by DCI. In this way, the terminal device can, according to the information indicated by the at least two SRI fields in the DCI, in a timely manner, using the at least two SRI fields respectively for the different PUSCH scheduled by the DCI to repeatedly transmit the repeated transmission, which is different from the method of repeatedly transmitting the at least two SRI fields. The first SRI field in the SRI fields is used for all PUSCH repeated transmissions scheduled by DCI to switch between repeated transmissions. Even if the TRP channel corresponding to a certain SRI field deteriorates during the transmission process, the terminal device can pass the network The indication in the device DCI supports switching between single TRP transmission (using a single SRI field) and multiple TRP transmissions (using multiple SRI fields), so that PUSCH repeated transmission can be flexibly implemented.

Embodiment 2

In this embodiment, the scheduled PUSCH is a codebook-based transmission, that is, the transmission mode configured by the high-level signaling is a codebook (CodeBook) as an example for description. Wherein, each SRI field is used to indicate one SRS resource.

The terminal device receives the downlink DCI for scheduling repeated transmission of the PUSCH, and the DCI includes two SRI fields, which are SRI field 1 and SRI field 2 respectively.

The terminal device determines, according to the contents indicated by the two SRI fields, whether to use the information in the SRI field 1 and the SRI field 2 for different PUSCH repeated transmissions, or use the information in the first SRI field for all PUSCH repeated transmissions.

Optionally, the first SRI domain is the first SRI domain among the two SRI domains included in the DCI.

In one embodiment, when at least one SRI field indicates a specific value in the two SRI fields, the terminal device uses the information of the first SRI field in SRI field 1 and SRI field 2 for all PUSCH repeated transmissions; When the two SRI fields indicate other values, the terminal device uses the information of SRI field 1 and SRI field 2 for repeated transmission of different PUSCHs respectively.

In an implementation manner, the specific value is a value pre-agreed by the terminal device and the network device. For example, when the SRI field 2 field indicates reservation, or when the SRI field 2 indicates all 0s or all 1s, the terminal device uses the information of the SRI field 1 for all PUSCH repeated transmissions, and the information of the SRI field 2 is not used for any transmission ( discarded or ignored). In other cases, the terminal device uses the information of SRI field 1 and SRI field 2 for repeated transmission of different PUSCHs, that is, the information of both SRI fields is used.

In another embodiment, the specific value is a value preconfigured by the network device. When the value indicated by the two SRI fields is the configuration value, the terminal device only uses one of the SRI fields, and the other SRI field is discarded.

In the above embodiment, dynamic switching between a single SRI domain (single-TRP PUSCH repeated transmission) and multiple SRI domains (multi-TRP PUSCH repeated transmission) can be achieved without additional DCI overhead, so as to achieve better uplink transmission. performance.

In one embodiment, the DCI contains two TPC fields: TPC Field 1 and TPC Field 2, each TPC field indicating a TPC command.

If the terminal equipment uses the information of SRI field 1 and SRI field 2 for different PUSCH repeated transmissions, the terminal equipment uses the two TPC fields for different PUSCH repeated transmissions, that is, the partial PUSCH repeated transmissions scheduled by DCI use the TPC field The TPC command in 1 is used to determine the closed-loop power adjustment state and transmission power, and other PUSCH repeated transmissions use the TPC command in TPC field 2 to determine the closed-loop power adjustment state and transmission power.

If the terminal device uses the information of the first SRI field for all PUSCH repeated transmissions, the terminal device uses the first TPC field associated with the first SRI field in the TPC field 1 and TPC field 2 fields for all PUSCH repeated transmissions. That is, all PUSCH repeated transmissions scheduled by DCI use the TPC command in the first TPC domain to determine the closed-loop power adjustment state and transmit power.

In an embodiment, the association relationship between the SRI domain and the TPC domain is as follows: the first SRI domain in the DCI is associated with the first TPC domain, and the second SRI domain in the DCI is associated with the second TPC domain.

In another embodiment, the first TPC domain is a TPC domain that is associated with the same closed-loop power adjustment state as the information indicated by the first SRI domain.

The two TPC domains are associated with different closed-loop power adjustment states, for example, the first TPC domain is associated with a closed-loop power adjustment state with an index of 0, and the second TPC domain is associated with a closed-loop power adjustment state with an index of 1.

Wherein, different values indicated by the first SRI field may be associated with different closed-loop power adjustment states, and the association may be notified to the terminal device through high-layer signaling. Alternatively, SRI domain 1 and SRI domain 2 themselves may be associated with different closed-loop power adjustment states. For example, SRI domain 1 is associated with a closed-loop power adjustment state with an index of 1, and SRI domain 2 is associated with a closed-loop power adjustment state with an index of 0.

In an embodiment, the second TPC domain in the DCI is not used for any PUSCH transmission, wherein the second TPC domain is a TPC domain other than the first TPC in the above-mentioned TPC domain 1 and TPC domain 2.

It should be noted that there is also a case where one TPC domain includes two TPC commands, and in this case, the SRI domain is associated with the TPC commands.

Exemplarily, as shown in FIG. 9A is a schematic diagram of PUSCH repeated transmission based on multiple SRI domains, the DCI includes SRI0 and SRI1, when the terminal device determines to use the information of SRI0 and SRI1 for different PUSCH repeated transmissions, the DCI The scheduled partial PUSCH repeated transmissions (eg, odd-numbered transmissions) determine the transmit beam/precoding matrix based on the SRS resources indicated by SRI0, and other PUSCH repeated transmissions (eg, even-numbered transmissions) determine the transmit beam/precoding matrix based on the SRS resources indicated by SRI1.

Exemplarily, as shown in FIG. 9B is a schematic diagram of PUSCH repeated transmission based on a single SRI domain, when the terminal device determines to use the information of SRI0 for all PUSCH repeated transmissions, all PUSCH repeated transmissions scheduled by DCI are based on the first SRI. The SRS resource indicated by the field determines the transmit beam/precoding matrix.

Based on the method in this embodiment, a single SRI domain (all repeated transmissions are directed to the same TRP, using the same beam/precoder) and multiple SRI domains (different repeated transmissions are directed to different TRPs, Using the dynamic switching of different beam/precoder), the configuration of repeated transmission is adjusted in real time according to the link quality of different TRPs, so as to achieve higher uplink spectral efficiency and improve the performance of uplink multi-TRP diversity transmission. Moreover, since there is no need to add additional DCI bits, nor to dynamically switch the size of the DCI, additional DCI overhead is avoided, and the blind detection complexity of the terminal device is reduced.

Embodiment 3

In this embodiment, the scheduled PUSCH is non-codebook-based transmission, that is, the transmission mode configured by the high-layer signaling is non-codebook (nonCodeBook) as an example for description. Wherein, each SRI field is used to indicate one or more single-port SRS resources.

In this embodiment, the first SRI domain may be one of the following:

(1) The first SRI field in the two SRI fields included in the DCI, for example, the SRI field with the first bit in the DCI;

(2) An SRI field with a smaller number of SRS resources indicated in the two SRI fields included in the DCI;

(3) An SRI field with a larger number of SRS resources indicated in the two SRI fields included in the DCI;

(4) An SRI field indicating a single SRS resource among the two SRI fields included in the DCI. At this time, the other SRI field in the two SRI fields indicates multiple SRS resources;

(5) An SRI field indicating one or two SRS resources among the two SRI fields included in the DCI. At this time, the other SRI field in the two SRI fields indicates more than two SRS resources;

(6) The SRI field selected by the terminal device from the two SRI fields included in the DCI. Specifically, the terminal device may randomly select an SRI domain from it, or select an SRI domain from it according to channel reciprocity and downlink channel information.

Optionally, when the PUSCH repeated transmission is non-codebook-based transmission, when two SRI fields indicate different numbers of SRS resources (for example, one SRI field indicates one SRS resource index, and the other SRI field indicates two SRS resources) SRS resource index), the terminal device uses the information of the first SRI field for all PUSCH repeated transmissions, and the information of the second SRI field is not used for any transmission (discarded or ignored). When the two SRI fields indicate the same number of SRS resources, the terminal device uses the information of the two SRI fields for repeated transmission of different PUSCHs respectively.

The second SRI domain is an SRI domain other than the first SRI domain in SRI domain 1 and SRI domain 2.

In the above embodiment, dynamic switching between a single SRI domain (single-TRP PUSCH repeated transmission) and multiple SRI domains (multi-TRP PUSCH repeated transmission) can be achieved without additional DCI overhead, so as to achieve better uplink transmission. performance. Further, since the method does not need to modify the definition and indication content of the existing SRI field, the impact on the implementation of the terminal device is reduced.

In one embodiment, the DCI contains two TPC commands: TPC Command 1 and TPC Command 2. Two TPC commands can be contained in the same TPC domain, or contained in different TPC domains.

If the terminal equipment uses the information in SRI field 1 and SRI field 2 for different PUSCH repeated transmissions, the terminal equipment uses the two TPC commands for different PUSCH repeated transmissions respectively, that is, the partial PUSCH repeated transmissions scheduled by DCI use TPC commands 1 to determine the closed-loop power adjustment state and transmit power, and other PUSCH repeated transmissions use TPC command 2 to determine the closed-loop power adjustment state and transmit power.

If the terminal device uses the information of the first SRI field for all PUSCH repeated transmissions, the terminal device uses the first TPC command associated with the first SRI field in TPC command 1 and TPC command 2 for all PUSCH repeated transmissions. That is, all PUSCH repeated transmissions scheduled by DCI use the first TPC command to determine the closed-loop power adjustment state and transmit power.

In an implementation manner, the relationship between the SRI field and the TPC command is as follows: the first SRI field in the DCI is associated with the first TPC command, and the second SRI field in the DCI is associated with the second TPC command.

In another embodiment, the first TPC command is a TPC command associated with the information indicated by the first SRI field in the same closed-loop power adjustment state.

The two TPC commands are associated with different closed-loop power adjustment states, for example, one TPC command is associated with a closed-loop power adjustment state with an index of 0, and the other TPC command is associated with a closed-loop power adjustment state with an index of 1.

The SRI field or the relationship between the information indicated in the SRI field and the closed-loop power adjustment state can be obtained in the following optional ways:

Optionally, the network device can also notify the terminal device in advance of the closed-loop power adjustment state associated with each TPC command through high-layer signaling.

In the second option, different values indicated by the SRI field may be associated with different closed-loop power adjustment states, and the association may also be notified to the terminal device through high-layer signaling.

The third option, SRI domain 1 and SRI domain 2 themselves can be associated with different closed-loop power adjustment states (regardless of the value indicated in the SRI field, all values correspond to the same closed-loop power adjustment state), for example, SRI Domain 1 is associated with a closed-loop power adjustment state with index 1, and SRI domain 2 is associated with a closed-loop power adjustment state with index 0.

The third option is that the terminal equipment can agree with the network equipment that the information indicated by different SRI fields needs to be associated with different closed-loop power adjustment states, but which closed-loop power adjustment state is associated with each SRI field is still configured by the network equipment.

In an embodiment, the second TPC command in the DCI is not used for the PUSCH scheduled by the DCI, but is still used for power accumulation in the second closed-loop power adjustment state, and the second closed-loop power adjustment state is based on the second SRI domain or the second The closed-loop power adjustment state determined by the information indicated in the SRI field.

Optionally, as shown in FIG. 9A , the DCI includes two SRI fields, SRI0 and SRI1. When the terminal device determines to use the information of SRI0 and SRI1 for different PUSCH repeated transmissions, the DCI schedules part of the PUSCH repeated transmissions (such as The first two transmissions) determine the transmit beam/precoding matrix based on the SRS resource indicated by SRI0, and other PUSCH repeated transmissions (eg, the next two transmissions) determine the transmit beam/precoding matrix based on the SRS resource indicated by SRI1.

As shown in FIG. 9B , the DCI includes two SRI fields, SRI0 and SRI1. When the terminal device determines to use the information of SRI0 for all PUSCH repeated transmissions, all PUSCH repeated transmissions scheduled by the DCI are determined to be sent based on the SRS resources indicated by the SRI0 field. Beam/precoding matrix.

Based on the method of the present invention, a single SRI field (all repeated transmissions are directed to the same TRP, using the same beam/precoder) and multiple SRI fields (different repeated transmissions are directed to different TRPs, can be implemented through the information content indicated by the SRI field, Using the dynamic switching of different beam/precoder), the configuration of repeated transmission is adjusted in real time according to the link quality of different TRPs, so as to achieve higher uplink spectral efficiency and improve the performance of uplink multi-TRP diversity transmission. Moreover, since there is no need to add additional DCI bits, nor to dynamically switch the size of the DCI, additional DCI overhead is avoided, and the blind detection complexity of the terminal device is reduced.

As shown in FIG. 10A , an embodiment of the present invention provides a terminal device, including:

A receiving module 1001, configured to receive a DCI sent by a network device for scheduling repeated PUSCH transmissions, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

The processing module 1002 is configured to determine, according to the information indicated by the at least two SRI fields, to use the at least two SRI fields for repeated transmission of the PUSCH scheduled by the DCI.

Optionally, the processing module 1002 is specifically configured to, according to the information indicated by the at least two SRI fields, determine whether to use the at least two SRI fields for repeated transmission of different PUSCH scheduled by the DCI, or whether to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI. The first SRI field is used for all PUSCH repeat transmissions scheduled by DCI.

Optionally, the PUSCH repeated transmission is codebook-based transmission;

The processing module 1002 is specifically configured to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI if at least one SRI field in the at least two SRI fields indicates a specific value;

The processing module 1002 is specifically configured to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI respectively if the at least two SRI fields indicate non-specific values.

Optionally, the specific value is pre-agreed between the terminal device and the network device;

or,

The specific value is pre-configured for the network device.

Optionally, the PUSCH repeated transmission is non-codebook-based transmission;

The processing module 1002 is specifically configured to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI if there are at least two SRIs in the at least two SRI fields indicating different numbers of SRS resources;

The processing module 1002 is specifically configured to use the at least two SRI fields respectively for repeated transmission of different PUSCHs scheduled by the DCI if both of the at least two SRI fields indicate the same number of SRS resources.

Optionally, the processing module 1002 is further configured to, if the information in the first SRI field is used for repeated transmission of all PUSCHs scheduled by the DCI, the information in the second SRI field is not used for any PUSCH transmission, and the second SRI field is at least two SRIs SRI domains other than the first SRI domain in the domain.

Optionally, the processing module 1002 is further configured to use the first TPC command for repeated transmission of all PUSCH scheduled by DCI if the first SRI field is used for repeated transmission of all PUSCH scheduled by DCI, and the DCI contains at least two TPC commands , the first TPC command is a TPC command associated with the first SRI domain in at least two TPC domains;

Optionally, the kth SRI field in the DCI is associated with the kth TPC command in the DCI, and k is a positive integer;

or,

At least two TPC commands are associated with different closed-loop power adjustment states, and the first TPC command is a TPC command associated with the same closed-loop power adjustment state as the information indicated by the first SRI field.

or,

The second TPC commands in the at least two TPC domains are used for power accumulation in a second closed-loop power adjustment state, and the second closed-loop power adjustment state is a closed-loop power adjustment state determined according to information indicated by the second SRI domain;

Optionally, the processing module 1002 is further configured to use the at least two TPC commands for the DCI scheduling if the at least two SRI fields are respectively used for the repeated transmission of different PUSCHs scheduled by the DCI, and the DCI contains at least two TPC commands. different PUSCH transmissions are repeated.

Optionally, each TPC command in the at least two TPC commands is indicated by different TPC fields in the DCI respectively;

or,

At least two TPC commands are indicated by the same TPC field in the DCI.

Optionally, the first SRI domain includes one of the following:

The nth SRI field in at least two SRI fields, where n is an integer greater than or equal to 1;

The SRI field with the least number of SRS resources indicated in at least two SRI fields;

The SRI field with the largest number of SRS resources indicated in at least two SRI fields;

an SRI field indicating a single SRS resource in at least two SRI fields;

SRI fields indicating multiple SRS resources in at least two SRI fields;

SRI fields indicating m SRS resources in at least two SRI fields, where m is an integer greater than or equal to 1;

An SRI domain selected from at least two SRI domains.

Optionally, an SRI domain selected from at least two SRI domains, including:

A randomly selected SRI domain from at least two SRI domains;

or,

An SRI field selected from at least two SRI fields according to channel reciprocity and downlink channel information.

As shown in FIG. 10B , an embodiment of the present invention provides a network device, including:

A sending module 1003, configured to send a DCI for scheduling repeated PUSCH transmission to the terminal device, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

Optionally, through the information indicated by the at least two SRI fields, instructing the terminal device to use the at least two SRI fields respectively for repeated transmission of different PUSCHs scheduled by the DCI, including: through the information indicated by the at least two SRI fields, indicating Whether the terminal device uses at least two SRI fields for different PUSCH repeated transmissions scheduled by DCI respectively, or instructs the terminal device to use the first SRI field of the at least two SRI fields for all PUSCH repeated transmissions scheduled by DCI.

Optionally, the PUSCH repeated transmission is codebook-based transmission;

If at least one SRI field in the at least two SRI fields indicates a specific value, instructing the terminal device to use the first SRI field for repeated transmission of all PUSCH scheduled by the DCI;

or,

If the at least two SRI fields indicate non-specific values, the terminal device is instructed to use the at least two SRI fields for different PUSCH repeated transmissions scheduled by the DCI respectively.

or,

The specific value is pre-configured for the network device.

Optionally, the PUSCH repeated transmission is non-codebook-based transmission;

If there are at least two SRIs in at least two SRI fields indicating different numbers of SRS resources, instructing the terminal device to use the first SRI field for repeated transmission of all PUSCH scheduled by DCI;

If the at least two SRI fields both indicate the same number of SRS resources, the terminal device is instructed to use the at least two SRI fields respectively for the repeated transmission of different PUSCHs scheduled by the DCI.

Optionally, if the first SRI field is used for repeated transmission of all PUSCH scheduled by DCI, and the DCI contains at least two TPC commands, the first TPC command is used for repeated transmission of all PUSCH scheduled by DCI, and the first TPC command is at least two TPC commands. TPC commands associated with the first SRI domain in each TPC domain.

or,

optional,

The second TPC commands in at least two TPC domains are not used for power control of any PUSCH transmission,

or,

Optionally, each TPC command in the at least two TPC commands is respectively indicated by different TPC fields in the DCI;

or,

At least two TPC commands are indicated by the same TPC field in the DCI.

Optionally, the first SRI domain includes one of the following:

an SRI field indicating a single SRS resource in at least two SRI fields;

SRI fields indicating multiple SRS resources in at least two SRI fields;

An SRI domain selected from at least two SRI domains.

Optionally, an SRI domain selected from at least two SRI domains, including:

A randomly selected SRI domain from at least two SRI domains;

or,

An embodiment of the present invention also provides a terminal device, including: a memory storing executable program codes;

a processor coupled to the memory;

The processor invokes the executable program code stored in the memory to execute the PUSCH repeated transmission method executed by the terminal device in the embodiment of the present invention.

An embodiment of the present invention also provides a network device, including: a memory storing executable program codes;

a processor coupled to the memory;

The processor invokes the executable program code stored in the memory to execute the PUSCH repeated transmission method executed by the network device in the embodiment of the present invention.

Exemplarily, the terminal device in this embodiment of the present invention may be a mobile phone. As shown in FIG. 11 , the mobile phone may include: a radio frequency (RF) circuit 1110, a memory 1120, an input unit 1130, a display unit 1140, a sensor 1150, Audio circuit 1160, wireless fidelity (WiFi) module 1170, processor 1180, and power supply 1190 and other components. The radio frequency circuit 1110 includes a receiver 1111 and a transmitter 1112 . Those skilled in the art can understand that the structure of the mobile phone shown in FIG. 11 does not constitute a limitation on the mobile phone, and may include more or less components than the one shown, or combine some components, or arrange different components.

The RF circuit 1110 can be used for receiving and sending signals during information transmission and reception or during a call. In particular, after receiving the downlink information of the base station, it is processed by the processor 1180; in addition, it sends the designed uplink data to the base station. Typically, RF circuitry 1110 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (LNA), a duplexer, and the like. In addition, the RF circuit 1110 may also communicate with networks and other devices via wireless communication. The above-mentioned wireless communication can use any communication standard or protocol, including but not limited to the global system of mobile communication (global system of mobile communication, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access) multiple access, CDMA), wideband code division multiple access (WCDMA), long term evolution (long term evolution, LTE), email, short message service (short messaging service, SMS) and so on.

The memory 1120 can be used to store software programs and modules, and the processor 1180 executes various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 1120 . The memory 1120 may mainly include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program (such as a sound playback function, an image playback function, etc.) required for at least one function, and the like; Data created by the use of the mobile phone (such as audio data, phone book, etc.), etc. Additionally, memory 1120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.

The input unit 1130 may be used to receive inputted numerical or character information, and generate key signal input related to user setting and function control of the mobile phone. Specifically, the input unit 1130 may include a touch panel 1131 and other input devices 1132 . The touch panel 1131, also referred to as a touch screen, can collect the user's touch operations on or near it (such as the user's finger, stylus, etc., any suitable object or accessory on or near the touch panel 1131). operation), and drive the corresponding connection device according to the preset program. Optionally, the touch panel 1131 may include two parts, a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the touch controller. To the processor 1180, and can receive the commands sent by the processor 1180 and execute them. In addition, the touch panel 1131 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 1131 , the input unit 1130 may further include other input devices 1132 . Specifically, other input devices 1132 may include, but are not limited to, one or more of physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, joysticks, and the like.

The display unit 1140 may be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 1140 may include a display panel 1141. Optionally, the display panel 1141 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like. Further, the touch panel 1131 may cover the display panel 1141. When the touch panel 1131 detects a touch operation on or near it, it transmits it to the processor 1180 to determine the type of the touch event, and then the processor 1180 determines the type of the touch event according to the touch event. Type provides corresponding visual output on display panel 1141. Although in FIG. 11, the touch panel 1131 and the display panel 1141 are used as two independent components to realize the input and input functions of the mobile phone, in some embodiments, the touch panel 1131 and the display panel 1141 can be integrated to form Realize the input and output functions of the mobile phone.

The cell phone may also include at least one sensor 1150, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1141 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 1141 and/or when the mobile phone is moved to the ear. or backlight. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (usually three axes), and can detect the magnitude and direction of gravity when it is stationary. games, magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors such as gyroscope, barometer, hygrometer, thermometer, infrared sensor, etc. Repeat.

The audio circuit 1160, the speaker 1161, and the microphone 1162 can provide an audio interface between the user and the mobile phone. The audio circuit 1160 can convert the received audio data into an electrical signal, and transmit it to the speaker 1161, and the speaker 1161 converts it into a sound signal for output; on the other hand, the microphone 1162 converts the collected sound signal into an electrical signal, which is converted by the audio circuit 1160 After receiving, it is converted into audio data, and then the audio data is output to the processor 1180 for processing, and then sent to, for example, another mobile phone through the RF circuit 1110, or the audio data is output to the memory 1120 for further processing.

WiFi is a short-distance wireless transmission technology. The mobile phone can help users to send and receive emails, browse web pages, and access streaming media through the WiFi module 1170, which provides users with wireless broadband Internet access. Although FIG. 11 shows the WiFi module 1170, it can be understood that it is not a necessary component of the mobile phone, and can be completely omitted as required within the scope of not changing the essence of the invention.

The processor 1180 is the control center of the mobile phone, using various interfaces and lines to connect various parts of the entire mobile phone, by running or executing the software programs and/or modules stored in the memory 1120, and calling the data stored in the memory 1120. Various functions of the mobile phone and processing data, so as to monitor the mobile phone as a whole. Optionally, the processor 1180 may include one or more processing units; preferably, the processor 1180 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, etc. , the modem processor mainly deals with wireless communication. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 1180.

The mobile phone also includes a power supply 1190 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 1180 through a power management system, so as to manage charging, discharging, and power consumption management functions through the power management system. Although not shown, the mobile phone may also include a camera, a Bluetooth module, and the like, which will not be repeated here.

In this embodiment of the present invention, the RF circuit 1110 is configured to receive a DCI sent by a network device for scheduling repeated PUSCH transmissions, where the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

The processor 1180 is specifically configured to determine, according to the information indicated by the at least two SRI fields, to use the at least two SRI fields respectively for different PUSCH repeated transmissions scheduled by the DCI

Optionally, the processor 1180 is specifically configured to determine, according to the information indicated by the at least two SRI fields, whether to use the at least two SRI fields for repeated transmission of different PUSCH scheduled by the DCI, or whether to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI. The first SRI field is used for all PUSCH repeat transmissions scheduled by DCI.

Optionally, the PUSCH repeated transmission is codebook-based transmission;

The processor 1180 is specifically configured to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI if at least one of the at least two SRI fields indicates a specific value;

The processor 1180 is specifically configured to, if the at least two SRI fields indicate non-specific values, use the at least two SRI fields respectively for repeated transmission of different PUSCHs scheduled by the DCI.

or,

The specific value is pre-configured for the network device.

Optionally, the PUSCH repeated transmission is non-codebook-based transmission;

The processor 1180 is specifically configured to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI if there are at least two SRIs in the at least two SRI fields indicating different numbers of SRS resources;

The processor 1180 is specifically configured to, if at least two SRI fields both indicate the same number of SRS resources, use the at least two SRI fields respectively for different PUSCH repeated transmissions scheduled by the DCI.

Optionally, the processor 1180 is further configured to, if the information in the first SRI field is used for repeated transmission of all PUSCHs scheduled by the DCI, the information in the second SRI field is not used for any PUSCH transmission, and the second SRI field is at least two SRIs SRI domains other than the first SRI domain in the domain.

Optionally, the processor 1180 is further configured to use the first TPC command for repeated transmission of all PUSCHs scheduled by DCI if the first SRI field is used for repeated transmission of all PUSCHs scheduled by DCI, and the DCI contains at least two TPC commands , the first TPC command is a TPC command associated with the first SRI domain in at least two TPC domains;

or,

Wherein, the second TPC command is a TPC command other than the first TPC command among the at least two TPC commands, and the second SRI field is an SRI field other than the first SRI field among the at least two SRI fields.

Optionally, the processor 1180 is further configured to use the at least two TPC commands for the DCI scheduling respectively if the at least two SRI fields are respectively used for the repeated transmission of different PUSCHs scheduled by the DCI, and the DCI contains at least two TPC commands. different PUSCH transmissions are repeated.

or,

At least two TPC commands are indicated by the same TPC field in the DCI.

Optionally, the first SRI domain includes one of the following:

an SRI field indicating a single SRS resource in at least two SRI fields;

SRI fields indicating multiple SRS resources in at least two SRI fields;

An SRI domain selected from at least two SRI domains.

Optionally, an SRI domain selected from at least two SRI domains, including:

A randomly selected SRI domain from at least two SRI domains;

or,

Exemplarily, as shown in FIG. 12 , the network device in this embodiment of the present invention may be a base station, and the base station includes:

A transmitter 1201, configured to send a DCI for scheduling repeated PUSCH transmissions to a terminal device, where the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

Optionally, through the information indicated by the at least two SRI fields, instructing the terminal device to use the at least two SRI fields for the repeated transmission of the PUSCH scheduled by the DCI, including: through the information indicated by the at least two SRI fields, instructing the terminal device to use the information indicated by the at least two SRI fields. Whether the at least two SRI fields are respectively used for different PUSCH repeated transmissions scheduled by DCI, or the terminal device is instructed to use the first SRI field of the at least two SRI fields for all PUSCH repeated transmissions scheduled by DCI.

Optionally, the PUSCH repeated transmission is codebook-based transmission;

or,

The specific value is pre-configured for the network device.

Optionally, the PUSCH repeated transmission is non-codebook-based transmission;

If there are at least two SRI fields in the at least two SRI fields indicating different numbers of SRS resources, instructing the terminal device to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI;

Optionally, if the first SRI field is used for repeated transmission of all PUSCH scheduled by DCI, and the DCI contains at least two TPC commands, the first TPC command is used for repeated transmission of all PUSCH scheduled by DCI, and the first TPC command is at least two TPC commands. TPC commands associated with the first SRI domain in the first SRI domain.

or,

optional,

or,

At least two TPC commands are indicated by the same TPC field in the DCI.

Optionally, the first SRI domain includes one of the following:

an SRI field indicating a single SRS resource in at least two SRI fields;

SRI fields indicating multiple SRS resources in at least two SRI fields;

An SRI domain selected from at least two SRI domains.

Optionally, an SRI domain selected from at least two SRI domains, including:

A randomly selected SRI domain from at least two SRI domains;

or,

Embodiments of the present invention further provide a computer-readable storage medium, including: computer instructions, which, when executed on a computer, cause the computer to execute various processes of the terminal device in the foregoing method embodiments.

Embodiments of the present invention further provide a computer-readable storage medium, including: computer instructions, which, when executed on a computer, cause the computer to execute various processes of the network device in the foregoing method embodiments.

Embodiments of the present invention further provide a computer program product, including computer instructions. When the computer program product runs on a computer, the computer executes the computer instructions, so that the computer executes each process of the terminal device in the above method embodiments.

Embodiments of the present invention further provide a computer program product, including computer instructions. When the computer program product runs on a computer, the computer executes the computer instructions, so that the computer executes each process of the network device in the above method embodiments.

Embodiments of the present invention further provide a chip, where the chip is coupled to a memory in a terminal device, so that the chip invokes program instructions stored in the memory when running, so that the terminal device performs various processes of the terminal device in the above method embodiments.

Embodiments of the present invention further provide a chip, where the chip is coupled to a memory in a network device, so that the chip invokes program instructions stored in the memory when running, so that the network device executes various processes of the network device in the foregoing method embodiments.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the procedures or functions according to the embodiments of the present invention result in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center over a wire (e.g. coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.) to another website site, computer, server, or data center. The computer-readable storage medium can be any available medium that can be stored by a computer or a data storage device such as a server, a data center, etc. that includes one or more available media integrated. Useful media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), among others.

The terms "first", "second", "third", "fourth", etc. (if present) in the description and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It is to be understood that data so used may be interchanged under appropriate circumstances so that the embodiments described herein can be practiced in sequences other than those illustrated or described herein. Furthermore, the terms "comprising" and "having" and any variations thereof, are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those expressly listed Rather, those steps or units may include other steps or units not expressly listed or inherent to these processes, methods, products or devices.

Claims

A PUSCH repeated transmission method, comprising:

receiving downlink control information DCI sent by the network device, where the DCI is used to schedule repeated transmission of the physical uplink shared channel PUSCH, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one sounding reference signal SRS resource;

According to the information indicated by the at least two SRI fields, it is determined that the at least two SRI fields are used for the repeated transmission of the PUSCH scheduled by the DCI.
The method according to claim 1, wherein the determining, according to the information indicated by the at least two SRI fields, to use the at least two SRI fields for the repeated transmission of the PUSCH scheduled by the DCI comprises:

According to the information indicated by the at least two SRI fields, it is determined whether to use the at least two SRI fields for different PUSCH repeated transmissions scheduled by the DCI respectively, or to use the first SRI in the at least two SRI fields field is used for all PUSCH repeat transmissions scheduled by the DCI.
The method according to claim 2, wherein if the PUSCH repeated transmission is codebook-based transmission, it is determined according to the information indicated by the at least two SRI fields to separate the at least two SRI fields. For different PUSCH repeated transmissions scheduled by the DCI, or using the first SRI field of the at least two SRI fields for all PUSCH repeated transmissions scheduled by the DCI, including:

If at least one SRI field of the at least two SRI fields indicates a specific value, the first SRI field is used for repeated transmission of all PUSCHs scheduled by the DCI;

If the at least two SRI fields indicate non-specific values, the at least two SRI fields are respectively used for different PUSCH repeated transmissions scheduled by the DCI.
The method of claim 3, wherein:

The specific value is pre-agreed between the terminal device and the network device;

or,

The specific value is pre-configured by the network device.
The method according to claim 2, wherein, if the PUSCH repeated transmission is non-codebook-based transmission, determining to transmit the at least two SRI fields according to information indicated by the at least two SRI fields Respectively used for the repeated transmission of different PUSCHs scheduled by the DCI, or using the first SRI field of the at least two SRI fields for the repeated transmission of all PUSCHs scheduled by the DCI, including:

If there are at least two SRIs in the at least two SRI fields indicating different numbers of SRS resources, the first SRI field is used for repeated transmission of all PUSCHs scheduled by the DCI;

If the at least two SRI fields both indicate the same number of SRS resources, the at least two SRI fields are respectively used for the repeated transmission of different PUSCHs scheduled by the DCI.
The method according to any one of claims 2 to 5, wherein the method further comprises:

If the information of the first SRI field is used for all PUSCH repeated transmissions scheduled by the DCI, the information of the second SRI field is not used for any PUSCH transmission, and the second SRI field is the division of the at least two SRI fields. SRI domains other than the first SRI domain.
The method according to any one of claims 2 to 6, wherein the method further comprises:

If the first SRI field is used for all PUSCH repeated transmissions scheduled by the DCI, and the DCI includes at least two TPC commands, the first TPC command is used for all PUSCH repeated transmissions scheduled by the DCI, the The first TPC command is a TPC command associated with the first SRI domain in the at least two TPC domains.
The method of claim 7, wherein:

The kth SRI field in the DCI is associated with the kth TPC command in the DCI, and k is a positive integer;

or,

The at least two TPC commands are associated with different closed-loop power adjustment states, and the first TPC command is a TPC command associated with the same closed-loop power adjustment state as the information indicated by the first SRI field.
The method of claim 7, wherein:

the second TPC commands in the at least two TPC domains are not used for power control of any PUSCH transmission,

or,

The second TPC commands in the at least two TPC domains are used for power accumulation in a second closed-loop power adjustment state, where the second closed-loop power adjustment state is a closed-loop power adjustment state determined according to information indicated by the second SRI domain;

Wherein, the second TPC command is a TPC command other than the first TPC command among the at least two TPC commands, and the second SRI field is a TPC command among the at least two SRI fields except the first SRI SRI domains other than domains.
The method according to any one of claims 2 to 6, wherein the method further comprises:

If the at least two SRI fields are respectively used for different PUSCH repeated transmissions scheduled by the DCI, and the DCI includes at least two TPC commands, the at least two TPC commands are respectively used for the DCI-scheduled Different PUSCHs are repeatedly transmitted.
The method according to any one of claims 7 to 10, wherein,

Each TPC command in the at least two TPC commands is indicated by a different TPC field in the DCI;

or,

The at least two TPC commands are indicated by the same TPC field in the DCI.
The method according to any one of claims 2 to 11, wherein the first SRI field comprises one of the following:

the nth SRI field in the at least two SRI fields, where n is an integer greater than or equal to 1;

the SRI field with the least number of SRS resources indicated in the at least two SRI fields;

the SRI field with the largest number of SRS resources indicated in the at least two SRI fields;

an SRI field indicating a single SRS resource in the at least two SRI fields;

an SRI field indicating a plurality of SRS resources in the at least two SRI fields;

an SRI field indicating m SRS resources in the at least two SRI fields, where m is an integer greater than or equal to 1;

An SRI domain selected from the at least two SRI domains.
The method according to claim 12, wherein the SRI domain selected from the at least two SRI domains comprises:

a randomly selected SRI domain from the at least two SRI domains;

or,

An SRI field selected from the at least two SRI fields according to channel reciprocity and downlink channel information.
A PUSCH repeated transmission method, comprising:

Sending DCI to the terminal device, where the DCI is used to schedule repeated PUSCH transmissions, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

According to the information indicated by the at least two SRI fields, the terminal device is instructed to use the at least two SRI fields for repeated transmission of the PUSCH scheduled by the DCI.
The method according to claim 14, wherein the information indicated by the at least two SRI fields instructs the terminal device to use the at least two SRI fields for PUSCH repetition scheduled by the DCI transmission, including:

According to the information indicated by the at least two SRI fields, whether to instruct the terminal device to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI, or to instruct the terminal device to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI, respectively. The first of the two SRI fields is used for all PUSCH repeat transmissions scheduled by the DCI.
The method according to claim 15, wherein, if the PUSCH repeated transmission is codebook-based transmission; the information indicated by the at least two SRI fields instructs the terminal device to transmit the Whether at least two SRI fields are respectively used for different PUSCH repeated transmissions scheduled by the DCI, or whether to instruct the terminal device to use the first SRI field of the at least two SRI fields for all PUSCH repeated transmissions scheduled by the DCI ,include:

If at least one SRI field in the at least two SRI fields indicates a specific value, instructing the terminal device to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI;

If the at least two SRI fields indicate non-specific values, the terminal device is instructed to use the at least two SRI fields for different PUSCH repeated transmissions scheduled by the DCI respectively.
The method of claim 16, wherein:

The specific value is pre-agreed between the terminal device and the network device;

or,

The specific value is pre-configured by the network device.
The method according to claim 15, wherein if the PUSCH repeated transmission is non-codebook-based transmission, the terminal device is instructed to transmit the at least two SRI fields through the information indicated by the at least two SRI fields. whether the two SRI fields are respectively used for different PUSCH repeated transmissions scheduled by the DCI, or to instruct the terminal device to use the first SRI field of the at least two SRI fields for all PUSCH repeated transmissions scheduled by the DCI, include:

If there are at least two SRIs in the at least two SRI fields indicating different numbers of SRS resources, instructing the terminal device to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI;

If the at least two SRI fields both indicate the same number of SRS resources, the terminal device is instructed to use the at least two SRI fields for different PUSCH repeated transmissions scheduled by the DCI respectively.
The method according to any one of claims 15 to 18, wherein,

If the information of the first SRI field is used for all PUSCH repeated transmissions scheduled by the DCI, the information of the second SRI field is not used for any PUSCH transmission, and the second SRI field is the division of the at least two SRI fields. SRI domains other than the first SRI domain.
The method according to any one of claims 15 to 19, wherein,

If the first SRI field is used for repeated transmission of all PUSCHs scheduled by the DCI, and the DCI includes at least two TPC commands, the first TPC command is used for repeated transmission of all PUSCHs scheduled by the DCI, and the first TPC command is used for repeated transmission of all PUSCHs scheduled by the DCI. A TPC command is a TPC command associated with the first SRI domain in the at least two TPC domains.
The method of claim 20, wherein:

The kth SRI field in the DCI is associated with the kth TPC command in the DCI, and k is a positive integer;

or,

The at least two TPC commands are associated with different closed-loop power adjustment states, and the first TPC command is a TPC command associated with the same closed-loop power adjustment state as the information indicated by the first SRI field.
The method of claim 20, wherein:

the second TPC commands in the at least two TPC domains are not used for power control of any PUSCH transmission,

or,

The second TPC commands in the at least two TPC domains are used for power accumulation in a second closed-loop power adjustment state, where the second closed-loop power adjustment state is a closed-loop power adjustment state determined according to information indicated by the second SRI domain;

Wherein, the second TPC command is a TPC command other than the first TPC command among the at least two TPC commands, and the second SRI field is a TPC command among the at least two SRI fields except the first SRI SRI domains other than domains.
The method according to any one of claims 15 to 19, wherein,

If the at least two SRI fields are respectively used for different PUSCH repeated transmissions scheduled by the DCI, and the DCI includes at least two TPC commands, the at least two TPC commands are respectively used for different PUSCH scheduled by the DCI. PUSCH repeated transmission.
The method according to any one of claims 20 to 23, wherein,

Each TPC command in the at least two TPC commands is indicated by a different TPC field in the DCI;

or,

The at least two TPC commands are indicated by the same TPC field in the DCI.
The method according to any one of claims 15 to 24, wherein the first SRI field comprises one of the following:

the nth SRI field in the at least two SRI fields, where n is an integer greater than or equal to 1;

the SRI field with the least number of SRS resources indicated in the at least two SRI fields;

the SRI field with the largest number of SRS resources indicated in the at least two SRI fields;

an SRI field indicating a single SRS resource in the at least two SRI fields;

an SRI field indicating a plurality of SRS resources in the at least two SRI fields;

an SRI field indicating m SRS resources in the at least two SRI fields, where m is an integer greater than or equal to 1;

An SRI domain selected from the at least two SRI domains.
The method according to claim 25, wherein the SRI field selected from the at least two SRI fields comprises:

a randomly selected SRI domain from the at least two SRI domains;

or,

An SRI field selected from the at least two SRI fields according to channel reciprocity and downlink channel information.
A terminal device, characterized in that it includes:

a receiving module, configured to receive a DCI sent by a network device, where the DCI is used to schedule repeated PUSCH transmissions, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

A processing module, configured to determine, according to the information indicated by the at least two SRI fields, to use the at least two SRI fields for the repeated transmission of the PUSCH scheduled by the DCI.
The terminal device according to claim 27, wherein,

The processing module is specifically configured to determine, according to the information indicated by the at least two SRI fields, whether to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI respectively, or to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI. The first SRI field of the SRI fields is used for all PUSCH repeated transmissions scheduled by the DCI.
The terminal device according to claim 28, wherein the PUSCH repeated transmission is codebook-based transmission;

The processing module is specifically configured to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI if at least one of the at least two SRI fields indicates a specific value;

The processing module is specifically configured to use the at least two SRI fields respectively for repeated transmission of different PUSCHs scheduled by the DCI if the at least two SRI fields indicate non-specific values.
The terminal device according to claim 29, wherein,

The specific value is pre-agreed between the terminal device and the network device;

or,

The specific value is pre-configured by the network device.
The terminal device according to claim 28, wherein the PUSCH repeated transmission is non-codebook-based transmission;

The processing module is specifically configured to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI if there are at least two SRIs in the at least two SRI fields indicating different numbers of SRS resources;

The processing module is specifically configured to use the at least two SRI fields respectively for repeated transmission of different PUSCHs scheduled by the DCI if the at least two SRI fields both indicate the same number of SRS resources.
The terminal device according to any one of claims 28 to 31, wherein,

The processing module is further configured to, if the information of the first SRI field is used for repeated transmission of all PUSCHs scheduled by the DCI, the information of the second SRI field is not used for any PUSCH transmission, and the second SRI field is all PUSCH transmissions. SRI domains other than the first SRI domain among the at least two SRI domains.
The terminal device according to any one of claims 28 to 32, wherein,

The processing module is further configured to use the first TPC command for the DCI scheduling if the first SRI field is used for repeated transmission of all PUSCH scheduled by the DCI, and the DCI includes at least two TPC commands All PUSCHs are repeatedly transmitted, and the first TPC command is a TPC command associated with the first SRI domain in the at least two TPC domains.
The terminal device according to claim 33, wherein,

The kth SRI field in the DCI is associated with the kth TPC command in the DCI, and k is a positive integer;

or,

The at least two TPC commands are associated with different closed-loop power adjustment states, and the first TPC command is a TPC command associated with the same closed-loop power adjustment state as the information indicated by the first SRI field.
The terminal device according to claim 33, wherein,

the second TPC commands in the at least two TPC domains are not used for power control of any PUSCH transmission,

or,

The second TPC commands in the at least two TPC domains are used for power accumulation in a second closed-loop power adjustment state, where the second closed-loop power adjustment state is a closed-loop power adjustment state determined according to information indicated by the second SRI domain;

Wherein, the second TPC command is a TPC command other than the first TPC command among the at least two TPC commands, and the second SRI field is a TPC command among the at least two SRI fields except the first SRI SRI domains other than domains.
The terminal device according to any one of claims 28 to 32, wherein,

The processing module is further configured to, if the at least two SRI fields are respectively used for the repeated transmission of different PUSCHs scheduled by the DCI, and the DCI includes at least two TPC commands, send the at least two TPC commands Different PUSCHs scheduled for the DCI are respectively used for repeated transmission.
The terminal device according to any one of claims 33 to 36, wherein,

Each TPC command in the at least two TPC commands is indicated by a different TPC field in the DCI;

or,

The at least two TPC commands are indicated by the same TPC field in the DCI.
The terminal device according to any one of claims 28 to 37, wherein the first SRI field includes one of the following:

the nth SRI field in the at least two SRI fields, where n is an integer greater than or equal to 1;

the SRI field with the least number of SRS resources indicated in the at least two SRI fields;

the SRI field with the largest number of SRS resources indicated in the at least two SRI fields;

an SRI field indicating a single SRS resource in the at least two SRI fields;

an SRI field indicating a plurality of SRS resources in the at least two SRI fields;

an SRI field indicating m SRS resources in the at least two SRI fields, where m is an integer greater than or equal to 1;

An SRI domain selected from the at least two SRI domains.
The terminal device according to claim 38, wherein the SRI field selected from the at least two SRI fields comprises:

a randomly selected SRI domain from the at least two SRI domains;

or,

An SRI field selected from the at least two SRI fields according to channel reciprocity and downlink channel information.
A network device, characterized in that it includes:

a sending module, configured to send DCI to the terminal device, where the DCI is used to schedule repeated transmission of the PUSCH, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

According to the information indicated by the at least two SRI fields, the terminal device is instructed to use the at least two SRI fields for repeated transmission of the PUSCH scheduled by the DCI.
The network device according to claim 40, wherein,

According to the information indicated by the at least two SRI fields, whether to instruct the terminal device to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI, or to instruct the terminal device to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI, respectively. The first of the two SRI fields is used for all PUSCH repeat transmissions scheduled by the DCI.
The network device according to claim 41, wherein the PUSCH repeated transmission is codebook-based transmission;

If at least one SRI field in the at least two SRI fields indicates a specific value, instructing the terminal device to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI;

If the at least two SRI fields indicate non-specific values, the terminal device is instructed to use the at least two SRI fields for different PUSCH repeated transmissions scheduled by the DCI respectively.
The network device of claim 42, wherein:

The specific value is pre-agreed between the terminal device and the network device;

or,

The specific value is pre-configured by the network device.
The network device according to claim 41, wherein the PUSCH repeated transmission is non-codebook-based transmission;

If there are at least two SRIs in the at least two SRI fields indicating different numbers of SRS resources, instructing the terminal device to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI;

If the at least two SRI fields both indicate the same number of SRS resources, the terminal device is instructed to use the at least two SRI fields for different PUSCH repeated transmissions scheduled by the DCI respectively.
The network device according to any one of claims 41 to 44, wherein,

If the information of the first SRI field is used for all PUSCH repeated transmissions scheduled by the DCI, the information of the second SRI field is not used for any PUSCH transmission, and the second SRI field is the division of the at least two SRI fields. SRI domains other than the first SRI domain.
The network device according to any one of claims 41 to 45, wherein,

If the first SRI field is used for repeated transmission of all PUSCHs scheduled by the DCI, and the DCI includes at least two TPC commands, the first TPC command is used for repeated transmission of all PUSCHs scheduled by the DCI, and the first TPC command is used for repeated transmission of all PUSCHs scheduled by the DCI. A TPC command is a TPC command associated with the first SRI domain in the at least two TPC domains.
The network device of claim 46, wherein:

The kth SRI field in the DCI is associated with the kth TPC command in the DCI, and k is a positive integer;

or,

The at least two TPC commands are associated with different closed-loop power adjustment states, and the first TPC command is a TPC command associated with the same closed-loop power adjustment state as the information indicated by the first SRI field.
The network device of claim 46, wherein:

the second TPC commands in the at least two TPC domains are not used for power control of any PUSCH transmission,

or,

The second TPC commands in the at least two TPC domains are used for power accumulation in a second closed-loop power adjustment state, where the second closed-loop power adjustment state is a closed-loop power adjustment state determined according to information indicated by the second SRI domain;

Wherein, the second TPC command is a TPC command other than the first TPC command among the at least two TPC commands, and the second SRI field is a TPC command among the at least two SRI fields except the first SRI SRI domains other than domains.
The network device according to any one of claims 41 to 45, wherein,

If the at least two SRI fields are respectively used for different PUSCH repeated transmissions scheduled by the DCI, and the DCI includes at least two TPC commands, the at least two TPC commands are respectively used for the DCI-scheduled Different PUSCHs are repeatedly transmitted.
The network device according to claims 46 to 49, characterized in that:

Each TPC command in the at least two TPC commands is indicated by a different TPC field in the DCI;

or,

The at least two TPC commands are indicated by the same TPC field in the DCI.
The network device according to any one of claims 41 to 50, wherein the first SRI field includes one of the following:

the nth SRI field in the at least two SRI fields, where n is an integer greater than or equal to 1;

the SRI field with the least number of SRS resources indicated in the at least two SRI fields;

the SRI field with the largest number of SRS resources indicated in the at least two SRI fields;

an SRI field indicating a single SRS resource in the at least two SRI fields;

an SRI field indicating a plurality of SRS resources in the at least two SRI fields;

an SRI field indicating m SRS resources in the at least two SRI fields, where m is an integer greater than or equal to 1;

An SRI domain selected from the at least two SRI domains.
The network device according to claim 51, wherein the SRI domain selected from the at least two SRI domains comprises:

a randomly selected SRI domain from the at least two SRI domains;

or,

An SRI field selected from the at least two SRI fields according to channel reciprocity and downlink channel information.
A terminal device, characterized in that it includes:

a receiver, configured to receive a DCI sent by a network device, where the DCI is used to schedule repeated PUSCH transmissions, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

The processor is configured to determine, according to the information indicated by the at least two SRI fields, to use the at least two SRI fields for the repeated transmission of the PUSCH scheduled by the DCI.
The terminal device according to claim 53, wherein,

The processor is specifically configured to determine, according to the information indicated by the at least two SRI fields, whether to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI respectively, or to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI. The first SRI field in the fields is used for all PUSCH repeat transmissions scheduled by the DCI.
The terminal device according to claim 54, wherein the PUSCH repeated transmission is codebook-based transmission;

The processor is specifically configured to, if at least one of the at least two SRI fields indicates a specific value, use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI;

The processor is specifically configured to use the at least two SRI fields respectively for repeated transmission of different PUSCHs scheduled by the DCI if the at least two SRI fields indicate non-specific values.
The terminal device according to claim 55, wherein,

The specific value is pre-agreed between the terminal device and the network device;

or,

The specific value is pre-configured by the network device.
The terminal device according to claim 54, wherein the PUSCH repeated transmission is non-codebook-based transmission;

The processor is specifically configured to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI if there are at least two SRIs in the at least two SRI fields indicating different numbers of SRS resources;

The processor is specifically configured to use the at least two SRI fields respectively for repeated transmission of different PUSCHs scheduled by the DCI if the at least two SRI fields both indicate the same number of SRS resources.
The terminal device according to any one of claims 54 to 57, wherein,

The processor is further configured to, if the information of the first SRI field is used for repeated transmission of all PUSCHs scheduled by the DCI, the information of the second SRI field is not used for any PUSCH transmission, and the second SRI field is all PUSCH transmissions. SRI domains other than the first SRI domain among the at least two SRI domains.
The terminal device according to any one of claims 54 to 58, wherein,

The processor is further configured to use the first TPC command for the DCI scheduling if the first SRI field is used for repeated transmission of all PUSCH scheduled by the DCI, and the DCI includes at least two TPC commands All PUSCHs are repeatedly transmitted, and the first TPC command is a TPC command associated with the first SRI domain in the at least two TPC domains.
The terminal device according to claim 59, wherein,

The kth SRI field in the DCI is associated with the kth TPC command in the DCI, and k is a positive integer;

or,

The at least two TPC commands are associated with different closed-loop power adjustment states, and the first TPC command is a TPC command associated with the same closed-loop power adjustment state as the information indicated by the first SRI field.
The terminal device according to claim 60, wherein,

the second TPC commands in the at least two TPC domains are not used for power control of any PUSCH transmission,

or,

The second TPC commands in the at least two TPC domains are used for power accumulation in a second closed-loop power adjustment state, where the second closed-loop power adjustment state is a closed-loop power adjustment determined according to information indicated by the second SRI domain state;

Wherein, the second TPC command is a TPC command other than the first TPC command among the at least two TPC commands, and the second SRI field is a TPC command among the at least two SRI fields except the first SRI SRI domains other than domains.
The terminal device according to any one of claims 54 to 58, wherein,

The processor is further configured to, if the at least two SRI fields are respectively used for different PUSCH repeated transmissions scheduled by the DCI, and the DCI includes at least two TPC commands, send the at least two TPC commands Different PUSCHs scheduled for the DCI are respectively used for repeated transmission.
The terminal device according to any one of claims 59 to 62, wherein,

Each TPC command in the at least two TPC commands is indicated by a different TPC field in the DCI;

or,

The at least two TPC commands are indicated by the same TPC field in the DCI.
The terminal device according to any one of claims 54 to 63, wherein the first SRI field includes one of the following:

the nth SRI field in the at least two SRI fields, where n is an integer greater than or equal to 1;

the SRI field with the least number of SRS resources indicated in the at least two SRI fields;

the SRI field with the largest number of SRS resources indicated in the at least two SRI fields;

an SRI field indicating a single SRS resource in the at least two SRI fields;

an SRI field indicating a plurality of SRS resources in the at least two SRI fields;

an SRI field indicating m SRS resources in the at least two SRI fields, where m is an integer greater than or equal to 1;

An SRI domain selected from the at least two SRI domains.
The terminal device according to claim 64, wherein the SRI field selected from the at least two SRI fields comprises:

a randomly selected SRI domain from the at least two SRI domains;

or,

An SRI field selected from the at least two SRI fields according to channel reciprocity and downlink channel information.
A network device, characterized in that it includes:

a transmitter, configured to send DCI to the terminal device, where the DCI is used to schedule repeated transmission of the PUSCH, the DCI includes at least two SRI fields, and each SRI field is used to indicate at least one SRS resource;

According to the information indicated by the at least two SRI fields, the terminal device is instructed to use the at least two SRI fields for repeated transmission of the PUSCH scheduled by the DCI.
The network device according to claim 66, wherein the information indicated by the at least two SRI fields instructs the terminal device to use the at least two SRI fields for the PUSCH scheduled by the DCI Repeat transmissions, including:

According to the information indicated by the at least two SRI fields, whether to instruct the terminal device to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI, or to instruct the terminal device to use the at least two SRI fields for repeated transmission of different PUSCHs scheduled by the DCI, respectively. The first of the two SRI fields is used for all PUSCH repeat transmissions scheduled by the DCI.
The network device according to claim 67, wherein the PUSCH repeated transmission is codebook-based transmission;

If at least one SRI field in the at least two SRI fields indicates a specific value, instructing the terminal device to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI;

or,

If the at least two SRI fields indicate non-specific values, the terminal device is instructed to use the at least two SRI fields for different PUSCH repeated transmissions scheduled by the DCI respectively.
The network device of claim 68, wherein:

The specific value is pre-agreed between the terminal device and the network device;

or,

The specific value is pre-configured by the network device.
The network device according to claim 67, wherein the PUSCH repeated transmission is non-codebook-based transmission;

If there are at least two SRIs in the at least two SRI fields indicating different numbers of SRS resources, instructing the terminal device to use the first SRI field for repeated transmission of all PUSCHs scheduled by the DCI;

If the at least two SRI fields both indicate the same number of SRS resources, the terminal device is instructed to use the at least two SRI fields for different PUSCH repeated transmissions scheduled by the DCI respectively.
The network device according to any one of claims 67 to 70, wherein,

If the information of the first SRI field is used for all PUSCH repeated transmissions scheduled by the DCI, the information of the second SRI field is not used for any PUSCH transmission, and the second SRI field is the division of the at least two SRI fields. SRI domains other than the first SRI domain.
The network device according to any one of claims 66 to 71, wherein,

If the first SRI field is used for repeated transmission of all PUSCHs scheduled by the DCI, and the DCI includes at least two TPC commands, the first TPC command is used for repeated transmission of all PUSCHs scheduled by the DCI, and the first TPC command is used for repeated transmission of all PUSCHs scheduled by the DCI. A TPC command is a TPC command associated with the first SRI domain in the at least two TPC domains.
The network device of claim 72, wherein:

The kth SRI field in the DCI is associated with the kth TPC command in the DCI, and k is a positive integer;

or,

The at least two TPC commands are associated with different closed-loop power adjustment states, and the first TPC command is a TPC command associated with the same closed-loop power adjustment state as the information indicated by the first SRI field.
The network device of claim 72, wherein:

the second TPC commands in the at least two TPC domains are not used for power control of any PUSCH transmission,

or,

The second TPC commands in the at least two TPC domains are used for power accumulation in a second closed-loop power adjustment state, where the second closed-loop power adjustment state is a closed-loop power adjustment state determined according to information indicated by the second SRI domain;

Wherein, the second TPC command is a TPC command other than the first TPC command among the at least two TPC commands, and the second SRI field is a TPC command among the at least two SRI fields except the first SRI SRI domains other than domains.
The network device according to any one of claims 74 to 70, wherein,

If the at least two SRI fields are respectively used for different PUSCH repeated transmissions scheduled by the DCI, and the DCI includes at least two TPC commands, the at least two TPC commands are respectively used for the DCI-scheduled Different PUSCHs are repeatedly transmitted.
The network device according to claims 72 to 75, characterized in that:

Each TPC command in the at least two TPC commands is respectively indicated by different TPC fields in the DCI;

or,

The at least two TPC commands are indicated by the same TPC field in the DCI.
The network device according to any one of claims 67 to 76, wherein the first SRI field includes one of the following:

the nth SRI field in the at least two SRI fields, where n is an integer greater than or equal to 1;

the SRI field with the least number of SRS resources indicated in the at least two SRI fields;

the SRI field with the largest number of SRS resources indicated in the at least two SRI fields;

an SRI field indicating a single SRS resource in the at least two SRI fields;

an SRI field indicating a plurality of SRS resources in the at least two SRI fields;

an SRI field indicating m SRS resources in the at least two SRI fields, where m is an integer greater than or equal to 1;

An SRI domain selected from the at least two SRI domains.
The network device according to claim 77, wherein the SRI domain selected from the at least two SRI domains comprises:

a randomly selected SRI domain from the at least two SRI domains;

or,

An SRI field selected from the at least two SRI fields according to channel reciprocity and downlink channel information.
A computer-readable storage medium comprising: computer instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1 to 13, or to perform the method of claim 14 The method of any one of to 26.