CN114915393A

CN114915393A - PUSCH (physical uplink shared channel) repeated transmission method and device and user equipment

Info

Publication number: CN114915393A
Application number: CN202110185535.0A
Authority: CN
Inventors: 宋扬; 孙荣荣
Original assignee: Vivo Mobile Communication Co Ltd
Current assignee: Vivo Mobile Communication Co Ltd
Priority date: 2021-02-10
Filing date: 2021-02-10
Publication date: 2022-08-16

Abstract

The application discloses a PUSCH (physical uplink shared channel) repeated transmission method, a PUSCH repeated transmission device and user equipment, belongs to the technical field of communication, and can solve the problem of low scheduling reliability of a network side caused by the fact that UE (user equipment) cannot be indicated to be converted from single TRP transmission to multi-TRP transmission or from multi-TRP transmission to single TRP transmission. The method comprises the following steps: the UE acquires first indication information; wherein the first indication information is used for indicating at least one of the following items: m target indications for use by a plurality of PUSCH transmission occasions; when M is larger than 1, the plurality of PUSCH transmission opportunities use the mapping sequence indicated by M targets; the target indication includes at least one of: the sounding reference signal resource indicates SRI, and the precoding matrix indicates TPMI; m is a positive integer; the UE transmits the plurality of PUSCH transmission opportunities using the M target indications according to the first indication information. The method and the device are applied to the PUSCH repeated transmission process.

Description

PUSCH (physical uplink shared channel) repeated transmission method and device and user equipment

Technical Field

The present application belongs to the field of communications technologies, and in particular, to a PUSCH retransmission method, an apparatus, and a User Equipment (UE).

Background

In a multi-transmission Receiving Point (MTRP) scenario, a Physical Uplink Shared Channel (PUSCH) repeated transmission opportunity is associated with one or more Sounding Reference Signal (SRS) resource indicators (SRIs) (or SRI groups), and Downlink Control Information (DCI) for scheduling a PUSCH includes multiple SRI domains (fields) or TPMI domains, so that two sets of parameters facing two TRP transmissions can be provided for a PUSCH transmission opportunity. Wherein each SRI field may indicate a corresponding SRI (or SRI group) and one TPMI field may indicate one TPMI.

However, since the related art cannot indicate whether the UE is converted from a single TRP transmission to a multi TRP transmission or from a multi TRP transmission to a single TRP transmission, and the order of the plurality of TRP transmission data (i.e., to which TRP data is transmitted first when two TRP transmissions are indicated), flexible scheduling on the network side cannot be guaranteed.

Disclosure of Invention

An object of the embodiments of the present application is to provide a PUSCH repetition transmission method, an apparatus, and a user equipment, which can solve a problem of low scheduling reliability on a network side due to inability to indicate whether a UE switches from a single TRP transmission to a multiple TRP transmission or from a multiple TRP transmission to a single TRP transmission.

In order to solve the technical problem, the present application is implemented as follows:

in a first aspect, a PUSCH repetition transmission method is provided, where the method includes: the UE acquires first indication information; wherein the first indication information is used for indicating at least one of the following items: m target indications for use by a plurality of PUSCH transmission occasions; when M is larger than 1, the plurality of PUSCH transmission opportunities use the mapping order indicated by the M targets; the target indication includes at least one of: SRI, TPMI; m is a positive integer; and the UE transmits a plurality of PUSCH transmission occasions by using the M target indications according to the first indication information.

In a second aspect, a PUSCH repetition transmission apparatus is provided, the apparatus comprising: the acquisition module is used for acquiring first indication information; wherein the first indication information is used for indicating at least one of the following items: m target indications for use by a plurality of PUSCH transmission occasions; when M is larger than 1, the plurality of PUSCH transmission opportunities use the mapping order indicated by M targets; the target indication includes at least one of: SRI, TPMI; m is a positive integer; and the transmission module is used for transmitting the plurality of PUSCH transmission opportunities by using M target indications according to the first indication information acquired by the acquisition module.

In a third aspect, a UE is provided, the UE comprising a processor, a memory and a program or instructions stored on the memory and executable on the processor, the program or instructions, when executed by the processor, implementing the steps of the method according to the first aspect.

In a fourth aspect, there is provided a readable storage medium having stored thereon a program or instructions which, when executed by a processor, carries out the steps of the method of the first aspect, or carries out the steps of the method of the first aspect.

In a fifth aspect, a chip is provided, where the chip includes a processor and a communication interface, where the communication interface is coupled to the processor, and the processor is configured to execute a network-side device program or instruction to implement the method according to the first aspect.

In this embodiment of the present application, after obtaining the first indication information, the UE may obtain target indications used for multiple PUSCH transmission occasions based on the first indication information (that is, based on M target indications used for multiple PUSCH transmission occasions and/or based on a mapping order in which M target indications are used for multiple PUSCH transmission occasions when M is greater than 1), so as to implement flexible switching between a single TRP and multiple TRPs for the UE, and ensure flexibility of network scheduling.

Drawings

Fig. 1 is a system architecture diagram of a wireless communication system according to an embodiment of the present application;

fig. 2 is a flowchart of a method for PUSCH repeated transmission according to an embodiment of the present application;

fig. 3 is a schematic structural diagram of a PUSCH repeated transmission apparatus according to an embodiment of the present application;

fig. 4 is a second schematic structural diagram of a PUSCH retransmission apparatus according to an embodiment of the present application;

fig. 5 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 6 is a schematic hardware structure diagram of a terminal according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some, but not all, of the embodiments of the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

The terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It should be understood that the data so used are interchangeable under appropriate circumstances such that embodiments of the application can be practiced in sequences other than those illustrated or described herein, and the terms "first" and "second" used herein generally do not denote any order, nor do they denote any order, for example, the first object may be one or more. In addition, "and/or" in the specification and the claims means at least one of connected objects, and a character "/" generally means that a preceding and succeeding related objects are in an "or" relationship.

It is noted that the techniques described in the embodiments of the present application are not limited to Long Term Evolution (LTE)/LTE Evolution (LTE-Advanced) systems, but may also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA), and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described techniques can be used for both the above-mentioned systems and radio technologies, as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for exemplary purposes, and the NR technique is used in much of the description belowAlthough these techniques may also be applied to applications other than NR system applications, such as generation 6 (6) ^th Generation, 6G) communication system.

Fig. 1 shows a block diagram of a wireless communication system to which embodiments of the present application are applicable. The wireless communication system includes a terminal 11 and a network-side device 12. Wherein, the terminal 11 may also be called as a terminal Device or a User Equipment (UE), the terminal 11 may be a Mobile phone, a Tablet Personal Computer (Tablet Personal Computer), a Laptop Computer (Laptop Computer) or a notebook Computer, a Personal Digital Assistant (PDA), a palmtop Computer, a netbook, a super-Mobile Personal Computer (UMPC), a Mobile Internet Device (MID), a Wearable Device (Wearable Device) or a vehicle-mounted Device (VUE), a pedestrian terminal (PUE), and other terminal side devices, the Wearable Device includes: bracelets, earphones, glasses and the like. It should be noted that the embodiment of the present application does not limit the specific type of the terminal 11. The network-side device 12 may be a Base Station or a core network, where the Base Station may be referred to as a node B, an evolved node B, an access Point, a Base Transceiver Station (BTS), a radio Base Station, a radio Transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a node B, an evolved node B (eNB), a home node B, a WLAN access Point, a WiFi node, a Transmit Receiving Point (TRP), or some other suitable terminology in the field, as long as the same technical effect is achieved, the Base Station is not limited to a specific technical vocabulary, and it should be noted that, in the embodiment of the present application, only the Base Station in the NR system is taken as an example, but a specific type of the Base Station is not limited.

Technical terms referred to in the embodiments of the present application will be exemplified below:

1) PUSCH transmission parameter indication

For the PUSCH transmission based on the codebook, the network side may configure at most one SRS resource set for codebook transmission for the UE, where the SRS resource set is obtained based on the uplink transmission CSI, and the SRS resource set includes at most two SRS resources. The number of ports contained in the two SRS resources is the same, and the ports are 1, 2 and 4; the two SRS resources described above generally correspond to different beams. The network side obtains uplink channel information by measuring the SRS on different SRS resources, selects parameters such as spatial relation, precoding matrix, power control, MCS and the like of PUSCH transmission for the UE according to the information, and then indicates the transmission parameters for the UE through an SRI domain/TPMI domain/TPC domain/MCS domain in a DCI format 0-1/0 _2 of a scheduling PUSCH. It should be noted that the same spatial relationship and ports as the SRS resources indicated by the SRI domain are adopted for PUSCH transmission.

For the non-codebook-based PUSCH transmission, only one SRS resource set used for the non-codebook transmission is supported, 4 SRS resource sets are configured in each SRS resource set at most, the number of ports of all the SRS resource sets is 1, and each SRS resource set is configured with an associated CSI-RS for the UE to measure a downlink channel. And the UE assumes the measured downlink channel as an uplink channel according to the channel reciprocity and calculates a precoding matrix of uplink transmission according to the channel information. And the network side determines the precoding used by the UE for PUSCH transmission according to the measured precoded SRS, and indicates the precoding through scheduling the SRI domain of the DCI of the PUSCH. The SRI field indicates a subset of all precoded SRS resources, i.e. SRI groups, sent by the UE to indicate the precoding matrix employed for PUSCH transmission.

2) PUSCH repeat transmission parameter indication in MTRP scenario

In a multiple TRP (mtrp) scenario, a repeated transmission (multiple PUSCH transmission occasions) of one Transport Block (TB) of PUSCH may be addressed to multiple TRPs. The repeated transmission of the PUSCH respectively adopts a plurality of sets of transmission parameters (including parameters such as spatial relation, precoding matrix, power control and the like) facing different TRPs. The related technology supports PUSCH repeated transmission and at most adopts two sets of spatial relation SRI (groups), and the corresponding TPMI also needs two sets of parameters. In the MTRP scenario, at most two SRS resource sets can be configured for codebook or non-codebook transmission. The DCI for correspondingly scheduling the PUSCH comprises two SRI domains and two TPMI domains. In order to support dynamic switching of single-TRP and multi-TRP PUSCH transmissions, DCI needs to indicate which set of transmission parameters is used for multiple PUSCH transmission occasions, or two sets of transmission parameters are used.

The following describes in detail an indication method, an indication device, and an indication apparatus provided by the embodiments of the present application through specific embodiments and application scenarios thereof with reference to the accompanying drawings.

As shown in fig. 2, an embodiment of the present application provides a PUSCH repeated transmission method, including the following steps:

step 201: first indication information is acquired.

In an embodiment of the present application, the first indication information is used to indicate at least one of:

m target indications used for M PUSCH transmission occasions,

the PUSCH transmission occasion uses the mapping order of the M target indications.

Wherein the target indication comprises at least one of: the sounding reference signal resource indicates SRI and the precoding matrix indicates TPMI. In one example, the first indication information is used for M SRIs or M TPMIs used by M PUSCH transmission occasions; m is a positive integer.

It can be understood that the first indication information may indicate only M target indications used by the PUSCH transmission timing, may indicate only the mapping order of the M target indications, and may indicate the mapping order of the M target indications while indicating the M target indications used by the PUSCH transmission timing.

Optionally, in this embodiment of the application, if the PUSCH transmission is a non-codebook transmission, the targeted indication includes an SRI; if the PUSCH transmission is a codebook transmission, the target indication includes SRI and TPMI.

Step 202: and transmitting the plurality of PUSCH transmission opportunities using M target indications according to the first indication information.

Optionally, in this embodiment of the present application, the first indication information is carried in a target domain in DCI or MAC CE; wherein the DCI is used for scheduling the plurality of PUSCH transmission opportunities. It should be noted that the above-mentioned target field is to introduce a new field based on reducing DCI bit overhead as much as possible.

In this way, a new target field is introduced into the DCI to indicate the mapping order of the M target indications associated with the multiple PUSCH transmission occasions, thereby implementing the transmission order switching of multiple TRPs and ensuring the flexibility of network scheduling.

Optionally, in this embodiment of the present application, before the step 202, the technical method provided in this embodiment of the present application may further include:

step 203 a: first configuration information is received, and DCI for scheduling a PUSCH.

In an embodiment of the present application, the first configuration information includes N SRS resource sets, where N is an integer greater than 1; the N SRS resource sets are used for codebook transmission or non-codebook transmission.

In the embodiment of the present application, the above M targets are indicated as: all or part of the X first indications corresponding to the N SRS resource sets are indicated, wherein X is an integer larger than 1 and is larger than or equal to M. Wherein the first indication comprises at least one of: SRI, TPMI. It is to be understood that the above-mentioned M target indications may include all or part of N TPMI corresponding to N SRS resource sets, and/or all or part of N SRI corresponding to N SRS resource sets.

Optionally, in this embodiment of the present application, in a case that the first indication information is only used for indicating the mapping order, before the step 202, the PUSCH repeated transmission method provided in this embodiment of the present application may further include the following steps:

step A1: according to the X first indications, M target indications are determined.

Or,

step A2: and determining M target indications according to the X first indications and the first indication information.

For example, the UE may directly determine, based on the X first indications corresponding to the N SRS resource sets, M target indications used by the multiple PUSCH transmission occasions. In the presence of the target domain, the UE may jointly determine M target indications based on the X first indications and the first indication information.

Further optionally, in this embodiment of the application, the step 201 may specifically include the following steps:

step 203 b: and acquiring the first indication information when the N SRS resource sets or the DCI satisfy a target condition.

Further optionally, in the embodiment of the present application, the target condition includes at least one of:

at least one of the N SRS resource sets includes only one SRS resource;

no reserved item exists in the SRI index tables corresponding to the N SRS resource sets;

reserved items are reserved in partial SRI index tables corresponding to the N SRS resource sets, and no reserved items are reserved in the partial SRI index tables;

or,

the target condition includes any one of:

the DCI does not include a TPMI domain;

when the DCI only has one TPMI domain, no reserved entry exists in the TPMI index table corresponding to the TPMI domain;

when the DCI includes at least two TPMI domains, there is no reserved entry in the TPMI index table corresponding to the at least two TPMI domains; or, there is a reserved entry in the TPMI index table corresponding to the partial TPMI domain of the at least two TPMI domains, and there is no reserved entry in the TPMI index table corresponding to the partial TPMI domain;

or,

the above target condition includes any one of:

under the condition that the N SRS resource sets correspond to at least one SRI domain, reserving items are reserved in SRI index tables corresponding to the N SRS resource sets;

when the DCI includes at least one TPMI field, the TPMI index table corresponding to the TPMI field in the DCI has a reserved entry.

It should be noted that, if each of the N SRS resource sets includes one SRS resource, it indicates that there is no SRI field in the DCI. Or, if a certain SRS resource set includes only one SRS resource, the SRI index table corresponding to the SRI field corresponding to the SRS resource set is used to indicate the SRS resource in the SRS resource set.

It should be noted that there is no TPMI domain for single port SRS.

Optionally, in an embodiment of the present application, the technical method provided in the embodiment of the present application may further include:

step 204: and acquiring second indication information through high-layer signaling.

Wherein the second indication information indicates the number of TPMI domains included in the DCI. In an example, in a case that the number of the TPMI domains is 1, each SRI used by the plurality of PUSCH transmission occasions corresponds to the same TPMI. When the number of the TPMI domains is the same as the number of the SRI domains, the SRIs used in the plurality of PUSCH transmission timings correspond to the TPMI on a one-to-one basis.

For example, for codebook transmission, assuming that PUSCH transmission uses SRI and TPMI, RRC signaling may indicate whether a second TPMI field exists by configuring DCI format0_1/0_2, and if so, repeated transmission occasions of PUSCH associated with different SRIs respectively corresponding to the TPMI indicated by different TPMI fields; if not, the repeated transmission opportunities of the PUSCH associated with different SRIs all adopt the TPMI indicated by one TPMI field.

Optionally, in this embodiment of the application, the first indication information is determined based on the second configuration information; wherein the second configuration information includes: target corresponding relations corresponding to the N SRS resource sets; the target correspondence includes: corresponding relations between different values of the target domain and different first indication information; the target correspondence is agreed by a protocol, or is predefined, or is configured by the network side. In an example, the target correspondence may be a target index table.

Further optionally, in this embodiment of the application, a value of the target field in the DCI is used to indicate the first indication information.

Further optionally, in this embodiment of the application, the domain size of the target domain in the DCI is determined based on the value number Y of the target domain in the target correspondence. For example, the upper rounding of the domain size of the target domain log2(Y) is determined according to the value number Y of the target domain in the target correspondence.

Further optionally, in this embodiment of the application, the value number Y of the target domain in the target correspondence is related to at least one of the following:

whether a reserved item exists in a first index table corresponding to each first indication in the X first indications;

each first indication in the X first indications takes a value in a corresponding first index table;

when M is larger than 1, exchanging a plurality of PUSCH transmission opportunities and using the mapping sequence indicated by the M targets is supported;

y is an integer greater than 1.

Optionally, in an embodiment of the present application, the first indication information is related to at least one of:

whether a reserved item exists in a first index table corresponding to each first indication in the X first indications or not is judged;

each of the X first indications is a value in a corresponding first index table;

when M is greater than 1, exchanging the plurality of PUSCH transmission occasions described above is supported using a mapping order of M target indications.

Optionally, in this embodiment of the application, in a case that there is a reserved entry in each of the first index tables corresponding to the X first indications,

if the values indicated by the X first indications in the corresponding first index tables are all unreserved values, the target domain is not present, and the first indication information is used for indicating the M target indications; or, the first indication information carried by the target domain is used to indicate a mapping order of the M target indications;

or,

in a case other than the case where all the first index tables corresponding to the X first indicators have a reserved entry, the first indication information carried by the target domain is used to indicate: the M target indications, or a mapping order of the M target indications and the M target indications.

For example, when there is a reserved entry in each of the first index tables corresponding to the X first indicators, if all values indicated by the X first indicators in the corresponding first index tables are non-reserved values, when the mapping order of the M target indicators is not supported for exchanging the plurality of PUSCH transmission timings, there is no target field in the DCI, and in this case, the first indication information is used to indicate the M target indicators; or, when a mapping order of M target indicators is used to support switching of the plurality of PUSCH transmission occasions, there is a target field in DCI, and in this case, the first indication information carried in the target field is used to indicate the mapping order of the M target indicators.

Illustratively, in a case other than the case where there is a reserved entry in each of the first index tables corresponding to the X first indications (e.g., there is no reserved entry in each of the first index tables corresponding to the X first indications, or there is a reserved entry in only some of the first indications), the target domain exists in the DCI. In this case, if the mapping order using M target indicators for exchanging the plurality of PUSCH transmission timings is not supported, the first indication information carried by the target field is used to indicate the M target indicators, or if the mapping order using M target indicators for exchanging the plurality of PUSCH transmission timings is supported, the first indication information carried by the target field is used to indicate the mapping order of the M target indicators and the M target indicators.

Optionally, in this embodiment of the application, when the N SRS resource sets include a first SRS resource set, the first indication information is related to a value indicated by a first target indication indicated by the first SRS resource set in a corresponding first index table; wherein, the first target indicates that a reserved entry exists in the corresponding first index table.

It should be noted that the above-mentioned "reserved items exist in the first index table" specifically includes: all sub-tables contained in the first index table contain reserved entries.

The value of the first indication information and the content of the indication will be described below by taking the SRI field as an example.

Specifically, the above is exemplified by taking 2 SRS resource sets as an example. The 2 SRS resource sets correspond to 2 SRI domains.

If the size of the target domain is 1bit, under the condition that all 2 SRI index tables corresponding to the 2 SRI domains have reserved entries,

when the SRIs indicated by the 2 SRI fields are all non-reserved values (valid values), the first indication information is a value of 1, which indicates that the first indication information indicates that the contents are ((Rm/RGm), (Rn/RGn)), i.e., the first indication information indicates that the target SRIs (Rm/RGm) and (Rn/RGn), and is mapped to the PUSCH transmission occasions in the order of first (Rm/RGm) and then (Rn/RGn); it should be noted that the detailed explanation of (Rm/RGm) and (Rn/RGn) can be found in example 1 below.

When the SRIs indicated by the 2 SRI fields are all unreserved values, the first indication information is a value of 2, which indicates that the first indication information indicates ((Rn/RGn), (Rm/RGm)), that is, the first indication information indicates that the contents are (Rm/RGm) and (Rn/RGn), and the first indication information is mapped to the PUSCH transmission occasions in the order of (Rn/RGn) first and (Rm/RGm) later;

when the value of the SRI index table indicated by the first SRI field in the 2 SRI fields is the reserved item, the first indication information is 3, which indicates that the indication content of the first indication information is (Rn/RGn);

when the value of the SRI index table indicated by the second SRI field of the 2 SRI fields is the reserved entry, the first indication information is a value of 4, which indicates that the first indication information indicates that the content is (Rm/RGm).

Wherein (Rm/RGm) is the value in the SRI index table indicated by the first SRI field, and (Rn/RGn) is the value in the SRI index table indicated by the second SRI field.

Note that (a, B) indicates mapping to the above M PUSCH transmission timings in the order of AB, and (a) indicates mapping a to the above M PUSCH transmission timings.

Under the condition that the index table corresponding to the first SRI domain in the 2 SRI domains has a reserved entry, if the size of the target domain is 2 bits,

when the SRI indicated by the first SRI field is the unreserved value or the reserved value, the first indication information is a value a1, indicating that the first indication information indicates that the content is (Rm/RGm);

when the SRI indicated by the first SRI field is the unreserved value or the reserved value, the first indication information is a value a2 indicating that the first indication information indicates that the content is (Rn/RGn);

when the SRI indicated by the second SRI field is the unreserved value, the first indication information is a value a3, indicating that the first indication information indicates that the content is ((Rm/RGm), (Rn/RGn));

when the SRI indicated by the second SRI field is a non-reserved value, the first indication information is a value A4, indicating that the first indication information indicates that the content is ((Rn/RGn), (Rm/RGm)).

In the case that no reserved entry is contained in the index table corresponding to the 2 SRI fields,

when the SRIs indicated by the above 2 SRI fields are all non-reserved values, the first indication information is a value B1, indicating that the first indication information indicates contents of ((Rm/RGm), (Rn/RGn));

when the SRIs indicated by the 2 SRI fields are all non-reserved values, the first indication information is a value B2, which indicates that the first indication information indicates that the content is ((Rn/RGn), (Rm/RGm));

when the SRIs indicated by the 2 SRI fields are all unreserved values, the first indication information is a value B3, which indicates that the first indication information indicates that the content is (Rm/RGm);

when the SRIs indicated by the 2 SRI fields are all non-reserved values, the first indication information is a value B4, which indicates that the first indication information indicates that the content is (Rn/RGn).

In the case where there is a reserved entry in the index table corresponding to the first SRI domain among the above 2 SRI domains,

when the SRI indicated by the first SRI field is the reserved value, the first indication information is a value C1, which indicates that the SRI indicated by the second SRI field corresponds to SRS resource set0, i.e., (Rm/RGm), and the corresponding first indication information indicates that the content is (Rm/RGm);

when the SRI indicated by the first SRI field is the reserved value, the first indication information is value C2, which indicates that the SRI indicated by the second SRI field corresponds to SRS resource set1, i.e., (Rn/RGn), and the corresponding first indication information indicates that the content is (Rn/RGn);

when the SRIs indicated by the 2 SRI fields are all non-reserved values, the SRI indicated by the first SRI field and the SRI indicated by the second SRI field correspond to the SRS resource set0 and the SRS resource set1, respectively, and at this time, if the first indication information is a value of C3, it indicates that the first indication information indicates that the contents are ((Rm/RGm), (Rn/RGn)), and if the first indication information is a value of C4, it indicates that the contents are ((Rn/RGn), (Rm/RGm)).

It should be noted that the value C1 and the value C3 may be the same value, and the value C2 and the value C4 may be the same value.

The content indicated by the first indication information will be described below by taking an SRI field as an example. Specifically, the following example refers to 2 relationships indicated by the first indication information, "M target indications indicating use of M PUSCH transmission occasions" as relationship 1, and a mapping order in which the PUSCH transmission occasions use the M target indications "as relationship 2. In the following scenario, the first indication information may be described by using a target domain, or the first indication information may not be described by using the target domain, which is not limited in the embodiment of the present application.

Scene 1:

the relationship indicated by the target domain may include relationship 1 and relationship 2 (requiring 2 bits), or only include relationship 1 (requiring 1bit), or only include relationship 2 (requiring 1bit and indicating two SRIs).

Illustratively, the relationships indicated in Table 1 below for the target domain described above include only one example of relationship 2. Where Rm/RGm in Table 1 indicates SRS resource m or SRS resource group m, and (S0, Rm/RGm) in Table 1 indicates SRS resource m or SRS resource group m in SRS resource set0, and (S1, Rn/RGn) indicates SRS resource n or SRS resource group n in SRS resource set 1.

TABLE 1

Threshold value	Means of
		0	(S0,Rm/RGm),(S1,Rn/RGn)
1	(S1,Rn/RGn),(S0,Rm/RGm)

Scene 2:

when at least one of the following conditions (i.e., the condition a1, the condition a2, and the condition a3) is satisfied, the relationship indicated by the target domain may include relationship 1 and relationship 2 (requiring 2 bits), or the relationship indicated by both the target domain and the SRI domain includes relationship 1 and relationship 2.

Condition a 1: at least one of the two SRS resource sets for codebook transmission or non-codebook transmission contains only one SRS resource, or no TPMI domain, or only one TPMI domain.

Example 1: taking the case that both SRS resource set0 and SRS resource set1 contain only one SRS resource, specifically, SRS resource0 (which may be described as (S0, R0)) is contained in SRS resource set0, and SRS resource1 (which may be described as (S1, R1)) is contained in SRS resource set 1. In this case, the relationship indicated by the value of the target domain may be as shown in table 2 below.

TABLE 2

Example 2: taking the example that SRS resource set0 includes L SRS resources (S0, R0), (S0, R1), … … (S0, R (M-1))), and SRS resource set1 includes only one SRS resource (i.e., (S1, R1)), it is assumed that SRI index entry and reserved entry exist in SRI index table 0 corresponding to SRS resource set 0. In this case, the relationship indicated by the values of the target field may be as shown in tables 3 and 4 below.

TABLE 3

SRI index Table 0 values	Threshold value	Means of
			(S0,Rm/RGm)	0	(S0,Rm/RGm)
Retention item	1	(S1,R0)
			(S0,Rm/RGm)	2	(S0,Rm/RGm),(S1,R0)
(S0,Rm/RGm)	3	(S1,R0),(S0,Rm/RGm)

TABLE 4

SRI index Table 0 values	Threshold value	Means of
			(S0,Rm/RGm)	0	(S0,Rm/RGm)
(S0,Rm/RGm)	1	(S0,Rm/RGm)(S1,R0)
			Retention item	Arbitrary value	(S1,R0)
(S0,Rm/RGm)	2	(S1,R0),(S0,Rm/RGm)

Condition a 2: under a specific configuration, no reserved entry (reserved entry) exists in the SRI index tables corresponding to the two SRS resource sets for codebook transmission or non-codebook transmission, or no reserved entry exists in the TPMI tables corresponding to the two TPMI domains.

Example 3: taking the example that the SRS resource set0 includes L SRS resources (S0, R0), (S0, R1), … … (S0, R (M-1))), and the SRS resource set0 includes L SRS resources (S1, R0), (S1, R1), … … (S1, R (M-1))), it is assumed that valid SRI index entries exist in both SRI index table 0 corresponding to SRS resource set0 and SRI index table 1 corresponding to SRS resource set1, but no reserved entries exist. At this time, the relationship indicated by the value of the target domain may be as shown in table 5 below.

TABLE 5

Condition a 3: under specific configuration, one reserved item and one unreserved item are in SRI index tables corresponding to two SRS resource sets used for codebook transmission or non-codebook transmission; or, one reserved item and one unreserved item in the TPMI table corresponding to the two TPMI domains are not reserved.

Example 4: taking the example that SRS resource set0 includes L SRS resource (S0, R0), (S0, R1), … … (S0, R (M-1))), and SRS resource set0 includes L SRS resource (S1, R0), (S1, R1), … … (S1, R (M-1))), it is assumed that SRI index table 0 corresponding to SRS resource set0 has valid SRI index entries and reserved entries, and SRI index table 1 corresponding to SRS resource set1 has valid SRI index entries but no reserved entries. In this case, the relationship indicated by the values of the target field may be as shown in tables 6 and 7 below.

TABLE 6

SRI index Table 0 values	SRI index Table 1 values	Threshold value	Means of
				(S0,Rm)	Arbitrary value	0	(S0,Rm/RGm)
Retention item	(S1,Rn/RGn)	-	(S1,Rn/RGn)
				(S0,Rm/RGm)	(S1,Rn/RGn)	1	(S0,Rm/RGm),(S1,Rn/RGn)
(S0,Rm/RGm)	(S1,Rn/RGn)	2	(S1,Rn/RGn),(S0,Rm/RGm)

TABLE 7

SRI index Table 0 values	SRI index Table 1 values	Threshold value	Means of
				(S0,Rm/RGm)	Arbitrary value of	0	(S0,Rm/RGm)
Valid or reserved entries	(S1,Rn/RGn)	1	(S1,Rn/RGn)
				(S0,Rm/RGm)	(S1,Rn/RGn)	2	(S0,Rm/RGm),(S1,Rn/RGn)
(S0,Rm/RGm)	(S1,Rn/RGn)	3	(S1,Rn/RGn),(S0,Rm/RGm)

Scene 3:

when at least one of the following conditions (i.e., the condition b1, the condition b2, and the condition b3) is satisfied, the relationship indicated by the target domain may include the relationship 1, or the relationship indicated by the target domain and the SRI domain/TPMI domain together includes the relationship 1 (2 bits are required).

Condition b 1: at least one of the two SRS resource sets for codebook transmission or non-codebook transmission contains only one SRS resource, or no TPMI domain, or only one TPMI domain.

Example 5: taking an example that each of SRS resource set0 and SRS resource set1 only includes one SRS resource, specifically, SRS resource0 (which may be described as (S0, R0)) is included in SRS resource set0, and SRS resource1 (which may be described as (S1, R1)) is included in SRS resource set 1. In this case, the relationship indicated by the value of the target field may be as shown in table 8 below.

TABLE 8

Threshold value	Means of
		0	(S0,R0)
1	(S1,R0)
		2	(S0,R0),(S1,R0)

Example 6: taking the example that SRS resource set0 includes L SRS resources (respectively (S0, R0), (S0, R1), … … (S0, R (M-1))), and SRS resource set1 includes only one SRS resource (i.e., (S1, R1)), it is assumed that the SRS resource set0 corresponds to an SRI index table 0 and a valid SRI index entry and a reserved entry exist. At this time, the relationship indicated by the value of the target domain may be as shown in table 9 below.

TABLE 9

SRI index Table 0 values	Threshold value	Means of
			(S0,Rm/RGm)	0	(S0,Rm/RGm)
Valid or reserved entries	1	(S1,R0)
			(S0,Rm/RGm)	2 (or 1)	(S0,Rm/RGm),(S1,R0)

Condition b 2: under a specific configuration, no reserved entry (reserved entry) exists in the SRI index tables corresponding to the two SRS resource sets used for codebook transmission or non-codebook transmission, or no reserved entry exists in the TPMI tables corresponding to the two TPMI domains.

Example 7: taking the example that the SRS resource set0 includes L SRS resources (S0, R0), (S0, R1), … … (S0, R (M-1))), and the SRS resource set0 includes L SRS resources (S1, R0), (S1, R1), … … (S1, R (M-1))), it is assumed that valid SRI index entries exist in both SRI index table 0 corresponding to SRS resource set0 and SRI index table 1 corresponding to SRS resource set1, but no reserved entries exist. At this time, the relationship indicated by the values of the target domain may be as shown in table 10 below.

Watch 10

SRI index Table 0 values	SRI index Table 1 values	Threshold value	Means of
				(S0,Rm/RGm)	(S1,Rn/RGn)	0	(S0,Rm/RGm)
(S0,Rm/RGm)	(S1,Rn/RGn)	1	(S1,Rn/RGn)
				(S0,Rm/RGm)	(S1,Rn/RGn)	2	(S0,Rm/RGm),(S1,Rn/RGn)

Condition b 3: under specific configuration, one reserved item and one unreserved item are in SRI index tables corresponding to two SRS resource sets used for codebook transmission or non-codebook transmission; or, one reserved item and one unreserved item in the TPMI table corresponding to the two TPMI domains are not reserved.

Example 8: taking the example that SRS resource set0 includes L SRS resources (S0, R0), (S0, R1), … … (S0, R (M-1))), and SRS resource set0 includes L SRS resources (S1, R0), (S1, R1), … … (S1, R (M-1))), it is assumed that SRI index table 0 corresponding to SRS resource set0 has valid SRI index entries and reserved entries, and SRI index table 1 corresponding to SRS resource set1 has valid SRI index entries but no reserved entries. In this case, the relationship indicated by the value of the target field may be as shown in tables 11 and 12 below.

TABLE 11

SRI index Table 0 values	SRI index Table 1 values	Threshold value	Means of
				(S0,Rm/RGm)	Arbitrary value of	0	(S0,Rm/RGm)
Retention item	(S1,Rn/RGn)	-	(S1,Rn/RGn)
				(S0,Rm/RGm)	(S1,Rn/RGn)	1	(S0,Rm/RGm),(S1,Rn/RGn)

TABLE 12

SRI index Table 0 values	SRI index Table 1 values	Threshold value	Means of
				(S0,Rm/RGm)	Arbitrary value	0	(S0,Rm/RGm)
Valid or reserved entries	(S1,Rn/RGn)	1	(S1,Rn/RGn)
				(S0,Rm/RGm)	(S1,Rn/RGn)	2	(S0,Rm/RGm),(S1,Rn/RGn)

Scene 4:

when at least one of the following conditions (i.e., the condition c1) is satisfied, the relationship indicated by the value of the target domain may include relationship 1 and relationship 2 (requiring 2 bits), or the relationship indicated by the target domain and the SRI domain together includes relationship 1 and relationship 2.

Condition c 1: under a specific configuration, both SRI index tables corresponding to two SRS resource sets for codebook transmission or non-codebook transmission have a reserved entry, or both TPMI tables corresponding to two TPMI domains have a reserved entry.

Example 9: taking the example that the SRS resource set0 includes L SRS resources (S0, R0), (S0, R1), … … (S0, R (M-1))), and the SRS resource set0 includes L SRS resources (S1, R0), (S1, R1), … … (S1, R (M-1))), it is assumed that valid SRI index entries exist in both SRI index table 0 corresponding to SRS resource set0 and SRI index table 1 corresponding to SRS resource set1, but no reserved entries exist. At this time, the relationship indicated by the values of the target domain may be as shown in table 13 below.

Watch 13

SRI index Table 0 values	SRI index Table 1 values	Threshold value	Means of
				(S0,Rm)	Retention item	-	(S0,Rm)
Retention item	(S1,Rn)	-	(S1,Rn)
				(S0,Rm)	(S1,Rn)	0	(S0,Rm),(S1,Rn)
(S0,Rm)	(S1,Rn)	1	(S1,Rn),(S0,Rm)

Scene 5:

the relationships collectively indicated by the above-mentioned SRI domains include relationship 1 when at least one of the following conditions (i.e., condition d1) is satisfied.

Condition d 1: under specific configuration, both SRI index tables corresponding to two SRS resource sets for codebook transmission or non-codebook transmission have reserved entries, or both TPMI tables corresponding to two TPMI domains have reserved entries.

Example 10: taking the example that SRS resource set0 includes L SRS resources (S0, R0), (S0, R1), … … (S0, R (M-1))), and SRS resource set0 includes L SRS resources (S1, R0), (S1, R1), … … (S1, R (M-1))), it is assumed that SRI index entries corresponding to SRI index table 0 and SRI index table 1 corresponding to SRI index table 1 of SRS resource set0 have valid SRI index entries but no reserved entries. At this time, the relationship indicated by the first indication information may be as shown in table 14 below.

TABLE 14

SRI index Table 0 values	SRI index Table 1 values	Threshold value	Means of
				(S0,Rm)	Retention item	-	(S0,Rm)
Retention item	(S1,Rn)	-	(S1,Rn)
				(S0,Rm)	(S1,Rn)	-	(S0,Rm),(S1,Rn)

Scene 6:

when at least one of the following conditions (i.e., the condition d1) is satisfied, the relationship indicated by the target domain includes the relationship 1 and the relationship 2, or the relationship indicated by the target domain includes only the relationship 1.

Condition e 3: under specific configuration, one reserved item and one unreserved item are in SRI index tables corresponding to two SRS resource sets used for codebook transmission or non-codebook transmission; alternatively, two TPMI domains correspond to TPMI tables with one reserved entry and one unreserved entry.

Example 11: taking the example that SRS resource set0 includes L SRS resources (S0, R0), (S0, R1), … … (S0, R (M-1))), and SRS resource set0 includes L SRS resources (S1, R0), (S1, R1), … … (S1, R (M-1))), it is assumed that SRI index table 0 corresponding to SRS resource set0 has valid SRI index entries but no reserved entries, and SRI index table 1 corresponding to SRS resource set1 has valid SRI index entries and reserved entries. At this time, the relationship indicated by the values of the target domain may be as shown in table 15 below. As shown in table 15, when the SRI index table 1 value is a reserved entry, and when the value of the target field is 0, the SRI index table 0 indicates: the second index table is the SRS index table 0 or the SRS resource set0 (i.e., S0); when the target threshold is 1, the SRI index table 0 indicates: the second index table is the SRS index table 1 or the SRS resource set1 (i.e., S1).

Watch 15

It should be noted that the target domains in tables 1 and 13 above may be unified as the following table 16:

TABLE 16

Threshold value	Means of
		0	S0,S1
1	S1,S0

It should be noted that the target domains in the above tables 2, 3, 4, 5, 7 may be unified as the following table 17:

TABLE 17

Threshold value	Means of
		0	S0
1	S1
		2	S0,S1
3	S1,S0

It should be noted that the target fields in tables 8, 9, 10, 12 above can be collectively described as the following table 18:

watch 18

Threshold value	Means of
		0	S0
1	S1
		2	S0,S1
3	Reserved

Wherein S0 in the above tables 16, 17, and 18 represents the SRI indicated by SRI field 0 in the presence of SRI field 0 (i.e., (S0, Rm/RGm)); alternatively, when the SRS resource set0 includes one SRS resource, the S0 is the SRS resource included in the SRS resource set0 (S0, R0). S1 in the above tables 16, 17, 18 represents the SRI indicated by SRI domain 1 in the presence of SRI domain 1, i.e. (S1, Rn/RGn); alternatively, when the SRS resource set1 includes one SRS resource, the S1 is the SRS resource included in the SRS resource set1 (S1, R0).

It should be noted that the values of the respective fields in the above tables 16, 17 and 18 have the following meanings:

0: the plurality of PUSCH transmission occasions all use target indications corresponding to S0;

1: the plurality of PUSCH transmission occasions all use target indications corresponding to S1;

2: the plurality of PUSCH transmission occasions use corresponding target indications in the order of S0, S1;

3: the plurality of PUSCH transmission occasions use the corresponding target indications in the order of S1, S0.

Scene 7:

take SRI domain (i.e. SRS resource indicator) as an example. The corresponding first index table is an SRI index table.

Example 12:

SRS resource indicator1 indicates the set of SRIs in the first SRS resource set as in table 19 below, where Lmax is 2:

watch 19

SRS resource indicator2 indicates the set of SRIs in the second SRS resource set as in table 20 below, where Lmax is 2:

watch 20

Illustratively, in conjunction with table 16 above, it can be seen that:

if the SRS resource indicator1 indicates the reserved entry (indicating value 3), it indicates that all PUSCH repetition transmission occasions are associated with the SRI group indicated by SRS resource indicator 2;

if the SRS resource indicator2 indicates the reserved entry (indicating value 3), it indicates that all PUSCH repetition transmission occasions are associated with the SRI group indicated by SRS resource indicator 1;

if both SRS resource indicator1 and SRS resource indicator2 indicate SRI groups instead of reserved entries, the order of mapping between two SRI groups and PUSCH transmission occasions is determined by the value of the target field newly introduced by DCI as explained in table 16.

Example 13:

and non-codebook transmission, wherein a target domain introduced into the DCI is 1bit and is used for indicating the association sequence of the SRI or the SRI group indicated by the two SRS resource indicators and the PUSCH repeated transmission opportunity.

Specifically, SRS resource indicator1 indicates the SRI group as shown in table 21 below, where Lmax is 4:

TABLE 21

Bit field mapped to index	SRI(s),N _SRS ＝4
		0	0
1	1
		2	2
3	3
		4	0,1
5	0,2
		6	0,3
7	1,2
		8	1,3
9	2,3
		10	0,1,2
11	0,1,3
		12	0,2,3
13	1,2,3
		14	0,1,2,3
15	reserved

The SRI set indicated by SRS resource indicator2 is shown in table 22 below, where Lmax is 4:

TABLE 22

In this example, all sub-tables of the SRS index table to which SRS resource indicator2 corresponds have at least two reserved entries (value 6 and value 7) in common.

Illustratively, in conjunction with Table 16 above, it can be seen that:

1) if the SRS resource indicator1 indicates an entry with a transmission layer number of 1 (one entry contains only 1 SRI), the SRS resource indicator2 indicates one SRI group (the SRI group contains only one SRI) corresponding to the column of table L-1; if the SRS resource indicator1 indicates an entry with 2 transport layer numbers (each entry contains only 2 SRIs), then the SRS resource indicator2 indicates one SRI group corresponding to the table L-2 column, and so on. If the SRS resource indicator2 indicates a reserved entry, it indicates that all PUSCH repeated transmission occasions are associated with the SRI group indicated by the SRS resource indicator1, where:

when the SRS resource indicator2 takes a value of 6, the SRI group indicated by the SRS resource indicator1 is the SRI (corresponding to the first latest reserved) in the first SRS resource set;

when the value of SRS resource indicator2 is 7 (corresponding to the second last) indicates that the SRI group indicated by SRS resource indicator1 is the SRI in the second SRS resource set.

2) Two SRS resource indicators are associated with two SRS resource sets, respectively, if both SRS resource indicator1 and SRS resource indicator2 indicate a SRI group instead of a reserved entry. The relationship between the two SRI groups and the PUSCH transmission opportunity is determined by the value of the target field newly introduced by the DCI and is explained according to table 16.

Example 14:

and non-codebook transmission, wherein a target domain 1bit is introduced into the DCI and is used for indicating the association sequence of the SRI or the SRI group indicated by the two SRS resource indicators and the PUSCH repeated transmission opportunity.

Specifically, the SRI set indicated by SRS resource indicator1 is shown in table 23 below, where Lmax is 4:

TABLE 23

Bit field mapped to index	SRI(s),N _SRS ＝3
		0	0
1	1
		2	2
3	0,1
		4	0,2
5	1,2
		6	0,1,2
7	reserved

The SRI set indicated by SRS resource indicator2 is as follows in table 24, where Lmax is 4:

watch 24

The SRI set indicated by SRS resource indicator2 is shown in table 25 below, where Lmax is 4:

TABLE 25

Exemplarily, if the SRS resource indicator1 indicates an entry with 1 transport layer number (each entry contains only 1 SRI), the SRS resource indicator2 indicates one SRI corresponding to one vertical column of table L ═ 1; if the SRS resource indicator1 indicates an entry with 2 transmission layer numbers (each entry contains only 2 SRIs), then the SRS resource indicator2 indicates an entry corresponding to table L-2 column, and so on. The mapping relationship between the two SRI groups and the PUSCH transmission opportunity is determined by the value of the target field newly introduced by the DCI and is explained according to table 17.

Note that, Lmax: refers to the maximum number of layers for non-codebook PUSCH transmission; n in the above _SRS : refers to the number of SRS resources contained in one SRS resource set; the reserved entry in the above context refers to a reserved entry.

It should be noted that typically SRIs for codebook transmission and SRI groups for non-codebook transmission.

It should be noted that, the above scenarios are all described by taking the SRI field as an example. Accordingly, the process of describing the content indicated by the first indication information through the TPMI domain may refer to the above-mentioned content, and will not be described herein again.

For example, taking example 1 as an example, since TPMIm is associated with SRS resource set0, TPMIN is associated with SRS resource set 1. Accordingly, the relationship indicated by the target domain described above includes only one example of the relationship 2, which may be shown in the following table 26.

Watch 26

Threshold value	Means of
		0	(S0,TPMIm),(S1,TPMIn)
1	(S1,TPMIn),(S0,TPMIm)

It should be noted that the above is only an example, and in practical applications, the present invention may also be applied to a scenario with more SRS resource sets, and the embodiment of the present application does not limit this scenario.

It should be noted that, in the PUSCH repetition transmission method provided in the embodiment of the present application, the execution main body may be the PUSCH repetition transmission apparatus, or a control module used in the PUSCH repetition transmission apparatus to execute the PUSCH repetition transmission method. In the embodiment of the present application, a PUSCH retransmission apparatus executes a PUSCH retransmission method as an example, and the PUSCH retransmission apparatus provided in the embodiment of the present application is described. However, in practical applications, the execution main body of the PUSCH repetition transmission method may also be other devices or apparatuses that can execute the PUSCH repetition transmission method, and this is not limited in this embodiment of the present application.

An embodiment of the present application provides a PUSCH retransmission apparatus, which is applied to a UE, and as shown in fig. 3, the PUSCH retransmission apparatus 400 includes: an obtaining module 401 and a transmitting module 402, wherein:

an obtaining module 401, configured to obtain first indication information; wherein the first indication information is used for indicating at least one of the following: m target indications for use by a plurality of PUSCH transmission occasions; when M is larger than 1, the plurality of PUSCH transmission opportunities use the mapping order indicated by M targets; the target indication includes at least one of: SRI, TPMI; m is a positive integer; a transmission module 402, configured to transmit the multiple PUSCH transmission occasions by using M target indications according to the first indication information acquired by the acquisition module 401.

Optionally, as shown in fig. 4, the apparatus 400 further includes: a receiving module 403, wherein: a receiving module 403, configured to receive first configuration information and DCI for scheduling the PUSCH; wherein the first configuration information includes N SRS resource sets, N being an integer greater than 1; the N SRS resource sets are used for codebook transmission or non-codebook transmission; the M target indications are: all or part of X first indications corresponding to the N SRS resource sets; the first indication comprises at least one of: SRI, TPMI; x is an integer greater than 1 and X is greater than or equal to M.

Optionally, as shown in fig. 4, the apparatus 400 further includes: a determining module 404, wherein the determining module 404 is configured to determine the M target indicators according to the X first indicators when the first indicator information indicates the mapping order; alternatively, the M target indications are determined according to the X first indications and the first indication information acquired by the acquiring module 401.

Optionally, the obtaining module is further configured to obtain second indication information through a high-level signaling; wherein the second indication information indicates the number of TPMI domains included in the DCI; when the number of the TPMI domains is 1, each of the SRIs used in the plurality of PUSCH transmission timings corresponds to the same TPMI.

Optionally, the first indication information is carried in a target domain in downlink control information DCI or MAC CE; wherein the DCI is configured to schedule the plurality of PUSCH transmission occasions.

Optionally, the first indication information is determined based on second configuration information; wherein the second configuration information includes: the target corresponding relations corresponding to the N SRS resource sets are obtained; the target correspondence includes: the corresponding relation between different values of the target domain and different first indication information; the target corresponding relation is agreed by a protocol, or is predefined, or is configured by a network side.

Optionally, the value of the target domain is used to indicate the first indication information;

the domain size of the target domain is determined based on the value number Y of the target domain in the target correspondence;

the value quantity Y of the target domain is related to at least one of:

whether a reserved entry exists in a first index table corresponding to each first indication in the X first indications;

each of the X first indications takes a value in a corresponding first index table;

when M is larger than 1, the mapping order of the M target instructions is used for supporting the exchange of the plurality of PUSCH transmission opportunities;

y is an integer greater than 1.

Optionally, the first indication information is related to at least one of the following:

and when M is larger than 1, exchanging the plurality of PUSCH transmission opportunities by using the mapping order of the M target indications is supported.

Optionally, in a case that there is a reserved entry in each of the first index tables corresponding to the X first indications,

or,

in a case other than the case where all the first index tables corresponding to the X first indicators have a reserved entry, the first indication information carried by the target domain is used to indicate: the M target indications, or the mapping order of the M target indications and the M target indications.

Optionally, when the N SRS resource sets include a first SRS resource set, the first indication information is related to a value indicated by a first target indication indicated by the first SRS resource set in a corresponding first index table; wherein, the first target indicates that a reserved entry exists in the corresponding first index table.

Optionally, the presence of a reserved entry in the first index table includes: all sub-tables contained in the first index table contain reserved entries.

In the PUSCH repeated transmission apparatus provided in the embodiment of the present application, after the first indication information is obtained, based on the content indicated by the first indication information (that is, M target indications used by multiple PUSCH transmission occasions and/or, when M is greater than 1, a mapping order of the M target indications is used by the multiple PUSCH transmission occasions), the target indications used by the multiple PUSCH transmission occasions may be obtained based on the first indication information, thereby implementing flexible switching of the UE between a single TRP and multiple TRPs, and ensuring flexibility of network scheduling.

The PUSCH repetition transmission apparatus in the embodiment of the present application may be an apparatus, or may also be a component, an integrated circuit, or a chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. By way of example, the mobile terminal may include, but is not limited to, the type of the terminal 11 listed above, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a Personal Computer (PC), a television (television), a teller machine (TV), a self-service machine (kiosk), or the like, and the embodiments of the present application are not limited in particular.

The PUSCH repeated transmission apparatus in the embodiment of the present application may be an apparatus having an operating system. The operating system may be an Android operating system, an ios operating system, or other possible operating systems, which is not specifically limited in the embodiment of the present application.

The PUSCH repetition transmission apparatus provided in the embodiment of the present application can implement each process implemented by the above method embodiment, and is not described here again to avoid repetition.

The beneficial effects of the various implementation manners in this embodiment may specifically refer to the beneficial effects of the corresponding implementation manners in the above method embodiments, and are not described herein again to avoid repetition.

Optionally, as shown in fig. 5, an embodiment of the present application further provides a communication device 500, which includes a processor 501, a memory 502, and a program or instruction stored in the memory 502 and executable on the processor 501, for example, when the communication device 500 is a UE, the program or instruction is executed by the processor 501 to implement each process of the foregoing PUSCH retransmission method embodiment, and the same technical effect can be achieved.

Fig. 6 is a schematic diagram of a hardware structure of a terminal implementing the embodiment of the present application.

The terminal 100 includes but is not limited to: radio frequency unit 101, network module 102, audio output unit 103, input unit 104, sensor 105, display unit 106, user input unit 107, interface unit 108, memory 109, and processor 110.

Those skilled in the art will appreciate that the terminal 100 may further include a power supply (e.g., a battery) for supplying power to various components, and the power supply may be logically connected to the processor 110 through a power management system, so as to implement functions of managing charging, discharging, and power consumption through the power management system. The terminal structure shown in fig. 6 does not constitute a limitation of the terminal, and the terminal may include more or less components than those shown, or may combine some components, or may be arranged differently, and thus, the description thereof is omitted.

It should be understood that, in the embodiment of the present application, the input Unit 104 may include a Graphics Processing Unit (GPU) 1041 and a microphone 1042, and the Graphics Processing Unit 1041 processes image data of a still picture or a video obtained by an image capturing device (such as a camera) in a video capturing mode or an image capturing mode. The display unit 106 may include a display panel 1061, and the display panel 1061 may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like. The user input unit 107 includes a touch panel 1071 and other input devices 1072. The touch panel 1071 is also referred to as a touch screen. The touch panel 1071 may include two parts of a touch detection device and a touch controller. Other input devices 1072 may include, but are not limited to, a physical keyboard, function keys (e.g., volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail herein.

In the embodiment of the present application, the radio frequency unit 101 receives downlink data from a network side device, and then processes the downlink data to the processor 110; in addition, the uplink data is sent to the network side equipment. Typically, radio frequency unit 101 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.

The memory 109 may be used to store software programs or instructions and various data. The memory 109 may mainly include a stored program or instruction area and a stored data area, wherein the stored program or instruction area may store an operating system, an application program or instruction (such as a sound playing function, an image playing function, etc.) required for at least one function, and the like. In addition, the Memory 109 may include a high-speed random access Memory, and may further include a nonvolatile Memory, wherein the nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (Erasable PROM, EPROM), an Electrically Erasable Programmable Read-Only Memory (EEPROM), or a flash Memory. Such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.

Processor 110 may include one or more processing units; alternatively, the processor 110 may integrate an application processor, which primarily handles operating systems, user interfaces, and applications or instructions, etc., and a modem processor, which primarily handles wireless communications, such as a baseband processor. It will be appreciated that the modem processor described above may not be integrated into the processor 110.

The processor 110 is configured to obtain first indication information; wherein the first indication information is used for indicating at least one of the following: m target indications for use by a plurality of PUSCH transmission occasions; when M is larger than 1, the plurality of PUSCH transmission opportunities use the mapping sequence indicated by M targets; the target indication includes at least one of: SRI, TPMI; m is a positive integer; a radio frequency unit 101, configured to transmit the multiple PUSCH transmission occasions using M target indications according to the first indication information obtained by the processor 110.

Optionally, the radio frequency unit 101 is further configured to receive the first configuration information and DCI for scheduling a PUSCH; wherein, the first configuration information includes N SRS resource sets, and N is an integer greater than 1; the N SRS resource sets are used for codebook transmission or non-codebook transmission; the above M target indications are: all or part of the X first indications corresponding to the N SRS resource sets; the first indication comprises at least one of: SRI, TPMI; x is an integer greater than 1 and X is greater than or equal to M.

Optionally, the processor 110 is further configured to determine the M target indications according to the X first indications when the first indication information is used to indicate the mapping order; alternatively, the M target instructions are determined according to the X first instructions and the first instruction information acquired by the acquisition module 401.

Optionally, the processor 110 is further configured to obtain second indication information through higher layer signaling; wherein the second indication information indicates the number of TPMI domains included in the DCI; when the number of the TPMI domains is 1, each of the SRIs used in the plurality of PUSCH transmission timings corresponds to the same TPMI.

Optionally, the first indication information is determined based on second configuration information; wherein the second configuration information includes: the target corresponding relation corresponding to the N SRS resource sets; the target correspondence includes: the corresponding relation between different values of the target domain and different first indication information; the target corresponding relation is agreed by a protocol, or is predefined, or is configured by a network side.

the value quantity Y of the target domain is related to at least one of:

y is an integer greater than 1.

Optionally, the first indication information is related to at least one of:

and when M is larger than 1, exchanging the mapping order of the plurality of PUSCH transmission opportunities using the M target indications is supported.

Optionally, in the case that there is a reserved entry in the first index table corresponding to the X first indications,

if the values indicated by the X first indications in the corresponding first index tables are all unreserved values, the target domain does not exist, and the first indication information is used for indicating the M target indications; or, the first indication information carried by the target domain is used to indicate a mapping order of the M target indications;

or,

Optionally, when a first SRS resource set is included in the N SRS resource sets, the first indication information is related to a value indicated by a first target indication indicated by the first SRS resource set in a corresponding first index table; wherein, the first target indicates that a reserved entry exists in the corresponding first index table.

In the terminal provided in the embodiment of the present application, after the first indication information is obtained, based on the content indicated by the first indication information (that is, M target indications used in multiple PUSCH transmission occasions and/or the mapping order of the M target indications used in the multiple PUSCH transmission occasions when M is greater than 1), the target indications used in the multiple PUSCH transmission occasions can be obtained based on the first indication information, so that flexible switching of the terminal between a single TRP and multiple TRPs is achieved, and flexibility of network scheduling is ensured.

The terminal provided by the embodiment of the present application can implement each process implemented by the above method embodiment, and is not described here again to avoid repetition.

An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or the instruction is executed by a processor, the program or the instruction implements each process of the method embodiment of the PUSCH retransmission method, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

Wherein, the processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and so on.

The embodiment of the present application further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is configured to run a network-side device program or an instruction, implement each process of the method embodiment of the above PUSCH retransmission method, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

It should be understood that the chips mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip or a system-on-chip, etc.

The embodiment of the present application provides a computer program product, where the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement the processes of the method embodiment of the PUSCH repeated transmission method, and can achieve the same technical effect, and in order to avoid repetition, details are not repeated here.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element identified by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element. Further, it should be noted that the scope of the methods and apparatuses in the embodiments of the present application is not limited to performing the functions in the order illustrated or discussed, but may include performing the functions in a substantially simultaneous manner or in a reverse order based on the functions recited, e.g., the described methods may be performed in an order different from that described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal (such as a mobile phone, a computer, a server, an air conditioner, or a network device) to execute the method according to the embodiments of the present application.

While the present embodiments have been described with reference to the accompanying drawings, it is to be understood that the present embodiments are not limited to those precise embodiments, which are intended to be illustrative rather than restrictive, and that various changes and modifications may be effected therein by one skilled in the art without departing from the scope of the appended claims.

Claims

1. A Physical Uplink Shared Channel (PUSCH) repeated transmission method is characterized by comprising the following steps:

user Equipment (UE) acquires first indication information;

wherein the first indication information is used for indicating at least one of the following:

m target indications for use by a plurality of PUSCH transmission occasions; m is a positive integer;

the plurality of PUSCH transmission occasions use a mapping order of the M target indications if M is greater than 1;

the target indication comprises at least one of: the sounding reference signal resource indicates SRI, and the precoding matrix indicates TPMI;

the UE transmits the plurality of PUSCH transmission opportunities using the M target indications according to the first indication information.

2. The method of claim 1, wherein before determining the M target indications according to the first indication information, the method further comprises:

receiving first configuration information and DCI for scheduling the PUSCH;

wherein the first configuration information includes N SRS resource sets, N being an integer greater than 1; the N SRS resource sets are used for codebook transmission or non-codebook transmission; the M target indications are: all or part of X first indications corresponding to the N SRS resource sets;

the first indication comprises at least one of: SRI, TPMI;

x is an integer greater than 1 and X is greater than or equal to M.

3. The method of claim 2, wherein if the first indication information is used to indicate the mapping order, prior to transmitting the plurality of PUSCH transmission occasions using the M target indications according to the first indication information, the method further comprises:

determining the M target indications according to the X first indications;

or,

and determining the M target indications according to the X first indications and the first indication information.

4. The method of claim 2, further comprising:

acquiring second indication information through a high-level signaling;

wherein the second indication information is used for indicating the number of TPMI domains contained in the DCI; and when the number of the TPMI domains is 1, each SRI used by the plurality of PUSCH transmission opportunities corresponds to the same TPMI.

5. The method of claim 2, wherein the first indication information is carried in a target domain in Downlink Control Information (DCI) or a media access control (MAC CE);

wherein the DCI is used to schedule the plurality of PUSCH transmission occasions.

6. The method of claim 5, wherein the first indication information is determined based on second configuration information;

wherein the second configuration information comprises: target corresponding relations corresponding to the N SRS resource sets; the target correspondence includes: the corresponding relation between different values of the target domain and different first indication information; the target corresponding relation is agreed by a protocol, or is predefined, or is configured by a network side.

7. The method of claim 6,

the value of the target domain is used for indicating the first indication information;

the domain size of the target domain is determined based on the value quantity Y of the target domain in the target corresponding relation;

the value quantity Y of the target domain is related to at least one of the following items:

in the case that M is greater than 1, supporting exchanging the mapping order of the plurality of PUSCH transmission occasions using the M target indications;

y is an integer greater than 1.

8. The method of claim 2,

the first indication information is related to at least one of:

in the case that M is greater than 1, exchanging the mapping order of the plurality of PUSCH transmission occasions using the M target indications is supported.

9. The method of claim 5,

in the case that there is a reserved entry in the first index table corresponding to the X first indications,

if the values indicated by the X first indications in the corresponding first index tables are all non-reserved values, the target domain does not exist, and the first indication information is used for indicating the M target indications; or, the first indication information carried by the target domain is used to indicate a mapping order of the M target indications;

or,

in other cases except for the case that all the first index tables corresponding to the X first indications have reserved entries, the first indication information carried by the target domain is used to indicate: the M target indications, or a mapping order of the M target indications and the M target indications.

10. The method of claim 2, wherein if a first SRS resource set is included in the N SRS resource sets, the first indication information is related to a value indicated by a first target indication indicated by the first SRS resource set in a corresponding first index table;

wherein the first target indicates that a reserved entry exists in a corresponding first index table.

11. The method of any of claims 7 to 10, wherein the presence of a reserved entry in the first index table comprises: all sub-tables contained in the first index table contain reserved entries.

12. An apparatus for PUSCH repetition transmission, the apparatus comprising:

the acquisition module is used for acquiring first indication information;

a transmission module, configured to transmit the multiple PUSCH transmission occasions using the M target indications according to the first indication information acquired by the acquisition module.

13. The apparatus of claim 12, further comprising:

a receiving module, configured to receive first configuration information and DCI for scheduling the PUSCH;

the first indication comprises at least one of: SRI, TPMI;

x is an integer greater than 1 and X is greater than or equal to M.

14. The apparatus of claim 13, further comprising:

a determining module, configured to determine the M target indications according to the X first indications when the first indication information is used to indicate the mapping order; or, determining the M target indications according to the X first indications and the first indication information acquired by the acquisition module.

15. The apparatus of claim 13, wherein the obtaining module is further configured to obtain the second indication information through higher layer signaling;

wherein the second indication information is used for indicating the number of TPMI domains contained in the DCI; and when the number of the TPMI domains is 1, each SRI used by the plurality of PUSCH transmission occasions corresponds to the same TPMI.

16. The apparatus of claim 13, wherein the first indication information is carried in a target field in downlink control information DCI or MAC CE;

17. The apparatus of claim 16, wherein the first indication information is determined based on second configuration information;

wherein the second configuration information comprises: the target corresponding relation corresponding to the N SRS resource sets; the target correspondence includes: the corresponding relation between different values of the target domain and different first indication information; the target corresponding relation is agreed by a protocol, or is predefined, or is configured by a network side.

18. The apparatus of claim 17,

the value number Y of the target domain is related to at least one of the following items:

whether a reserved item exists in a first index table corresponding to each first indication in the X first indications or not;

supporting exchanging the mapping order of the plurality of PUSCH transmission occasions using the M target indications if M is greater than 1;

y is an integer greater than 1.

19. The apparatus of claim 13,

the first indication information is related to at least one of:

20. The apparatus of claim 16,

if the values indicated by the X first indications in the respective corresponding first index tables are all unreserved values, the target domain is absent, and the first indication information is used for indicating the M target indications; or, the first indication information carried by the target domain is used to indicate a mapping order of the M target indications;

or,

21. The apparatus of claim 13, wherein if a first SRS resource set is included in the N SRS resource sets, the first indication information is related to a value indicated by a first target indication indicated by the first SRS resource set in a corresponding first index table;

22. The apparatus according to any one of claims 18 to 21, wherein the presence of a reserved entry in the first index table comprises: all sub-tables contained in the first index table contain reserved entries.

23. A UE comprising a processor, a memory, and a program or instructions stored on the memory and executable on the processor, which when executed by the processor, implement the steps of the PUSCH retransmission method according to any of claims 1 to 11.

24. A readable storage medium, characterized in that it stores thereon a program or instructions which, when executed by a processor, implement the steps of the PUSCH retransmission method according to any of claims 1 to 11.