A PUSCH repetition transmission method, a terminal device, and a network device

Abstract

The embodiment of the application provides a PUSCH repeated transmission method, a terminal device and network equipment, which are applied to the technical field of communication, and the embodiment of the application comprises the following steps: receiving DCI for scheduling PUSCH repeated transmission which is sent by network equipment, wherein the DCI comprises at least two SRI domains, each SRI domain is used for indicating at least one sounding reference signal (SRS) resource; and determining that the at least two SRI domains are used for PUSCH repeated transmission which is scheduled by the DCI according to the information indicated by the at least two SRI domains.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a PUSCH repetition transmission method, a terminal device and a network device. BACKGROUND

[0002] In order to improve the transmission reliability of a physical uplink shared channel (PUSCH), New Radio (NR) introduces PUSCH repetition transmission, that is, one downlink control information (DCI) can schedule multiple PUSCHs to be transmitted on multiple consecutive slots or multiple orthogonal frequency division multiplexing (OFDM) symbols. At present, the DCI scheduling the PUSCH repetition transmission can contain two SRI fields, which are respectively used to determine the beams and / or precoding matrices of the PUSCH repetition transmission sent to different transmission reception points (TRPs). However, if the channel between one of the TRPs and the terminal becomes poor, the repetition transmission sent to the TRP is difficult to be received by the corresponding TRP, which will cause waste of resources and power and deterioration of uplink transmission performance. Therefore, how to realize flexible switching between PUSCH repetition transmission based on a single TRP and PUSCH repetition transmission based on multiple TRPs to improve the uplink transmission performance is a problem to be solved. SUMMARY

[0003] The embodiments of the present application provide a PUSCH repetition transmission method, a terminal device and a network device, which can realize flexible switching between PUSCH repetition transmission based on a single TRP and PUSCH repetition transmission based on multiple TRPs to improve the uplink transmission performance.

[0004] In a first aspect, a PUSCH repetition transmission method is provided, comprising:

[0005] receiving a DCI sent by a network device, the DCI being used to schedule PUSCH repetition transmission, and the DCI comprising at least two SRI fields, each SRI field being used to indicate at least one sounding reference signal (SRS) resource;

[0006] determining, according to information indicated by the at least two SRI fields, that the at least two SRI fields are used for PUSCH repetition transmission scheduled by the DCI.

[0007] In a second aspect, a PUSCH repetition transmission method is provided, comprising:

[0008] The DCI is used for scheduling PUSCH repetition transmission, and the DCI includes at least two SRI fields, and each SRI field is used for indicating at least one SRS resource.

[0009] The terminal device is instructed to use the at least two SRI fields for the PUSCH repetition transmission scheduled by the DCI according to information indicated by the at least two SRI fields.

[0010] In a third aspect, a terminal device is provided, including:

[0011] The receiving module is configured to receive DCI sent by a network device, the DCI being used for scheduling PUSCH repetition transmission, and the DCI including at least two SRI fields, and each SRI field being used for indicating at least one SRS resource.

[0012] The processing module is configured to determine, according to information indicated by the at least two SRI fields, that the at least two SRI fields are used for the PUSCH repetition transmission scheduled by the DCI.

[0013] In a fourth aspect, a network device is provided, including:

[0014] The sending module is configured to send DCI to a terminal device, the DCI being used for scheduling PUSCH repetition transmission, and the DCI including at least two SRI fields, and each SRI field being used for indicating at least one SRS resource.

[0015] The processing module is configured to instruct the terminal device to use the at least two SRI fields for the PUSCH repetition transmission scheduled by the DCI according to information indicated by the at least two SRI fields.

[0016] In a fifth aspect, a terminal device is provided, including:

[0017] The receiver is configured to receive DCI sent by a network device, the DCI being used for scheduling PUSCH repetition transmission, and the DCI including at least two SRI fields, and each SRI field being used for indicating at least one SRS resource.

[0018] The processor is configured to determine, according to information indicated by the at least two SRI fields, that the at least two SRI fields are used for the PUSCH repetition transmission scheduled by the DCI.

[0019] In a sixth aspect, a network device is provided, including:

[0020] The transmitter is configured to send DCI to a terminal device, the DCI being used for scheduling PUSCH repetition transmission, and the DCI including at least two SRI fields, and each SRI field being used for indicating at least one SRS resource.

[0021] A processor is configured to instruct a terminal device to use the at least two SRI fields for repeated transmission of PUSCH scheduled by the DCI, based on information indicated by the at least two SRI fields.

[0022] A seventh aspect provides a computer-readable storage medium comprising: computer instructions, which, when executed on a computer, cause the computer to perform a method as described in the first aspect or any optional implementation thereof, or to perform a method as described in the second aspect or any optional implementation thereof.

[0023] Eighthly, a computer program product is provided, comprising computer instructions that, when the computer program product is run on a computer, cause the computer to execute the computer instructions, such that the computer performs a method as described in the first aspect or any optional implementation thereof, or performs a method as described in the second aspect or any optional implementation thereof.

[0024] Ninthly, a chip is provided, which is coupled to a memory in a terminal device, such that the chip, when running, calls program instructions stored in the memory, causing the terminal device to execute a method as described in the first aspect or any optional implementation thereof, or causing a network device to execute a method as described in the second aspect or any optional implementation thereof.

[0025] In this embodiment of the invention, the terminal device can receive downlink control information (DCI) sent by the network device for scheduling repeated PUSCH transmissions. The DCI includes at least two SRI fields, each SRI field indicating at least one SRS resource. Based on the information indicated by the at least two SRI fields, the terminal device determines to use the at least two SRI fields for the repeated PUSCH transmissions scheduled by the DCI, thus providing an uplink transmission method that uses at least two SRI fields for repeated PUSCH transmissions.

[0026] Furthermore, the terminal device can determine, based on the information indicated by at least two SRI fields, whether to use each of the at least two SRI fields separately for different PUSCH repetitions scheduled by the DCI, or to use the first SRI field of the at least two SRI fields for all PUSCH repetitions scheduled by the DCI. In this way, the terminal device can promptly switch between the repetition transmission method of using each of the at least two SRI fields separately for different PUSCH repetitions scheduled by the DCI, and the repetition transmission method of using the first SRI field of the at least two SRI fields for all PUSCH repetitions scheduled by the DCI, based on the information indicated by the at least two SRI fields in the DCI. Even if the TRP channel corresponding to a certain SRI field deteriorates during transmission, the terminal device can still support switching between single TRP transmission (using a single SRI field) and multiple TRP transmission (using multiple SRI fields) based on the indication in the network device's DCI, thereby improving uplink transmission performance. Attached Figure Description

[0027] Figure 1 A schematic diagram of PUSCH transmission based on a codebook is provided for an embodiment of the present invention;

[0028] Figure 2 A schematic diagram of a non-codebook-based PUSCH transmission is provided for an embodiment of the present invention;

[0029] Figure 3 A schematic diagram of a time-slot-based PUSCH repetition transmission provided in an embodiment of the present invention;

[0030] Figure 4 A schematic diagram of PUSCH repetition transmission based on OFDM symbols provided in an embodiment of the present invention;

[0031] Figure 5 A schematic diagram of PUSCH repetitive transmission based on multiple TRPs and multiple panels is provided for an embodiment of the present invention;

[0032] Figure 6 A schematic diagram of PUSCH repetitive transmission based on multiple TRP provided in an embodiment of the present invention;

[0033] Figure 7 A system architecture diagram of a communication system provided in an embodiment of the present invention;

[0034] Figure 8 This is a schematic diagram of a PUSCH retransmission method provided in an embodiment of the present invention;

[0035] Figure 9A A schematic diagram of PUSCH repetitive transmission based on multiple SRI domains is provided for an embodiment of the present invention;

[0036] Figure 9B A schematic diagram of PUSCH repetitive transmission based on a single SRI field is provided for an embodiment of the present invention;

[0037] Figure 10A This is a schematic diagram of the structure of a terminal device provided in an embodiment of the present invention;

[0038] Figure 10B A schematic diagram of the structure of a network device provided in an embodiment of the present invention;

[0039] Figure 11 This is a schematic diagram of the structure of a mobile phone provided in an embodiment of the present invention;

[0040] Figure 12 This is a schematic diagram of a base station structure provided in an embodiment of the present invention. Detailed Implementation

[0041] The technical solutions of the embodiments of the present invention will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0042] In embodiments of the present invention, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in embodiments of the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0043] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. The symbol " / " in this article indicates that the related objects are in an "or" relationship; for example, A / B means A or B.

[0044] The relevant technologies involved in the embodiments of the present invention will be described below:

[0045] Uplink codebook transmission and non-codebook transmission

[0046] When a terminal device transmits uplink data (PUSCH), it needs to perform precoding processing to obtain uplink precoding gain. Precoding processing generally consists of two parts: analog domain processing and digital domain processing. Analog domain processing deals with the transmitted analog signal, typically using beamforming to map the RF signal onto the physical antenna. Digital domain processing deals with the digital signal, generally performed in the baseband, using a precoding matrix to precode the digital signal and map the data from the transport layer onto the RF port. Because the number of RF channels in a terminal device is limited, both processing methods are usually used simultaneously: precoding the digital signal and then beamforming the analog signal.

[0047] PUSCH transmission can be divided into codebook-based transmission and non-codebook-based transmission based on the different precoding methods mentioned above.

[0048] In uplink codebook-based precoding, the network side (network device) configures a dedicated SRS resource set for codebook transmission for the terminal device, such as... Figure 1 The diagram shown illustrates a codebook-based PUSCH transmission method, where the terminal device ( Figure 1 The UE will transmit SRS on multiple Sounding Reference Signal (SRS) resources in the SRS resource set. Each SRS resource uses a different beam. The network side ( Figure 1 The network selects the best SRS resource from the gNB (gNodeB) to obtain uplink channel state information (CSI). The network side then uses downlink control information (DCI) to indicate the resource index to the terminal device through the SRS resource indicator (SRI) field, instructing the terminal device to use the corresponding beam of the SRS resource to perform simulated beamforming on the data. The network side can also indicate the rank indication (RI), precoding matrix indicator (PMI), and modulation and coding scheme (MCS) through the DCI. In this way, the terminal device can determine the transmission layer number and precoding matrix from the codebook based on the RI and PMI, and send the precoded data and demodulation reference signal (DMRS) to the terminal device.

[0049] For some terminal devices that support uplink and downlink channel reciprocity, non-codebook-based precoding methods can also be supported. For example... Figure 2The diagram shown illustrates a non-codebook-based PUSCH transmission method, where the terminal device ( Figure 2 The UE (User Equipment) can use downlink channel information to obtain uplink channel information, thereby performing uplink analog beamforming and / or digital precoding. At this time, the network side (network equipment)... Figure 2 In the case of a gNB, the terminal device (DCI) no longer needs to indicate precoding matrix information, thus reducing DCI overhead. Specifically, the network side first sends a CSI Resource Indicator (CSI-RS), instructing the terminal device to determine the beams and precoding matrices for N layers based on the CSI-RS. The terminal device uses these N layer beams and precoding matrices to transmit N single-port SRS resources (i.e., N SRS ports). These N SRS resources are configured as a set of SRS resources for non-codebook transmission. After receiving the SRS resources, the network side measures them, selects the best K SRS resources, and indicates the corresponding SRIs to the terminal device through the SRI field in the DCI. The terminal device determines the transmission layer, precoding matrix, and analog beams to be used based on the SRIs. The number of indicated SRS resources is the transmission layer number, and the precoding matrix and analog beams used for the corresponding SRS resources are the precoding matrix and beams used for the corresponding data layer. At this time, the DCI does not need to indicate RIs and PMIs.

[0050] PUSCH repeated transmission

[0051] To improve the transmission reliability of PUSCH, NR introduced PUSCH retransmission, which means that PUSCH carrying the same data is transmitted multiple times through different time and frequency resources, antennas and redundant versions, thereby obtaining diversity gain and reducing the probability of false detection (Block Error Rate, BLER).

[0052] Optional, such as Figure 3 The diagram shown illustrates a time-slot-based PUSCH repetitive transmission method. Figure 3 The PUSCH repeat transmission shown can be performed in different time slots.

[0053] Optional, such as Figure 4 The diagram shown illustrates a PUSCH repetition transmission based on OFDM symbols. Figure 4 The PUSCH repetition shown can be performed in different Orthogonal Frequency Division Multiplexing (OFDM) symbols. Figure 4 Repeated transmissions can occur within the same time slot or across time slots.

[0054] Optional, such as Figure 5 The diagram shows a PUSCH repetition transmission based on multiple TRPs and multiple panels. PUSCH transmission can also be performed on multiple antenna panels. Figure 5 The DCI for scheduling PUSCH retransmissions can contain two SRI fields. The PUSCH retransmission sent to TRP1 uses one SRI field to obtain the beam and / or precoding matrix, while the PUSCH retransmission sent to TRP2 uses another SRI field to obtain the beam and / or precoding matrix, thereby determining the beam and / or precoding matrix according to the channel conditions of different TRPs.

[0055] For PUSCH repetitive transmissions with multiple time slots or multiple symbols (as described above) Figure 3 or Figure 4 As shown in the PUSCH repetition transmission diagram, a DCI can schedule multiple PUSCHs to be transmitted on multiple consecutive time slots or multiple OFDM symbols, carrying the same data but using different redundancy versions. In this case, the receivers of different repetition transmissions can be the same TRP or different TRPs. For multi-panel repetition, PUSCHs carrying the same data are transmitted simultaneously on different panels, and the receivers can be the same TRP or different TRPs. In PUSCH repetition transmission, different repetition transmissions can use different beams, different precoding matrices, different redundancy versions, and different frequency domain resources.

[0056] For multiple TRP PUSCH retransmissions (as described above) Figure 5 As shown in the PUSCH retransmission diagram, PUSCHs sent to different TRPs can employ different beams and / or precoding matrices, which are typically indicated by different SRI fields. Currently, the DCI for scheduling PUSCH retransmissions can contain two SRI fields, used to determine the beams and / or precoding matrices for PUSCH retransmissions sent to different TRPs.

[0057] For example, such as Figure 6 The diagram illustrates a PUSCH retransmission based on multiple TRPs. If the channel between TRP0 and the terminal device deteriorates, the retransmission sent to TRP0 may be difficult for the corresponding TRP to receive, resulting in a waste of resources and power. In this case, if switching between single TRP (e.g., TRP0) transmission (using a single SRI field) and multiple TRP transmission (i.e., two TRPs, TRP0 and TRP1, using multiple SRI fields, SRI0 and SRI1) can be supported, this waste of resources and power can be avoided.

[0058] In practical applications, if the number of SRI fields is configured using RRC signaling, it is difficult to support dynamic switching and cannot switch in real time according to the channel. If additional bits in the DCI are used for indication, it will increase the DCI overhead and affect the performance of the control channel. If the number of SRI fields contained in the DCI is determined by blind detection and then the switching is performed, it will significantly increase the blind detection complexity of the terminal equipment. Therefore, how to achieve dynamic switching between a single SRI field and multiple SRI fields without increasing DCI overhead and blind detection complexity is a problem that needs to be solved.

[0059] To address the aforementioned problems, this invention provides a PUSCH retransmission method. The method involves a terminal device receiving Downlink Control Information (DCI) from a network device for scheduling PUSCH retransmission. The DCI includes at least two SRI fields, each indicating at least one SRS resource. Based on the information indicated by the at least two SRI fields, the terminal device determines whether to use each of the at least two SRI fields for different PUSCH retransmissions scheduled by the DCI, or to use the first SRI field of the at least two SRI fields for all PUSCH retransmissions scheduled by the DCI. This allows the terminal device to promptly switch between the retransmission method of using each of the at least two SRI fields for different PUSCH retransmissions scheduled by the DCI and the retransmission method of using the first SRI field of the at least two SRI fields for all PUSCH retransmissions scheduled by the DCI, based on the information indicated by the at least two SRI fields in the DCI. Even if the TRP channel corresponding to a certain SRI field deteriorates during transmission, the terminal device can still support switching between single TRP transmission (using a single SRI field) and multiple TRP transmissions (using multiple SRI fields) based on the indication in the network device's DCI, thereby improving uplink transmission performance.

[0060] like Figure 7 The diagram shown illustrates the system architecture of the communication system used in this embodiment of the invention. This communication system may include network devices, which can communicate with terminal devices (or communication terminals, terminals). The network devices can provide communication coverage for a specific geographical area and can communicate with terminal devices located within that coverage area. Figure 7 An exemplary embodiment shows one network device and two terminal devices. Optionally, the communication system may include multiple network devices, and each network device may include other numbers of terminal devices within its coverage area. This application embodiment does not limit this. Optionally, the communication system may also include other network entities such as a network controller and a mobility management entity. This application embodiment does not limit this.

[0061] Optionally, the communication system may include multiple network devices, and each network device may include other terminal devices within its coverage area; this embodiment of the invention does not limit this. Optionally, the communication system may also include other network entities such as a network controller and a mobility management entity; this embodiment of the invention does not limit this.

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

[0063] Terminal devices can be stations (STAION, ST) in WLANs, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in next-generation communication systems such as NR networks, or terminal devices in future evolved Public Land Mobile Network (PLMN) networks, etc.

[0064] In this embodiment of the invention, the terminal device can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (e.g., on airplanes, balloons and satellites).

[0065] In embodiments of the present invention, the terminal device may be a mobile phone, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical care, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0066] By way of example and not limitation, in this embodiment of the invention, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on only one type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0067] Network equipment can be further divided into access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks used to communicate with the access network equipment. Access network equipment can be evolved Node Bs (eNBs or e-NodeBs) in Long-Term Evolution (LTE), Next-Generation Radio (NR) (mobile communication system), or Authorized Auxiliary Access Long-Term Evolution (LAA-LTE) systems, such as macro base stations, micro base stations (also called "small base stations"), pico base stations, access points (APs), transmission points (TPs), or new generation Node Bs (gNodeBs).

[0068] In this embodiment of the invention, the network device can be a device for communicating with mobile devices. The network device can be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a vehicle-mounted device, wearable device, or a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or an NTN network, etc.

[0069] By way of example and not limitation, in this embodiment of the invention, the network device may have mobility characteristics; 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 located on land, water, or other similar locations.

[0070] In this embodiment of the invention, a network device can provide services to a cell. A terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0071] It should be understood that devices with communication functions in the network / system of this invention can be referred to as communication devices. Figure 7 Taking the communication system shown as an example, the communication equipment may include network devices and terminal devices with communication functions. The network devices and terminal devices may be specific devices in the embodiments of the present invention, which will not be described in detail here. The communication equipment may also include other devices in the communication system, such as network controllers, mobility management entities and other network entities. This is not limited in the embodiments of the present invention.

[0072] The technical solutions of this invention can be applied to various communication systems, such as: Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), General Packet Radio Service (GPRS), Long Term Evolution (LTE), Advanced Long Term Evolution (LTE-A), New Radio (NR), evolution systems of NR, LTE-based access to unlicensed spectrum (LTE-U), NR-based access to unlicensed spectrum (NR-U), Non-Terrestrial Networks (NTN), Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), and Wireless Fidelity. Fidelity (WiFi), 5th-Generation (5G) communication systems, or other communication systems.

[0073] Traditional communication systems typically 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, for example, 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. The embodiments of this invention can also be applied to these communication systems.

[0074] The communication system in this embodiment of the invention can be applied to carrier aggregation (CA) scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0075] The PUSCH retransmission method provided in this embodiment of the invention allows a terminal device to receive downlink control information (DCI) sent by a network device. The DCI is used to schedule retransmission of the Physical Uplink Shared Channel (PUSCH). The DCI includes at least two SRI fields, each of which is used to indicate at least one Sounding Reference Signal (SRS) resource. Based on the information indicated by the at least two SRI fields, the terminal device determines the PUSCH retransmission to be scheduled by the DCI.

[0076] Example 1

[0077] like Figure 8 As shown, this embodiment of the invention provides a PUSCH retransmission method, including:

[0078] 801. The network device sends a DCI to the terminal device to schedule repeated transmissions of PUSCH.

[0079] The DCI includes at least two SRI fields, each of which is used to indicate at least one probe reference signal (SRS) resource.

[0080] Optionally, at least two SRI fields in the DCI may indicate resources in different SRS resource sets. For example, the DCI may include two SRI fields, SRI field 1 and SRI field 2, where 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.

[0081] The network device can use the information indicated by at least two SRI fields to instruct the terminal device to use the at least two SRI fields respectively for different PUSCH repetitions scheduled by DCI, or to instruct the terminal device to use the first SRI field of the at least two SRI fields for all PUSCH repetitions scheduled by DCI.

[0082] 802. The terminal device determines, based on the information indicated by at least two SRI fields, whether to use the at least two SRI fields for different PUSCH repetitions scheduled by DCI, or to use the first SRI field of the at least two SRI fields for all PUSCH repetitions scheduled by DCI.

[0083] Optionally, the first SRI field mentioned above includes one of the following:

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

[0085] (b) The SRI domain that indicates the fewest SRS resources among at least two SRI domains;

[0086] (c) The SRI domain that indicates the most SRS resources among at least two SRI domains.

[0087] (d) At least two SRI domains that indicate a single SRS resource;

[0088] (e) At least two SRI fields indicate multiple SRS resources;

[0089] (f) At least two SRI fields indicate m SRS resources, where m is an integer greater than or equal to 1;

[0090] (g) SRI fields selected from at least two SRI fields.

[0091] 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 based on channel reciprocity and downlink channel information.

[0092] In this embodiment of the invention, PUSCH repetition transmission is divided into codebook-based transmission and non-codebook-based transmission.

[0093] (1) PUSCH repetition is a codebook-based transmission, and the above 802 can have two possible cases:

[0094] (1.1) If at least one of the above at least two SRI fields indicates a specific value, the terminal device will use the first SRI field for all PUSCH retransmissions scheduled by DCI.

[0095] If at least one of the at least two SRI fields indicates a specific value, then these at least two SRI fields indicate that the terminal device will use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI.

[0096] There are several possible ways to indicate feature values:

[0097] One implementation: If at least one of the two SRI fields indicates a specific value, then these at least two SRI fields instruct the terminal device to use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI.

[0098] Another implementation: If at least two SRI fields contain multiple SRI fields indicating specific values, but not all of them indicate specific values, then these at least two SRI fields instruct the terminal device to use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI.

[0099] Another implementation: if at least two SRI fields indicate a specific value, then these at least two SRI fields instruct the terminal device to use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI.

[0100] Among these, the specific value is agreed upon in advance by the terminal device and the network device; or, the specific value is pre-configured by the network device.

[0101] For example, the aforementioned specific value may be an indication of reservation, or the aforementioned specific value may be all 0, or the aforementioned specific value may be all 1.

[0102] Optionally, in cases 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 field from SRI field 1 and SRI field 2 for all PUSCH repetitions scheduled by the DCI, and discard the other SRI field. For example, the terminal device can select the SRI field with the earlier bit position in SRI field 1 and SRI field 2 (i.e., the first SRI field) for all PUSCH repetitions scheduled by the DCI, and discard the SRI field with the later bit position (i.e., the second SRI field).

[0103] For example, assuming the SRI field includes two bits, SRI field 1 and SRI field 2 both indicate a specific value of 11, then the terminal device can select SRI field 1, which has the first bit in SRI field 1, for all PUSCH retransmissions scheduled by DCI, and discard SRI field 2, which has the last bit in SRI field 2.

[0104] Optionally, for cases where the DCI includes two SRI fields, SRI field 1 and SRI field 2, if SRI field 2 indicates a specific value, the terminal device can repeatedly transmit all PUSCHs scheduled using SRI field 1 for DCI and discard the other SRI field 2. Alternatively, if SRI field 1 indicates a specific value, the terminal device can repeatedly transmit all PUSCHs scheduled using SRI field 2 for DCI and discard the other SRI field 1.

[0105] For example, assuming the SRI field includes two bits, with SRI field 2 indicating a specific value of 11, then the terminal device can choose to use SRI1 for all PUSCH duplicate transmissions in DCI scheduling, and discard SRI field 2.

[0106] Optionally, for cases where the DCI includes three SRI fields (SRI field 1, SRI field 2, and SRI field 3), if both SRI field 2 and SRI field 3 indicate specific values, the terminal device can use SRI field 1 for all PUSCH retransmissions scheduled by the DCI, and discard the other two SRI fields. For example, the terminal device can select the SRI field with the earliest bit position (i.e., the first SRI field) from SRI field 1, SRI field 2, and SRI field 3 for all PUSCH retransmissions scheduled by the DCI, and discard the other two SRI fields with the latest bit position.

[0107] For example, assuming the SRI field includes two bits, SRI field 2 and SRI field 3 both indicate a specific value of 11, then the terminal device can repeatedly transmit all PUSCHs for DCI scheduling using SRI field 1, and discard SRI field 2 and SRI field 3 with the later bits.

[0108] Optionally, for cases 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 repeatedly transmit all PUSCHs for DCI scheduling using SRI field 1, and discard the other SRI fields 2 and SRI field 3.

[0109] For example, assuming the SRI field includes two bits, SRI field 1 indicates a specific value 11, and SRI field 2 and SRI field 3 indicate other values, then the terminal device can choose to use SRI1 for all PUSCH duplicate transmissions in DCI scheduling, and discard SRI field 2.

[0110] Optionally, for cases 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, then the terminal device can repeatedly transmit all PUSCHs for DCI scheduling using SRI field 3, and discard the other SRI fields 2 and SRI field 1.

[0111] For example, assuming the SRI field includes 2 bits, SRI field 1 and SRI field 2 indicate a specific value 00, and SRI field 3 indicates other values, then the terminal device can use SRI3 for all PUSCH retransmissions in DCI scheduling, and discard SRI field 2 and SRI field 1.

[0112] (1.2) If at least two of the above SRI fields indicate non-specific values, the terminal device will use the at least two SRI fields respectively for different PUSCH retransmissions scheduled by DCI.

[0113] If at least two SRI fields indicate non-specific values, then these at least two SRI fields indicate that the terminal device will use at least two SRI fields respectively for different PUSCH retransmissions scheduled by DCI.

[0114] Optionally, for cases 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 different PUSCH retransmissions in the DCI scheduling.

[0115] For example, assuming the SRI field includes two bits, SRI field 1 and SRI field 2 both indicate values ​​other than the specific value 11, the terminal device can use SRI field 1 and SRI field 2 for different PUSCH retransmissions scheduled by DCI.

[0116] Optionally, for cases where the DCI includes SRI field 1, SRI field 2, and SRI field 3, totaling 3 SRI fields, if SRI field 1, SRI field 2, and SRI field 3 all indicate non-specific values, the terminal device can use SRI field 1, SRI field 2, and SRI field 3 for different PUSCH retransmissions in the DCI scheduling.

[0117] For example, assuming the SRI field includes two bits, SRI field 1 and SRI field 2 both indicate values ​​other than the specific value 11, the terminal device can use SRI field 1, SRI field 2 and SRI field 3 for different PUSCH retransmissions in DCI scheduling.

[0118] (2) PUSCH repetition is a non-codebook-based transmission, and there are two possible scenarios:

[0119] (2.1) If at least two of the above at least two SRI fields indicate different numbers of SRS resources, the terminal device will use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI.

[0120] Optionally, for cases where the DCI includes two SRI fields, one SRI field indicates one SRS resource and the other SRI field indicates multiple SRS resources, if the terminal device determines that one SRI field indicates one SRS resource and the other SRI field indicates multiple SRS resources, the terminal device will use the first SRI field for all PUSCH duplicate transmissions scheduled by the DCI.

[0121] If at least two SRI fields indicate different numbers of SRS resources, then the terminal device is instructed to use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI.

[0122] The number of SRS resources indicated by all SRI fields in the aforementioned at least two SRI fields is different, or the number of SRS resources indicated by at least two SRI fields in the aforementioned at least two SRI fields is different.

[0123] At least two SRI domains, where different SRI domains indicate different numbers of SRS resources, can be implemented in the following ways:

[0124] The first implementation involves each of at least two SRI domains indicating a different number of SRS resources.

[0125] For example, the two SRI domains are SRI domain 1 and SRI domain 2, where SRI domain 1 indicates one SRS resource and SRI domain 2 indicates four SRS resources.

[0126] The second implementation method is to have at least two SRI fields indicating different numbers of SRS resources. For example, the three SRI fields are SRI field 1, SRI field 2 and SRI field 3, where SRI field 1 indicates 1 SRS resource, SRI field 3 indicates 1 SRS resource and SRI field 2 indicates 4 SRS resources.

[0127] The third implementation method is: at least two SRI fields indicate 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, where SRI field 1 indicates 1 SRS resource, SRI field 3 indicates 1 SRS resource, SRI field 2 indicates 4 SRS resources and SRI field 4 indicates 2 SRS resources.

[0128] Optionally, at least two SRI fields in the DCI may indicate SRS resources in different SRS resource sets. For example, the DCI may include two SRI fields, SRI field 1 and SRI field 2, where 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.

[0129] Optionally, each SRI field can be used to indicate an index of a single-port SRS resource or an index of multiple single-port SRS resources, where the number of SRS resource indexes is equal to the number of SRS resources. The terminal device determines whether to use the first SRI field for repeated transmission of all PUSCHs scheduled by DCI based on whether the number of SRS resources indicated by different SRI fields is the same.

[0130] When at least two SRI fields indicate SRS resources in different SRS resource sets, and each SRI field indicates an index of one or more single-port SRS resources, the different SRI fields indicate the indices of SRS resources in different SRS resource sets. For example, in a DCI, there are SRI fields 1 and 2. SRI field 1 indicates SRS resources in SRS resource set A, and SRI field 2 indicates SRS resources in SRS resource set B. If SRI field 1 indicates index 0 of a single-port SRS resource, and SRI field 2 indicates indices 1 and 2 of two single-port SRS resources, then SRI field 1 indicates the SRS resource with index 0 in SRS resource set A, and SRI field 2 indicates the SRS resource with index 1 and index 2 in SRS resource set B.

[0131] For example, the 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 indices 1 and 2 of two single-port SRS resources. In this case, SRI field 1 indicates one SRS resource, and SRI field 2 indicates two SRS resources. Since the number of SRS resources indicated by the two is different, it can be determined that the first SRI field (which can be the SRI field with the first bit in SRI field 1 and SRI field 2) will be used for all PUSCH retransmissions scheduled by the DCI.

[0132] For example, the DCI includes SRI field 1, SRI field 2, and SRI 3. SRI field 1 indicates index 0 of a single-port SRS resource, SRI field 2 indicates indices 1 and 2 of two single-port SRS resources, and SRI 3 indicates index 1 of a single-port SRS resource. In this case, SRI field 1 indicates one SRS resource, SRI field 2 indicates two SRS resources, and SRI 3 indicates one SRS resource. The number of SRS resources indicated by SRI field 2 is different from that of SRI field 1 and SRI field 3. It can be determined that the first SRI field (which can be the SRI field with the first bit position among SRI field 1, SRI field 2, and SRI field 3) will be used for all PUSCH retransmissions scheduled by the DCI.

[0133] For example, the DCI includes SRI field 1, SRI field 2, and SRI 3. SRI field 1 indicates index 0 of a single-port SRS resource, SRI field 2 indicates indices 1 and 2 of two single-port SRS resources, and SRI 3 indicates indices 0, 1, and 2 of three single-port SRS resources. In this case, SRI field 1 indicates one SRS resource, SRI field 2 indicates two SRS resources, and SRI 3 indicates three SRS resources. The number of SRS resources indicated by SRI field 1, SRI field 2, and SRI field 3 are all different. It can be determined that the first SRI field (which can be the SRI field with the first bit position among SRI field 1, SRI field 2, and SRI field 3) will be used for all PUSCH retransmissions scheduled by the DCI.

[0134] Optionally, the number of SRS resources indicated by the SRI is equal to the transport layer rank. In this embodiment of the invention, different SRI fields can indicate different numbers of SRS resources or the same number of SRS resources. Correspondingly, different SRI fields can also indicate the same transport layer rank or different transport layers.

[0135] Optionally, when determining the number of SRS resources based on the content indicated by the SRS field, the maximum number of transport layers L configured with higher-layer signaling can be used. max Regarding this, the following explanation uses a maximum transmission layer number of 2 to 4 as an example, in conjunction with Tables 1 to 4, where SRI(s), N SRS =2 indicates that the SRS resource set includes 2 SRS resources, SRI(s),N SRS =3 indicates that the SRS resource set includes 3 SRS resources; SRI(s),N SRS =4 indicates that the SRS resource set includes 4 SRS resources.

[0136] As shown in Table 1, this is for the maximum number of transmission layers L. max When SRI = 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.

[0137] Specifically, as shown in Table 1 below, for SRI(s), N SRS =2: If the value indicated by the bit field mapped to index in the SRI field is 0 (for example, two bits are 00), the corresponding SRI indicates one resource with index 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 one resource with index 1 in the SRS resource set.

[0138] For SRI(s), N SRS =3. If the bit field mapped to index is 2 (e.g., two bits are 10), then the corresponding SRI indicates one resource with index 2 in the SRS resource set; if the bit field mapped to index is 3 (e.g., two bits are 11), then the corresponding SRI does not indicate any resource in the SRS resource set. Here, reserved indicates that it is reserved.

[0139] For SRI(s), N SRS =4. If the bit field mapped to index is 3 (for example, two bits are 11), then the corresponding SRI indicates one resource with index 3 in the SRS resource set.

[0140] Table 1

[0141]

[0142] As shown in Table 2, this is for the maximum number of transmission layers L. max When the value is 2, the content indicated by the SRI field corresponds to the corresponding SRS resource. In this case, the SRI field can indicate a maximum of 2 SRS resources.

[0143] 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 one resource with index 0 in the SRS resource set; if the bit field mapped to index is 1, the corresponding SRI indicates one resource with index 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 (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.

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

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

[0146] Table 2

[0147]

[0148]

[0149] As shown in Table 3, this is for the maximum number of transmission layers L. max When the SRI field indicates 3 resources, it represents the correspondence between the SRI field and the corresponding SRS resources. In this case, the SRI field can indicate a maximum of 3 SRS resources. The specific indication method is similar to that in Tables 1 and 2 above, and will not be repeated here.

[0150] Table 3

[0151]

[0152] As shown in Table 4, this is for the maximum number of transmission layers L. max When the SRI field indicates 4 resources, it represents the correspondence between the SRI field and the corresponding SRS resources. In this case, the SRI field can indicate a maximum of 4 SRS resources. The specific indication method is similar to that in Tables 1 and 2 above, and will not be repeated here.

[0153]

[0154]

[0155] (2.2) If at least two SRI fields indicate the same number of SRS resources, the terminal device will use the at least two SRI fields for different PUSCH retransmissions scheduled by DCI.

[0156] Optionally, the terminal device may use at least two SRI fields for different PUSCH repetition transmissions scheduled by DCI. This can be understood as the terminal device using at least two SRI fields for PUSCH repetition transmissions scheduled by DCI for different TRPs.

[0157] If at least two SRI fields indicate the same number of SRS resources, then the terminal device is instructed to use at least two SRI fields for different PUSCH retransmissions scheduled by DCI.

[0158] Optionally, if the number of SRS resources indicated by all SRI fields in the at least two SRI fields is the same, the terminal device will use the at least two SRI fields respectively for different PUSCH retransmissions scheduled by DCI.

[0159] For example, the 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 a single-port SRS resource. In this case, both SRI field 1 and SRI field 2 indicate one SRS resource, and the number of SRS resources indicated by both is the same. It can be determined that all PUSCH repetition transmissions using SRI field 1 and SRI field 2 for DCI scheduling are respectively used for different PUSCH repetition transmissions in DCI scheduling.

[0160] For example, 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 field 2 indicates indices 1, 2 and 3 of three single-port SRS resources. In this case, both SRI field 1 and SRI field 2 indicate three SRS resources, and the number of SRS resources indicated by both is the same. It can be determined that all PUSCH repetition transmissions using SRI field 1 and SRI field 2 for DCI scheduling are respectively used for different PUSCH repetition transmissions in DCI scheduling.

[0161] Optionally, if the information in the first SRI field is used for all PUSCH repetitions scheduled by DCI, then the information in the second SRI field is not used for any PUSCH transmission, and the second SRI field is an SRI field other than the first SRI field among at least two SRI fields.

[0162] Optionally, if the first SRI field is used for all PUSCH repetitive transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the first TPC command is used for all PUSCH repetitive transmissions scheduled by the DCI, and the first TPC command is the TPC command associated with the first SRI field in at least two TPC fields.

[0163] Optionally, the association between the SRI field and the TPC command can have the following two possible scenarios:

[0164] The first possible scenario: The k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where k is a positive integer;

[0165] For example, suppose the DCI includes two SRI fields and two TPC commands. According to their 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 SRI field 1 is associated with TPC command 1, and SRI field 2 is associated with TCP command 2.

[0166] For example, suppose the DCI includes three SRI fields and three TPC commands. According to their bit order, the first SRI field is SRI field 1, the second SRI field is SRI field 2, and the third SRI field is SRI field 3. The first TPC command is TPC command 1, the second TPC command is TCP command 2, and the third TPC command is TCP command 3. Here, SRI field 1 is associated with TPC command 1, SRI field 2 is associated with TCP command 2, and SRI field 3 is associated with TCP command 3.

[0167] The second possible scenario is that 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.

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

[0169] For example, suppose the DCI includes two SRI fields (SRI field 1 and SRI field 2) and two TPC commands (TPC command 1 and TPC command 2). TPC command 1 is associated with the closed-loop power adjustment state with index 0, and 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, when SRI field 1 is the first SRI field, TPC command 1 is the first TPC command.

[0170] For example, suppose 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). TPC command 1 is associated with the closed-loop power adjustment state with index 0, and 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. TPC command 3 is associated with the closed-loop power adjustment state with index 0, and SRI field 3 is associated with the closed-loop power adjustment state with index 1. Then, when SRI field 1 is the first SRI field, TPC command 1 and TPC command 3 are the first TPC commands.

[0171] In one implementation, if none of the at least two TPC commands is associated with the same closed-loop power adjustment state as the information indicated by the first SRI field, then neither of the at least two TPC commands is used for the DCI-scheduled PUSCH retransmission.

[0172] In another implementation, if 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, then the at least two TPC commands are used for the PUSCH retransmission scheduled by the DCI, that is, the at least two TPC commands are used for the transmission power adjustment of the PUSCH.

[0173] Optionally, the second TPC command in at least two TPC domains may not be used for power control of any PUSCH transmissions.

[0174] Optionally, a second TPC command in at least two TPC fields is used for power accumulation in a second closed-loop power adjustment state, which is a closed-loop power adjustment state determined according to information indicated by a second SRI field.

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

[0176] Optionally, if at least two SRI fields are used for different PUSCH repetitions scheduled by the DCI, and the DCI contains at least two TPC commands, then the at least two TPC commands are used for different PUSCH repetitions scheduled by the DCI.

[0177] Optionally, each of the at least two TPC commands may be indicated by a different TPC field in the DCI. For example, for two TPC commands, TPC command 1 and TPC command 2, the DCI includes TCP field 1 and TCP field 2, where TCP field 1 indicates TPC command 1 and TCP field 2 indicates TPC command 2.

[0178] Optionally, at least two TPC commands may be indicated through the same TPC field in the DCI. For example, for two TPC commands, TPC command 1 and TPC command 2, the DCI may include TCP field 1, where TCP field 1 indicates TPC command 1 and TPC command 2.

[0179] In this embodiment of the invention, the terminal device can receive Downlink Control Information (DCI) sent by the network device for scheduling repeated PUSCH transmissions. The DCI includes at least two SRI fields, each SRI field indicating at least one SRS resource. Based on the information indicated by the at least two SRI fields, the terminal device determines whether to use the at least two SRI fields separately for different repeated PUSCH transmissions scheduled by the DCI, or to use the first SRI field of the at least two SRI fields for all repeated PUSCH transmissions scheduled by the DCI. Thus, the terminal device can promptly switch between the repeated transmission method of using the at least two SRI fields separately for different repeated PUSCH transmissions scheduled by the DCI and the repeated transmission method of using the first SRI field of the at least two SRI fields for all repeated PUSCH transmissions scheduled by the DCI, based on the information indicated by the at least two SRI fields in the DCI. Even if the TRP channel corresponding to a certain SRI field deteriorates during transmission, the terminal device can still switch between single TRP transmission (using a single SRI field) and multiple TRP transmissions (using multiple SRI fields) based on the indication in the network device's DCI, thereby flexibly implementing repeated PUSCH transmissions.

[0180] Example 2

[0181] This embodiment uses codebook-based transmission as an example, where the transmission mode configured by the higher-layer signaling is codebook. Each SRI field indicates an SRS resource.

[0182] The terminal device receives a downlink DCI for scheduling repeated PUSCH transmissions. The DCI contains two SRI fields, namely SRI field 1 and SRI field 2.

[0183] Based on the contents indicated by the two SRI fields, the terminal device determines whether to use the information in SRI field 1 and SRI field 2 for different PUSCH repeat transmissions, or to use the information in the first SRI field for all PUSCH repeat transmissions.

[0184] Optionally, the first SRI field is the first of the two SRI fields contained in the DCI.

[0185] In one implementation, when at least one of the two SRI fields indicates a specific value, the terminal device uses the information of the first SRI field in SRI field 1 and SRI field 2 for all PUSCH repeat transmissions; when the two SRI fields indicate other values, the terminal device uses the information of SRI field 1 and SRI field 2 for different PUSCH repeat transmissions respectively.

[0186] In one implementation, the specific value is a value pre-agreed upon by the terminal device and the network device. For example, when SRI field 2 indicates reservation, or when SRI field 2 indicates all 0s or all 1s, the terminal device uses the information from SRI field 1 for all PUSCH repeat transmissions, and the information from SRI field 2 is not used for any transmission (it is discarded or ignored). In other cases, the terminal device uses the information from SRI field 1 and SRI field 2 for different PUSCH repeat transmissions, that is, the information from both SRI fields is used.

[0187] In another implementation, the specific value is a value pre-configured by the network device. When both SRI fields indicate the same value, the terminal device uses only one of the SRI fields, and the other SRI field is discarded.

[0188] In the above embodiments, dynamic switching between a single SRI domain (repeated transmission of PUSCH in a single TRP) and multiple SRI domains (repeated transmission of PUSCH in multiple TRPs) can be achieved without additional DCI overhead, thereby achieving better uplink transmission performance.

[0189] In one implementation, the DCI includes two TPC domains: TPC domain 1 and TPC domain 2, each TPC domain indicating a TPC command.

[0190] If the terminal device uses the information in SRI domain 1 and SRI domain 2 for different PUSCH repetition transmissions, then the terminal device will use the two TPC domains for different PUSCH repetition transmissions. That is, the PUSCH repetition transmissions scheduled by DCI use the TPC command in TPC domain 1 to determine the closed-loop power adjustment status and transmission power, while the PUSCH repetition transmissions use the TPC command in TPC domain 2 to determine the closed-loop power adjustment status and transmission power.

[0191] If the terminal device uses the information in the first SRI field for all PUSCH repeat transmissions, then the terminal device will use the first TPC field associated with the first SRI field in TPC field 1 and TPC field 2 for all PUSCH repeat transmissions. That is, all PUSCH repeat transmissions scheduled by DCI use the TPC command in the first TPC field to determine the closed-loop power adjustment status and transmission power.

[0192] In one implementation, the SRI field and the TPC field are associated as follows: the first SRI field in the DCI is associated with the first TPC field, and the second SRI field in the DCI is associated with the second TPC field.

[0193] In another implementation, the first TPC field is the TPC field that is associated with the information indicated by the first SRI field and has the same closed-loop power adjustment state.

[0194] The two TPC fields are associated with different closed-loop power adjustment states. For example, the first TPC field is associated with the closed-loop power adjustment state with index 0, and the second TPC field is associated with the closed-loop power adjustment state with index 1.

[0195] Different values ​​indicated by the first SRI field can be associated with different closed-loop power adjustment states, and this association can be notified to the terminal device through higher-layer signaling. Alternatively, SRI field 1 and SRI field 2 can themselves be associated with different closed-loop power adjustment states. For example, SRI field 1 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 0.

[0196] In one implementation, 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 among the aforementioned TPC domain 1 and TPC domain 2.

[0197] It should be noted that there are also cases where a TPC domain includes two TPC commands. In this case, the SRI domain is associated with the TPC command.

[0198] For example, such as Figure 9A The diagram illustrates a PUSCH repetition 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 repetition transmissions, the DCI schedules some PUSCH repetition transmissions (e.g., odd-numbered transmissions) to determine the transmission beam / precoding matrix based on the SRS resources indicated by SRI0, while other PUSCH repetition transmissions (e.g., even-numbered transmissions) determine the transmission beam / precoding matrix based on the SRS resources indicated by SRI1.

[0199] For example, such as Figure 9BThe diagram shows a PUSCH repetition transmission based on a single SRI field. When the terminal device determines to use the SRI0 information for all PUSCH repetition transmissions, all PUSCH repetition transmissions scheduled by DCI determine the transmission beam / precoding matrix based on the SRS resource indicated by the first SRI field.

[0200] Based on the method of this embodiment, dynamic switching between a single SRI field (all repeated transmissions are for the same TRP, using the same beam / precoder) and multiple SRI fields (different repeated transmissions are for different TRPs, using different beam / precoders) can be achieved through the information indicated by the SRI field. This allows for real-time adjustment of the repeated transmission configuration according to the link quality of different TRPs, achieving higher uplink spectral efficiency and improving the performance of uplink multi-TRP diversity transmission. Moreover, since no additional DCI bits are required, and the DCI size does not need to be dynamically switched, additional DCI overhead is avoided, and the complexity of blind detection in terminal equipment is reduced.

[0201] Example 3

[0202] This embodiment uses the scheduled PUSCH as an example of non-codebook-based transmission, that is, the transmission mode configured by the higher-layer signaling is non-codebook. Each SRI field is used to indicate one or more single-port SRS resources.

[0203] The terminal device receives a downlink DCI for scheduling repeated PUSCH transmissions. The DCI contains two SRI fields, namely SRI field 1 and SRI field 2.

[0204] Based on the contents indicated by the two SRI fields, the terminal device determines whether to use the information in SRI field 1 and SRI field 2 for different PUSCH repeat transmissions, or to use the information in the first SRI field for all PUSCH repeat transmissions.

[0205] In this embodiment, the first SRI field can be one of the following:

[0206] (1) The first SRI field of the two SRI fields contained in the DCI, for example, the SRI field that comes first in the DCI.

[0207] (2) The SRI domain with fewer SRS resources indicated in the two SRI domains included in the DCI.

[0208] (3) The SRI domain that indicates the larger number of SRS resources in the two SRI domains included in the DCI.

[0209] (4) The SRI field in the two SRI fields included in the DCI indicates a single SRS resource. In this case, the other SRI field in the two SRI fields indicates multiple SRS resources;

[0210] (5) The SRI field in the two SRI fields included in the DCI indicates one or two SRS resources. In this case, the other SRI field in the two SRI fields indicates more than two SRS resources;

[0211] (6) The terminal device selects an SRI field from the two SRI fields included in the DCI. Specifically, the terminal device may randomly select one SRI field, or select one SRI field based on channel reciprocity and downlink channel information.

[0212] Optionally, when the PUSCH retransmission is a non-codebook-based transmission, if the two SRI fields indicate different numbers of SRS resources (e.g., one SRI field indicates one SRS resource index and the other indicates two SRS resource indices), the terminal device uses the information from the first SRI field for all PUSCH retransmissions, and the information from the second SRI field is not used for any transmission (it is discarded or ignored). When the two SRI fields indicate the same number of SRS resources, the terminal device uses the information from the two SRI fields for different PUSCH retransmissions.

[0213] The second SRI field is the SRI field other than the first SRI field in SRI field 1 and SRI field 2.

[0214] In the above embodiments, dynamic switching between a single SRI field (repeated PUSCH transmission in a single TRP) and multiple SRI fields (repeated PUSCH transmission in multiple TRPs) can be achieved without additional DCI overhead, thereby achieving better uplink transmission performance. Furthermore, since this method does not require modification of the existing SRI field definitions and indications, it reduces the impact on the implementation of terminal equipment.

[0215] In one implementation, the DCI includes two TPC commands: TPC command 1 and TPC command 2. The two TPC commands may be contained in the same TPC domain or in different TPC domains.

[0216] If the terminal device uses the information from SRI field 1 and SRI field 2 for different PUSCH repetition transmissions, then the terminal device will use two TPC commands for different PUSCH repetition transmissions. That is, for some PUSCH repetition transmissions scheduled by DCI, TPC command 1 is used to determine the closed-loop power adjustment status and transmission power, while for other PUSCH repetition transmissions, TPC command 2 is used to determine the closed-loop power adjustment status and transmission power.

[0217] If the terminal device uses the information in the first SRI field for all PUSCH repeat transmissions, then the terminal device will use the first TPC command associated with the first SRI field in TPC command 1 and TPC command 2 for all PUSCH repeat transmissions. That is, all PUSCH repeat transmissions scheduled by DCI use the first TPC command to determine the closed-loop power adjustment status and transmission power.

[0218] In one implementation, the SRI field is associated with the TPC command 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.

[0219] In another implementation, 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.

[0220] Two TPC commands are associated with different closed-loop power adjustment states. For example, one TPC command is associated with the closed-loop power adjustment state with index 0, and the other TPC command is associated with the closed-loop power adjustment state with index 1.

[0221] The correlation between the SRI field or the information indicated by the SRI field and the closed-loop power regulation status can be obtained through the following optional methods:

[0222] The first option is that the network device can also notify the terminal device in advance of the closed-loop power adjustment status associated with each TPC command via higher-layer signaling.

[0223] Alternatively, different values ​​indicated by the SRI field can be associated with different closed-loop power adjustment states, and this association can also be communicated to the terminal equipment via higher-layer signaling.

[0224] The third option is that SRI field 1 and SRI field 2 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 field 1 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 0.

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

[0226] In one implementation, the second TPC command in the DCI is not used for the PUSCH of the DCI scheduling, but is still used for the power accumulation of the second closed-loop power adjustment state, which is the closed-loop power adjustment state determined according to the information indicated by the second SRI field.

[0227] Optional, such as Figure 9A As shown, DCI includes two SRI fields, SRI0 and SRI1. When the terminal device determines to use the information of SRI0 and SRI1 for different PUSCH repetition transmissions, the DCI schedules some PUSCH repetition transmissions (e.g., the first two transmissions) to determine the transmission beam / precoding matrix based on the SRS resources indicated by SRI0, and other PUSCH repetition transmissions (e.g., the last two transmissions) to determine the transmission beam / precoding matrix based on the SRS resources indicated by SRI1.

[0228] like Figure 9B As shown, DCI includes two SRI fields, SRI0 and SRI1. When the terminal device determines to use the information of SRI0 for all PUSCH repetition transmissions, all PUSCH repetition transmissions scheduled by DCI are based on the SRS resources indicated by the SRI0 field to determine the transmission beam / precoding matrix.

[0229] Based on the method of this invention, dynamic switching between a single SRI field (all repeated transmissions are for the same TRP, using the same beam / precoder) and multiple SRI fields (different repeated transmissions are for different TRPs, using different beam / precoders) can be achieved through the information content indicated by the SRI field. This allows for real-time adjustment of the repeated transmission configuration according to the link quality of different TRPs, achieving higher uplink spectral efficiency and improving the performance of uplink multi-TRP diversity transmission. Furthermore, since no additional DCI bits are required, and dynamic switching of the DCI size is unnecessary, additional DCI overhead is avoided, and the complexity of blind detection in terminal equipment is reduced.

[0230] like Figure 10A As shown, an embodiment of the present invention provides a terminal device, including:

[0231] The receiving module 1001 is used to receive the DCI sent by the network device for scheduling PUSCH repetitive transmissions. The DCI includes at least two SRI fields, each SRI field being used to indicate at least one SRS resource.

[0232] Processing module 1002 is configured to determine, based on information indicated by at least two SRI fields, to use at least two SRI fields for DCI-scheduled PUSCH retransmission.

[0233] Optionally, the processing module 1002 is specifically configured to determine, based on the information indicated by at least two SRI fields, whether to use the at least two SRI fields for different PUSCH repetitions scheduled by DCI, or to use the first SRI field of the at least two SRI fields for all PUSCH repetitions scheduled by DCI.

[0234] Optionally, PUSCH retransmission is a codebook-based transmission;

[0235] The processing module 1002 is specifically used to use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI if at least one of the at least two SRI fields indicates a specific value.

[0236] The processing module 1002 is specifically used to use at least two SRI fields for different PUSCH retransmissions scheduled by DCI if at least two SRI fields indicate non-specific values.

[0237] Optionally, the specific value is pre-agreed upon by the terminal device and the network device;

[0238] or,

[0239] Specific values ​​are pre-configured by network devices.

[0240] Optionally, PUSCH retransmission is a non-codebook-based transmission;

[0241] The processing module 1002 is specifically used to use the first SRI field for all PUSCH duplicate transmissions in DCI scheduling if at least two SRI fields indicate different numbers of SRS resources.

[0242] The processing module 1002 is specifically used to use at least two SRI fields for different PUSCH retransmissions scheduled by DCI if at least two SRI fields indicate the same number of SRS resources.

[0243] Optionally, the processing module 1002 is further configured to, if the information of the first SRI field is used for all PUSCH repetitive transmissions scheduled by DCI, then the information of the second SRI field is not used for any PUSCH transmission, wherein the second SRI field is an SRI field other than the first SRI field among at least two SRI fields.

[0244] Optionally, the processing module 1002 is further configured to use the first TPC command for all PUSCH repetitive transmissions scheduled by the DCI if the first SRI domain is used for all PUSCH repetitive transmissions scheduled by the DCI and the DCI contains at least two TPC commands. The first TPC command is a TPC command associated with the first SRI domain among at least two TPC domains.

[0245] Optionally, the k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where k is a positive integer;

[0246] or,

[0247] 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.

[0248] Optionally, the second TPC command in at least two TPC domains may not be used for power control of any PUSCH transmissions.

[0249] or,

[0250] The second TPC command in at least two TPC fields is used for power accumulation in the second closed-loop power adjustment state, which is the closed-loop power adjustment state determined according to the information indicated by the second SRI field.

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

[0252] Optionally, the processing module 1002 is further configured to use at least two TPC commands for different PUSCH repeat transmissions scheduled by the DCI if at least two SRI fields are used for different PUSCH repeat transmissions scheduled by the DCI, and the DCI contains at least two TPC commands.

[0253] Optionally, each of the at least two TPC commands may be indicated through a different TPC field in the DCI;

[0254] or,

[0255] At least two TPC commands are indicated through the same TPC field in the DCI.

[0256] Optionally, the first SRI field includes one of the following:

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

[0258] The SRI domain that indicates the fewest SRS resources among at least two SRI domains;

[0259] The SRI domain that indicates the most SRS resources among at least two SRI domains;

[0260] At least two SRI fields indicate a single SRS resource;

[0261] At least two SRI fields indicate multiple SRS resources;

[0262] At least two SRI fields indicate m SRS resources, where m is an integer greater than or equal to 1;

[0263] SRI domains selected from at least two SRI domains.

[0264] Optionally, the SRI fields selected from at least two SRI fields include:

[0265] The SRI domain is randomly selected from at least two SRI domains;

[0266] or,

[0267] The SRI field is selected from at least two SRI fields based on channel reciprocity and downlink channel information.

[0268] like Figure 10B As shown, an embodiment of the present invention provides a network device, including:

[0269] The sending module 1003 is used to send a DCI for scheduling repeated PUSCH transmissions to the terminal device. The DCI includes at least two SRI fields, each SRI field being used to indicate at least one SRS resource.

[0270] The terminal device is instructed to use at least two SRI fields for DCI-scheduled PUSCH retransmissions, based on the information indicated by at least two SRI fields.

[0271] Optionally, by using the information indicated by at least two SRI fields, the terminal device is instructed to use at least two SRI fields for different PUSCH repetition transmissions scheduled by DCI, including: using the information indicated by at least two SRI fields to instruct the terminal device to use at least two SRI fields for different PUSCH repetition transmissions scheduled by DCI, or instructing the terminal device to use the first SRI field of at least two SRI fields for all PUSCH repetition transmissions scheduled by DCI.

[0272] Optionally, PUSCH retransmission is a codebook-based transmission;

[0273] If at least one of the two SRI fields indicates a specific value, the terminal device is instructed to use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI.

[0274] or,

[0275] If at least two SRI fields indicate non-specific values, the terminal device is instructed to use at least two SRI fields for different PUSCH retransmissions scheduled by DCI.

[0276] Optionally, the specific value is pre-agreed upon by the terminal device and the network device;

[0277] or,

[0278] Specific values ​​are pre-configured by network devices.

[0279] Optionally, PUSCH retransmission is a non-codebook-based transmission;

[0280] If at least two SRI fields indicate different numbers of SRS resources, then instruct the terminal device to use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI.

[0281] If at least two SRI fields indicate the same number of SRS resources, then the terminal device is instructed to use at least two SRI fields for different PUSCH retransmissions scheduled by DCI.

[0282] Optionally, if the information in the first SRI field is used for all PUSCH repetitions scheduled by DCI, then the information in the second SRI field is not used for any PUSCH transmission, and the second SRI field is an SRI field other than the first SRI field among at least two SRI fields.

[0283] Optionally, if the first SRI field is used for all PUSCH repetitive transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the first TPC command is used for all PUSCH repetitive transmissions scheduled by the DCI, and the first TPC command is the TPC command associated with the first SRI field among the at least two TPC fields.

[0284] Optionally, the k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where k is a positive integer;

[0285] or,

[0286] 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.

[0287] Optional,

[0288] The second TPC command in at least two TPC domains is not used for power control of any PUSCH transmission.

[0289] or,

[0290] The second TPC command in at least two TPC fields is used for power accumulation in the second closed-loop power adjustment state, which is the closed-loop power adjustment state determined according to the information indicated by the second SRI field.

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

[0292] Optionally, if at least two SRI fields are used for different PUSCH repetitions scheduled by the DCI, and the DCI contains at least two TPC commands, then the at least two TPC commands are used for different PUSCH repetitions scheduled by the DCI.

[0293] Optionally, each of the at least two TPC commands may be indicated separately through different TPC fields in the DCI;

[0294] or,

[0295] At least two TPC commands are indicated through the same TPC field in the DCI.

[0296] Optionally, the first SRI field includes one of the following:

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

[0298] The SRI domain that indicates the fewest SRS resources among at least two SRI domains;

[0299] The SRI domain that indicates the most SRS resources among at least two SRI domains;

[0300] At least two SRI fields indicate a single SRS resource;

[0301] At least two SRI fields indicate multiple SRS resources;

[0302] At least two SRI fields indicate m SRS resources, where m is an integer greater than or equal to 1;

[0303] SRI domains selected from at least two SRI domains.

[0304] Optionally, the SRI fields selected from at least two SRI fields include:

[0305] The SRI domain is randomly selected from at least two SRI domains;

[0306] or,

[0307] The SRI field is selected from at least two SRI fields based on channel reciprocity and downlink channel information.

[0308] This invention also provides a terminal device, including: a memory storing executable program code;

[0309] A processor coupled to memory;

[0310] The processor calls the executable program code stored in the memory to execute the PUSCH repeated transmission method executed by the terminal device in this embodiment of the invention.

[0311] This invention also provides a network device, including: a memory storing executable program code;

[0312] A processor coupled to memory;

[0313] The processor calls the executable program code stored in the memory to execute the PUSCH repeat transmission method performed by the network device in this embodiment of the invention.

[0314] For example, the terminal device in this embodiment of the invention can be a mobile phone, such as... Figure 11 As shown, a mobile phone may include components such as a radio frequency (RF) circuit 1110, a memory 1120, an input unit 1130, a display unit 1140, a sensor 1150, an audio circuit 1160, a wireless fidelity (WiFi) module 1170, a processor 1180, and a power supply 1190. The RF circuit 1110 includes a receiver 1111 and a transmitter 1112. Those skilled in the art will understand that... Figure 11 The mobile phone structure shown does not constitute a limitation on the mobile phone and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0315] RF circuit 1110 can be used for receiving and transmitting signals during information transmission or calls. Specifically, it receives downlink information from the base station and processes it with processor 1180; additionally, it transmits uplink data to the base station. Typically, RF circuit 1110 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier (LNA), a duplexer, etc. Furthermore, RF circuit 1110 can also communicate wirelessly with networks and other devices. The aforementioned wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile Communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Message Service (SMS), etc.

[0316] The memory 1120 can be used to store software programs and modules. The processor 1180 executes various functions 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 program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the mobile phone (such as audio data, phonebook, etc.). In addition, the memory 1120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device.

[0317] The input unit 1130 can be used to receive input numerical or character information, and to generate key signal inputs related to user settings 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 known as a touch screen, can collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel 1131), and drive the corresponding connection devices according to a pre-set program. Optionally, the touch panel 1131 may include two parts: a touch detection device and a touch controller. The touch detection device detects the user's touch position and the signal generated by the touch operation, and transmits the signal to the touch controller; the touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to the processor 1180, and can receive and execute commands sent by the processor 1180. In addition, the touch panel 1131 can be implemented using various types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 1131, the input unit 1130 may also include other input devices 1132. Specifically, other input devices 1132 may include, but are not limited to, one or more of the following: physical keyboard, function keys (such as volume control buttons, power buttons, etc.), trackball, mouse, joystick, etc.

[0318] Display unit 1140 can be used to display information input by the user or information provided to the user, as well as various menus of the mobile phone. Display unit 1140 may include display panel 1141, optionally configured as a liquid crystal display (LCD), organic light-emitting diode (OLED), or similar form. Further, touch panel 1131 may cover display panel 1141. When touch panel 1131 detects a touch operation on or near it, it transmits the information to processor 1180 to determine the type of touch event. Subsequently, processor 1180 provides corresponding visual output on display panel 1141 based on the type of touch event. Although in Figure 11 In this embodiment, the touch panel 1131 and the display panel 1141 are two separate components to realize the input and output functions of the mobile phone. However, in some embodiments, the touch panel 1131 and the display panel 1141 can be integrated to realize the input and output functions of the mobile phone.

[0319] The mobile 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. The ambient light sensor can adjust the brightness of the display panel 1141 according to the ambient light level, and the proximity sensor can turn off the display panel 1141 and / or the backlight when the phone is moved to the ear. As a type of motion sensor, an accelerometer sensor can detect the magnitude of acceleration in various directions (generally three axes). When stationary, it can detect the magnitude and direction of gravity and can be used for applications that recognize the phone's posture (such as landscape / portrait switching, related games, magnetometer posture calibration), vibration recognition-related functions (such as pedometer, taps), etc. Other sensors that may be configured in the mobile phone, such as gyroscopes, barometers, hygrometers, thermometers, and infrared sensors, will not be described in detail here.

[0320] Audio circuit 1160, speaker 1161, and microphone 1162 provide an audio interface between the user and the mobile phone. Audio circuit 1160 converts received audio data into electrical signals and transmits them to speaker 1161, where speaker 1161 converts them into sound signals for output. On the other hand, microphone 1162 converts collected sound signals into electrical signals, which are received by audio circuit 1160, converted into audio data, and then processed by processor 1180 before being transmitted via RF circuit 1110 to, for example, another mobile phone, or the audio data can be output to memory 1120 for further processing.

[0321] WiFi is a short-range wireless transmission technology. Through the WiFi module 1170, mobile phones can help users send and receive emails, browse web pages, and access streaming media, providing users with wireless broadband internet access. Although Figure 11 WiFi module 1170 is shown, but it is understood that it is not an essential component of a mobile phone and can be omitted as needed without changing the essence of the invention.

[0322] The processor 1180 is the control center of the mobile phone, connecting various parts of the phone through various interfaces and lines. It executes software programs and / or modules stored in the memory 1120, and calls data stored in the memory 1120 to perform various functions and process data, thereby providing overall monitoring of the phone. 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 handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 1180.

[0323] The mobile phone also includes a power supply 1190 (such as a battery) that supplies power to various components. Preferably, the power supply can be logically connected to the processor 1180 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. Although not shown, the mobile phone may also include a camera, Bluetooth module, etc., which will not be described in detail here.

[0324] In this embodiment of the invention, RF circuit 1110 is used to receive DCI sent by network device for scheduling PUSCH repetitive transmissions. The DCI includes at least two SRI fields, each SRI field being used to indicate at least one SRS resource.

[0325] Processor 1180 is specifically configured to determine, based on information indicated by at least two SRI fields, to use the at least two SRI fields for different PUSCH retransmissions scheduled by DCI.

[0326] Optionally, the processor 1180 is specifically configured to determine, based on the information indicated by at least two SRI fields, whether to use the at least two SRI fields for different PUSCH repetitions scheduled by the DCI, or to use the first SRI field of the at least two SRI fields for all PUSCH repetitions scheduled by the DCI.

[0327] Optionally, PUSCH retransmission is a codebook-based transmission;

[0328] Processor 1180 is specifically configured to use the first SRI field for all PUSCH retransmissions scheduled by DCI if at least one of the at least two SRI fields indicates a specific value.

[0329] Processor 1180 is specifically configured to use at least two SRI fields for different PUSCH repetition transmissions scheduled by DCI if at least two SRI fields indicate non-specific values.

[0330] Optionally, the specific value is pre-agreed upon by the terminal device and the network device;

[0331] or,

[0332] Specific values ​​are pre-configured by network devices.

[0333] Optionally, PUSCH retransmission is a non-codebook-based transmission;

[0334] The processor 1180 is specifically configured to use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI if at least two SRI fields indicate different numbers of SRS resources.

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

[0336] Optionally, the processor 1180 is further configured to, if the information of the first SRI field is used for all PUSCH retransmissions scheduled by DCI, the information of the second SRI field is not used for any PUSCH transmission, where the second SRI field is the SRI field other than the first SRI field among the at least two SRI fields.

[0337] Optionally, the processor 1180 is further configured to, if the first SRI field is used for all PUSCH retransmissions scheduled by DCI and the DCI contains at least two TPC commands, use the first TPC command for all PUSCH retransmissions scheduled by DCI, where the first TPC command is the TPC command associated with the first SRI field among the at least two TPC fields;

[0338] Optionally, the k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where k is a positive integer;

[0339] Or,

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

[0341] Optionally, the second TPC command in the at least two TPC fields is not used for power control of any PUSCH transmission,

[0342] Or,

[0343] The second TPC command in the at least two TPC fields is used for power accumulation in the second closed-loop power adjustment state, where the second closed-loop power adjustment state is the closed-loop power adjustment state determined according to the information indicated by the second SRI field;

[0344] Where the second TPC command is the TPC command other than the first TPC command among the at least two TPC commands, and the second SRI field is the SRI field other than the first SRI field among the at least two SRI fields.

[0345] Optionally, the processor 1180 is further configured to, if at least two SRI fields are used for different PUSCH retransmissions scheduled by DCI respectively and the DCI contains at least two TPC commands, use the at least two TPC commands for different PUSCH retransmissions scheduled by DCI respectively.

[0346] Optionally, each TPC command in the at least two TPC commands is indicated by a different TPC field in the DCI;

[0347] or,

[0348] At least two TPC commands are indicated through the same TPC field in the DCI.

[0349] Optionally, the first SRI field includes one of the following:

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

[0351] The SRI domain that indicates the fewest SRS resources among at least two SRI domains;

[0352] The SRI domain that indicates the most SRS resources among at least two SRI domains;

[0353] At least two SRI fields indicate a single SRS resource;

[0354] At least two SRI fields indicate multiple SRS resources;

[0355] At least two SRI fields indicate m SRS resources, where m is an integer greater than or equal to 1;

[0356] SRI domains selected from at least two SRI domains.

[0357] Optionally, the SRI fields selected from at least two SRI fields include:

[0358] The SRI domain is randomly selected from at least two SRI domains;

[0359] or,

[0360] The SRI field is selected from at least two SRI fields based on channel reciprocity and downlink channel information.

[0361] For example, such as Figure 12 As shown, the network device in this embodiment of the invention can be a base station, which includes:

[0362] Transmitter 1201 is used to send a DCI for scheduling repeated PUSCH transmissions to the terminal device. The DCI includes at least two SRI fields, each SRI field indicating at least one SRS resource.

[0363] The terminal device is instructed to use at least two SRI fields for DCI-scheduled PUSCH retransmissions, based on the information indicated by at least two SRI fields.

[0364] Optionally, by using the information indicated by at least two SRI fields, the terminal device is instructed to use at least two SRI fields for repeated transmission of PUSCH scheduled by DCI, including: using the information indicated by at least two SRI fields to instruct the terminal device to use at least two SRI fields respectively for repeated transmission of different PUSCH scheduled by DCI, or instructing the terminal device to use the first SRI field of at least two SRI fields for repeated transmission of all PUSCH scheduled by DCI.

[0365] Optionally, PUSCH retransmission is a codebook-based transmission;

[0366] If at least one of the two SRI fields indicates a specific value, the terminal device is instructed to use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI.

[0367] or,

[0368] If at least two SRI fields indicate non-specific values, the terminal device is instructed to use at least two SRI fields for different PUSCH retransmissions scheduled by DCI.

[0369] Optionally, the specific value is pre-agreed upon by the terminal device and the network device;

[0370] or,

[0371] Specific values ​​are pre-configured by network devices.

[0372] Optionally, PUSCH retransmission is a non-codebook-based transmission;

[0373] If at least two SRI fields indicate different numbers of SRS resources, then instruct the terminal device to use the first SRI field for all PUSCH duplicate transmissions scheduled by DCI.

[0374] If at least two SRI fields indicate the same number of SRS resources, then the terminal device is instructed to use at least two SRI fields for different PUSCH retransmissions scheduled by DCI.

[0375] Optionally, if the information in the first SRI field is used for all PUSCH repetitions scheduled by DCI, then the information in the second SRI field is not used for any PUSCH transmission, and the second SRI field is an SRI field other than the first SRI field among at least two SRI fields.

[0376] Optionally, if the first SRI field is used for all PUSCH repetitive transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the first TPC command is used for all PUSCH repetitive transmissions scheduled by the DCI, and the first TPC command is the TPC command associated with the first SRI field among the at least two TPC fields.

[0377] Optionally, the k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where k is a positive integer;

[0378] or,

[0379] 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.

[0380] Optional,

[0381] The second TPC command in at least two TPC domains is not used for power control of any PUSCH transmission.

[0382] or,

[0383] The second TPC command in at least two TPC fields is used for power accumulation in the second closed-loop power adjustment state, which is the closed-loop power adjustment state determined according to the information indicated by the second SRI field.

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

[0385] Optionally, if at least two SRI fields are used for different PUSCH repetitions scheduled by the DCI, and the DCI contains at least two TPC commands, then the at least two TPC commands are used for different PUSCH repetitions scheduled by the DCI.

[0386] Optionally, each of the at least two TPC commands may be indicated through a different TPC field in the DCI;

[0387] or,

[0388] At least two TPC commands are indicated through the same TPC field in the DCI.

[0389] Optionally, the first SRI field includes one of the following:

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

[0391] The SRI domain that indicates the fewest SRS resources among at least two SRI domains;

[0392] The SRI domain that indicates the most SRS resources among at least two SRI domains;

[0393] At least two SRI fields indicate a single SRS resource;

[0394] At least two SRI fields indicate multiple SRS resources;

[0395] At least two SRI fields indicate m SRS resources, where m is an integer greater than or equal to 1;

[0396] SRI domains selected from at least two SRI domains.

[0397] Optionally, the SRI fields selected from at least two SRI fields include:

[0398] The SRI domain is randomly selected from at least two SRI domains;

[0399] or,

[0400] The SRI field is selected from at least two SRI fields based on channel reciprocity and downlink channel information.

[0401] This invention also provides a computer-readable storage medium, including: computer instructions, which, when executed on a computer, cause the computer to perform various processes of the terminal device as described in the above method embodiments.

[0402] This invention also provides a computer-readable storage medium, including: computer instructions that, when executed on a computer, cause the computer to perform various processes of the network device as described in the above method embodiments.

[0403] This invention also provides a computer program product, including computer instructions. When the computer program product is run on a computer, the computer executes the computer instructions, causing the computer to perform various processes of the terminal device as described in the above method embodiments.

[0404] This invention also provides a computer program product, including computer instructions. When the computer program product is run on a computer, the computer executes the computer instructions, causing the computer to perform various processes of the network device as described in the above method embodiments.

[0405] This invention also provides a chip coupled to a memory in a terminal device, such that the chip calls program instructions stored in the memory during operation, enabling the terminal device to execute various processes as described in the above method embodiments.

[0406] This invention also provides a chip coupled to a memory in a network device, such that the chip calls program instructions stored in the memory during operation, enabling the network device to execute various processes of the network device as described in the above method embodiments.

[0407] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as 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, all or part of the flow or function according to the embodiments of the present invention is generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can store or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., a solid-state disk (SSD)).

[0408] The terms “first,” “second,” “third,” “fourth,” etc. (if present) in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

Claims

1. A method for repeated PUSCH transmission, characterized in that, include: The network device receives downlink control information (DCI) sent by the network device. The DCI is used to schedule repeated transmissions of the Physical Uplink Shared Channel (PUSCH). The DCI includes at least two Probe Reference Signal Resource Indication (SRI) fields, each of which is used to indicate at least one Probe Reference Signal Resource (SRS) resource. Based on the information indicated by the at least two SRI fields, it is determined that the at least two SRI fields will be used for the PUSCH retransmission scheduled by the DCI. The step of determining, based on the information indicated by the at least two SRI fields, to use the at least two SRI fields for the PUSCH retransmission scheduled by the DCI includes: Based on the information indicated by the at least two SRI fields, determine whether to use the at least two SRI fields for different PUSCH repetitions scheduled by the DCI, or to use the first SRI field of the at least two SRI fields for all PUSCH repetitions scheduled by the DCI. Wherein, if the PUSCH repetition transmission is a codebook-based transmission, then based on 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 repetition transmissions scheduled by the DCI, or to use the first SRI field of the at least two SRI fields for all PUSCH repetition transmissions scheduled by the DCI, including: If at least one of the at least two SRI fields indicates a specific value, then the first SRI field is used for all PUSCH duplicate transmissions scheduled by the DCI. If the at least two SRI fields indicate non-specific values, then the at least two SRI fields are used for different PUSCH repetition transmissions scheduled by the DCI.

2. The method according to claim 1, characterized in that, The specific value is agreed upon in advance between the terminal device and the network device; or, The specific value is pre-configured by the network device.

3. The method according to claim 1, characterized in that, If the PUSCH retransmission is a non-codebook-based transmission, then based on 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 retransmissions scheduled by the DCI, or to use the first SRI field of the at least two SRI fields for all PUSCH retransmissions scheduled by the DCI, including: If at least two SRI fields indicate different numbers of SRS resources, then the first SRI field is used for all PUSCH duplicate transmissions scheduled by the DCI. If the at least two SRI fields indicate the same number of SRS resources, then the at least two SRI fields are used for different PUSCH retransmissions scheduled by the DCI.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: If the information in the first SRI field is used for all PUSCH repetitive transmissions scheduled by the DCI, then the information in the second SRI field is not used for any PUSCH transmission. The second SRI field is the SRI field other than the first SRI field among the at least two SRI fields.

5. The method according to any one of claims 1 to 3, characterized in that, The method further includes: If the first SRI domain is used for all PUSCH repetitive transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the first TPC command is used for all PUSCH repetitive transmissions scheduled by the DCI, and the first TPC command is the TPC command associated with the first SRI domain among the at least two TPC domains.

6. The method according to claim 5, characterized in that, The k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where 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.

7. The method according to claim 5, characterized in that, The second TPC command in at least two TPC domains is not used for power control of any PUSCH transmission. or, The second TPC command in the at least two TPC fields is used for power accumulation in the second closed-loop power adjustment state, which is a closed-loop power adjustment state determined according to the information indicated by the second SRI field. 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.

8. The method according to any one of claims 1 to 3, characterized in that, The method further includes: If the at least two SRI fields are used for different PUSCH repeat transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the at least two TPC commands are used for different PUSCH repeat transmissions scheduled by the DCI.

9. The method according to claim 5, characterized in that, Each of the at least two TPC commands is indicated through a different TPC field in the DCI; or, The at least two TPC commands are indicated through the same TPC field in the DCI.

10. The method according to any one of claims 1 to 3, characterized in that, 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 domain that indicates the fewest SRS resources among the at least two SRI domains; The SRI domain that indicates the largest number of SRS resources among the at least two SRI domains. The SRI field that indicates a single SRS resource among the at least two SRI fields; The at least two SRI fields indicate SRI fields for multiple SRS resources; The at least two SRI fields indicate the SRI fields of m SRS resources, where m is an integer greater than or equal to 1; The SRI field selected from the at least two SRI fields.

11. The method according to claim 10, characterized in that, The SRI fields selected from the at least two SRI fields include: An SRI field randomly selected from the at least two SRI fields; or, The SRI field selected from the at least two SRI fields based on channel reciprocity and downlink channel information.

12. A method for repeated PUSCH transmission, characterized in that, include: The network device sends downlink control information (DCI) to the terminal device. The DCI is used to schedule repeated transmissions of the Physical Uplink Shared Channel (PUSCH). The DCI includes at least two sounding reference signal resource indication (SRI) fields, and each SRI field is used to indicate at least one sounding reference signal (SRS) resource. The terminal device is instructed to use the information indicated by the at least two SRI fields for repeated transmission of PUSCH in the DCI scheduling; The step of instructing the terminal device to use the at least two SRI fields for PUSCH retransmission scheduled by the DCI, through the information indicated by the at least two SRI fields, includes: The information indicated by the at least two SRI fields indicates whether the terminal device should use the at least two SRI fields for different PUSCH retransmissions scheduled by the DCI, or whether the terminal device should use the first SRI field of the at least two SRI fields for all PUSCH retransmissions scheduled by the DCI. Wherein, if the PUSCH repetition transmission is a codebook-based transmission; then the step of instructing the terminal device, through the information indicated by the at least two SRI fields, to use the at least two SRI fields respectively for different PUSCH repetition transmissions scheduled by the DCI, or instructing the terminal device to use the first SRI field of the at least two SRI fields for all PUSCH repetition transmissions scheduled by the DCI, includes: If at least one of the at least two SRI fields indicates a specific value, the terminal device is instructed to use the first SRI field for all PUSCH duplicate transmissions 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 retransmissions scheduled by the DCI.

13. The method according to claim 12, characterized in that, The specific value is agreed upon in advance between the terminal device and the network device; or, The specific value is pre-configured by the network device.

14. The method according to claim 12, characterized in that, If the PUSCH retransmission is a non-codebook-based transmission, then the information indicated by the at least two SRI fields indicates whether the terminal device should use the at least two SRI fields for different PUSCH retransmissions scheduled by the DCI, or whether the terminal device should use the first SRI field of the at least two SRI fields for all PUSCH retransmissions scheduled by the DCI, including: If at least two SRIs in the at least two SRI fields indicate different numbers of SRS resources, then the terminal device is instructed to use the first SRI field for all PUSCH duplicate transmissions scheduled by the DCI. If at least two SRI fields indicate the same number of SRS resources, then the terminal device is instructed to use the at least two SRI fields for different PUSCH retransmissions scheduled by the DCI.

15. The method according to any one of claims 12 to 14, characterized in that, If the information in the first SRI field is used for all PUSCH repetitive transmissions scheduled by the DCI, then the information in the second SRI field is not used for any PUSCH transmission. The second SRI field is the SRI field other than the first SRI field among the at least two SRI fields.

16. The method according to any one of claims 12 to 14, characterized in that, If the first SRI domain is used for all PUSCH repetitive transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the first TPC command is used for all PUSCH repetitive transmissions scheduled by the DCI, and the first TPC command is the TPC command associated with the first SRI domain among the at least two TPC domains.

17. The method according to claim 16, characterized in that, The k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where 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.

18. The method according to claim 16, characterized in that, The second TPC command in at least two TPC domains is not used for power control of any PUSCH transmission. or, The second TPC command in the at least two TPC fields is used for power accumulation in the second closed-loop power adjustment state, which is a closed-loop power adjustment state determined according to the information indicated by the second SRI field. 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.

19. The method according to any one of claims 12 to 14, characterized in that, If the at least two SRI fields are used for different PUSCH repetition transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the at least two TPC commands are used for different PUSCH repetition transmissions scheduled by the DCI.

20. The method according to claim 16, characterized in that, Each of the at least two TPC commands is indicated through a different TPC field in the DCI; or, The at least two TPC commands are indicated through the same TPC field in the DCI.

21. The method according to any one of claims 12 to 14, characterized in that, 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 domain that indicates the fewest SRS resources among the at least two SRI domains; The SRI domain that indicates the largest number of SRS resources among the at least two SRI domains. The SRI field that indicates a single SRS resource among the at least two SRI fields; The at least two SRI fields indicate SRI fields for multiple SRS resources; The at least two SRI fields indicate the SRI fields of m SRS resources, where m is an integer greater than or equal to 1; The SRI field selected from the at least two SRI fields.

22. The method according to claim 21, characterized in that, The SRI fields selected from the at least two SRI fields include: An SRI field randomly selected from the at least two SRI fields; or, The SRI field selected from the at least two SRI fields based on channel reciprocity and downlink channel information.

23. A terminal device, characterized in that, include: The receiving module is used to receive downlink control information (DCI) sent by the network device. The DCI is used to schedule repeated transmissions of the Physical Uplink Shared Channel (PUSCH). The DCI includes at least two Probe Reference Signal Resource Indication (SRI) fields, and each SRI field is used to indicate at least one Probe Reference Signal Resource (SRS) resource. The processing module is configured to determine, based on the information indicated by the at least two SRI fields, whether to use the at least two SRI fields for repeated transmission of PUSCHs scheduled by the DCI; specifically, the processing module is configured to determine, based on 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 all PUSCHs scheduled by the DCI. Wherein, the PUSCH repetition transmission is a codebook-based transmission; The processing module is specifically configured to use the first SRI field for all PUSCH retransmissions 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 for different PUSCH retransmissions scheduled by the DCI if the at least two SRI fields indicate non-specific values.

24. The terminal device according to claim 23, characterized in that, The specific value is agreed upon in advance between the terminal device and the network device; or, The specific value is pre-configured by the network device.

25. The terminal device according to claim 23, characterized in that, The PUSCH repetition transmission is a non-codebook-based transmission; The processing module is specifically configured to, if at least two SRIs in the at least two SRIs indicate different numbers of SRS resources, use the first SRI for repeated transmission of all PUSCHs scheduled by the DCI. The processing module is specifically configured to use the at least two SRI fields for different PUSCH retransmissions scheduled by the DCI if the at least two SRI fields indicate the same number of SRS resources.

26. The terminal device according to any one of claims 23 to 25, characterized in that, The processing module is further configured to, if the information of the first SRI field is used for all PUSCH repetitive transmissions scheduled by the DCI, then the information of the second SRI field is not used for any PUSCH transmission, wherein the second SRI field is an SRI field other than the first SRI field among the at least two SRI fields.

27. The terminal device according to any one of claims 23 to 25, characterized in that, The processing module is further configured to, if the first SRI domain is used for all PUSCH repetitive transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, use the first TPC command for all PUSCH repetitive transmissions scheduled by the DCI, wherein the first TPC command is a TPC command associated with the first SRI domain among the at least two TPC domains.

28. The terminal device according to claim 27, characterized in that, The k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where 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.

29. The terminal device according to claim 27, characterized in that, The second TPC command in at least two TPC domains is not used for power control of any PUSCH transmission. or, The second TPC command in the at least two TPC fields is used for power accumulation in the second closed-loop power adjustment state, which is a closed-loop power adjustment state determined according to the information indicated by the second SRI field. 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.

30. The terminal device according to any one of claims 23 to 25, characterized in that, The processing module is further configured to, if the at least two SRI fields are respectively used for different PUSCH repeat transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then use the at least two TPC commands respectively for different PUSCH repeat transmissions scheduled by the DCI.

31. The terminal device according to claim 27, characterized in that, Each of the at least two TPC commands is indicated through a different TPC field in the DCI; or, The at least two TPC commands are indicated through the same TPC field in the DCI.

32. The terminal device according to any one of claims 23 to 25, characterized in that, 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 domain that indicates the fewest SRS resources among the at least two SRI domains; The SRI domain that indicates the largest number of SRS resources among the at least two SRI domains. The SRI field that indicates a single SRS resource among the at least two SRI fields; The at least two SRI fields indicate SRI fields for multiple SRS resources; The at least two SRI fields indicate the SRI fields of m SRS resources, where m is an integer greater than or equal to 1; The SRI field selected from the at least two SRI fields.

33. The terminal device according to claim 32, characterized in that, The SRI fields selected from the at least two SRI fields include: An SRI field randomly selected from the at least two SRI fields; or, The SRI field selected from the at least two SRI fields based on channel reciprocity and downlink channel information.

34. A network device, characterized in that, include: The transmitting module is used to send downlink control information (DCI) to the terminal device. The DCI is used to schedule repeated transmissions of the physical uplink shared channel (PUSCH). The DCI includes at least two sounding reference signal resource indication (SRI) fields, and each SRI field is used to indicate at least one sounding reference signal (SRS) resource. The terminal device is instructed to use the information indicated by the at least two SRI fields for repeated transmission of PUSCH in the DCI scheduling; Specifically, the information indicated by the at least two SRI fields can be used to instruct the terminal device to use the at least two SRI fields for different PUSCH repetitions 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 repetitions scheduled by the DCI. Wherein, the PUSCH repetition transmission is a codebook-based transmission; If at least one of the at least two SRI fields indicates a specific value, the terminal device is instructed to use the first SRI field for all PUSCH duplicate transmissions 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 retransmissions scheduled by the DCI.

35. The network device according to claim 34, characterized in that, The specific value is agreed upon in advance between the terminal device and the network device; or, The specific value is pre-configured by the network device.

36. The network device according to claim 34, characterized in that, The PUSCH repetition transmission is a non-codebook-based transmission; If at least two SRIs in the at least two SRI fields indicate different numbers of SRS resources, then the terminal device is instructed to use the first SRI field for all PUSCH duplicate transmissions scheduled by the DCI. If the at least two SRI fields indicate the same number of SRS resources, then the terminal device is instructed to use the at least two SRI fields respectively for different PUSCH retransmissions scheduled by the DCI.

37. The network device according to any one of claims 34 to 36, characterized in that, If the information in the first SRI field is used for all PUSCH repetitive transmissions scheduled by the DCI, then the information in the second SRI field is not used for any PUSCH transmission. The second SRI field is the SRI field other than the first SRI field among the at least two SRI fields.

38. The network device according to any one of claims 34 to 36, characterized in that, If the first SRI domain is used for all PUSCH repetitive transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the first TPC command is used for all PUSCH repetitive transmissions scheduled by the DCI, and the first TPC command is the TPC command associated with the first SRI domain among the at least two TPC domains.

39. The network device according to claim 38, characterized in that, The k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where 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.

40. The network device according to claim 38, characterized in that, The second TPC command in at least two TPC domains is not used for power control of any PUSCH transmission. or, The second TPC command in the at least two TPC fields is used for power accumulation in the second closed-loop power adjustment state, which is a closed-loop power adjustment state determined according to the information indicated by the second SRI field. 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.

41. The network device according to any one of claims 34 to 36, characterized in that, If the at least two SRI fields are used for different PUSCH repeat transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the at least two TPC commands are used for different PUSCH repeat transmissions scheduled by the DCI.

42. The network device according to claim 38, characterized in that, Each of the at least two TPC commands is indicated through a different TPC field in the DCI; or, The at least two TPC commands are indicated through the same TPC field in the DCI.

43. The network device according to any one of claims 34 to 36, characterized in that, 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 domain that indicates the fewest SRS resources among the at least two SRI domains; The SRI domain that indicates the largest number of SRS resources among the at least two SRI domains. The SRI field that indicates a single SRS resource among the at least two SRI fields; The at least two SRI fields indicate SRI fields for multiple SRS resources; The at least two SRI fields indicate the SRI fields of m SRS resources, where m is an integer greater than or equal to 1; The SRI field selected from the at least two SRI fields.

44. The network device according to claim 43, characterized in that, The SRI fields selected from the at least two SRI fields include: An SRI field randomly selected from the at least two SRI fields; or, The SRI field selected from the at least two SRI fields based on channel reciprocity and downlink channel information.

45. A terminal device, characterized in that, include: A receiver is used to receive downlink control information (DCI) sent by a network device. The DCI is used to schedule repeated transmissions of the Physical Uplink Shared Channel (PUSCH). The DCI includes at least two Probe Reference Signal Resource Indication (SRI) fields, each SRI field indicating at least one Probe Reference Signal Resource (SRS) resource. A processor is configured to determine, based on information indicated by the at least two SRI fields, to use the at least two SRI fields for PUSCH retransmissions scheduled by the DCI. Specifically, the processor is configured to determine, based on the information indicated by the at least two SRI fields, whether to use the at least two SRI fields for different PUSCH repetitions scheduled by the DCI, or to use the first SRI field of the at least two SRI fields for all PUSCH repetitions scheduled by the DCI. Wherein, the PUSCH repetition transmission is a codebook-based transmission; The processor is specifically configured to use the first SRI field for all PUSCH retransmissions scheduled by the DCI if at least one of the at least two SRI fields indicates a specific value. The processor is specifically configured to use the at least two SRI fields for different PUSCH retransmissions of the DCI schedule if the at least two SRI fields indicate non-specific values.

46. ​​The terminal device according to claim 45, characterized in that, The specific value is agreed upon in advance between the terminal device and the network device; or, The specific value is pre-configured by the network device.

47. The terminal device according to claim 45, characterized in that, The PUSCH repetition transmission is a non-codebook-based transmission; The processor is specifically configured to use the first SRI domain for all PUSCH duplicate transmissions of the DCI schedule if at least two SRI domains indicate different numbers of SRS resources. The processor is specifically configured to use the at least two SRI fields for different PUSCH repeat transmissions scheduled by the DCI if the at least two SRI fields indicate the same number of SRS resources.

48. The terminal device according to any one of claims 45 to 47, characterized in that, The processor is further configured to, if the information of the first SRI field is used for all PUSCH repetitive transmissions scheduled by the DCI, then the information of the second SRI field is not used for any PUSCH transmission, wherein the second SRI field is an SRI field other than the first SRI field among the at least two SRI fields.

49. The terminal device according to any one of claims 45 to 47, characterized in that, The processor is further configured to, if the first SRI domain is used for all PUSCH repetitive transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, use the first TPC command for all PUSCH repetitive transmissions scheduled by the DCI, wherein the first TPC command is a TPC command associated with the first SRI domain among the at least two TPC domains.

50. The terminal device according to claim 49, characterized in that, The k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where 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.

51. The terminal device according to claim 49, characterized in that, The second TPC command in at least two TPC domains is not used for power control of any PUSCH transmission. or, The second TPC command in the at least two TPC fields is used for power accumulation in the second closed-loop power adjustment state, which is a closed-loop power adjustment state determined according to the information indicated by the second SRI field. 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.

52. The terminal device according to any one of claims 45 to 47, characterized in that, The processor is further configured to, if the at least two SRI domains are respectively used for different PUSCH repeat transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then use the at least two TPC commands respectively for different PUSCH repeat transmissions scheduled by the DCI.

53. The terminal device according to claim 49, characterized in that, Each of the at least two TPC commands is indicated through a different TPC field in the DCI; or, The at least two TPC commands are indicated through the same TPC field in the DCI.

54. The terminal device according to any one of claims 45 to 47, characterized in that, 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 domain that indicates the fewest SRS resources among the at least two SRI domains; The SRI domain that indicates the largest number of SRS resources among the at least two SRI domains. The SRI field that indicates a single SRS resource among the at least two SRI fields; The at least two SRI fields indicate SRI fields for multiple SRS resources; The at least two SRI fields indicate the SRI fields of m SRS resources, where m is an integer greater than or equal to 1; The SRI field selected from the at least two SRI fields.

55. The terminal device according to claim 54, characterized in that, The SRI fields selected from the at least two SRI fields include: An SRI field randomly selected from the at least two SRI fields; or, The SRI field selected from the at least two SRI fields based on channel reciprocity and downlink channel information.

56. A network device, characterized in that, include: A transmitter is used to send downlink control information (DCI) to a terminal device. The DCI is used to schedule repeated transmissions of the physical uplink shared channel (PUSCH). The DCI includes at least two sounding reference signal resource indication (SRI) fields, each SRI field being used to indicate at least one sounding reference signal (SRS) resource. The terminal device is instructed to use the information indicated by the at least two SRI fields for repeated transmission of PUSCH in the DCI scheduling; The step of instructing the terminal device to use the at least two SRI fields for PUSCH retransmission scheduled by the DCI, through the information indicated by the at least two SRI fields, includes: The information indicated by the at least two SRI fields indicates whether the terminal device should use the at least two SRI fields for different PUSCH retransmissions scheduled by the DCI, or whether the terminal device should use the first SRI field of the at least two SRI fields for all PUSCH retransmissions scheduled by the DCI. Wherein, the PUSCH repetition transmission is a codebook-based transmission; If at least one of the at least two SRI fields indicates a specific value, the terminal device is instructed to use the first SRI field for all PUSCH duplicate transmissions 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 retransmissions scheduled by the DCI.

57. The network device according to claim 56, characterized in that, The specific value is agreed upon in advance between the terminal device and the network device; or, The specific value is pre-configured by the network device.

58. The network device according to claim 56, characterized in that, The PUSCH repetition transmission is a non-codebook-based transmission; If at least two SRIs in the at least two SRI fields indicate different numbers of SRS resources, then the terminal device is instructed to use the first SRI field for all PUSCH duplicate transmissions scheduled by the DCI. If at least two SRI fields indicate the same number of SRS resources, then the terminal device is instructed to use the at least two SRI fields for different PUSCH retransmissions scheduled by the DCI.

59. The network device according to any one of claims 56 to 58, characterized in that, If the information in the first SRI field is used for all PUSCH repetitive transmissions scheduled by the DCI, then the information in the second SRI field is not used for any PUSCH transmission. The second SRI field is the SRI field other than the first SRI field among the at least two SRI fields.

60. The network device according to any one of claims 56 to 58, characterized in that, If the first SRI domain is used for all PUSCH repetitive transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the first TPC command is used for all PUSCH repetitive transmissions scheduled by the DCI, and the first TPC command is the TPC command associated with the first SRI domain among the at least two TPC domains.

61. The network device according to claim 60, characterized in that, The k-th SRI field in the DCI is associated with the k-th TPC command in the DCI, where 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.

62. The network device according to claim 60, characterized in that, The second TPC command in at least two TPC domains is not used for power control of any PUSCH transmission. or, The second TPC command in the at least two TPC fields is used for power accumulation in the second closed-loop power adjustment state, which is a closed-loop power adjustment state determined according to the information indicated by the second SRI field. 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.

63. The network device according to any one of claims 56 to 58, characterized in that, If the at least two SRI fields are used for different PUSCH repeat transmissions scheduled by the DCI, and the DCI contains at least two TPC commands, then the at least two TPC commands are used for different PUSCH repeat transmissions scheduled by the DCI.

64. The network device according to claim 60, characterized in that, Each of the at least two TPC commands is indicated through a different TPC field in the DCI; or, The at least two TPC commands are indicated through the same TPC field in the DCI.

65. The network device according to any one of claims 56 to 58, characterized in that, 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 domain that indicates the fewest SRS resources among the at least two SRI domains; The SRI domain that indicates the largest number of SRS resources among the at least two SRI domains. The SRI field that indicates a single SRS resource among the at least two SRI fields; The at least two SRI fields indicate SRI fields for multiple SRS resources; The at least two SRI fields indicate the SRI fields of m SRS resources, where m is an integer greater than or equal to 1; The SRI field selected from the at least two SRI fields.

66. The network device according to claim 65, characterized in that, The SRI fields selected from the at least two SRI fields include: An SRI field randomly selected from the at least two SRI fields; or, The SRI field selected from the at least two SRI fields based on channel reciprocity and downlink channel information.

67. A computer-readable storage medium comprising: Computer instructions, when executed on a computer, cause the computer to perform the method as described in any one of claims 1 to 11, or the method as described in any one of claims 12 to 22.

Images