CN116326100A

CN116326100A - PUSCH repeated transmission method, terminal equipment and network equipment

Info

Publication number: CN116326100A
Application number: CN202180071939.5A
Authority: CN
Inventors: 陈文洪; 方昀
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2021-03-01
Filing date: 2021-03-01
Publication date: 2023-06-23
Also published as: WO2022183347A1

Abstract

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

Description

PUSCH repeated transmission method, terminal equipment and network equipment

Technical Field

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

Background

In order to improve the transmission reliability of the physical uplink shared channel (Physical Uplink Shared Channel, PUSCH), new Radio (NR) introduces PUSCH retransmission, and one downlink control information (Downlink Control Information, DCI) may schedule multiple PUSCHs to be transmitted on multiple consecutive slots or multiple orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM) symbols. The DCI currently scheduling PUSCH retransmission may include two SRI fields for determining a beam and/or a precoding matrix for PUSCH retransmission addressed to different transmission nodes (Transmission Reception Point, TRP), respectively. However, if the channel between one TRP and the terminal is poor, the repeated transmission to the TRP is difficult to be received by the corresponding TRP, which causes waste of resources and power and poor uplink transmission performance, so how to achieve flexible switching between PUSCH repeated transmission based on a single TRP and PUSCH repeated transmission based on multiple TRPs to improve uplink transmission performance is a problem to be solved.

Disclosure of Invention

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

In a first aspect, a PUSCH retransmission method is provided, including:

receiving DCI sent by network equipment, wherein the DCI is used for scheduling PUSCH repeated transmission, and comprises at least two SRI domains, and 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 the PUSCH repeated transmission scheduled by the DCI according to the information indicated by the at least two SRI domains.

In a second aspect, a PUSCH retransmission method is provided, including:

transmitting DCI to terminal equipment, wherein the DCI is used for scheduling PUSCH repeated transmission, and comprises at least two SRI domains, and each SRI domain is used for indicating at least one SRS resource;

and indicating the terminal equipment to use the at least two SRI domains for the PUSCH repeated transmission scheduled by the DCI through the information indicated by the at least two SRI domains.

In a third aspect, there is provided a terminal device comprising:

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

And the processing module is used for determining that the at least two SRI domains are used for the PUSCH repeated transmission scheduled by the DCI according to the information indicated by the at least two SRI domains.

In a fourth aspect, there is provided a network device comprising:

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

and the processing module is used for indicating the terminal equipment to use the at least two SRI domains for the PUSCH repeated transmission scheduled by the DCI through the information indicated by the at least two SRI domains.

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

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

and the processor is used for determining that the at least two SRI domains are used for the PUSCH repeated transmission scheduled by the DCI according to the information indicated by the at least two SRI domains.

In a sixth aspect, there is provided a network device comprising:

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

And the processor is used for indicating the terminal equipment to use the at least two SRI domains for the PUSCH repeated transmission scheduled by the DCI through the information indicated by the at least two SRI domains.

In a seventh aspect, there is provided a computer readable storage medium comprising: computer instructions which, when run on a computer, cause the computer to perform the method of or the method of any of the alternative implementations of the first aspect or the second aspect described above.

In an eighth aspect, there is provided a computer program product comprising computer instructions which, when run on a computer, cause the computer to perform the method of any of the alternative implementations of the first aspect or the second aspect as described above, or to perform the method of any of the alternative implementations of the second aspect or the second aspect as described above.

In a ninth aspect, there is provided a chip coupled to a memory in a terminal device, such that the chip, when run, invokes program instructions stored in the memory, such that the terminal device performs the method as described above for the first aspect or any of the alternative implementations of the first aspect, or such that the network device performs the method as described above for the second aspect or any of the alternative implementations of the second aspect.

In the embodiment of the invention, the terminal equipment can receive downlink control information DCI which is sent by the network equipment and is used for scheduling the repeated transmission of the PUSCH, wherein the DCI comprises at least two SRI domains, and each SRI domain is used for indicating at least one SRS resource; and determining that at least two SRI domains are used for the PUSCH repeated transmission scheduled by the DCI according to the information indicated by the at least two SRI domains, and providing an uplink transmission mode for using the at least two SRI domains for the PUSCH repeated transmission.

Further, the terminal device may determine, according to the information indicated by the at least two SRI domains, whether to use the at least two SRI domains for different PUSCH retransmission for DCI scheduling, respectively, or use a first SRI domain of the at least two SRI domains for all PUSCH retransmission for DCI scheduling. In this way, the terminal device can switch between the repeated transmission mode of using at least two SRI domains for different PUSCH repeated transmission of DCI scheduling respectively and the repeated transmission mode of using the first SRI domain of at least two SRI domains for all PUSCH repeated transmission of DCI scheduling according to the information indicated by at least two SRI domains in DCI in time, and even if the TRP channel corresponding to a certain SRI domain is degraded in the transmission process, the terminal device can support the switching between a single TRP transmission (using a single SRI domain) and multiple TRP transmissions (using multiple SRI domains) through the indication in the DCI of the network device, so that the uplink transmission performance can be improved.

Drawings

Fig. 1 is a schematic diagram of PUSCH transmission based on a codebook according to an embodiment of the present invention;

fig. 2 is a schematic diagram of PUSCH transmission based on a non-codebook according to an embodiment of the present invention;

fig. 3 is a schematic diagram of PUSCH retransmission based on a slot according to an embodiment of the present invention;

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

fig. 5 is a schematic diagram of PUSCH retransmission based on multiple TRP and multiple Panel according to an embodiment of the present invention;

fig. 6 is a schematic diagram of PUSCH retransmission based on multiple TRP according to an embodiment of the present invention;

fig. 7 is a system architecture diagram of a communication system according to an embodiment of the present invention;

fig. 8 is a schematic diagram of a PUSCH retransmission method according to an embodiment of the present invention;

fig. 9A is a schematic diagram of PUSCH retransmission based on multiple SRI fields according to an embodiment of the present invention;

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

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

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

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

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

Detailed Description

The following description of the technical solutions according to the embodiments of the present invention will be given with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to fall within the scope of the invention.

In embodiments of the invention, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "e.g." in an embodiment should not be taken as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

The term "and/or" is herein merely an association relationship describing an associated object, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. The symbol "/" herein indicates that the associated object is or is a relationship, e.g., A/B indicates A or B.

The related art relating to the embodiments of the present invention will be described below:

uplink codebook transmission and non-codebook transmission

When the terminal device transmits uplink data (PUSCH), precoding processing needs to be performed on the uplink data to obtain uplink precoding gain. The precoding process is generally divided into two parts: analog domain processing and digital domain processing. The analog domain processes the transmitted analog signals, and generally adopts a wave beam forming mode to map the radio frequency signals to the physical antennas; the digital domain processing is generally performed on a baseband for digital signals, and a precoding matrix is adopted to precode the digital signals, so that data of a transmission layer is mapped to a radio frequency port. Because of the limited number of radio frequency channels of the terminal device, two processing modes are generally adopted at the same time, namely, the digital signal is precoded, and then the analog signal is shaped by adopting wave beams.

The PUSCH transmission may be classified into codebook-based transmission and non-codebook-based transmission according to the above-described precoding scheme.

In the uplink precoding manner based on the codebook, a network side (network device) configures an SRS resource set dedicated for codebook transmission for a terminal device, as shown in fig. 1, which is a PUSCH transmission schematic diagram based on the codebook, the terminal device (UE in fig. 1) sends SRS on a plurality of sounding reference signals (Sounding Reference Signal, SRS) resources in the SRS resource set, where the SRS on each SRS resource adopts different beams, the network side (gNB in fig. 1) selects the best SRS resource from the SRS resources to obtain uplink channel state information (Channel State Information, CSI), and the network side indicates a resource index to the terminal device through an SRS resource indication (SRS Resource Indicator, SRI) domain by using downlink control information (Downlink Control Information, DCI), so that the terminal device adopts the corresponding beam of the SRS resource to perform analog beamforming on data. The network side may also indicate a Rank Indication (RI), a precoding matrix indication (Precoding Matrix Indicator, PMI), and a modulation and coding strategy (Modulation and Coding Scheme, MCS) through DCI, so that the terminal device may determine the number of transmission layers and the precoding matrix from the codebook according to the RI and the PMI, and send the precoding data and the demodulation reference signal (Demodulation Reference Signal, DMRS) to the terminal device.

For some terminal devices supporting reciprocity of uplink and downlink channels, a precoding mode based on a non-codebook can be supported. As shown in fig. 2, a PUSCH transmission schematic diagram based on a non-codebook is shown, where a terminal device (UE in fig. 2) may use downlink channel information to obtain uplink channel information, so as to perform uplink analog beamforming and/or digital precoding, and at this time, a network side (network device, gNB in fig. 2) does not need to indicate related information of a precoding matrix any more, so that the cost of DCI can be reduced. Specifically, the network side first sends a CSI resource indicator (CSI Resource Indicator, CSI-RS), so that the terminal device determines beams and precoding matrices of N layers (layers) based on the CSI-RS. The terminal device employs the N layer beams and the precoding matrix to transmit N single-port SRS resources (i.e., N SRS ports) configured as one SRS resource set for non-codebook transmission. The network side receives SRS resources and then measures the SRS resources, selects the best K SRS resources and indicates the corresponding SRI to the terminal equipment through an SRI domain in the DCI, and the terminal equipment determines the adopted transmission layer number, precoding matrix and analog beam according to the SRI. The indicated number of SRS resources is the number of transmission layers, and the precoding matrix and the analog beam adopted by the corresponding SRS resources are the precoding matrix and the beam adopted by the corresponding layer of data. At this time, RI and PMI need not be indicated in DCI.

PUSCH repetition transmission

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

Alternatively, as shown in fig. 3, a schematic diagram of PUSCH retransmission based on time slots, and as shown in fig. 3, PUSCH retransmission may be performed in different time slots (slots).

Alternatively, as shown in fig. 4, a PUSCH retransmission scheme based on OFDM symbols is shown, where PUSCH retransmission may be performed in different orthogonal frequency division multiplexing (Orthogonal Frequency Division Multiplexing, OFDM) symbols as shown in fig. 4, and the retransmission in fig. 4 may be performed in the same slot or across slots.

Optionally, as shown in fig. 5, a PUSCH retransmission scheme based on multiple TRP and multiple Panel is shown, and PUSCH transmission may be performed on multiple antenna panels (panels). The DCI for scheduling PUSCH retransmission in fig. 5 may include two SRI fields, and PUSCH retransmission to TRP1 uses one SRI field to obtain a beam and/or a precoding matrix, and PUSCH retransmission to TRP2 uses another SRI field to obtain a beam and/or a precoding matrix, so as to determine respective beam and/or precoding moment according to channel conditions of different TRPs.

For multi-slot or multi-symbol PUSCH repeat transmission (PUSCH repeat transmission as shown in fig. 3 or fig. 4 above), one DCI may schedule multiple PUSCHs to be transmitted on consecutive multiple slots or multiple OFDM symbols, carrying the same data but employing different redundancy versions. At this time, the receiving ends of the different retransmission may be the same TRP or different TRP. For multi-Panel repetition, PUSCHs carrying the same data are simultaneously and respectively transmitted on different Panels, and a receiving end can be the same TRP or different TRPs. In PUSCH repetition transmission, different repetition transmissions may use different beams, different precoding matrices, different redundancy versions and different frequency domain resources.

For multi-TRP PUSCH retransmission (PUSCH retransmission as shown in fig. 5 above), PUSCHs addressed to different TRPs may employ different beams and/or precoding matrices, which may generally be indicated by different SRI fields. Currently, two SRI fields may be included in DCI for scheduling PUSCH retransmission, which are used to determine beams and/or precoding matrices for PUSCH retransmission addressed to different TRPs, respectively.

Exemplary, as shown in fig. 6, a PUSCH retransmission scheme based on multiple TRPs is shown, if the channel between TRP0 and the terminal device is poor, the retransmission to TRP0 is difficult to be received by the corresponding TRP, which may cause waste of resources and power. At this time, if a handover between a single TRP (e.g., TRP 0) transmission (using a single SRI domain) and a plurality of TRP transmissions (i.e., two TRPs of TRP0 and TRP1, using a plurality of SRI domains of SRI0 and SRI 1) can be supported, a waste of resources and power can be avoided.

In practical application, if the number of SRI domains is configured by using RRC signaling, dynamic switching is difficult to support, and switching cannot be performed according to channels in real time; if the indication is performed by using extra bits in the DCI, DCI overhead is increased, and the performance of a control channel is affected; if the number of SRI fields contained in the DCI is determined through blind detection, so that the handover is performed, the blind detection complexity of the terminal device is obviously increased, so how to implement dynamic handover between a single SRI field and multiple SRI fields without increasing DCI overhead and blind detection complexity is a problem to be solved.

Based on the above problems, the embodiments of the present invention provide a PUSCH retransmission method, where a terminal device may receive downlink control information DCI sent by a network device and used for scheduling PUSCH retransmission, where the DCI includes at least two SRI fields, where each SRI field is used to indicate at least one SRS resource; and determining whether to use at least two SRI domains for different PUSCH repeated transmission of DCI scheduling respectively or to use a first SRI domain of the at least two SRI domains for all PUSCH repeated transmission of DCI scheduling according to the information indicated by the at least two SRI domains. In this way, the terminal device can switch between the repeated transmission mode of using at least two SRI domains for different PUSCH repeated transmission scheduled by DCI and the repeated transmission mode of using the first SRI domain in at least two SRI domains for all PUSCH repeated transmission scheduled by DCI in time according to the information indicated by at least two SRI domains in DCI, and even if the TRP channel corresponding to a certain SRI domain is degraded in the transmission process, the terminal device can support the switch between single TRP transmission (using a single SRI domain) and multiple TRP transmission (using multiple SRI domains) through the indication in the DCI of the network device, so as to improve the uplink transmission performance.

As shown in fig. 7, a system architecture diagram of a communication system to which an embodiment of the present invention is applied is shown. The communication system may comprise a network device, which may be a device in communication with a terminal device (or called communication terminal, terminal). The network device may provide communication coverage for a particular geographic area and may communicate with terminal devices located within the coverage area. Fig. 7 exemplarily illustrates one network device and two terminal devices, alternatively, the communication system may include a plurality of network devices and each network device may include other number of terminal devices within a coverage area of the network device, which is not limited in the embodiment of the present application. Optionally, the communication system may further include a network controller, a mobility management entity, and other network entities, which are not limited in this embodiment of the present application.

Alternatively, the communication system may include a plurality of network devices and each network device may include other numbers of terminal devices within a coverage area of the network device, which is not limited by the embodiment of the present invention. Optionally, the communication system may further include a network controller, a mobility management entity, and other network entities, which are not limited by the embodiments of the present invention.

Embodiments of the present invention are described in connection with a network device and a terminal device, where the terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, a User Equipment, or the like.

The terminal device may be a Station (ST) in a WLAN, may be a cellular telephone, a cordless telephone, a session initiation protocol (Session Initiation Protocol, SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, a personal digital assistant (Personal Digital Assistant, PDA) device, a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, a vehicle device, a wearable device, a terminal device in a next generation communication system such as an NR network, or a terminal device in a future evolved public land mobile network (Public Land Mobile Network, PLMN) network, etc.

In the embodiment of the invention, the terminal equipment can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; can also be deployed on the water surface (such as ships, etc.); but may also be deployed in the air (e.g., on aircraft, balloon, satellite, etc.).

In the embodiment of the present invention, the terminal device may be a Mobile Phone (Mobile Phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an augmented Reality (Augmented Reality, AR) terminal device, a wireless terminal device in industrial control (industrial control), a wireless terminal device in unmanned driving (self driving), a wireless terminal device in remote medical (remote medical), a wireless terminal device in smart grid (smart grid), a wireless terminal device in transportation security (transportation safety), a wireless terminal device in smart city (smart city), or a wireless terminal device in smart home (smart home), and the like.

By way of example, and not limitation, in embodiments of the present invention, the terminal device may also be a wearable device. The wearable device can also be called as a wearable intelligent device, and is a generic name for intelligently designing daily wear by applying wearable technology and developing wearable devices, such as glasses, gloves, watches, clothes, shoes and the like. The wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also can realize a powerful function through software support, data interaction and cloud interaction. The generalized wearable intelligent device includes full functionality, large size, and may not rely on the smart phone to implement complete or partial functionality, such as: smart watches or smart glasses, etc., and focus on only certain types of application functions, and need to be used in combination with other devices, such as smart phones, for example, various smart bracelets, smart jewelry, etc. for physical sign monitoring.

The network device may further include an access network device and a core network device. I.e. the wireless communication system further comprises a plurality of core networks for communicating with the access network devices. The access network device may be a long-term evolution (LTE) system, a next-generation (NR) system, or an evolved base station (evolutional node B, abbreviated as eNB or e-NodeB) macro base station, a micro base station (also called "small base station"), a pico base station, an Access Point (AP), a transmission point (transmission point, TP), a new generation base station (new generation Node B, gNodeB), or the like in an licensed assisted access long-term evolution (LAA-LTE) system.

In the embodiment of the present invention, the network device may be a device for communicating with a mobile device, where the network device may be an Access Point (AP) in WLAN, a base station (Base Transceiver Station, BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, a relay station or an Access Point, a vehicle device, a wearable device, a network device (gNB) in NR network, a network device in future evolved PLMN network, or a network device in NTN network, etc.

By way of example, and not limitation, in embodiments of the present invention, a network device may have a mobile nature, e.g., the network device may be a mobile device. Alternatively, the network device may be a satellite, a balloon station. For example, the satellite may be a Low Earth Orbit (LEO) satellite, a medium earth orbit (medium earth orbit, MEO) satellite, a geosynchronous orbit (geostationary earth orbit, GEO) satellite, a high elliptical orbit (High Elliptical Orbit, HEO) satellite, or the like. Alternatively, the network device may be a base station disposed on land, in a water area, or the like.

In the embodiment of the present invention, a network device may provide services for a cell, where a terminal device communicates with the network device through a transmission resource (e.g., a frequency domain resource, or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (e.g., a base station), and the cell may belong to a macro base station, or may belong to a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), micro cells (Micro cells), pico cells (Pico cells), femto cells (Femto cells) and the like, and the small cells have the characteristics of small coverage area and low transmitting power and are suitable for providing high-rate data transmission services.

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

The technical scheme of the embodiment of the invention can be applied to various communication systems, such as: global system for mobile communications (Global System of Mobile communication, GSM), code division multiple access (Code Division Multiple Access, CDMA) system, wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) system, general packet Radio service (General Packet Radio Service, GPRS), long term evolution (Long Term Evolution, LTE) system, advanced long term evolution (Advanced long term evolution, LTE-a) system, new Radio (NR) system, evolved system of NR system, LTE-based access to unlicensed spectrum, LTE-U) system on unlicensed spectrum, NR (NR-based access to unlicensed spectrum, NR-U) system on unlicensed spectrum, non-terrestrial communication network (Non-Terrestrial Networks, NTN) system, universal mobile communication system (Universal Mobile Telecommunication System, UMTS), wireless local area network (Wireless Local Area Networks, WLAN), wireless fidelity (Wireless Fidelity, wiFi), fifth Generation communication (5 th-Generation, 5G) system, or other communication system, etc.

Generally, the number of connections supported by the conventional communication system is limited and easy to implement, however, as the communication technology advances, the mobile communication system will support not only conventional communication but also, for example, device-to-Device (D2D) communication, machine-to-machine (Machine to Machine, M2M) communication, machine type communication (Machine Type Communication, MTC), inter-vehicle (Vehicle to Vehicle, V2V) communication, or internet of vehicles (Vehicle to everything, V2X) communication, etc., to which the embodiments of the present invention can also be applied.

The communication system in the embodiment of the invention can be applied to a carrier aggregation (Carrier Aggregation, CA) scene, a dual-connection (Dual Connectivity, DC) scene and an independent (SA) network deployment scene.

According to the PUSCH repeated transmission method provided by the embodiment of the invention, the terminal equipment can receive Downlink Control Information (DCI) sent by the network equipment, the DCI is used for scheduling Physical Uplink Shared Channel (PUSCH) repeated transmission, the DCI comprises at least two SRI domains, and each SRI domain is used for indicating at least one Sounding Reference Signal (SRS) resource; and determining that the at least two SRI domains are used for the PUSCH repeated transmission of the DCI scheduling according to the information indicated by the at least two SRI domains.

Example 1

As shown in fig. 8, an embodiment of the present invention provides a PUSCH retransmission method, including:

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

Wherein the DCI includes at least two SRI fields, each for indicating at least one sounding reference signal, SRS, resource.

Optionally, different SRI fields in the at least two SRI fields in the DCI indicate resources in different SRS resource sets. For example, the DCI includes two SRI fields, SRI field 1 and SRI field 2, respectively, 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.

The network device may instruct, through information indicated by the at least two SRI domains, whether the terminal device uses the at least two SRI domains for different PUSCH retransmission for DCI scheduling, respectively, or instruct the terminal device to use a first SRI domain of the at least two SRI domains for all PUSCH retransmission for DCI scheduling.

802. And the terminal equipment determines whether the at least two SRI domains are respectively used for different PUSCH repeated transmission of DCI scheduling or whether the first SRI domain in the at least two SRI domains is used for all PUSCH repeated transmission of DCI scheduling according to the information indicated by the at least two SRI domains.

Optionally, the first SRI field includes one of:

(a) An nth one of the at least two SRI domains, n being an integer greater than or equal to 1;

(b) An SRI domain with a minimum number of SRS resources indicated in the at least two SRI domains;

(c) An SRI domain with the largest number of SRS resources indicated in the at least two SRI domains;

(d) At least two SRI domains indicating an SRI domain of a single SRS resource;

(e) An SRI domain indicating a plurality of SRS resources among the at least two SRI domains;

(f) At least two SRI domains indicating m SRS resources, m being an integer greater than or equal to 1;

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

Wherein the SRI domain selected from the at least two SRI domains comprises: an SRI domain randomly selected from the at least two SRI domains; or, an SRI domain selected from at least two SRI domains according to channel reciprocity and downlink channel information.

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

(1) PUSCH retransmission is codebook-based transmission, and there are two possible scenarios for 802 described above:

(1.1) if at least one of the at least two SRI fields indicates a specific value, the terminal device uses the first SRI field for all PUSCH retransmission for DCI scheduling;

If at least one of the at least two SRI fields indicates a specific value, the at least two SRI fields indicate that the terminal device uses the first SRI field for all PUSCH repetition transmissions for DCI scheduling.

There are several alternative ways of indicating the characteristic value:

one implementation: one of the at least two SRI fields indicates a specific value, and the at least two SRI fields indicate that the terminal device uses the first SRI field for all PUSCH repetition transmissions for DCI scheduling.

Another implementation: there are a plurality of SRI fields indicating a specific value but not all of the at least two SRI fields indicating a specific value, the at least two SRI fields indicate that the terminal device uses the first SRI field for all PUSCH repetition transmissions for DCI scheduling.

Yet another implementation is: at least two SRI fields each indicate a specific value, and the at least two SRI fields instruct the terminal device to use the first SRI field for all PUSCH repetition transmissions for DCI scheduling.

The specific value is pre-agreed by the terminal equipment and the network equipment; alternatively, the specific value is preconfigured for the network device.

The specific value may be an indication reservation, or the specific value may be all 0, or the specific value may be all 1, for example.

Optionally, in the case that 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 may select one SRI field from SRI field 1 and SRI field 2 for all PUSCH repeated transmissions for DCI scheduling, and discard the other SRI field. Illustratively, the terminal device may select the SRI field with the first bit (i.e., the first SRI field) of SRI and 1 and SRI field 2 for all PUSCH repeated transmissions for DCI scheduling, and discard the SRI field with the last bit (i.e., the second SRI field).

Illustratively, assuming that the SRI field includes two bits, and that the SRI field 1 and the SRI field 2 each indicate a specific value of 11, the terminal device may select the SRI field 1 with the preceding bit of the SRI field 1 and the SRI field 2 for all PUSCH repetition transmissions for DCI scheduling, and discard the SRI field 2 with the following bit.

Optionally, for the case that the DCI includes two SRI fields, SRI field 1 and SRI field 2, if SRI field 2 indicates a specific value, then the terminal device may discard the SRI field 1 for all PUSCH retransmissions scheduled by the DCI, and another SRI field 2, or if SRI field 1 indicates a specific value, the terminal device may discard the SRI field 2 for all PUSCH retransmissions scheduled by the DCI, and another SRI field 1.

Illustratively, assuming that the SRI field includes two bits, SRI field 2 indicates a specific value of 11, the terminal device may select SRI1 for all PUSCH repetition transmissions for DCI scheduling, SRI field 2 dropping.

Alternatively, for the case that the DCI includes SRI field 1, SRI field 2 and SRI field 3, for a total of 3 SRI fields, if both SRI field 2 and SRI field 3 indicate a specific value, the terminal device may use SRI field 1 for all PUSCH repeated transmissions for DCI scheduling, and discard the other two SRI fields. For example, the terminal device may select SRI domain with the first bit (i.e., the first SRI domain) of SRI and 1, SRI domain 2, and SRI domain 3 for all PUSCH repeated transmissions for DCI scheduling, and discard the other two SRI domains with the last bit.

Illustratively, assuming that the SRI field includes two bits, SRI field 2 and SRI field 3 each indicate a specific value of 11, the terminal device may use SRI field 1 for all PUSCH repetition transmissions for DCI scheduling, with the SRI field 2 and SRI field 3 that are later in the bits discarded.

Optionally, for the case that SRI and 1, SRI field 2 and SRI field 3 are included in the DCI, if SRI field 1 indicates a specific value and SRI field 2 and SRI field 3 indicate other values, then the terminal device may use SRI field 1 for all PUSCH repeated transmissions for DCI scheduling, and the other SRI field 2 and SRI field 3 may be discarded.

For example, assuming that the SRI field includes two bits, SRI field 1 indicates a specific value 11, SRI field 2 and SRI field 3 indicate other values, the terminal device may select SRI1 for all PUSCH repetition transmissions for DCI scheduling, SRI field 2 dropping.

Alternatively, for the case that SRIs and 1, SRI field 2 and SRI field 3 are included in the DCI, if SRI field 1 and SRI field 2 indicate specific values and SRI field 3 indicates other values, then the terminal device may use SRI field 3 for all PUSCH repeated transmissions for DCI scheduling, and the other SRI field 2 and SRI field 1 are discarded.

For example, assuming that the SRI field includes 2 bits, the SRI field 1 and the SRI field 2 indicate a specific value of 00, and the SRI field 3 indicates other values, the terminal device may discard the SRI3 for all PUSCH repetition transmissions for DCI scheduling.

(1.2) if the at least two SRI fields indicate non-specific values, the terminal device uses the at least two SRI fields for different PUSCH repetition transmissions for DCI scheduling, respectively.

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

Optionally, for the case that 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 may use SRI field 1 and SRI field 2 for different PUSCH repeated transmissions for DCI scheduling.

For example, assuming that the SRI field includes two bits, the SRI field 1 and the SRI field 2 each indicate other values than the specific value 11, the terminal device may use the SRI field 1 and the SRI field 2 for different PUSCH repetition transmission for DCI scheduling.

Optionally, for the case that the DCI includes SRI field 1, SRI field 2 and SRI field 3, and a total of 3 SRI fields, if SRI field 1, SRI field 2 and SRI field 3 each indicate a non-specific value, the terminal device may use SRI field 1, SRI field 2 and SRI field 3 for different PUSCH retransmission for DCI scheduling.

For example, assuming that the SRI field includes two bits, the SRI field 1 and the SRI field 2 each indicate other values than the specific value 11, the terminal device may use the SRI field 1, the SRI field 2, and the SRI field 3 for different PUSCH repetition transmission for DCI scheduling.

(2) PUSCH repetition transmission is a non-codebook based transmission, there may be two possible scenarios:

(2.1) if at least two SRI domains exist in the at least two SRI domains to indicate different numbers of SRS resources, the terminal device uses the first SRI domain for all PUSCH repeated transmissions of DCI scheduling;

optionally, for the case that two SRI domains are included in the DCI, one SRI domain indicates one SRS resource, the other SRI domain indicates multiple SRS resources, and the terminal device uses the first SRI domain for all PUSCH repeated transmissions for DCI scheduling if it is determined that one SRI domain indicates one SRS resource and the other SRI domain indicates multiple SRS resources in the two SRI domains.

And if at least two SRI domains exist in the at least two SRI domains to indicate different numbers of SRS resources, indicating the terminal equipment to use the first SRI domain for all PUSCH repeated transmission of DCI scheduling.

The number of SRS resources indicated by all SRI domains in the at least two SRI domains is different, or the number of SRS resources indicated by at least two SRI domains in the at least two SRI domains is different.

Different ones of the at least two SRI domains indicating different amounts of SRS resources may include the following implementations:

the first implementation mode: each of the at least two SRI domains indicates a different number of SRS resources.

For example, the two SRI domains are SRI domain 1 and SRI domain 2, respectively, SRI domain 1 indicating 1 SRS resource and SRI domain 2 indicating 4 SRS resources.

The second implementation mode: the presence of two SRI fields in at least two SRI fields indicates a different number of SRS resources. For example, the three SRI domains are SRI domain 1, SRI domain 2, and SRI domain 3, respectively, SRI domain 1 indicates 1 SRS resource, SRI domain 3 indicates 1 SRS resource, and SRI domain 2 indicates 4 SRS resources.

Third implementation: the presence of more than two SRI fields in at least two SRI fields indicates a different number of SRS resources. For example, the four SRI domains are SRI domain 1, SRI domain 2, SRI domain 3, and SRI domain 4, respectively, SRI domain 1 indicates 1 SRS resource, SRI domain 3 indicates 1 SRS resource, SRI domain 2 indicates 4 SRS resources, and SRI domain 4 indicates 2 SRS resources.

Optionally, different SRI fields in the at least two SRI fields in the DCI indicate SRS resources in different SRS resource sets. For example, the DCI includes two SRI fields, SRI field 1 and SRI field 2, respectively, 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.

Alternatively, each SRI field may be used to indicate an index of one single-port SRS resource or indexes of a plurality of single-port SRS resources, the number of SRS resource indexes, i.e. the number of SRS resources. And the terminal equipment judges whether the first SRI domain is used for all the PUSCH repeated transmission of DCI scheduling according to whether the number of SRS resources indicated by different SRI domains is the same.

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

For example, the DCI includes SRI field 1 and SRI field 2, where SRI field 1 indicates index 0 of one single-port SRS resource, SRI field 2 indicates indexes 1 and 2 of 2 single-port SRS resources, and then SRI field 1 indicates one SRS resource, SRI field 2 indicates 2 SRS resources, and the number of SRS resources indicated by the two is different, which may determine that all PUSCHs of the first SRI field (which may be the SRI field with the earlier bit in SRI field 1 and SRI field 2) are used for DCI scheduling are repeatedly transmitted.

Illustratively, the DCI includes SRI field 1, SRI field 2 and SRI3, where SRI field 1 indicates index 0 of one single-port SRS resource, SRI field 2 indicates indexes 1 and 2 of 2 single-port SRS resources, and SRI3 indicates index 1 of 1 single-port SRS resource; then SRI field 1 indicates one SRS resource, SRI field 2 indicates 2 SRS resources, and SRI3 indicates 1 SRS resource, where the number of SRS resources indicated by SRI field 2, unlike SRI field 1 and SRI field 3, may determine that the first SRI field (which may be the SRI field with the earlier bit of SRI field 1, SRI field 2, and SRI field 3) is used for all PUSCH retransmission for DCI scheduling.

Illustratively, the DCI includes SRI field 1, SRI field 2 and SRI3, where SRI field 1 indicates index 0 of one single-port SRS resource, SRI field 2 indicates indexes 1 and 2 of 2 single-port SRS resources, and SRI3 indicates indexes 0, 1 and 2 of 3 single-port SRS resources; then, at this time, SRI field 1 indicates one SRS resource, SRI field 2 indicates 2 SRS resources, and SRI3 indicates 3 SRS resources, where the number of SRS resources indicated by SRI field 1, SRI field 2, and SRI field 3 are all different, it may be determined that the first SRI field (may be the SRI field with the earlier bit of SRI field 1, SRI field 2, and SRI field 3) is used for all PUSCH repetition transmissions for DCI scheduling.

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

Optionally, when determining the number of SRS resources according to the content indicated by the SRS domain, the maximum number of transmission layers L configured with the higher layer signaling _max In the following, the maximum number of transmission layers is exemplified as 2 to 4, and is described in conjunction with tables 1 to 4, wherein SRI(s), N _SRS =2 denotes that the number of SRS resources included in the SRS resource set is 2, SRI(s), N _SRS =3 denotes that the number of SRS resources included in the SRS resource set is 3; SRI(s), N _SRS =4 indicates that the number of SRS resources included in the SRS resource set is 4.

As shown in Table 1, for the maximum number of transmission layers L _max In the case of=1, the SRI field indicates a correspondence between the content indicated by the SRI field and the corresponding SRS resource, and at this time, the SRI field indicates at most 1 SRS resource.

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

For SRI(s), N _SRS =3, if Bit field mapped to index is 2 (e.g., two bits are 10), the corresponding SRI indicates 1 resource with index 2 in the SRS resource set; if Bit field mapped to index is 3 (e.g., two bits are 11), then the corresponding SRI does not indicate any resources in the SRS resource set. Where reserved is denoted reservation.

For SRI(s), N _SRS =4, if Bit field mapped to index is 3 (e.g., two bits are 11), the corresponding SRI indicates 1 resource with an index of 3 in the SRS resource set.

TABLE 1

As shown in Table 2, for the maximum number of transmission layers L _max In the case of=2, the SRI field indicates a correspondence between the content indicated by the SRI field and the corresponding SRS resource, and at this time, the SRI field indicates a maximum of 2 SRS resources.

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

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

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

TABLE 2

As shown in Table 3, for the maximum number of transmission layers L _max In the case of=3, the content indicated by the SRI field and the corresponding SRS resourceCorrespondence of sources. The SRI field at this time indicates a maximum of 3 SRS resources. Specific indication manners are similar to those of the above tables 1 and 2, and are not repeated here.

TABLE 3 Table 3

As shown in Table 4, for the maximum number of transmission layers L _max In the case of=4, the content indicated by the SRI field corresponds to the corresponding SRS resource. The SRI field at this time indicates a maximum of 4 SRS resources. Specific indication manners are similar to those of the above tables 1 and 2, and are not repeated here.

(2.2) if the at least two SRI fields indicate the same number of SRS resources, the terminal device uses the at least two SRI fields for different PUSCH repetition transmissions for DCI scheduling, respectively.

Alternatively, the terminal device uses at least two SRI fields for different PUSCH retransmission for DCI scheduling, which may be understood that the terminal device uses at least two SRI fields for PUSCH retransmission for different TRPs for DCI scheduling.

And if the at least two SRI domains indicate the same number of SRS resources, indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmissions of DCI scheduling.

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 uses the at least two SRI fields for different PUSCH repetition transmissions for DCI scheduling, respectively.

For example, the DCI includes SRI field 1 and SRI field 2, where SRI field 1 indicates index 0 of one single-port SRS resource, SRI field 2 indicates index 1 of 1 single-port SRS resource, and then both SRI field 1 and SRI field 2 indicate 1 SRS resource, and the number of SRS resources indicated by both fields is the same, it may be determined that all PUSCH repeated transmissions using SRI field 1 and SRI field 2 for DCI scheduling are respectively used for different PUSCH repeated transmissions for DCI scheduling.

For example, the DCI includes SRI field 1 and SRI field 2, where SRI field 1 indicates indexes 0, 1 and 2 of 3 single-port SRS resources, SRI field 2 indicates indexes 1, 2 and 3 of 3 single-port SRS resources, and then both SRI field 1 and SRI field 2 indicate 3 SRS resources, and the number of SRS resources indicated by both fields is the same, and it may be determined that all PUSCH repeated transmissions using SRI field 1 and SRI field 2 for DCI scheduling are respectively used for different PUSCH repeated transmissions for DCI scheduling.

Optionally, if the information of the first SRI domain is used for all PUSCH repeated transmissions of DCI scheduling, the information of the second SRI domain is not used for any PUSCH transmission, and the second SRI domain is an SRI domain other than the first SRI domain of the at least two SRI domains.

Optionally, if the first SRI domain is used for all PUSCH repeated transmissions of DCI scheduling and the DCI includes at least two TPC commands, the first TPC command is used for all PUSCH repeated transmissions of DCI scheduling, where the first TPC command is a TPC command associated with the first SRI domain in at least two TPC domains;

Optionally, the association between the SRI field and the TPC command may be two possible cases:

a first possible scenario is: k SRI domain in DCI is associated with a kth TPC command in DCI, wherein k is a positive integer;

illustratively, it is assumed that two SRI fields, and two TPC commands are included in the DCI. According to the bit sequence, the first SRI domain is SRI domain 1, the second SRI domain is SRI domain 2, the first TPC command is TPC command 1, and the second TPC command is TCP command 2, wherein SRI domain 1 is associated with TPC command 1, and SRI domain 2 is associated with TCP command 2.

Illustratively, assume that three SRI fields, and three TPC commands are included in the DCI. According to the bit sequence, the first SRI domain is SRI domain 1, the second SRI domain is SRI domain 2, the third SRI domain is SRI domain 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, wherein SRI domain 1 is associated with TPC command 1, SRI domain 2 is associated with TCP command 2, and SRI domain 3 is associated with TCP command 3.

A second possible scenario: at least two TPC commands are associated with different closed loop power adjustment states, the first TPC command being a TPC command associated with the same closed loop power adjustment state as the information indicated by the first SRI field.

Wherein at least two SRI fields are associated with different closed loop highway adjustment states.

For example, assuming that two SRI fields (SRI field 1 and SRI field 2) and two TPC commands (TPC command 1 and TPC command 2) are included in the DCI, where TPC command 1 associates a closed-loop power adjustment state with index 0, SRI field 1 also associates a closed-loop power adjustment state with index 0, TPC command 2 associates a closed-loop power adjustment state with index 1, and SRI field 2 associates a closed-loop power adjustment state with index 1, TPC command 1 is a first TPC command when SRI field 1 is a first SRI field.

For example, assuming that 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) are included in the DCI, where TPC command 1 is associated with a closed-loop power adjustment state with index 0, SRI field 1 is also associated with a closed-loop power adjustment state with index 0, TPC command 2 is associated with a closed-loop power adjustment state with index 1, SRI field 2 is associated with a closed-loop power adjustment state with index 1, TPC command 3 is associated with a closed-loop power adjustment state with index 0, SRI field 3 is associated with a closed-loop power adjustment state with index 1, then TPC commands 1 and TPC command 3 are the first TPC commands when SRI field 1 is the first SRI field.

In one embodiment, if none of the at least two TPC commands is associated with a TPC command of the same closed loop power adjustment state as the information indicated by the first SRI field, none of the at least two TPC commands is used for PUSCH repetition transmission for the DCI schedule.

In another embodiment, if the at least two TPC commands are both associated with the same closed loop power adjustment state as the information indicated by the first SRI field, the at least two TPC commands are both used for PUSCH repetition transmission for the DCI schedule, i.e. the at least two TPC commands are both used for transmit power adjustment of the PUSCH.

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

optionally, the second TPC command in the at least two TPC domains is used for power accumulation of a second closed loop power adjustment state, the second closed loop power adjustment state being a closed loop power adjustment state determined from information indicated by the second SRI domain.

Wherein the second TPC command is a TPC command other than the first TPC command of the at least two TPC commands, and the second SRI domain is an SRI domain other than the first SRI domain of the at least two SRI domains.

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

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

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

In the embodiment of the invention, the terminal equipment can receive downlink control information DCI which is sent by the network equipment and is used for scheduling the repeated transmission of the PUSCH, wherein the DCI comprises at least two SRI domains, and each SRI domain is used for indicating at least one SRS resource; and determining whether to use at least two SRI domains for different PUSCH repeated transmission of DCI scheduling respectively or to use a first SRI domain of the at least two SRI domains for all PUSCH repeated transmission of DCI scheduling according to the information indicated by the at least two SRI domains. In this way, the terminal device can switch between the repeated transmission mode of using at least two SRI domains for different PUSCH repeated transmission scheduled by DCI and the repeated transmission mode of using the first SRI domain in at least two SRI domains for all PUSCH repeated transmission scheduled by DCI in time according to the information indicated by at least two SRI domains in DCI, and even if the TRP channel corresponding to a certain SRI domain is degraded in the transmission process, the terminal device can support the switching between a single TRP transmission (using a single SRI domain) and multiple TRP transmissions (using multiple SRI domains) through the indication in the DCI of the network device, so that PUSCH repeated transmission can be flexibly implemented.

Example two

The present embodiment is described taking the scheduled PUSCH as a CodeBook-based transmission, that is, the transmission mode of the higher layer signaling configuration is CodeBook (CodeBook). Wherein each SRI field is used to indicate one SRS resource.

The terminal equipment receives downlink DCI for scheduling PUSCH repeated transmission, wherein the DCI comprises two SRI domains, namely SRI domain 1 and SRI domain 2.

And the terminal equipment determines whether the information of the SRI domain 1 and the SRI domain 2 are respectively used for different PUSCH repeated transmission or whether the information of the first SRI domain is used for all the PUSCH repeated transmission according to the content indicated by the two SRI domains.

Optionally, the first SRI domain is a first one of two SRI domains contained in the DCI.

In one embodiment, when there is at least one SRI field indicating a specific value in the two SRI fields, the terminal device uses information of a first SRI field in SRI field 1 and SRI field 2 for all PUSCH retransmission; 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 repetition transmissions, respectively.

In one embodiment, the specific value is a value agreed in advance by the terminal device and the network device. For example, when SRI domain 2 indicates reservation, or when SRI domain 2 indicates all 0 or all 1, the terminal device uses the information of SRI domain 1 for all PUSCH retransmission, and the information of SRI domain 2 is not used for any transmission (discarded or ignored). In other cases, the terminal device uses the information of SRI domain 1 and SRI domain 2 for different PUSCH retransmission, i.e. the information of both SRI domains is used.

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

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

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

If the terminal device uses the information of the SRI domain 1 and the SRI domain 2 for different PUSCH retransmission, the terminal device uses the two TPC domains for different PUSCH retransmission, i.e. the part of PUSCH retransmission scheduled by DCI uses TPC commands in TPC domain 1 to determine the closed-loop power adjustment state and the transmit power, and the other PUSCH retransmission uses TPC commands in TPC domain 2 to determine the closed-loop power adjustment state and the transmit power.

If the terminal device uses the information of the first SRI domain for all PUSCH repeated transmission, the terminal device uses the first TPC domain associated with the first SRI domain in the TPC domain 1 and the TPC domain 2 for all PUSCH repeated transmission. That is, all PUSCH repetition transmissions for DCI scheduling employ TPC commands in the first TPC domain to determine the closed loop power adjustment state and transmit power.

In one embodiment, the SRI domain and TPC domain association relationship is: a first SRI field in the DCI is associated with a first TPC field and a second SRI field in the DCI is associated with a second TPC field.

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

Wherein the two TPC domains are associated with different closed loop power adjustment states, e.g., a closed loop power adjustment state with a first TPC domain associated with index 0 and a second TPC domain associated with index 1.

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

In an embodiment, the second TPC field in the DCI is not used for any PUSCH transmission, where the second TPC field is a TPC field other than the first TPC in TPC field 1 and TPC field 2 described above.

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

For example, as shown in fig. 9A, a schematic diagram of PUSCH retransmission based on multiple SRI fields is shown, where the DCI includes SRI0 and SRI1, when the terminal device determines that the information of SRI0 and SRI1 are used for different PUSCH retransmission, a part of PUSCH retransmission scheduled by the DCI (for example, odd number of transmissions) determines a transmit beam/precoding matrix based on SRS resources indicated by SRI0, and other PUSCH retransmission (for example, even number of transmissions) determines a transmit beam/precoding matrix based on SRS resources indicated by SRI 1.

For example, as shown in fig. 9B, a PUSCH retransmission diagram based on a single SRI field is shown, and when the terminal device determines that the information of SRI0 is used for all PUSCH retransmissions, all PUSCH retransmissions scheduled by the DCI determine the transmit beam/precoding matrix based on the SRS resource indicated by the first SRI field.

Based on the method of the embodiment, dynamic switching of a single SRI domain (all repeated transmissions are directed to the same TRP and the same beam/precoder) and a plurality of SRI domains (different repeated transmissions are directed to different TRPs and different beam/precoder) can be realized through the information indicated by the SRI domain, so that the configuration of repeated transmissions is adjusted in real time according to the link quality of different TRPs, higher uplink frequency spectrum efficiency is achieved, and the performance of uplink multi-TRP diversity transmission is improved. In addition, since no additional DCI bit is needed, and the size of DCI is not needed to be dynamically switched, the additional DCI overhead is avoided, and the blind detection complexity of the terminal equipment is reduced.

Example III

The present embodiment is described taking the scheduled PUSCH as a non-codebook-based transmission, that is, the transmission mode of the higher layer signaling configuration is a non-codebook (non codebook). Wherein each SRI field is to indicate one or more single-port SRS resources.

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

(1) The first of two SRI fields contained in the DCI, e.g., the SRI field preceding the bit in the DCI;

(2) SRI domains with fewer SRS resources indicated in the two SRI domains contained in the DCI;

(3) SRI domains with more SRS resources indicated in the two SRI domains contained in the DCI;

(4) The DCI includes two SRI fields indicating a single SRS resource. At this time, the other one of the two SRI fields indicates a plurality of SRS resources;

(5) The DCI includes two SRI fields indicating one or two SRS resources. At this time, another one of the two SRI fields indicates more than two SRS resources;

(6) The terminal device selects an SRI field from the two SRI fields contained in the DCI. Specifically, the terminal device may randomly select one SRI domain from among them, or select one SRI domain from among them according to channel reciprocity and downlink channel information.

Alternatively, in the case where PUSCH retransmission is non-codebook based transmission, when two SRI domains indicate different amounts of SRS resources (e.g., one SRI domain indicates 1 SRS resource index and the other SRI domain indicates two SRS resource indexes), the terminal device uses the information of the first SRI domain therein for all PUSCH retransmission, and the information of the second SRI domain is not used for any transmission (discarded or ignored). When the two SRI domains indicate the same number of SRS resources, the terminal device uses the information of the two SRI domains for different PUSCH repetition transmissions, respectively.

Wherein the second SRI domain is an SRI domain other than the first SRI domain of SRI domain 1 and SRI domain 2.

In the above embodiment, dynamic switching of a single SRI domain (PUSCH retransmission with single TRP) and multiple SRI domains (PUSCH retransmission with multiple TRP) can be achieved without additional DCI overhead, so as to achieve better uplink transmission performance. Further, the method does not need to modify the definition and indication content of the existing SRI domain, so that the influence on the realization of the terminal equipment is reduced.

In one embodiment, the DCI contains 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.

If the terminal device uses the information of the SRI domain 1 and the SRI domain 2 for different PUSCH repeated transmission, the terminal device uses two TPC commands for different PUSCH repeated transmission, that is, part of PUSCH repeated transmission scheduled by DCI adopts TPC command 1 to determine the closed-loop power adjustment state and the transmit power, and other PUSCH repeated transmission adopts TPC command 2 to determine the closed-loop power adjustment state and the transmit power.

If the terminal equipment uses the information of the first SRI domain for all PUSCH repeated transmission, the terminal equipment uses the first TPC command associated with the first SRI domain in TPC command 1 and TPC command 2 for all PUSCH repeated transmission. I.e. all PUSCH repeated transmissions for DCI scheduling employ the first TPC command to determine the closed loop power adjustment state and the transmit power.

In one embodiment, the SRI field is associated with TPC commands as follows: a first SRI field in the DCI is associated with a first TPC command and a second SRI field in the DCI is associated with a second TPC command.

In another embodiment, 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.

Wherein two TPC commands are associated with different closed loop power adjustment states, e.g., one TPC command associated with a closed loop power adjustment state with index 0 and the other TPC command associated with a closed loop power adjustment state with index 1.

The association of the SRI field or the information indicated by the SRI field with the closed loop power adjustment state may be obtained in several alternative ways:

the first alternative, the network device may also pre-notify the terminal device via higher layer signaling of the closed loop power adjustment status associated with each TPC command.

The second alternative, different values of the SRI field indication may be associated with different closed loop power adjustment states, and the association may also be notified to the terminal device through higher layer signaling.

Third, the SRI field 1 and the SRI field 2 may themselves be associated with different closed loop power adjustment states (regardless of the values indicated in the SRI field, all values correspond to the same closed loop power adjustment state), for example, SRI field 1 is associated with a closed loop power adjustment state with index 1 and SRI field 2 is associated with a closed loop power adjustment state with index 0.

A third alternative, the terminal device may agree with the network device that the information indicated by the different SRI fields needs to be associated with different closed-loop power adjustment states, but each SRI field specifically associates which closed-loop power adjustment state is still configured by the network device.

In one embodiment, the second TPC command in the DCI is not used for PUSCH for DCI scheduling but is still used for power accumulation of a second closed loop power adjustment state, the second closed loop power adjustment state being a closed loop power adjustment state determined from the second SRI field or information indicated by the second SRI field.

Optionally, as shown in fig. 9A, the DCI includes two SRI fields, SRI0 and SRI1, and when the terminal device determines that the information of SRI0 and SRI1 is used for different PUSCH retransmission, a part of PUSCH retransmission scheduled by the DCI (for example, the first two transmissions) determines a transmit beam/precoding matrix based on SRS resources indicated by SRI0, and the other PUSCH retransmission (for example, the second two transmissions) determines a transmit beam/precoding matrix based on SRS resources indicated by SRI 1.

As shown in fig. 9B, the DCI includes two SRI fields, SRI0 and SRI1, and when the terminal device determines that the information of SRI0 is used for all PUSCH retransmission, all PUSCH retransmission scheduled by the DCI determines a transmit beam/precoding matrix based on SRS resources indicated by the SRI0 field.

Based on the method of the invention, the dynamic switching of a single SRI domain (all repeated transmissions are aimed at the same TRP and the same beam/precoder) and a plurality of SRI domains (different repeated transmissions are aimed at different TRPs and different beam/precoder) can be realized through the information content indicated by the SRI domain, thereby adjusting the configuration of repeated transmissions in real time according to the link quality of different TRPs, achieving higher uplink frequency spectrum efficiency and improving the performance of uplink multi-TRP diversity transmission. In addition, since no additional DCI bit is needed, and the size of DCI is not needed to be dynamically switched, the additional DCI overhead is avoided, and the blind detection complexity of the terminal equipment is reduced.

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

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

a processing module 1002, configured to determine, according to information indicated by the at least two SRI domains, to use the at least two SRI domains for PUSCH repetition transmission for DCI scheduling.

Optionally, the processing module 1002 is specifically configured to determine, according to information indicated by the at least two SRI domains, whether to use the at least two SRI domains for different PUSCH retransmission for DCI scheduling, or to use a first SRI domain of the at least two SRI domains for all PUSCH retransmission for DCI scheduling.

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

a processing module 1002, specifically configured to use the first SRI domain for all PUSCH retransmission for DCI scheduling if at least one of the at least two SRI domains indicates a specific value;

the processing module 1002 is specifically configured to use the at least two SRI fields for different PUSCH retransmission for DCI scheduling if the at least two SRI fields indicate a non-specific value.

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

Or alternatively, the process may be performed,

the specific value is preconfigured for the network device.

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

the processing module 1002 is specifically configured to use the first SRI domain for all PUSCH repeated transmissions for DCI scheduling if there are at least two SRI domains with at least two SRI indications of different numbers of SRS resources;

the processing module 1002 is specifically configured to use the at least two SRI fields for different PUSCH repetition transmissions for DCI scheduling if the at least two SRI fields both indicate the same number of SRS resources.

Optionally, the processing module 1002 is further configured to, if the information of the first SRI domain is used for all PUSCH repetition transmissions for DCI scheduling, not use the information of the second SRI domain for any PUSCH transmission, where the second SRI domain is an SRI domain of at least two SRI domains other than the first SRI domain.

Optionally, the processing module 1002 is further configured to, if the first SRI field is used for all PUSCH repeated transmissions of DCI scheduling and the DCI includes at least two TPC commands, use the first TPC command for all PUSCH repeated transmissions of DCI scheduling, where the first TPC command is a TPC command associated with the first SRI field in the at least two TPC fields;

optionally, the kth SRI field in the DCI associates the kth TPC command in the DCI, k being a positive integer;

Or alternatively, the process may be performed,

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

or alternatively, the process may be performed,

the second TPC commands in the at least two TPC domains are used for power accumulation for a second closed loop power adjustment state, the second closed loop power adjustment state being a closed loop power adjustment state determined from information indicated by the second SRI domain;

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

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

or alternatively, the process may be performed,

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

Optionally, the first SRI domain comprises one of:

an nth one of the at least two SRI domains, n being an integer greater than or equal to 1;

an SRI domain with a minimum number of SRS resources indicated in the at least two SRI domains;

an SRI domain with the largest number of SRS resources indicated in the at least two SRI domains;

at least two SRI domains indicating an SRI domain of a single SRS resource;

an SRI domain indicating a plurality of SRS resources among the at least two SRI domains;

at least two SRI domains indicating m SRS resources, m being an integer greater than or equal to 1;

an SRI domain selected from the at least two SRI domains.

Optionally, the SRI domain selected from the at least two SRI domains comprises:

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

or alternatively, the process may be performed,

and an SRI domain selected from at least two SRI domains according to the channel reciprocity and the downlink channel information.

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

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

and indicating the terminal equipment to use the at least two SRI domains for the PUSCH repeated transmission of the DCI scheduling through the information indicated by the at least two SRI domains.

Optionally, the information indicated by the at least two SRI fields indicates that the terminal device uses the at least two SRI fields for different PUSCH retransmission for DCI scheduling, including: and through the information indicated by the at least two SRI domains, indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmission of DCI scheduling or indicating the terminal equipment to use the first SRI domain of the at least two SRI domains for all PUSCH repeated transmission of DCI scheduling.

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

if at least one SRI domain in at least two SRI domains indicates a specific value, indicating the terminal equipment to use the first SRI domain for all PUSCH repeated transmission of DCI scheduling;

or alternatively, the process may be performed,

and if the at least two SRI domains indicate non-specific values, indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmissions of DCI scheduling.

or alternatively, the process may be performed,

the specific value is preconfigured for the network device.

if at least two SRI (SRI) domains exist, indicating terminal equipment to use a first SRI domain for repeated transmission of all PUSCHs scheduled by DCI (physical uplink control channel);

Optionally, if the first SRI field is used for all PUSCH repeated transmissions of DCI scheduling and the DCI includes at least two TPC commands, the first TPC command is used for all PUSCH repeated transmissions of DCI scheduling, and the first TPC command is a TPC command associated with the first SRI field in at least two TPC fields.

or alternatively, the process may be performed,

Alternatively to this, the method may comprise,

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

or alternatively, the process may be performed,

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

Optionally, the first SRI domain comprises one of:

at least two SRI domains indicating an SRI domain of a single SRS resource;

an SRI domain selected from the at least two SRI domains.

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

or alternatively, the process may be performed,

The embodiment of the invention also provides a terminal device, which comprises: a memory storing executable program code;

a processor coupled to the memory;

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

The embodiment of the invention also provides a network device, which comprises: a memory storing executable program code;

a processor coupled to the memory;

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

For example, in the embodiment of the present invention, the terminal device may be a mobile phone, as shown in fig. 11, where the mobile phone may include: radio Frequency (RF) circuitry 1110, memory 1120, input unit 1130, display unit 1140, sensors 1150, audio circuitry 1160, wireless fidelity (wireless fidelity, wiFi) module 1170, processor 1180, and power supply 1190. Wherein radio frequency circuitry 1110 includes a receiver 1111 and a transmitter 1112. Those skilled in the art will appreciate that the handset configuration shown in fig. 11 is not limiting of the handset and may include more or fewer components than shown, or may combine certain components, or may be arranged in a different arrangement of components.

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

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

The input unit 1130 may be used to receive input numeric or character information and to generate key signal inputs related to user settings and function control of the mobile phone. In particular, the input unit 1130 may include a touch panel 1131 and other input devices 1132. The touch panel 1131, also referred to as a touch screen, may collect touch operations thereon or thereabout by a user (e.g., operations of the user on the touch panel 1131 or thereabout using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a predetermined program. Alternatively, the touch panel 1131 may include two parts, a touch detection device and a touch controller. The touch detection device detects the touch azimuth of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device and converts it into touch point coordinates, which are then sent to the processor 1180, and can receive commands from the processor 1180 and execute them. In addition, the touch panel 1131 may be implemented in various types such as resistive, capacitive, infrared, and surface acoustic wave. The input unit 1130 may include other input devices 1132 in addition to the touch panel 1131. In particular, other input devices 1132 may include, but are not limited to, one or more of a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, mouse, joystick, etc.

The display unit 1140 may be used to display information input by a user or information provided to the user as well as various menus of the mobile phone. The display unit 1140 may include a display panel 1141, and optionally, the display panel 1141 may be configured in the form of a liquid crystal display (liquid crystal display, LCD), an organic light-Emitting diode (OLED), or the like. Further, the touch panel 1131 may overlay the display panel 1141, and when the touch panel 1131 detects a touch operation thereon or thereabout, the touch panel is transferred to the processor 1180 to determine the type of touch event, and then the processor 1180 provides a corresponding visual output on the display panel 1141 according to the type of touch event. Although in fig. 11, the touch panel 1131 and the display panel 1141 are two separate components to implement the input and output functions of the mobile phone, in some embodiments, the touch panel 1131 may be integrated with the display panel 1141 to implement the input and output functions of the mobile phone.

The handset may also include at least one sensor 1150, such as a light sensor, motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1141 according to the brightness of ambient light, and the proximity sensor may turn off the display panel 1141 and/or the backlight when the mobile phone moves to the ear. As one of the motion sensors, the accelerometer sensor can detect the acceleration in all directions (generally three axes), and can detect the gravity and direction when stationary, and can be used for applications of recognizing the gesture of a mobile phone (such as horizontal and vertical screen switching, related games, magnetometer gesture calibration), vibration recognition related functions (such as pedometer and knocking), and the like; other sensors such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc. that may also be configured with the handset are not described in detail herein.

Audio circuitry 1160, speaker 1161, and microphone 1162 may provide an audio interface between a user and a cell phone. The audio circuit 1160 may transmit the received electrical signal converted from audio data to the speaker 1161, and may be converted into a sound signal by the speaker 1161 to be output; on the other hand, the microphone 1162 converts the collected sound signals into electrical signals, which are received by the audio circuit 1160 and converted into audio data, which are processed by the audio data output processor 1180 for transmission to, for example, another cell phone via the RF circuit 1110, or which are output to the memory 1120 for further processing.

WiFi belongs to a short-distance wireless transmission technology, and a mobile phone can help a user to send and receive emails, browse webpages, access streaming media and the like through a WiFi module 1170, so that wireless broadband Internet access is provided for the user. Although fig. 11 shows a WiFi module 1170, it is understood that it does not belong to the necessary constitution of the mobile phone, and can be omitted entirely as required within the scope of not changing the essence of the invention.

The processor 1180 is a control center of the mobile phone, and connects various parts of the entire mobile phone using various interfaces and lines, and performs various functions and processes of the mobile phone by running or executing software programs and/or modules stored in the memory 1120 and calling data stored in the memory 1120, thereby performing overall monitoring of the mobile phone. In the alternative, 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 primarily handles operating systems, user interfaces, applications, etc., and the modem processor primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 1180.

The handset further includes a power supply 1190 (e.g., a battery) for powering the various components, which may be logically connected to the processor 1180 via a power management system so as to provide for the management of charging, discharging, and power consumption by the power management system. Although not shown, the mobile phone may further include a camera, a bluetooth module, etc., which will not be described herein.

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

a processor 1180, configured to determine, according to the information indicated by the at least two SRI domains, different PUSCH retransmission for the DCI scheduling using the at least two SRI domains, respectively

Optionally, the processor 1180 is specifically configured to determine, according to the information indicated by the at least two SRI domains, whether to use the at least two SRI domains for different PUSCH retransmission for DCI scheduling, or use a first SRI domain of the at least two SRI domains for all PUSCH retransmission for DCI scheduling.

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

a processor 1180, configured to, if at least one of the at least two SRI fields indicates a specific value, use the first SRI field for all PUSCH retransmission for DCI scheduling;

The processor 1180 is specifically configured to use the at least two SRI fields for different PUSCH retransmission for DCI scheduling if the at least two SRI fields indicate a non-specific value.

or alternatively, the process may be performed,

the specific value is preconfigured for the network device.

a processor 1180, configured to, if there are at least two SRI domains in the at least two SRI domains indicating different amounts of SRS resources, use the first SRI domain for all PUSCH repeated transmissions for DCI scheduling;

the processor 1180 is specifically configured to use the at least two SRI fields for different PUSCH repetition transmissions for DCI scheduling if the at least two SRI fields both indicate the same number of SRS resources.

Optionally, the processor 1180 is further configured to, if the information of the first SRI domain is used for all PUSCH repetition transmissions for DCI scheduling, not use the information of the second SRI domain for any PUSCH transmission, where the second SRI domain is an SRI domain of at least two SRI domains other than the first SRI domain.

Optionally, the processor 1180 is further configured to, if the first SRI field is used for all PUSCH retransmission scheduled by the DCI and the DCI includes at least two TPC commands, use the first TPC command for all PUSCH retransmission scheduled by the DCI, where the first TPC command is a TPC command associated with the first SRI field in the at least two TPC fields;

or alternatively, the process may be performed,

the second TPC command is a TPC command other than the first TPC command in the at least two TPC commands, and the second SRI domain is an SRI domain other than the first SRI domain in the at least two SRI domains.

Optionally, the processor 1180 is further configured to, if the at least two SRI fields are respectively used for different PUSCH retransmission for DCI scheduling and the DCI includes at least two TPC commands, respectively use the at least two TPC commands for different PUSCH retransmission for DCI scheduling.

Or alternatively, the process may be performed,

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

Optionally, the first SRI domain comprises one of:

at least two SRI domains indicating an SRI domain of a single SRS resource;

an SRI domain selected from the at least two SRI domains.

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

or alternatively, the process may be performed,

As shown in fig. 12, the network device in the embodiment of the present invention may be a base station, where the base station includes:

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

Optionally, the information indicated by the at least two SRI fields indicates that the terminal device uses the at least two SRI fields for PUSCH repeated transmission for DCI scheduling, including: and through the information indicated by the at least two SRI domains, indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmission of DCI scheduling or indicating the terminal equipment to use the first SRI domain of the at least two SRI domains for all PUSCH repeated transmission of DCI scheduling.

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

or alternatively, the process may be performed,

the specific value is preconfigured for the network device.

If at least two SRI domains exist in the at least two SRI domains to indicate different numbers of SRS resources, indicating the terminal equipment to use the first SRI domain for repeated transmission of all PUSCHs scheduled by DCI;

or alternatively, the process may be performed,

Alternatively to this, the method may comprise,

or alternatively, the process may be performed,

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

Optionally, the first SRI domain comprises one of:

At least two SRI domains indicating an SRI domain of a single SRS resource;

an SRI domain selected from the at least two SRI domains.

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

or alternatively, the process may be performed,

The embodiment of the invention also provides a computer readable storage medium, comprising: computer instructions, when run on a computer, cause the computer to perform the respective processes of the terminal device as in the method embodiments described above.

The embodiment of the invention also provides a computer readable storage medium, comprising: computer instructions, when run on a computer, cause the computer to perform the various processes of the network device as in the method embodiments described above.

The embodiment of the invention also provides a computer program product, which comprises computer instructions, when the computer program product runs on a computer, the computer runs the computer instructions, so that the computer executes the processes of the terminal equipment in the embodiment of the method.

The embodiment of the invention also provides a computer program product, which comprises computer instructions, and when the computer program product runs on a computer, the computer executes the computer instructions to enable the computer to execute each process of the network device in the embodiment of the method.

The embodiment of the invention also provides a chip, which is coupled with the memory in the terminal equipment, so that the chip calls the program instructions stored in the memory when in operation, and the terminal equipment executes the processes of the terminal equipment in the embodiment of the method.

The embodiment of the invention also provides a chip, which is coupled with the memory in the network equipment, so that the chip calls the program instructions stored in the memory when running, and the network equipment executes the processes of the network equipment in the embodiment of the method.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions in accordance with embodiments of the present invention are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). Computer readable storage media can be any available media that can be stored by a computer or data storage devices such as servers, data centers, etc. that contain an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

Claims

A PUSCH repetition transmission method, comprising:

receiving Downlink Control Information (DCI) sent by network equipment, wherein the DCI is used for scheduling repeated transmission of a Physical Uplink Shared Channel (PUSCH), and comprises at least two SRI domains, and 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 the PUSCH repeated transmission scheduled by the DCI according to the information indicated by the at least two SRI domains.
The method of claim 1, wherein the determining to use the at least two SRI fields for PUSCH retransmission for the DCI scheduling based on the information indicated by the at least two SRI fields comprises:

and determining whether the at least two SRI domains are respectively used for different PUSCH repeated transmission scheduled by the DCI or the first SRI domain in the at least two SRI domains is used for all PUSCH repeated transmission scheduled by the DCI according to the information indicated by the at least two SRI domains.
The method of claim 2, wherein if the PUSCH retransmission is a codebook-based transmission, determining whether to use the at least two SRI fields for different PUSCH retransmission for the DCI schedule, respectively, or to use a first SRI field of the at least two SRI fields for all PUSCH retransmission for the DCI schedule, based on the information indicated by the at least two SRI fields, comprises:

if at least one of the at least two SRI fields indicates a specific value, using the first SRI field for all PUSCH retransmission scheduled by the DCI;

And if the at least two SRI domains indicate non-specific values, respectively using the at least two SRI domains for different PUSCH repeated transmissions scheduled by the DCI.
The method of claim 3, wherein the step of,

the specific value is pre-agreed by the terminal equipment and the network equipment;

or alternatively, the process may be performed,

the specific value is preconfigured for the network device.
The method of claim 2, wherein if the PUSCH retransmission is a non-codebook based transmission, determining whether to use the at least two SRI fields for different PUSCH retransmission for the DCI schedule, respectively, or to use a first SRI field of the at least two SRI fields for all PUSCH retransmission for the DCI schedule, based on the information indicated by the at least two SRI fields, comprises:

if at least two SRI (SRI) indicating different numbers of SRS resources exist in the at least two SRI domains, using the first SRI domain for all PUSCH repeated transmission scheduled by the DCI;

and if the at least two SRI domains indicate the same number of SRS resources, respectively using the at least two SRI domains for different PUSCH repeated transmissions scheduled by the DCI.
The method according to any one of claims 2 to 5, further comprising:

If the information of the first SRI domain is used for all PUSCH repeated transmissions scheduled by the DCI, the information of a second SRI domain is not used for any PUSCH transmission, and the second SRI domain is an SRI domain of the at least two SRI domains except the first SRI domain.
The method according to any one of claims 2 to 6, further comprising:

and if the first SRI domain is used for all PUSCH repeated transmissions scheduled by the DCI and the DCI comprises at least two TPC commands, using a first TPC command for all PUSCH repeated transmissions scheduled by the DCI, wherein the first TPC command is a TPC command associated with the first SRI domain in the at least two TPC domains.
The method of claim 7, wherein the step of determining the position of the probe is performed,

the kth SRI domain in the DCI is associated with the kth TPC command in the DCI, wherein k is a positive integer;

or alternatively, the process may be performed,

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

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

Or alternatively, the process may be performed,

the second TPC commands in the at least two TPC domains are used for power accumulation for a second closed loop power adjustment state, the second closed loop power adjustment state being a closed loop power adjustment state determined from information indicated by a second SRI domain;

wherein the second TPC command is a TPC command other than the first TPC command in the at least two TPC commands, and the second SRI domain is an SRI domain other than the first SRI domain in the at least two SRI domains.
The method according to any one of claims 2 to 6, further comprising:

and if the at least two SRI domains are respectively used for different PUSCH repeated transmissions scheduled by the DCI and the DCI comprises at least two TPC commands, respectively using the at least two TPC commands for the different PUSCH repeated transmissions scheduled by the DCI.
The method according to any one of claims 7 to 10, wherein,

each TPC command of the at least two TPC commands is indicated by a different TPC field in the DCI, respectively;

or alternatively, the process may be performed,

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

An nth one of the at least two SRI domains, n being an integer greater than or equal to 1;

an SRI domain with the least number of SRS resources indicated in the at least two SRI domains;

an SRI domain with the largest SRS resource quantity indicated in the at least two SRI domains;

the at least two SRI domains indicating an SRI domain of a single SRS resource;

an SRI domain indicating a plurality of SRS resources among the at least two SRI domains;

an SRI domain indicating m SRS resources among the at least two SRI domains, m being an integer greater than or equal to 1;

an SRI domain selected from the at least two SRI domains.
The method of claim 12, wherein the SRI domain selected from the at least two SRI domains comprises:

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

or alternatively, the process may be performed,

and an SRI domain selected from the at least two SRI domains according to channel reciprocity and downlink channel information.
A PUSCH repetition transmission method, comprising:

transmitting DCI to terminal equipment, wherein the DCI is used for scheduling PUSCH repeated transmission, the DCI comprises at least two SRI domains, and each SRI domain is used for indicating at least one SRS resource;

and indicating the terminal equipment to use the at least two SRI domains for the PUSCH repeated transmission scheduled by the DCI through the information indicated by the at least two SRI domains.
The method of claim 14, wherein the information indicated by the at least two SRI fields instructs the terminal device to use the at least two SRI fields for PUSCH repetition transmission for the DCI schedule, comprising:

and indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmission scheduled by the DCI or indicating the terminal equipment to use the first SRI domain in the at least two SRI domains for all PUSCH repeated transmission scheduled by the DCI through the information indicated by the at least two SRI domains.
The method of claim 15, wherein if the PUSCH retransmission is a codebook-based transmission; the information indicated by the at least two SRI fields indicates whether the terminal device uses the at least two SRI fields for different PUSCH retransmission scheduled by the DCI, respectively, or indicates whether the terminal device uses a first SRI field of the at least two SRI fields for all PUSCH retransmission scheduled by the DCI, including:

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

And if the at least two SRI domains indicate non-specific values, indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmissions scheduled by the DCI.
The method of claim 16, wherein the step of determining the position of the probe comprises,

the specific value is pre-agreed by the terminal equipment and the network equipment;

or alternatively, the process may be performed,

the specific value is preconfigured for the network device.
The method of claim 15, wherein if the PUSCH retransmission is a non-codebook based transmission, instructing the terminal device to use the at least two SRI fields for different PUSCH retransmission for the DCI schedule, respectively, or instructing the terminal device to use a first SRI field of the at least two SRI fields for all PUSCH retransmission for the DCI schedule, by the information indicated by the at least two SRI fields, comprises:

if at least two SRI (SRI) domains exist in the at least two SRI domains, indicating the terminal equipment to use the first SRI domain for all PUSCH repeated transmission scheduled by the DCI;

and if at least two SRI domains indicate the same number of SRS resources, indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmissions scheduled by the DCI.
The method according to any one of claims 15 to 18, wherein,

if the information of the first SRI domain is used for all PUSCH repeated transmissions scheduled by the DCI, the information of a second SRI domain is not used for any PUSCH transmission, and the second SRI domain is an SRI domain of the at least two SRI domains except the first SRI domain.
The method according to any one of claims 15 to 19, wherein,

if the first SRI field is used for all PUSCH retransmission scheduled by the DCI and the DCI includes at least two TPC commands, a first TPC command is used for all PUSCH retransmission scheduled by the DCI, and the first TPC command is a TPC command associated with the first SRI field in the at least two TPC fields.
The method of claim 20, wherein the step of determining the position of the probe is performed,

the kth SRI domain in the DCI is associated with the kth TPC command in the DCI, wherein k is a positive integer;

or alternatively, the process may be performed,

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

The second TPC command in the at least two TPC domains is not used for power control of any PUSCH transmission,

or alternatively, the process may be performed,

the second TPC commands in the at least two TPC domains are used for power accumulation for a second closed loop power adjustment state, the second closed loop power adjustment state being a closed loop power adjustment state determined from information indicated by a second SRI domain;

wherein the second TPC command is a TPC command other than the first TPC command in the at least two TPC commands, and the second SRI domain is an SRI domain other than the first SRI domain in the at least two SRI domains.
The method according to any one of claims 15 to 19, wherein,

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

each TPC command of the at least two TPC commands is indicated by a different TPC field in the DCI, respectively;

or alternatively, the process may be performed,

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

an nth one of the at least two SRI domains, n being an integer greater than or equal to 1;

an SRI domain with the least number of SRS resources indicated in the at least two SRI domains;

an SRI domain with the largest SRS resource quantity indicated in the at least two SRI domains;

the at least two SRI domains indicating an SRI domain of a single SRS resource;

an SRI domain indicating a plurality of SRS resources among the at least two SRI domains;

an SRI domain indicating m SRS resources among the at least two SRI domains, m being an integer greater than or equal to 1;

an SRI domain selected from the at least two SRI domains.
The method of claim 25, wherein the SRI domain selected from the at least two SRI domains comprises:

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

or alternatively, the process may be performed,

and an SRI domain selected from the at least two SRI domains according to channel reciprocity and downlink channel information.
A terminal device, comprising:

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

And the processing module is used for determining that the at least two SRI domains are used for the PUSCH repeated transmission scheduled by the DCI according to the information indicated by the at least two SRI domains.
The terminal device of claim 27, wherein the terminal device,

the processing module is specifically configured to determine, according to the information indicated by the at least two SRI domains, whether the at least two SRI domains are used for different PUSCH retransmission scheduled by the DCI, or whether a first SRI domain of the at least two SRI domains is used for all PUSCH retransmission scheduled by the DCI.
The terminal device of claim 28, wherein the PUSCH retransmission is a codebook-based transmission;

the processing module is specifically configured to use the first SRI field for all PUSCH repeated transmissions 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, if the at least two SRI fields indicate a non-specific value, respectively use the at least two SRI fields for different PUSCH repeated transmissions scheduled by the DCI.
The terminal device of claim 29, wherein the terminal device,

the specific value is pre-agreed by the terminal equipment and the network equipment;

Or alternatively, the process may be performed,

the specific value is preconfigured for the network device.
The terminal device of claim 28, wherein the PUSCH retransmission is a non-codebook based transmission;

the processing module is specifically configured to use the first SRI domain for all PUSCH retransmission scheduled by the DCI if at least two SRIs in the at least two SRI domains indicate different numbers of SRS resources;

the processing module is specifically configured to, if the at least two SRI domains both indicate the same number of SRS resources, respectively use the at least two SRI domains for different PUSCH repeated transmissions scheduled by the DCI.
Terminal device according to any of the claims 28 to 31, characterized in that,

the processing module is further configured to, if the information of the first SRI domain is used for all PUSCH retransmission scheduled by the DCI, not use the information of a second SRI domain for any PUSCH retransmission, where the second SRI domain is an SRI domain of the at least two SRI domains other than the first SRI domain.
Terminal device according to any of the claims 28 to 32, characterized in that,

the processing module is further configured to use a first TPC command for all PUSCH retransmissions scheduled by the DCI if the first SRI field is used for all PUSCH retransmissions scheduled by the DCI and the DCI includes at least two TPC commands, where the first TPC command is a TPC command associated with the first SRI field in the at least two TPC fields.
The terminal device of claim 33, wherein the terminal device,

the kth SRI domain in the DCI is associated with the kth TPC command in the DCI, wherein k is a positive integer;

or alternatively, the process may be performed,

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

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

or alternatively, the process may be performed,

the second TPC commands in the at least two TPC domains are used for power accumulation for a second closed loop power adjustment state, the second closed loop power adjustment state being a closed loop power adjustment state determined from information indicated by a second SRI domain;

wherein the second TPC command is a TPC command other than the first TPC command in the at least two TPC commands, and the second SRI domain is an SRI domain other than the first SRI domain in the at least two SRI domains.
Terminal device according to any of the claims 28 to 32, characterized in that,

the processing module is further configured to, if the at least two SRI fields are respectively used for different PUSCH retransmission scheduled by the DCI and the DCI includes at least two TPC commands, respectively use the at least two TPC commands for different PUSCH retransmission scheduled by the DCI.
Terminal device according to any of the claims 33 to 36, characterized in that,

each TPC command of the at least two TPC commands is indicated by a different TPC field in the DCI, respectively;

or alternatively, the process may be performed,

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

an nth one of the at least two SRI domains, n being an integer greater than or equal to 1;

an SRI domain with the least number of SRS resources indicated in the at least two SRI domains;

an SRI domain with the largest SRS resource quantity indicated in the at least two SRI domains;

the at least two SRI domains indicating an SRI domain of a single SRS resource;

an SRI domain indicating a plurality of SRS resources among the at least two SRI domains;

an SRI domain indicating m SRS resources among the at least two SRI domains, m being an integer greater than or equal to 1;

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

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

Or alternatively, the process may be performed,

and an SRI domain selected from the at least two SRI domains according to channel reciprocity and downlink channel information.
A network device, comprising:

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

and indicating the terminal equipment to use the at least two SRI domains for the PUSCH repeated transmission scheduled by the DCI through the information indicated by the at least two SRI domains.
The network device of claim 40, wherein,

and indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmission scheduled by the DCI or indicating the terminal equipment to use the first SRI domain in the at least two SRI domains for all PUSCH repeated transmission scheduled by the DCI through the information indicated by the at least two SRI domains.
The network device of claim 41, wherein the PUSCH retransmission is a codebook-based transmission;

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

And if the at least two SRI domains indicate non-specific values, indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmissions scheduled by the DCI.
The network device of claim 42,

the specific value is pre-agreed by the terminal equipment and the network equipment;

or alternatively, the process may be performed,

the specific value is preconfigured for the network device.
The network device of claim 41, wherein the PUSCH retransmission is a non-codebook based transmission;

if at least two SRI (SRI) domains exist in the at least two SRI domains, indicating the terminal equipment to use the first SRI domain for all PUSCH repeated transmission scheduled by the DCI;

and if the at least two SRI domains indicate the same number of SRS resources, indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmissions scheduled by the DCI.
The network device of any one of claims 41 to 44,

if the information of the first SRI domain is used for all PUSCH repeated transmissions scheduled by the DCI, the information of a second SRI domain is not used for any PUSCH transmission, and the second SRI domain is an SRI domain of the at least two SRI domains except the first SRI domain.
The network device of any one of claims 41 to 45,

if the first SRI field is used for all PUSCH retransmission scheduled by the DCI and the DCI includes at least two TPC commands, a first TPC command is used for all PUSCH retransmission scheduled by the DCI, and the first TPC command is a TPC command associated with the first SRI field in the at least two TPC fields.
The network device of claim 46, wherein the network device,

the kth SRI domain in the DCI is associated with the kth TPC command in the DCI, wherein k is a positive integer;

or alternatively, the process may be performed,

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

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

or alternatively, the process may be performed,

the second TPC commands in the at least two TPC domains are used for power accumulation for a second closed loop power adjustment state, the second closed loop power adjustment state being a closed loop power adjustment state determined from information indicated by a second SRI domain;

Wherein the second TPC command is a TPC command other than the first TPC command in the at least two TPC commands, and the second SRI domain is an SRI domain other than the first SRI domain in the at least two SRI domains.
The network device of any one of claims 41 to 45,

and if the at least two SRI domains are respectively used for different PUSCH repeated transmissions scheduled by the DCI and the DCI comprises at least two TPC commands, respectively using the at least two TPC commands for the different PUSCH repeated transmissions scheduled by the DCI.
The network device of claim 46 to 49, wherein,

each TPC command of the at least two TPC commands is indicated by a different TPC field in the DCI, respectively;

or alternatively, the process may be performed,

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

an nth one of the at least two SRI domains, n being an integer greater than or equal to 1;

an SRI domain with the least number of SRS resources indicated in the at least two SRI domains;

an SRI domain with the largest SRS resource quantity indicated in the at least two SRI domains;

The at least two SRI domains indicating an SRI domain of a single SRS resource;

an SRI domain indicating a plurality of SRS resources among the at least two SRI domains;

an SRI domain indicating m SRS resources among the at least two SRI domains, m being an integer greater than or equal to 1;

an SRI domain selected from the at least two SRI domains.
The network device of claim 51, wherein the SRI domain selected from the at least two SRI domains comprises:

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

or alternatively, the process may be performed,

and an SRI domain selected from the at least two SRI domains according to channel reciprocity and downlink channel information.
A terminal device, comprising:

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

and the processor is used for determining that the at least two SRI domains are used for the PUSCH repeated transmission scheduled by the DCI according to the information indicated by the at least two SRI domains.
The terminal device of claim 53, wherein,

and the processor is specifically configured to determine whether to use the at least two SRI domains for different PUSCH retransmission scheduled by the DCI or use a first SRI domain of the at least two SRI domains for all PUSCH retransmission scheduled by the DCI according to information indicated by the at least two SRI domains.
The terminal device of claim 54, wherein the PUSCH retransmission is a codebook-based transmission;

the processor is specifically configured to use the first SRI field for all PUSCH repeated transmissions 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 repeated transmissions scheduled by the DCI, respectively, if the at least two SRI fields indicate a non-specific value.
The terminal device of claim 55, wherein the wireless communication network comprises a wireless communication network,

the specific value is pre-agreed by the terminal equipment and the network equipment;

or alternatively, the process may be performed,

the specific value is preconfigured for the network device.
The terminal device of claim 54, wherein the PUSCH retransmission is a non-codebook based transmission;

the processor is specifically configured to use the first SRI domain for all PUSCH retransmission scheduled by the DCI if at least two SRIs in the 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 repetition transmissions scheduled by the DCI if the at least two SRI fields both indicate the same number of SRS resources.
The terminal device of any of claims 54 to 57, wherein,

the processor is further configured to, if the information of the first SRI domain is used for all PUSCH retransmission scheduled by the DCI, not use the information of a second SRI domain for any PUSCH retransmission, where the second SRI domain is an SRI domain of the at least two SRI domains other than the first SRI domain.
The terminal device of any of claims 54 to 58, wherein,

the processor is further configured to use a first TPC command for all PUSCH retransmissions scheduled by the DCI if the first SRI field is used for all PUSCH retransmissions scheduled by the DCI and the DCI includes at least two TPC commands, where the first TPC command is a TPC command associated with the first SRI field among the at least two TPC fields.
The terminal device of claim 59, wherein,

the kth SRI domain in the DCI is associated with the kth TPC command in the DCI, wherein k is a positive integer;

or alternatively, the process may be performed,

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

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

or alternatively, the process may be performed,

the second TPC commands in the at least two TPC domains are used for power accumulation of a second closed loop power adjustment state, the second closed loop power adjustment state being a closed loop power adjustment state determined from information indicated by the second SRI domain;

wherein the second TPC command is a TPC command other than the first TPC command in the at least two TPC commands, and the second SRI domain is an SRI domain other than the first SRI domain in the at least two SRI domains.
The terminal device of any of claims 54 to 58, wherein,

the processor is further configured to, if the at least two SRI fields are respectively used for different PUSCH retransmission scheduled by the DCI and the DCI includes at least two TPC commands, respectively use the at least two TPC commands for different PUSCH retransmission scheduled by the DCI.
The terminal device of any of claims 59 to 62,

each TPC command of the at least two TPC commands is indicated by a different TPC field in the DCI, respectively;

Or alternatively, the process may be performed,

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

an nth one of the at least two SRI domains, n being an integer greater than or equal to 1;

an SRI domain with the least number of SRS resources indicated in the at least two SRI domains;

an SRI domain with the largest SRS resource quantity indicated in the at least two SRI domains;

the at least two SRI domains indicating an SRI domain of a single SRS resource;

an SRI domain indicating a plurality of SRS resources among the at least two SRI domains;

an SRI domain indicating m SRS resources among the at least two SRI domains, m being an integer greater than or equal to 1;

an SRI domain selected from the at least two SRI domains.
The terminal device of claim 64, wherein the selected one of the at least two SRI domains comprises:

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

or alternatively, the process may be performed,

and an SRI domain selected from the at least two SRI domains according to channel reciprocity and downlink channel information.
A network device, comprising:

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

And indicating the terminal equipment to use the at least two SRI domains for the PUSCH repeated transmission scheduled by the DCI through the information indicated by the at least two SRI domains.
The network device of claim 66, wherein the information indicated by the at least two SRI fields instructs the terminal device to use the at least two SRI fields for PUSCH repetition transmission for the DCI schedule, comprising:

and indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmission scheduled by the DCI or indicating the terminal equipment to use the first SRI domain in the at least two SRI domains for all PUSCH repeated transmission scheduled by the DCI through the information indicated by the at least two SRI domains.
The network device of claim 67, wherein the PUSCH retransmission is a codebook-based transmission;

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

or alternatively, the process may be performed,

and if the at least two SRI domains indicate non-specific values, indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmissions scheduled by the DCI.
The network device of claim 68,

the specific value is pre-agreed by the terminal equipment and the network equipment;

or alternatively, the process may be performed,

the specific value is preconfigured for the network device.
The network device of claim 67, wherein the PUSCH retransmission is a non-codebook based transmission;

if at least two SRI (SRI) domains exist in the at least two SRI domains, indicating the terminal equipment to use the first SRI domain for all PUSCH repeated transmission scheduled by the DCI;

and if at least two SRI domains indicate the same number of SRS resources, indicating the terminal equipment to respectively use the at least two SRI domains for different PUSCH repeated transmissions scheduled by the DCI.
The network device of any one of claims 67 to 70,

if the information of the first SRI domain is used for all PUSCH repeated transmissions scheduled by the DCI, the information of a second SRI domain is not used for any PUSCH transmission, and the second SRI domain is an SRI domain of the at least two SRI domains except the first SRI domain.
The network device of any one of claims 66 to 71,

If the first SRI field is used for all PUSCH retransmission scheduled by the DCI and the DCI includes at least two TPC commands, a first TPC command is used for all PUSCH retransmission scheduled by the DCI, and the first TPC command is a TPC command associated with the first SRI field in the at least two TPC fields.
The network device of claim 72,

the kth SRI domain in the DCI is associated with the kth TPC command in the DCI, wherein k is a positive integer;

or alternatively, the process may be performed,

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

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

or alternatively, the process may be performed,

the second TPC commands in the at least two TPC domains are used for power accumulation for a second closed loop power adjustment state, the second closed loop power adjustment state being a closed loop power adjustment state determined from information indicated by a second SRI domain;

wherein the second TPC command is a TPC command other than the first TPC command in the at least two TPC commands, and the second SRI domain is an SRI domain other than the first SRI domain in the at least two SRI domains.
The network device of any one of claims 74 to 70,

and if the at least two SRI domains are respectively used for different PUSCH repeated transmissions scheduled by the DCI and the DCI comprises at least two TPC commands, respectively using the at least two TPC commands for the different PUSCH repeated transmissions scheduled by the DCI.
The network device of claim 72 to 75, wherein,

each TPC command of the at least two TPC commands is indicated by a different TPC field in the DCI, respectively;

or alternatively, the process may be performed,

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

an nth one of the at least two SRI domains, n being an integer greater than or equal to 1;

an SRI domain with the least number of SRS resources indicated in the at least two SRI domains;

an SRI domain with the largest SRS resource quantity indicated in the at least two SRI domains;

the at least two SRI domains indicating an SRI domain of a single SRS resource;

an SRI domain indicating a plurality of SRS resources among the at least two SRI domains;

an SRI domain indicating m SRS resources among the at least two SRI domains, m being an integer greater than or equal to 1;

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

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

or alternatively, the process may be performed,

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