WO2021155788A1

WO2021155788A1 - Pusch transmission method, pusch transmission control method, and related device

Info

Publication number: WO2021155788A1
Application number: PCT/CN2021/074883
Authority: WO
Inventors: 宋扬; 孙鹏
Original assignee: 维沃移动通信有限公司
Priority date: 2020-02-07
Filing date: 2021-02-02
Publication date: 2021-08-12
Also published as: CN113259073A; CN113259073B

Abstract

The present invention provides a PUSCH transmission method, a PUSCH transmission control method, and a related device. The method comprises: receiving M pieces of Downlink Control Information (DCI), the M pieces of DCI being used for scheduling M PUSCHs; and sending the M PUSCHs; wherein the M pieces of DCI belong to K control resource sets, the K control resource sets are associated with N control resource set group identifiers, M is an integer greater than 1, K is a positive integer less than or equal to N, and N is a positive integer; the M pieces of DCI satisfy that: a Hybrid Automatic Repeat Request (HARQ) process identifier is the same, and a New Data Indication (NDI) is the same.

Description

PUSCH transmission method, PUSCH transmission control method and related equipment

Cross-references to related applications

This application claims the priority of Chinese Patent Application No. 202010083025.8 filed in China on February 7, 2020, the entire content of which is incorporated herein by reference.

Technical field

The present invention relates to the field of communication technology, in particular to a PUSCH transmission method, a PUSCH transmission control method and related equipment.

Background technique

In the current communication system, in order to ensure the reliability of communication, usually one or multiple transmissions can be set for the same uplink transmission. For example, for ultra-reliable and low-latency communications (Ultra-reliable and Low Latency Communications, URLLC) physical uplink shared channel (Physical Uplink Shared Channel, PUSCH) transmission, usually by a downlink control information (Downlink Control Information, DCI) Indicates the transmission parameters such as the time-frequency resource and the nominal number of repetitions for the first PUSCH transmission. When the terminal and the network device miss the DCI reception or PUSCH transmission for reasons such as blocking, the PUSCH reception performance will be affected, and the reliability of PUSCH transmission will be low.

Summary of the invention

The embodiments of the present invention provide a PUSCH transmission method, a PUSCH transmission control method and related equipment to solve the problem of low reliability of PUSCH transmission.

In the first aspect, an embodiment of the present invention provides a physical uplink shared channel PUSCH transmission method, which is executed by a terminal, and includes:

Receiving M downlink control information DCIs, where the M DCIs are used to schedule M PUSCHs;

Sending the M PUSCHs;

Wherein, the M DCIs belong to K control resource sets, the K control resource sets are associated with N control resource set group identities, M is an integer greater than 1, K is a positive integer less than or equal to N, and N It is a positive integer; the M DCIs satisfy: the hybrid automatic repeat request HARQ process identifier is the same; and the new data indicates that the NDI is the same.

In the second aspect, embodiments of the present invention provide a physical uplink shared channel PUSCH transmission control method, which is applied to network equipment, and includes:

Sending M downlink control information DCIs to the terminal, where the M DCIs are used to schedule M PUSCHs;

In a third aspect, an embodiment of the present invention provides a terminal, including:

A receiving module, configured to receive M downlink control information DCIs, and the M DCIs are used to schedule M PUSCHs;

The first sending module is configured to send the M PUSCHs;

In a fourth aspect, an embodiment of the present invention provides a network device, including:

The second sending module is configured to send M downlink control information DCIs to the terminal, where the M DCIs are used to schedule M PUSCHs;

In a fifth aspect, an embodiment of the present invention provides a terminal, including: a memory, a processor, and a program stored in the memory and capable of running on the processor, and when the program is executed by the processor, the foregoing The steps in the physical uplink shared channel PUSCH transmission method.

In a sixth aspect, an embodiment of the present invention provides a network device, including: a memory, a processor, and a program that is stored on the memory and can run on the processor, and is implemented when the program is executed by the processor The steps in the above physical uplink shared channel PUSCH transmission control method.

In a seventh aspect, an embodiment of the present invention provides a computer-readable storage medium having a computer program stored on the computer-readable storage medium, and when the computer program is executed by a processor, the steps of the above physical uplink shared channel PUSCH transmission method are implemented , Or when the computer program is executed by a processor, the steps of the above physical uplink shared channel PUSCH transmission control method are implemented.

In the embodiment of the present invention, by receiving M downlink control information DCIs, the M DCIs are used to schedule M PUSCHs; sending the M PUSCHs; wherein, the M DCIs belong to K control resource sets, and the K N control resource sets are associated with N control resource set group identities, M is an integer greater than 1, K is a positive integer less than or equal to N, and N is a positive integer; the M DCI satisfy: Hybrid automatic repeat request HARQ process The identifiers are the same; and the new data indicates that the NDI is the same. Since the terminal can transmit the PUSCH after receiving any one of the M DCIs, the reliability of DCI reception can be ensured, and the reliability of PUSCH transmission can be improved. At the same time, at least two PUSCHs can be sent, thereby improving the reliability of the network device to receive the PUSCH. Therefore, the embodiment of the present invention improves the reliability of PUSCH transmission and reduces the transmission delay of PUSCH.

Description of the drawings

In order to explain the technical solutions of the embodiments of the present invention more clearly, the following will briefly introduce the drawings used in the description of the embodiments of the present invention. Obviously, the drawings in the following description are only some embodiments of the present invention. It is understandable that other drawings can be obtained based on these drawings.

Figure 1 is a structural diagram of a network system applicable to an embodiment of the present invention;

Figure 2 is a flowchart of a PUSCH transmission method provided by an embodiment of the present invention;

FIG. 3 is an exemplary diagram of PUSCH transmission in a PUSCH transmission method provided by an embodiment of the present invention;

4 is a flowchart of a PUSCH transmission control method provided by an embodiment of the present invention;

Figure 5 is a structural diagram of a terminal provided by an embodiment of the present invention;

Figure 6 is a structural diagram of a network device provided by an embodiment of the present invention;

FIG. 7 is a structural diagram of another terminal provided by an embodiment of the present invention;

Fig. 8 is a structural diagram of another network device provided by an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative work shall fall within the protection scope of the present invention.

The term "including" in the specification and claims of this application and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not necessarily limited to clear Instead, those steps or units listed below may include other steps or units that are not clearly listed or are inherent to these processes, methods, products, or equipment. In addition, the use of "and/or" in the specification and claims means at least one of the connected objects, such as A and/or B, which means that A and B alone are included, and there are three cases for both A and B.

In the embodiments of the present invention, words such as "for example" are used as examples, illustrations, or illustrations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present invention should not be construed as being more preferable or advantageous than other embodiments or design solutions. To be precise, words such as "exemplary" or "for example" are used to present related concepts in a specific manner.

The embodiments of the present invention will be described below in conjunction with the drawings. The PUSCH transmission method, PUSCH transmission control method, and related equipment provided by the embodiments of the present invention can be applied to a wireless communication system. The wireless communication system may be a 5G system, or an evolved Long Term Evolution (eLTE) system, or a subsequent evolved communication system.

Please refer to FIG. 1. FIG. 1 is a structural diagram of a network system applicable to an embodiment of the present invention. As shown in FIG. 1, it includes a terminal (User Equipment, UE) 11 and a network device 12, where the terminal 11 may be a user Terminals or other terminal-side devices, such as: mobile phones, tablet computers (Personal Computer), laptop computers (Laptop Computer), personal digital assistants (personal digital assistant, PDA), mobile Internet devices (Mobile Internet Device, MID) or For terminal-side devices such as wearable devices (Wearable Device), it should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present invention. The above-mentioned network device 12 may be a 5G base station, or a later version base station, or a base station in other communication systems, or it is called Node B, Evolved Node B, or Transmission Reception Point (TRP), or access point (Access Point, AP), or other vocabulary in the field, as long as the same technical effect is achieved, the network device is not limited to a specific technical vocabulary. In addition, the aforementioned network device 12 may be a master node (Master Node, MN) or a secondary node (Secondary Node, SN). It should be noted that, in the embodiment of the present invention, only a 5G base station is taken as an example, but the specific type of network equipment is not limited.

Please refer to FIG. 2. FIG. 2 is a flowchart of a physical uplink shared channel PUSCH transmission method according to an embodiment of the present invention. The method is applied to a terminal, as shown in FIG. 2, and includes the following steps:

Step 201: Receive M downlink control information DCIs, where the M DCIs are used to schedule M PUSCHs;

Step 202: Send the M PUSCHs;

Wherein, the M DCIs belong to K control resource sets, the K control resource sets are associated with N control resource set group identities, M is an integer greater than 1, K is a positive integer less than or equal to N, and N It is a positive integer; the M DCIs satisfy: the hybrid automatic repeat request (HARQ) process identifier is the same; and the new data indicator (New Data Indicator, NDI) is the same.

In the embodiment of the present invention, the network device sends M DCIs to the terminal, and the network device may include one or more TRPs. The foregoing M DCIs may come from the same TRP or different TRPs, that is, one or more TRPs send M DCIs to the terminal to schedule M PUSCH transmissions. Among them, one TRP can send one or more DCIs to the terminal to schedule the terminal to send one or more PUSCHs.

Take M equal to 2 as an example. The two DCIs received can belong to the same control resource set (CORESET), or they can belong to different control resource sets; when the two DCIs belong to different control resource sets, the two control resource sets can be The same control resource set group identifier (for example, the high-level parameter CORESETPoolIndex) is associated, and can also be associated with different control resource set group identifiers. Optionally, one control resource set group identifier corresponds to one TRP. That is, one or more control resource sets of each TRP are associated with the same control resource set group identifier, and the control resource sets of different TRPs are associated with different control resource set group identifiers.

Optionally, the redundancy version (Redundancy Version, RV) of the transport block (Transport, block, TB) carried in the PUSCH sent by the terminal to one or more TRPs may be the same or different.

In the embodiment of the present invention, when N is equal to 1, the same TRP can send M DCIs within a period of time to schedule the terminal to send M PUSCH transmissions without having to determine whether each PUSCH transmission is correct and then schedule retransmissions. Avoid the need to retransmit DCI scheduling PUSCH retransmission due to poor channel quality in time, such as short-term occlusion or deep channel fading, resulting in the terminal not detecting a certain DCI or PUSCH transmission error, thereby improving the DCI transmission and PUSCH transmission reliability.

When N is greater than 1, the terminal receives M DCIs sent from multiple TRPs, and sends M PUSCH transmissions to the TRP based on the M DCIs. In this way, when the terminal is obscured with one of the TRPs, it can also receive DCIs from other TRPs. Or send PUSCH to other TRPs, which can further effectively improve the reliability of DCI transmission and PUSCH transmission, and ensure the demand for URLLC service transmission.

For example, each TRP sends a physical downlink control channel (PDCCH) in its own control resource set (each control resource set is associated with a different identifier to distinguish the TRP, for example, the control resource set group identifier), which can be scheduled One PUSCH, the PUSCH may include one or more PUSCH transmissions of the same transport block (Transport Block, TB) according to configuration or instructions. When multiple PUSCH transmissions are included, each PUSCH transmission is a different RV version of a TB. One PUSCH scheduled by each TRP is sent according to the configuration or instruction using the power control parameters and beam space relationship corresponding to the TRP.

Optionally, the time interval between the reception time of the first DCI and the reception time of the second DCI is less than a first preset value;

And/or, the time interval between the reception time of the first DCI and the reception time of the second DCI is greater than a second preset value, and the first preset value is greater than the second preset value;

Wherein, the first DCI and the second DCI are DCIs received twice adjacently among the M DCIs, or the first DCI is the earliest DCI received among the M DCIs, so The second DCI is the latest DCI received among the M DCIs.

In the embodiment of the present invention, the foregoing M DCIs can be understood as DCIs with the same HARQ process ID (HARQ process ID) and the same NDI (that is, non-inverted) on the indicated PUSCH received within a period of time, and the first DCI is the The DCI received earliest among the M DCIs, the second DCI is the DCI received the latest among the M DCIs, for example, the start symbol or the end symbol of the PDCCH where the first DCI is located and the PDCCH where the second DCI is located The start symbol or end symbol interval of is less than or equal to the first preset value (for example, T symbols); another understanding is: after the terminal receives and detects the first DCI, it determines the PDCCH where the first DCI is located Start symbol or end symbol, and within the following T symbols, the DCI with the same HARQ process identifier and the same NDI as the first DCI can be received; after the following T symbols, the terminal does not expect to receive any more data. The first DCI has the same HARQ process ID and the same NDI DCI, or after T symbols thereafter, the terminal does not process the received DCI that has the same HARQ process ID and the same NDI as the first DCI.

The time interval between the receiving time of the first DCI and the receiving time of the second DCI is less than the first preset value, thereby avoiding the transmitted TB from occupying the buffer for a long time. Therefore, the embodiment of the present invention improves the utilization of the buffer and reduces the complexity of the terminal. .

Optionally, the M DCIs satisfy at least one of the following:

The indicated time-frequency resources are the same or different in size;

The indicated modulation and coding scheme (Modulation and Coding Scheme, MCS) are the same or different.

In this embodiment, the time-frequency resource sizes indicated by any two DCIs are the same or different, and any two DCIs indicate the same or different MCS modulation and coding schemes. For example, in an embodiment, the size of the time-frequency resources indicated by the M DCIs is the same, and the indicated modulation and coding scheme MCS are the same.

In an embodiment, the M PUSCHs include a first PUSCH and a second PUSCH, the DCI scheduling the first PUSCH belongs to the first control resource set, and the DCI scheduling the second PUSCH belongs to the second control resource Set, the control resource set group identifiers associated with the first control resource set and the second control resource set are different. In other words, in this embodiment, the first PUSCH and the second PUSCH are sent to different TRPs.

Optionally, the start symbol of the first PUSCH is before the end symbol of the second PUSCH and after the start symbol of the second PUSCH.

The foregoing transmission of one PUSCH may be understood as one PUSCH transmission or multiple PUSCH repeated transmissions, which is not further limited here. As shown in FIG. 3, the foregoing first PUSCH transmission may include L1 PUSCH transmissions, and the second PUSCH transmission may include L2 PUSCH transmissions. Among them, the L1 PUSCH transmission can be continuous, or there can be a certain time interval between two adjacent transmissions; the same L2 PUSCH transmission can be continuous, or there can be a certain interval between two adjacent transmissions. Time interval. The start symbol of the first PUSCH can be understood as the start symbol of the first PUSCH transmission in the L1 PUSCH transmission, and the start symbol of the second PUSCH can be understood as the start of the first PUSCH transmission in the L2 PUSCH transmission. Symbol, the end symbol of the second PUSCH can be understood as the end symbol of the last PUSCH transmission in the L2 PUSCH transmission.

In other words, in the embodiment of the present invention, the terminal can be identified by the Cell Radio Network Temporary Identifier (C-RNTI) or Modulation and Coding Scheme before the end of one PUSCH transmission. The coding scheme-C-RNTI, MCS-C-RNTI) scrambling DCI (format 0_0 or 0_1) schedules another PUSCH of the same HARQ process and NDI.

Further, the power control parameter of the PUSCH is determined by a target power control parameter, and the target power control parameter is the power control parameter corresponding to the control resource set group identifier associated with the control resource set to which the target DCI belongs; the target DCI is Scheduling the DCI of the PUSCH.

Among them, the power control parameters include open-loop power control parameters and closed-loop power control parameters. It should be understood that the open-loop power control parameter corresponding to each control resource set group identifier is configured by a higher layer parameter. In this embodiment, the open loop power control parameter is a target open loop power control parameter, the control resource set group identifier corresponding to the target open loop power control parameter and the control resource set group associated with the DCI ownership control resource set The identity is the same.

Optionally, in an embodiment, the DCI carries the closed-loop power control parameter, and the closed-loop power control parameter is used to control the transmission power of the PUSCH scheduled by the DCI.

Further, the DCI carries indication information, the indication information is used to control the transmission of the PUSCH scheduled by the DCI, and the indication information includes a sounding reference signal resource indicator (Sounding Reference Signal resource indicator, SRI) and/or transmission Precoding matrix indicator (Transmit Precoding Matrix Indicator, TPMI).

The SRI is used to indicate the SRS resource of the target SRS resource group, and the control resource set group identifier corresponding to the target SRS resource group is the same as the control resource set group identifier associated with the DCI attributed control resource set.

In this embodiment, the closed-loop power control parameters and indication information carried by the DCI are used to adjust the transmission of the PUSCH scheduled by the DCI.

Optionally, in an embodiment, before the sending the M PUSCHs, the method further includes:

Determine the spatial relationship of the PUSCH transmission.

In the embodiment of the present invention, the spatial relationship of the PUSCH transmission scheduled by each DCI may be determined by the DCI. Specifically, in the case of the SRI carried in the DCI of the scheduled PUSCH, the PUSCH transmission is determined according to the SRI. Spatial relationship; in the case of scheduling SRI that is not carried in the DCI of the PUSCH, the default spatial relationship is determined as the spatial relationship of the PUSCH transmission.

Optionally, the above-mentioned default spatial relationship can be determined according to actual needs. For example, in one embodiment, the default spatial relationship corresponds to the space of the target physical uplink control channel (PUCCH) resource. relation. In another embodiment, the default spatial relationship corresponds to the transmission configuration indicator (Transmission Configuration Indicator, TCI) state or Quasi co-location (Quasi co-location) of the control resource set with the smallest index in the target control resource set group identifier. location, QCL). The target PUCCH resource is the PUCCH resource with the smallest index among the PUCCH resources corresponding to the target control resource set group identifier, and the target control resource set group identifier is the control resource set group identifier associated with the control resource set to which the DCI belongs.

In this embodiment, in the case of scheduling the SRI that is not carried in the DCI of the PUSCH, which default spatial relationship the terminal uses as the spatial relationship for PUSCH transmission can be determined according to the currently met conditions.

For example, in a case where the first preset condition is met, the default spatial relationship corresponds to the spatial relationship of the target physical uplink control channel PUCCH resource;

In the case that the second preset condition is met, the default spatial relationship corresponds to the transmission configuration indication of the control resource set with the smallest index in the target control resource set group identification TCI state or quasi co-located QCL.

Optionally, the first preset condition includes:

The preset high-level parameters are not configured, or the preset high-level parameters are not enabled;

The PUCCH resource corresponding to the target control resource set group identifier is configured for the terminal on the activated uplink bandwidth part (Bandwidth Part, BWP);

Among the PUCCH resources corresponding to the target control resource set group identifier, some or all of the PUCCH resources are configured with a spatial relationship.

The preset high-level parameter can be expressed as "enableDefaultBeamPlForPUSCH0_0". For the solution that satisfies the above first preset condition, it can be understood that the high-level parameters "enableDefaultBeamPlForPUSCH0_0" or "enableDefaultBeamPlForPUSCH0_0" are not configured, and PUCCH resources are configured for the UE on the activated uplink BWP (associated with the target control resource set group identifier) Corresponding PUCCH resource) and the PUCCH resource is configured with a spatial relationship, the spatial relationship of the PUSCH transmission scheduled by the DCI corresponds to the spatial relationship of the PUCCH resource associated with the smallest index of the target control resource set group identifier.

The second preset condition includes:

The preset high-level parameters are enabled;

The PUCCH resource corresponding to the target control resource set group identifier is not configured for the terminal on the activated uplink BWP; or the PUCCH resource corresponding to the target control resource set group identifier is configured for the terminal on the activated uplink BWP, and the target control resource The PUCCH resource corresponding to the set group identifier is not configured with a spatial relationship.

Wherein, in the case that the second preset condition includes activating the uplink BWP and the PUCCH resource corresponding to the target control resource set group identifier is not configured for the terminal, the default path loss reference signal (Path loss) of the power control parameter of the PUSCH Loss Reference Signal, PL RS) is: the RS corresponding to the TCI state of the control resource set with the smallest index in the target control resource set group identifier or the RS corresponding to the QCL type D of the QCL (ie, QCL Type-D RS).

In the embodiment of the present invention, in the case where the foregoing second preset condition includes activating the uplink BWP and the PUCCH resource corresponding to the target control resource set group identifier is not configured for the terminal, it is understandable for the solution that satisfies the foregoing second preset condition It is: when the high-level parameter "enableDefaultBeamPlForPUSCH0_0" is enabled, and the PUCCH resource (associated to the PUCCH resource corresponding to the target control resource set group identifier) is not configured for the UE on the uplink BWP and the UE is in the RRC connected state, the spatial relationship of PUSCH transmission Refer to an RS, which is the QCL of the control resource set associated with the minimum control resource set index of the target control resource set group identifier. The QCL hypothesis corresponds to the RS of QCL Type-D (that is, the default spatial relationship corresponds to the cell where the PDCCH of the PUSCH is scheduled. The activated downlink BWP is associated with the TCI state or QCL of the control resource set with the smallest control resource set index identified by the target control resource set group. The default PL RS (used for power control) is the RS or QCL Type-D RS of the QCL corresponding to the TCI state of the control resource set indexed by the minimum control resource set index identified by the target control resource set group.

In the case where the foregoing second preset condition includes that the PUCCH resource corresponding to the target control resource set group identifier is configured for the terminal on the activation of the uplink BWP, and the PUCCH resource corresponding to the target control resource set group identifier is not configured with a spatial relationship, For the solution that meets the above second preset condition, it can be understood as: the high-level parameter "enableDefaultBeamPlForPUSCH0_0" is enabled, and PUCCH resources are configured for the UE on the uplink BWP, but all PUCCH resources are not configured with spatial relationships and the terminal is in RRC connection State, the spatial relationship of PUSCH transmission and/or PL RS refers to an RS, which is related to the QCL of the control resource set with the smallest control resource set index in the control resource set identified by the target control resource set group. Assume the corresponding QCL Type-D RS.

In other words, the spatial relationship of PUSCH transmission refers to the default spatial relationship and/or PL RS associated with the PUCCH identified by the target control resource set group, that is, the spatial setting (spatial relationship) of PUCCH corresponds to activation on the primary serving cell (PCell) The space setting (TCI state or QCL) received in the PDCCH sent in the control resource set of the minimum control resource set index associated with the target control resource set group identifier in the downlink BWP.

In order to better understand the present invention, the specific implementation of the present invention will be described in detail below.

Each TRP sends a physical downlink control channel (PDCCH) in its own control resource set (each control resource set is associated with a different identifier to distinguish the TRP, for example, the control resource set group identifier) to send a physical downlink control channel (PDCCH) to schedule a PUSCH The PUSCH may include one or multiple PUSCH transmissions of the same transport block (Transport Block, TB) according to the configuration or instruction. When multiple PUSCH transmissions are included, each PUSCH transmission is a different RV version of a TB. One PUSCH scheduled by each TRP is sent according to the configuration or instruction using the power control parameters and beam spatial relationship corresponding to the TRP.

The specific plan is as follows:

The UE receives at least two DCIs.

Optionally, the two DCIs belong to different control resource sets, and the control resource sets correspond to different control resource set group identifiers (TRP IDs used to distinguish TRPs, such as high-level parameters CORESETPoolIndex).

Optionally, the at least two DCI scheduled PUSCHs have the same HARQ process identifier and the same NDI (that is, not flipped).

Optionally, the time interval of the at least two DCIs satisfies a certain threshold, for example, less than a predefined time (for example, within a time slot), greater than a predefined time, and so on.

Optionally, the time-frequency resource sizes (number of REs) indicated by the at least two DCIs are the same, and the MCS is the same.

Optionally, the UE can schedule another PUSCH of the same HARQ process and NDI by DCI (format 0_0 or 0_1) scrambled by C-RNTI or MSC-C-RNTI before one PUSCH transmission ends.

Optionally, the power control of one PUSCH transmission is determined by the power control parameter corresponding to the TRP ID (for example, the control resource set group identifier) associated with the control resource set to which the DCI scheduling the PUSCH belongs.

Among them, the high-level parameters include open-loop power control parameters corresponding to two CORESETPoolIndex (for example, the high-level parameter PUSCH-PowerControl). The closed-loop power control indicator, SRI, and TPMI in the DCI only adjust the PUSCH scheduled by the DCI that is centrally transmitted by the control resource that belongs to the same TRP ID as the DCI.

Optionally, determine a default spatial relation information (spatial relation) for PUSCH transmission. For example, when there is no SRI indication in the DCI format 0_0 (DCI format 0_0) scheduling, or the high-level parameters are not configured with SRS, in the multi-TRP scenario, when the multi-DCI scheduling transmits multiple PUSCHs on the activated BWP, if the DCI of the PUSCH is scheduled The spatial relationship of the PUSCH transmission is determined by the SRI indication in the DCI; if there is no SRI carried in the DCI of the scheduled PUSCH (for example, DCI format 0_0), the spatial relationship of the PUSCH transmission should satisfy:

1. The high-level parameters "enableDefaultBeamPlForPUSCH0_0" or "enableDefaultBeamPlForPUSCH0_0" are not configured, and PUCCH resources (associated to the PUCCH resources corresponding to the target control resource set group identifier) are configured for the UE on the activated uplink BWP, and the PUCCH resources are configured with a spatial relationship , The spatial relationship of the PUSCH transmission scheduled by the DCI corresponds to the spatial relationship of the PUCCH resource associated with the smallest index of the target control resource set group identifier.

2. The high-level parameter "enableDefaultBeamPlForPUSCH0_0" is enabled, and no PUCCH resource is configured for the UE on the uplink BWP (associated with the PUCCH resource corresponding to the target control resource set group identifier) and the UE is in the RRC connected state, the spatial relationship of PUSCH transmission Refer to an RS, which is the QCL of the control resource set associated with the minimum control resource set index of the target control resource set group identifier. The QCL hypothesis corresponds to the RS of QCL Type-D (that is, the default spatial relationship corresponds to the cell where the PDCCH of the PUSCH is scheduled. The activated downlink BWP is associated with the TCI state or QCL of the control resource set with the minimum control resource set index identified by the target control resource set group). The default PL RS (used for power control) is the RS or QCL Type-D RS of the QCL corresponding to the TCI state of the control resource set indexed by the minimum control resource set index identified by the target control resource set group.

3. The high-level parameter "enableDefaultBeamPlForPUSCH0_0" is enabled, and PUCCH resources are configured for the UE on the uplink BWP, but all PUCCH resources are not configured with spatial relationships and the terminal is in RRC connection state, the spatial relationship and/or PL RS of PUSCH transmission With reference to an RS, the RS is an RS of QCL Type-D that is associated with the QCL hypothesis of the control resource set of the smallest control resource set index in the control resource set identified by the target control resource set group.

In other words, the spatial relationship of PUSCH transmission refers to the default spatial relationship and/or PL RS associated with the PUCCH identified by the target control resource set group, that is, the spatial setting of the PUCCH corresponds to the activated downlink BWP on the PCell that is associated with the target control resource set. The space setting (TCI state or QCL) received by the PDCCH sent in the control resource set of the minimum control resource set index of the group identifier.

Please refer to FIG. 4. FIG. 4 is a flowchart of a PUSCH transmission control method according to an embodiment of the present invention. The method is applied to a network device. As shown in FIG. 4, it includes the following steps:

Step 401: Send M downlink control information DCIs to the terminal, where the M DCIs are used to schedule M PUSCHs;

Optionally, N is an integer greater than 1.

And/or, the time interval between the receiving time of the first DCI and the receiving time of the second DCI is greater than a second preset value, and the first preset value is greater than the second preset value;

Optionally, the M DCIs satisfy at least one of the following:

The indicated time-frequency resources are the same or different in size;

The indicated modulation and coding scheme MCS are the same or different.

Optionally, the M PUSCHs include a first PUSCH and a second PUSCH, the DCI scheduling the first PUSCH belongs to a first control resource set, and the DCI scheduling the second PUSCH belongs to a second control resource set, The control resource set group identifiers associated with the first control resource set and the second control resource set are different.

Optionally, the DCI for scheduling the first PUSCH belongs to a first control resource set, and the DCI for scheduling the second PUSCH belongs to a second control resource set, and the first control resource set and the second control resource The group ID of the control resource set associated with the set is different.

Optionally, the DCI carries a closed-loop power control parameter, and the closed-loop power control parameter is used to control the transmission power of the PUSCH scheduled by the DCI.

Optionally, the open loop power control parameter corresponding to each control resource set group identifier is configured by a higher layer parameter.

Optionally, the DCI carries indication information, the indication information is used to control the transmission of the PUSCH scheduled by the DCI, and the indication information includes a sounding reference signal resource indicator SRI and/or a transmission precoding matrix indicator TPMI.

It should be noted that this embodiment is used as an implementation manner of a network device corresponding to the embodiment shown in FIG. 2. For specific implementation manners, please refer to the relevant description of the embodiment shown in FIG. Repeat the description, so I won’t repeat it here.

Please refer to FIG. 5. FIG. 5 is a structural diagram of a terminal provided by an embodiment of the present invention. As shown in FIG. 5, the terminal 500 includes:

The receiving module 501 is configured to receive M downlink control information DCIs, and the M DCIs are used to schedule M PUSCHs;

The first sending module 502 is configured to send the M PUSCHs;

Optionally, N is an integer greater than 1.

Optionally, the M DCIs satisfy at least one of the following:

The indicated time-frequency resources are the same or different in size;

The indicated modulation and coding scheme MCS are the same or different.

Optionally, the power control parameter of the PUSCH is determined by a target power control parameter, and the target power control parameter is a power control parameter corresponding to a control resource set group identifier associated with the control resource set to which the target DCI belongs; the target DCI Is the DCI for scheduling the PUSCH.

Optionally, the power control parameter includes at least one of an open-loop power control parameter and a closed-loop power control parameter; wherein the DCI carries the closed-loop power control parameter, and the closed-loop power control parameter is used to control the The transmission power of the PUSCH scheduled by the DCI; the open loop power control parameter is a target open loop power control parameter, and the control resource set group identifier corresponding to the target open loop power control parameter is associated with the DCI ownership control resource set The group ID of the control resource set is the same.

Optionally, the DCI carries indication information, the indication information is used to control the transmission of the PUSCH scheduled by the DCI, and the indication information includes a sounding reference signal resource indicator SRI and/or a transmission precoding matrix indicator TPMI;

Optionally, the terminal 500 further includes:

The determining module is used to determine the spatial relationship of the PUSCH transmission.

Optionally, the determining module is specifically configured to perform at least one of the following:

In the case of scheduling the SRI carried in the DCI of the PUSCH, determine the spatial relationship of the PUSCH transmission according to the SRI;

In the case of scheduling SRI that is not carried in the DCI of the PUSCH, the default spatial relationship is determined as the spatial relationship of the PUSCH transmission.

Optionally, when the first preset condition is met, the default spatial relationship corresponds to the spatial relationship of the target physical uplink control channel PUCCH resource;

In the case that the second preset condition is met, the default spatial relationship corresponds to the transmission configuration indication of the control resource set with the smallest index in the target control resource set group identification TCI state or quasi co-location QCL;

The target PUCCH resource is the PUCCH resource with the smallest index among the PUCCH resources corresponding to the target control resource set group identifier, and the target control resource set group identifier is the control resource set group identifier associated with the control resource set to which the DCI belongs.

Optionally, the first preset condition includes:

The PUCCH resource corresponding to the target control resource set group identifier is configured for the terminal on the activated uplink bandwidth part BWP;

Optionally, the second preset condition includes:

The preset high-level parameters are enabled;

Optionally, in the case where the second preset condition includes activating the uplink BWP and the PUCCH resource corresponding to the target control resource set group identifier is not configured for the terminal, the default path loss reference signal of the power control parameter of the PUSCH The PL RS is: the RS corresponding to the TCI state of the control resource set with the smallest index in the target control resource set group identifier or the RS corresponding to the QCL type D of the QCL.

The terminal provided in the embodiment of the present invention can implement the various processes implemented by the terminal in the method embodiment of FIG. 2. To avoid repetition, details are not described herein again.

Please refer to FIG. 6. FIG. 6 is a structural diagram of a network device according to an embodiment of the present invention. As shown in FIG. 6, the network device 600 includes:

The second sending module 601 is configured to send M downlink control information DCIs to the terminal, where the M DCIs are used to schedule M PUSCHs;

Optionally, N is an integer greater than 1.

Optionally, the M DCIs satisfy at least one of the following:

The indicated time-frequency resources are the same or different in size;

The indicated modulation and coding scheme MCS are the same or different.

The network device provided by the embodiment of the present invention can implement each process implemented by the network device in the method embodiment of FIG. 4, and in order to avoid repetition, details are not described herein again.

FIG. 7 is a schematic diagram of the hardware structure of a terminal for implementing various embodiments of the present invention.

The terminal 700 includes but is not limited to: a radio frequency unit 701, a network module 702, an audio output unit 703, an input unit 704, a sensor 705, a display unit 706, a user input unit 707, an interface unit 708, a memory 709, a processor 710, and a power supply 711 and other components. Those skilled in the art can understand that the terminal structure shown in FIG. 7 does not constitute a limitation on the terminal, and the terminal may include more or fewer components than shown in the figure, or combine some components, or arrange different components. In the embodiment of the present invention, the terminal includes, but is not limited to, a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle-mounted terminal, a wearable device, a pedometer, and the like.

The radio frequency unit 701 is configured to receive M downlink control information DCIs, where the M DCIs are used to schedule M PUSCHs; and send the M PUSCHs;

It should be understood that, in this embodiment, the above-mentioned processor 710 and radio frequency unit 701 can implement each process implemented by the terminal in the method embodiment of FIG. 2. To avoid repetition, details are not described herein again.

It should be understood that, in this embodiment of the present invention, the radio frequency unit 701 can be used for receiving and sending signals in the process of sending and receiving information or talking. Specifically, after receiving the downlink data from the base station, it is processed by the processor 710; Uplink data is sent to the base station. Generally, the radio frequency unit 701 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit 701 can also communicate with the network and other devices through a wireless communication system.

The terminal provides users with wireless broadband Internet access through the network module 702, such as helping users to send and receive emails, browse web pages, and access streaming media.

The audio output unit 703 can convert the audio data received by the radio frequency unit 701 or the network module 702 or stored in the memory 709 into an audio signal and output it as sound. Moreover, the audio output unit 703 may also provide audio output related to a specific function performed by the terminal 700 (for example, call signal reception sound, message reception sound, etc.). The audio output unit 703 includes a speaker, a buzzer, a receiver, and the like.

The input unit 704 is used to receive audio or video signals. The input unit 704 may include a graphics processing unit (GPU) 7041 and a microphone 7042. The graphics processor 7041 is used to capture images of still pictures or videos obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. Data is processed. The processed image frame may be displayed on the display unit 706. The image frame processed by the graphics processor 7041 may be stored in the memory 709 (or other storage medium) or sent via the radio frequency unit 701 or the network module 702. The microphone 7042 can receive sound, and can process such sound into audio data. The processed audio data can be converted into a format that can be sent to the mobile communication base station via the radio frequency unit 701 for output in the case of a telephone call mode.

The terminal 700 further includes at least one sensor 705, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor. The ambient light sensor can adjust the brightness of the display panel 7061 according to the brightness of the ambient light. The proximity sensor can close the display panel 7061 and/or when the terminal 700 is moved to the ear. Or backlight. As a kind of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in various directions (usually three-axis), and can detect the magnitude and direction of gravity when stationary, and can be used to identify terminal gestures (such as horizontal and vertical screen switching, related games, Magnetometer attitude calibration), vibration recognition related functions (such as pedometer, tap), etc.; sensor 705 can also include fingerprint sensors, pressure sensors, iris sensors, molecular sensors, gyroscopes, barometers, hygrometers, thermometers, infrared Sensors, etc., will not be repeated here.

The display unit 706 is used to display information input by the user or information provided to the user. The display unit 706 may include a display panel 7061, and the display panel 7061 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc.

The user input unit 707 may be used to receive inputted numeric or character information, and generate key signal input related to user settings and function control of the terminal. Specifically, the user input unit 707 includes a touch panel 7071 and other input devices 7072. The touch panel 7071, also called a touch screen, can collect user touch operations on or near it (for example, the user uses any suitable objects or accessories such as fingers, stylus, etc.) on the touch panel 7071 or near the touch panel 7071. operate). The touch panel 7071 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch position, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it To the processor 710, the command sent by the processor 710 is received and executed. In addition, the touch panel 7071 can be implemented in multiple types such as resistive, capacitive, infrared, and surface acoustic wave. In addition to the touch panel 7071, the user input unit 707 may also include other input devices 7072. Specifically, other input devices 7072 may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), trackball, mouse, and joystick, which will not be repeated here.

Further, the touch panel 7071 can be overlaid on the display panel 7061. When the touch panel 7071 detects a touch operation on or near it, it is transmitted to the processor 710 to determine the type of touch event, and then the processor 710 determines the type of the touch event according to the touch. The type of event provides corresponding visual output on the display panel 7061. Although in FIG. 7, the touch panel 7071 and the display panel 7061 are used as two independent components to realize the input and output functions of the terminal, in some embodiments, the touch panel 7071 and the display panel 7061 can be integrated. Realize the input and output functions of the terminal, the specifics are not limited here.

The interface unit 708 is an interface for connecting an external device and the terminal 700. For example, the external device may include a wired or wireless headset port, an external power source (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, audio input/output (I/O) port, video I/O port, headphone port, etc. The interface unit 708 can be used to receive input (for example, data information, power, etc.) from an external device and transmit the received input to one or more elements in the terminal 700 or can be used to communicate between the terminal 700 and the external device. Transfer data between.

The memory 709 can be used to store software programs and various data. The memory 709 may mainly include a program storage area and a data storage area. The program storage area may store an operating system, an application program required by at least one function (such as a sound playback function, an image playback function, etc.), etc.; Data created by the use of mobile phones (such as audio data, phone book, etc.), etc. In addition, the memory 709 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices.

The processor 710 is the control center of the terminal. It uses various interfaces and lines to connect various parts of the entire terminal. Various functions of the terminal and processing data, so as to monitor the terminal as a whole. The processor 710 may include one or more processing units; preferably, the processor 710 may integrate an application processor and a modem processor, where the application processor mainly processes the operating system, user interface, application programs, etc., and the modem The processor mainly deals with wireless communication. It can be understood that the foregoing modem processor may not be integrated into the processor 710.

The terminal 700 may also include a power source 711 (such as a battery) for supplying power to various components. Preferably, the power source 711 may be logically connected to the processor 710 through a power management system, so as to manage charging, discharging, and power consumption management through the power management system. Function.

In addition, the terminal 700 includes some functional modules not shown, which will not be repeated here.

Preferably, the embodiment of the present invention also provides a terminal, including a processor 710, a memory 709, a computer program stored on the memory 709 and running on the processor 710, and the computer program is implemented when the processor 710 is executed. Each process of the foregoing PUSCH transmission method embodiment can achieve the same technical effect, and to avoid repetition, it will not be repeated here.

Referring to FIG. 8, FIG. 8 is a structural diagram of another network device provided by an embodiment of the present invention. As shown in FIG. 8, the network device 800 includes a processor 801, a transceiver 802, a memory 803, and a bus interface, where:

The transceiver 802 is configured to send M downlink control information DCIs to the terminal, and the M DCIs are used to schedule M PUSCHs;

It should be understood that in this embodiment, the above-mentioned processor 801 and transceiver 802 can implement each process implemented by the network device in the method embodiment of FIG.

In FIG. 8, the bus architecture may include any number of interconnected buses and bridges. Specifically, one or more processors represented by the processor 801 and various circuits of the memory represented by the memory 803 are linked together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are all known in the art, and therefore, no further descriptions are provided herein. The bus interface provides the interface. The transceiver 802 may be a plurality of elements, including a transmitter and a receiver, and provide a unit for communicating with various other devices on a transmission medium. For different user equipment, the user interface 804 may also be an interface capable of connecting externally and internally with the required equipment. The connected equipment includes but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

The processor 801 is responsible for managing the bus architecture and general processing, and the memory 803 can store data used by the processor 801 when performing operations.

Preferably, the embodiment of the present invention also provides a network device, including a processor 801, a memory 803, and a computer program stored on the memory 803 and running on the processor 801. When the computer program is executed by the processor 801, Each process of the foregoing embodiment of the PUSCH transmission control method is implemented, and the same technical effect can be achieved. In order to avoid repetition, details are not repeated here.

The embodiment of the present invention also provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium. When the computer program is executed by a processor, the embodiment of the PUSCH transmission control method on the network device side provided by the embodiment of the present invention is implemented. When the computer program is executed by the processor, the various processes of the PUSCH transmission method on the terminal side provided in the embodiment of the present invention are implemented, and the same technical effect can be achieved. To avoid repetition, details are not repeated here. Wherein, the computer-readable storage medium, such as read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disk, or optical disk, etc.

It should be noted that in this article, the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, It also includes other elements that are not explicitly listed, or elements inherent to the process, method, article, or device. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, article, or device that includes the element.

Through the description of the above implementation manners, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of software plus the necessary general hardware platform, of course, it can also be implemented by hardware, but in many cases the former is better.的实施方式。 Based on this understanding, the technical solution of the present invention essentially or the part that contributes to the existing technology can be embodied in the form of a software product, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, The optical disc) includes several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a base station, etc.) execute the method described in each embodiment of the present invention.

The embodiments of the present invention are described above with reference to the accompanying drawings, but the present invention is not limited to the above-mentioned specific embodiments. The above-mentioned specific embodiments are only illustrative and not restrictive. Those of ordinary skill in the art are Under the enlightenment of the present invention, many forms can be made without departing from the purpose of the present invention and the scope of protection of the claims, and they all fall within the protection of the present invention.

Claims

A physical uplink shared channel PUSCH transmission method, applied to a terminal, and characterized in that it includes:

Receiving M downlink control information DCIs, where the M DCIs are used to schedule M PUSCHs;

Sending the M PUSCHs;

Wherein, the M DCIs belong to K control resource sets, the K control resource sets are associated with N control resource set group identities, M is an integer greater than 1, and N is a positive integer; the M DCIs satisfy : The HARQ process ID of the hybrid automatic repeat request is the same; and the new data indicates that the NDI is the same.
The method according to claim 1, wherein N is an integer greater than one.
The method according to claim 1, wherein the time interval between the reception time of the first DCI and the reception time of the second DCI is less than a first preset value;

And/or, the time interval between the receiving time of the first DCI and the receiving time of the second DCI is greater than a second preset value, and the first preset value is greater than the second preset value;

Wherein, the first DCI and the second DCI are DCIs received twice adjacently among the M DCIs, or the first DCI is the earliest DCI received among the M DCIs, so The second DCI is the latest DCI received among the M DCIs.
The method according to claim 1, wherein the M DCIs satisfy at least one of the following:

The indicated time-frequency resources are the same or different in size;

The indicated modulation and coding scheme MCS are the same or different.
The method according to claim 1, wherein the M PUSCHs include a first PUSCH and a second PUSCH, the DCI scheduling the first PUSCH belongs to a first control resource set, and the scheduling of the second PUSCH The DCI belongs to a second control resource set, and the control resource set group identifiers associated with the first control resource set and the second control resource set are different.
The method according to claim 5, wherein the start symbol of the first PUSCH is before the end symbol of the second PUSCH and after the start symbol of the second PUSCH.
The method according to claim 1, wherein the power control parameter of the PUSCH is determined by a target power control parameter, and the target power control parameter corresponds to the control resource set group identifier associated with the control resource set to which the target DCI belongs The power control parameters of; the target DCI is the DCI for scheduling the PUSCH.
The method according to claim 7, wherein the power control parameter includes at least one of an open-loop power control parameter and a closed-loop power control parameter; wherein the DCI carries the closed-loop power control parameter, so The closed-loop power control parameter is used to control the transmission power of the PUSCH scheduled by the DCI; the open-loop power control parameter is a target open-loop power control parameter, and the control resource set group identifier corresponding to the target open-loop power control parameter is The control resource set group identifiers associated with the DCI attribution control resource set are the same.
The method according to claim 1, wherein the DCI carries indication information, the indication information is used to control the transmission of the PUSCH scheduled by the DCI, and the indication information includes a sounding reference signal resource indication (SRI) and/ Or the transmission precoding matrix indicates TPMI;

The SRI is used to indicate the SRS resource of the target SRS resource group, and the control resource set group identifier corresponding to the target SRS resource group is the same as the control resource set group identifier associated with the DCI attributed control resource set.
The method according to claim 1, wherein before the sending the M PUSCHs, the method further comprises:

Determine the spatial relationship of the PUSCH transmission.
The method according to claim 10, wherein the determining the spatial relationship of the PUSCH transmission comprises at least one of the following:

In the case of scheduling the SRI carried in the DCI of the PUSCH, determine the spatial relationship of the PUSCH transmission according to the SRI;

In the case of scheduling SRI that is not carried in the DCI of the PUSCH, the default spatial relationship is determined as the spatial relationship of the PUSCH transmission.
The method according to claim 11, wherein the default spatial relationship corresponds to the spatial relationship of the target physical uplink control channel PUCCH resource when the first preset condition is satisfied;

In the case that the second preset condition is met, the default spatial relationship corresponds to the transmission configuration indication of the control resource set with the smallest index in the target control resource set group identification TCI state or quasi co-location QCL;

The target PUCCH resource is the PUCCH resource with the smallest index among the PUCCH resources corresponding to the target control resource set group identifier, and the target control resource set group identifier is the control resource set group identifier associated with the control resource set to which the DCI belongs.
The method according to claim 12, wherein the first preset condition comprises:

The preset high-level parameters are not configured, or the preset high-level parameters are not enabled;

The PUCCH resource corresponding to the target control resource set group identifier is configured for the terminal on the activated uplink bandwidth part BWP;

Among the PUCCH resources corresponding to the target control resource set group identifier, some or all of the PUCCH resources are configured with a spatial relationship.
The method according to claim 12, wherein the second preset condition comprises:

The preset high-level parameters are enabled;

The PUCCH resource corresponding to the target control resource set group identifier is not configured for the terminal on the activated uplink BWP; or the PUCCH resource corresponding to the target control resource set group identifier is configured for the terminal on the activated uplink BWP, and the target control resource The PUCCH resource corresponding to the set group identifier is not configured with a spatial relationship.
The method according to claim 12, wherein when the second preset condition includes activating the uplink BWP and the PUCCH resource corresponding to the target control resource set group identifier is not configured for the terminal, the PUSCH resource The default path loss reference signal PL RS of the power control parameter is: the RS corresponding to the TCI state of the control resource set with the smallest index in the target control resource set group identifier or the RS corresponding to the QCL type D of the QCL.
A physical uplink shared channel PUSCH transmission control method, applied to network equipment, is characterized in that it includes:

Sending M downlink control information DCIs to the terminal, where the M DCIs are used to schedule M PUSCHs;

Wherein, the M DCIs belong to K control resource sets, the K control resource sets are associated with N control resource set group identities, M is an integer greater than 1, and N is a positive integer; the M DCIs satisfy : The HARQ process ID of the hybrid automatic repeat request is the same; and the new data indicates that the NDI is the same.
The method according to claim 16, wherein N is an integer greater than one.
The method according to claim 16, wherein the time interval between the reception time of the first DCI and the reception time of the second DCI is less than a first preset value;

And/or, the time interval between the receiving time of the first DCI and the receiving time of the second DCI is greater than a second preset value, and the first preset value is greater than the second preset value;

Wherein, the first DCI and the second DCI are DCIs received twice adjacently among the M DCIs, or the first DCI is the earliest DCI received among the M DCIs, so The second DCI is the latest DCI received among the M DCIs.
The method according to claim 16, wherein the M DCIs satisfy at least one of the following:

The indicated time-frequency resources are the same or different in size;

The indicated modulation and coding scheme MCS are the same or different.
The method according to claim 16, wherein the M PUSCHs include a first PUSCH and a second PUSCH, the DCI scheduling the first PUSCH belongs to a first control resource set, and the scheduling of the second PUSCH The DCI belongs to a second control resource set, and the control resource set group identifiers associated with the first control resource set and the second control resource set are different.
The method according to claim 20, wherein the start symbol of the first PUSCH is before the end symbol of the second PUSCH and is after the start symbol of the second PUSCH.
The method according to claim 16, wherein the DCI carries a closed-loop power control parameter, and the closed-loop power control parameter is used to control the transmission power of the PUSCH scheduled by the DCI.
The method according to claim 16, wherein the open loop power control parameter corresponding to each control resource set group identifier is configured by a higher layer parameter.
The method according to claim 16, wherein the DCI carries indication information, the indication information is used to control the transmission of the PUSCH scheduled by the DCI, and the indication information includes a sounding reference signal resource indication (SRI) and/ Or the transmission precoding matrix indicates TPMI;

The SRI is used to indicate the SRS resource of the target SRS resource group, and the control resource set group identifier corresponding to the target SRS resource group is the same as the control resource set group identifier associated with the DCI attributed control resource set.
A terminal, characterized in that it comprises:

A receiving module, configured to receive M downlink control information DCIs, and the M DCIs are used to schedule M PUSCHs;

The first sending module is configured to send the M PUSCHs;

Wherein, the M DCIs belong to K control resource sets, the K control resource sets are associated with N control resource set group identities, M is an integer greater than 1, and N is a positive integer; the M DCIs satisfy : The HARQ process ID of the hybrid automatic repeat request is the same; and the new data indicates that the NDI is the same.
A network device, characterized in that it comprises:

The second sending module is configured to send M downlink control information DCIs to the terminal, where the M DCIs are used to schedule M PUSCHs;

Wherein, the M DCIs belong to K control resource sets, the K control resource sets are associated with N control resource set group identities, M is an integer greater than 1, and N is a positive integer; the M DCIs satisfy : The HARQ process ID of the hybrid automatic repeat request is the same; and the new data indicates that the NDI is the same.
A terminal, characterized by comprising: a memory, a processor, and a program stored on the memory and capable of running on the processor, and when the program is executed by the processor, the implementation is as claimed in claims 1 to 15 Steps in any one of the physical uplink shared channel PUSCH transmission methods.
A network device, characterized by comprising: a memory, a processor, and a program stored on the memory and capable of running on the processor, and when the program is executed by the processor, it can implement as claimed in claims 16 to Steps in the physical uplink shared channel PUSCH transmission control method described in any one of 24.
A computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the physical uplink according to any one of claims 1 to 15 is realized. The steps of the shared channel PUSCH transmission method, or the steps of the physical uplink shared channel PUSCH transmission control method according to any one of claims 16 to 24 when the computer program is executed by a processor.